Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

What software to use at Windows 10 to backup to FreeNAS

Status
Not open for further replies.

Johnny Tangstad

Neophyte
Joined
May 6, 2017
Messages
7
As it says in title, I wonder what software are recommended to use at the Windows 10 platform to do automatic backups to the FreeNAS server. Is it possible to set it and forget it, and then have a similar service as the Apple's time machine? I am talking about if it is possible to having it making snapshots, in case you would want to set your system back to a certain time and date.

And also; is it possible to back up iPads, and even to use the FreeNAS server as a storage device when your iPad is out of storage capacity? If so, what mesures should one make to get it up and running?

Thank you for your support!
 

m0nkey_

Dedicated Sage
Joined
Oct 27, 2015
Messages
2,732
I use Veeam Endpoint to backup my Windows 10 computer to FreeNAS. Works great, seamless, pretty much set and forget. Also does bare metal restore. It's already saved my ass a couple of times where I've inadvertently deleted a file or two from my computer. Another option is EaseUS, pretty much the same as Veeam Endpoint, probably had a couple more features.
 

Johnny Tangstad

Neophyte
Joined
May 6, 2017
Messages
7
I use Veeam Endpoint to backup my Windows 10 computer to FreeNAS. Works great, seamless, pretty much set and forget. Also does bare metal restore. It's already saved my ass a couple of times where I've inadvertently deleted a file or two from my computer. Another option is EaseUS, pretty much the same as Veeam Endpoint, probably had a couple more features.
Thank you very much, I will look into it!

If anyone have viewpoints about setting up an iPad for use with FreeNAS i would appreciate that too.

Thank you for your support!
 

Ericloewe

Not-very-passive-but-aggressive
Moderator
Joined
Feb 15, 2014
Messages
17,019
If anyone have viewpoints about setting up an iPad for use with FreeNAS i would appreciate that too.
How so? What's an iPad going to do? It's basically up to the applications to do whatever they need.
 

Johnny Tangstad

Neophyte
Joined
May 6, 2017
Messages
7
How so? What's an iPad going to do? It's basically up to the applications to do whatever they need.
The thing is that one person in the household has too many pictures and videos and so on, and don't wish to subscribe to expensive sevices from Apple to store above aviable 32 Gb storage. So the though behind my request is that I wonder about how to store, lets say old videos and so, from the Ipad at the server.
 

Spearfoot

He of the long foot
Moderator
Joined
May 13, 2015
Messages
2,266

adrianwi

Neophyte Sage
Joined
Oct 15, 2013
Messages
1,180
Plex will allow you to upload pictures (and video I think, but check) directly from iOS devices to a Plex library (which can be stored on FreeNAS) although I think it's a PlexPass feature, so need a subscription of some kind
 

zoomzoom

Neophyte Sage
Joined
Sep 6, 2015
Messages
671
Windows 10 natively supports real time backup with versioning via: Settings -> Update & Security -> Backup. Advanced settings can be accessed via: Control Panel\System and Security\File History
  • File History requires some customization, as you must specify individual folders if you don't want to backup an entire partition, otherwise you can simply select the root of the partition. You'll also likely want to remove the redundant OneDrive folder backup if you backup the main OneDrive directory.

Windows has always supported native backup and restore, and it's always baffled me why people choose 3rd Party products like Acronis or Macrium since they require a dependency on their own image formats, as well as their own separate boot environment. Using the native Windows support for ESDs & WIMs, one can backup or restore a partition through WinRE/WinPE if it's the system partition, else directly booted to Windows for any other partition.
  • For example, I have a task set in Task Scheduler that runs once a week to backup my data partition, which is where the main User directories are saved to.
To create a backup:
  • System Partition:
    • DISM /Capture-Image /ImageFile:Z:\OS-Backup.esd /CaptureDir:C: /Name:"Windows 10 Pro x64 System Backup 1" /Description:"2017.06.03 v1701" /Compress:Recovery /NoRpFix /CheckIntegrity /Verify
      • ESD utilizes a far more efficient compression algorithm, with a 33% size reduction versus that of WIM, however ESDs can only be captured from partitions containing the Windows OS.
      • By default, C:\System Volume Information is not backed up, ergo system restore checkpoints will not be backed up. This can be changed by specifying the /ConfigFile: parameter, removing C:\System Volume Information as an exclusion in Z:\WIMscript.ini

        Default Exclusion list:
        If /ConfigFile not specified, else copy and paste the following into Z:\WIMscript.ini, removing: "\System Volume Information", and specifying in the command /ConfigFile:Z:\WIMscript.ini
        Code:
        [ExclusionList]
        \$ntfs.log
        \hiberfil.sys
        \pagefile.sys
        \swapfile.sys
        "\System Volume Information"
        \RECYCLER
        \Windows\CSC
        
        [CompressionExclusionList]
        *.mp3
        *.zip
        *.cab
        \WINDOWS\inf\*.pnf
        

  • All Other Partitions:
    • DISM /Capture-Image /ImageFile:Z:\Data-Backup.wim /CaptureDir:D: /Name:"Windows 10 Pro x64 User Data Backup 1" /Description:"2017.06.03 User Data" /Compress:Max /NoRpFix /CheckIntegrity /Verify
      • One can convert a WIM to an ESD, or vice versa, via DISM /Export-Image.
        • An unknown MSFN forum member wrote an ESD <-> WIM script, which I have on my GitHub

Adding a Backup to an Image:
  • DISM /Append-Image /ImageFile:Z:\OS-Backup.esd /CaptureDir:C: /Name:"Windows 10 Pro x64 System Backup 2" /Description:"2017.06.04 v1701" /NoRpFix /CheckIntegrity /Verify
    • Compression level cannot be changed on an appended image... it will utilize the compression level from the original image.
    • Each appended image will be assigned the next chronological index #.
      1. Initial Image Backup
      2. 1st appended image backup
      3. 2nd appended image backup (etc.)
        Code:
        	# For example, this is what's contained within the Install.esd of a Windows Install ISO
        #-------------------------------------------------------------------------------------------------------
        
        PS F:\sources> dism /get-wiminfo /wimfile:f:\sources\install.esd
        
        Deployment Image Servicing and Management tool
        Version: 10.0.15063.0
        
        Details for image : f:\sources\install.esd
        
        Index : 1
        Name : Windows 10 Pro
        Description : Windows 10 Pro
        Size : 15,305,539,033 bytes
        
        Index : 2
        Name : Windows 10 Home
        Description : Windows 10 Home
        Size : 15,127,824,725 bytes
        
        Index : 3
        Name : Windows 10 Home Single Language
        Description : Windows 10 Home Single Language
        Size : 15,129,601,869 bytes
        
        Index : 4
        Name : Windows 10 Education
        Description : Windows 10 Education
        Size : 15,125,050,322 bytes
        
        The operation completed successfully.
        PS F:\sources> dism /get-wiminfo /wimfile:f:\sources\install.esd /index:1
        
        Deployment Image Servicing and Management tool
        Version: 10.0.15063.0
        
        Details for image : f:\sources\install.esd
        
        Index : 1
        Name : Windows 10 Pro
        Description : Windows 10 Pro
        Size : 15,305,539,033 bytes
        WIM Bootable : No
        Architecture : x64
        Hal : <undefined>
        Version : 10.0.15063
        ServicePack Build : 0
        ServicePack Level : 0
        Edition : Professional
        Installation : Client
        ProductType : WinNT
        ProductSuite : Terminal Server
        System Root : WINDOWS
        Directories : 19668
        Files : 101896
        Created : 2017.03.18 - 21:40:43
        Modified : 2017.04.13 - 12:23:48
        Languages : en-US (Default)
        
        The operation completed successfully.
        PS F:\sources> dism /get-wiminfo /wimfile:f:\sources\install.esd /index:2
        
        Deployment Image Servicing and Management tool
        Version: 10.0.15063.0
        
        Details for image : f:\sources\install.esd
        
        Index : 2
        Name : Windows 10 Home
        Description : Windows 10 Home
        Size : 15,127,824,725 bytes
        WIM Bootable : No
        Architecture : x64
        Hal : <undefined>
        Version : 10.0.15063
        ServicePack Build : 0
        ServicePack Level : 0
        Edition : Core
        Installation : Client
        ProductType : WinNT
        ProductSuite : Terminal Server
        System Root : WINDOWS
        Directories : 19507
        Files : 100750
        Created : 2017.03.18 - 21:40:40
        Modified : 2017.04.13 - 12:23:49
        Languages : en-US (Default)
        
        The operation completed successfully.
        PS F:\sources> dism /get-wiminfo /wimfile:f:\sources\install.esd /index:3
        
        Deployment Image Servicing and Management tool
        Version: 10.0.15063.0
        
        Details for image : f:\sources\install.esd
        
        Index : 3
        Name : Windows 10 Home Single Language
        Description : Windows 10 Home Single Language
        Size : 15,129,601,869 bytes
        WIM Bootable : No
        Architecture : x64
        Hal : <undefined>
        Version : 10.0.15063
        ServicePack Build : 0
        ServicePack Level : 0
        Edition : CoreSingleLanguage
        Installation : Client
        ProductType : WinNT
        ProductSuite : Terminal Server
        System Root : WINDOWS
        Directories : 19521
        Files : 100858
        Created : 2017.03.18 - 21:43:23
        Modified : 2017.04.13 - 12:23:50
        Languages : en-US (Default)
        
        The operation completed successfully.
        PS F:\sources> dism /get-wiminfo /wimfile:f:\sources\install.esd /index:4
        
        Deployment Image Servicing and Management tool
        Version: 10.0.15063.0
        
        Details for image : f:\sources\install.esd
        
        Index : 4
        Name : Windows 10 Education
        Description : Windows 10 Education
        Size : 15,125,050,322 bytes
        WIM Bootable : No
        Architecture : x64
        Hal : <undefined>
        Version : 10.0.15063
        ServicePack Build : 0
        ServicePack Level : 0
        Edition : Education
        Installation : Client
        ProductType : WinNT
        ProductSuite : Terminal Server
        System Root : WINDOWS
        Directories : 19519
        Files : 100691
        Created : 2017.03.18 - 21:36:11
        Modified : 2017.04.13 - 12:23:52
        Languages : en-US (Default)
        
        The operation completed successfully.
        
        

    Restoring from an Image:
    • DISM /Apply-Image /ImageFile:Z:\OS-Backup.esd /ApplyDir:C: /Index:1 /NoRpFix /CheckIntegrity /Verify
      • It's best to format the System partition prior to applying an image
        • If User files aren't saved on a separate partition, either copy the User files to a separate partition and format, or if not available, use del to delete everything except the User folder and do not format. Once done, apply the image.
      • Index # will vary depending on the backup within the image one would like to restore.

    Checking the Content of an Image:
    • Full Image:
      • DISM /Get-WimInfo /ImageFile:Z:\OS-Backup.esd

    • Individual Indexes:
      • DISM /Get-WimInfo /ImageFile:Z:\OS-Backup.esd /Index:1

    • Mount an Image:
      • DISM /Mount-Image /ImageFile:Z:\OS-Backup.esd /MountDir:C:\Mount /Index:1
 
Last edited:

Spearfoot

He of the long foot
Moderator
Joined
May 13, 2015
Messages
2,266
Windows 10 natively supports real time backup with versioning via: Settings -> Update & Security -> Backup. Advanced settings can be accessed via: Control Panel\System and Security\File History
  • File History requires some customization, as you must specify individual folders if you don't want to backup an entire partition, otherwise you can simply select the root of the partition. You'll also likely want to remove the redundant OneDrive folder backup if you backup the main OneDrive directory.

Windows has always supported native backup and restore, and it's always baffled me why people choose 3rd Party products like Acronis or Macrium since they require a dependency on their own image formats, as well as their own separate boot environment. Using the native Windows support for ESDs & WIMs, one can backup or restore a partition through WinRE/WinPE if it's the system partition, else directly booted to Windows for any other partition.
  • For example, I have a task set in Task Scheduler that runs once a week to backup my data partition, which is where the main User directories are saved to.
To create a backup:
  • System Partition:
    • DISM /Capture-Image /ImageFile:Z:\OS-Backup.esd /CaptureDir:C: /Name:"Windows 10 Pro x64 System Backup 1" /Description:"2017.06.03 v1701" /Compress:Recovery /NoRpFix /CheckIntegrity /Verify
      • ESD utilizes a far more efficient compression algorithm, with a 33% size reduction versus that of WIM, however ESDs can only be captured from partitions containing the Windows OS.
      • By default, C:\System Volume Information is not backed up, ergo system restore checkpoints will not be backed up. This can be changed by specifying the /ConfigFile: parameter, removing C:\System Volume Information as an exclusion in Z:\WIMscript.ini

        Default Exclusion list:
        If /ConfigFile not specified, else copy and paste the following into Z:\WIMscript.ini, removing: "\System Volume Information"
        Code:
        [ExclusionList]
        \$ntfs.log
        \hiberfil.sys
        \pagefile.sys
        \swapfile.sys
        "\System Volume Information"
        \RECYCLER
        \Windows\CSC
        
        [CompressionExclusionList]
        *.mp3
        *.zip
        *.cab
        \WINDOWS\inf\*.pnf
        

  • All Other Partitions:
    • DISM /Capture-Image /ImageFile:Z:\Data-Backup.wim /CaptureDir:D: /Name:"Windows 10 Pro x64 User Data Backup 1" /Description:"2017.06.03 User Data" /Compress:Max /NoRpFix /CheckIntegrity /Verify
      • One can convert a WIM to an ESD via DISM /Export-Image

Adding a Backup to an Image:
  • DISM /Append-Image /ImageFile:Z:\OS-Backup.esd /CaptureDir:C: /Name:"Windows 10 Pro x64 System Backup 2" /Description:"2017.06.04 v1701" /NoRpFix /CheckIntegrity /Verify
    • Compression level cannot be changed on an appended image... it will utilize the compression level from the original image.
    • Each appended image will be assigned the next chronological index #.
      1. Initial Image Backup
      2. 1st appended image backup
      3. 2nd appended image backup (etc.)
    • For example, this is what's contained within the Install.esd of a Windows Install ISO
      Code:
      PS F:\sources> dism /get-wiminfo /wimfile:f:\sources\install.esd
      
      Deployment Image Servicing and Management tool
      Version: 10.0.15063.0
      
      Details for image : f:\sources\install.esd
      
      Index : 1
      Name : Windows 10 Pro
      Description : Windows 10 Pro
      Size : 15,305,539,033 bytes
      
      Index : 2
      Name : Windows 10 Home
      Description : Windows 10 Home
      Size : 15,127,824,725 bytes
      
      Index : 3
      Name : Windows 10 Home Single Language
      Description : Windows 10 Home Single Language
      Size : 15,129,601,869 bytes
      
      Index : 4
      Name : Windows 10 Education
      Description : Windows 10 Education
      Size : 15,125,050,322 bytes
      
      The operation completed successfully.
      PS F:\sources> dism /get-wiminfo /wimfile:f:\sources\install.esd /index:1
      
      Deployment Image Servicing and Management tool
      Version: 10.0.15063.0
      
      Details for image : f:\sources\install.esd
      
      Index : 1
      Name : Windows 10 Pro
      Description : Windows 10 Pro
      Size : 15,305,539,033 bytes
      WIM Bootable : No
      Architecture : x64
      Hal : <undefined>
      Version : 10.0.15063
      ServicePack Build : 0
      ServicePack Level : 0
      Edition : Professional
      Installation : Client
      ProductType : WinNT
      ProductSuite : Terminal Server
      System Root : WINDOWS
      Directories : 19668
      Files : 101896
      Created : 2017.03.18 - 21:40:43
      Modified : 2017.04.13 - 12:23:48
      Languages : en-US (Default)
      
      The operation completed successfully.
      PS F:\sources> dism /get-wiminfo /wimfile:f:\sources\install.esd /index:2
      
      Deployment Image Servicing and Management tool
      Version: 10.0.15063.0
      
      Details for image : f:\sources\install.esd
      
      Index : 2
      Name : Windows 10 Home
      Description : Windows 10 Home
      Size : 15,127,824,725 bytes
      WIM Bootable : No
      Architecture : x64
      Hal : <undefined>
      Version : 10.0.15063
      ServicePack Build : 0
      ServicePack Level : 0
      Edition : Core
      Installation : Client
      ProductType : WinNT
      ProductSuite : Terminal Server
      System Root : WINDOWS
      Directories : 19507
      Files : 100750
      Created : 2017.03.18 - 21:40:40
      Modified : 2017.04.13 - 12:23:49
      Languages : en-US (Default)
      
      The operation completed successfully.
      PS F:\sources> dism /get-wiminfo /wimfile:f:\sources\install.esd /index:3
      
      Deployment Image Servicing and Management tool
      Version: 10.0.15063.0
      
      Details for image : f:\sources\install.esd
      
      Index : 3
      Name : Windows 10 Home Single Language
      Description : Windows 10 Home Single Language
      Size : 15,129,601,869 bytes
      WIM Bootable : No
      Architecture : x64
      Hal : <undefined>
      Version : 10.0.15063
      ServicePack Build : 0
      ServicePack Level : 0
      Edition : CoreSingleLanguage
      Installation : Client
      ProductType : WinNT
      ProductSuite : Terminal Server
      System Root : WINDOWS
      Directories : 19521
      Files : 100858
      Created : 2017.03.18 - 21:43:23
      Modified : 2017.04.13 - 12:23:50
      Languages : en-US (Default)
      
      The operation completed successfully.
      PS F:\sources> dism /get-wiminfo /wimfile:f:\sources\install.esd /index:4
      
      Deployment Image Servicing and Management tool
      Version: 10.0.15063.0
      
      Details for image : f:\sources\install.esd
      
      Index : 4
      Name : Windows 10 Education
      Description : Windows 10 Education
      Size : 15,125,050,322 bytes
      WIM Bootable : No
      Architecture : x64
      Hal : <undefined>
      Version : 10.0.15063
      ServicePack Build : 0
      ServicePack Level : 0
      Edition : Education
      Installation : Client
      ProductType : WinNT
      ProductSuite : Terminal Server
      System Root : WINDOWS
      Directories : 19519
      Files : 100691
      Created : 2017.03.18 - 21:36:11
      Modified : 2017.04.13 - 12:23:52
      Languages : en-US (Default)
      
      The operation completed successfully.
      PS F:\sources> PS F:\sources>
      

Restoring from an Image:
  • DISM /Apply-Image /ImageFile:Z:\OS-Backup.esd /ApplyDir:C: /Index:1 /NoRpFix /CheckIntegrity /Verify
    • It's best to format the System partition prior to applying an image
      • If User files aren't saved on a separate partition, either copy the User files to a separate partition, or if not available, use del to delete everything except the User folder. Once done, apply the image.
    • Index # will vary depending on the backup within the image one would like to restore.

Checking the Content of an Image:
  • Full Image:
    • DISM /Get-WimInfo /ImageFile:Z:\OS-Backup.esd

  • Individual Indexes:
    • DISM /Get-WimInfo /ImageFile:Z:\OS-Backup.esd /Index:1
But... Macrium has electrolytes, man!
 

zoomzoom

Neophyte Sage
Joined
Sep 6, 2015
Messages
671
But... Macrium has electrolytes, man!
LOL I used to utilize Acronis and realized after researching how to create a custom WinRE image back in 2012ish that utilizing 3rd Party backup solutions appear "convenient" and "simple", but doing the exact same thing natively on Windows was faster and far more convenient since one can either boot to WinRE or boot from any Windows ISO to restore.
  • Windows 8.1+ utilizes DISM for image management
  • Windows 8 and backwards supports the same, just using ImageX instead of DISM
Some Windows users are leery of CLI, however, even for those users, all that needs to be done is to copy and paste the DISM command to a text file, say DISM.txt, mount the WinRE.wim (located in Recovery/WindowsRE), copy the text file to the mount folder, and commit the change to the image. Now, whenever they boot into WinRE, they can simply do
  1. Issue: notepad
  2. CTRL+ O
  3. Navigate to X: and open DISM.txt.
  4. CTRL+ A
  5. Right click in Command Prompt to paste, hit ENTER
 
Last edited:

Spearfoot

He of the long foot
Moderator
Joined
May 13, 2015
Messages
2,266
LOL I used to utilize Acronis and realized after researching how to create a custom WinRE image back in 2012ish that utilizing 3rd Party backup solutions appear "convenient" and "simple", but doing the exact same thing natively on Windows was faster and far more convenient since one can either boot to WinRE or boot from any Windows ISO to restore.
  • Windows 8.1+ utilizes DISM for image management
  • Windows 8 and backwards supports the same, just using ImageX instead of DISM
Some Windows users are leery of CLI, however, even for those users, all that needs to be done is to copy and paste the DISM command to a text file, say DISM.txt, mount the WinRE.wim (located in Recovery/WindowsRE), copy the text file to the mount folder, and commit the change to the image. Now, whenever they boot into WinRE, they can simply do
  1. Issue: notepad
  2. CTRL+ O
  3. Navigate to X: and open DISM.txt.
  4. CTRL+ A
  5. Right click in Command Prompt to paste, hit ENTER
I'm sure everything you say is true. It's just that I was burned once about 17 years ago when I depended on Microsoft's backup scheme and I've been wary ever since. I'm sure their system is much more reliable these days.

Once nice thing about the Macrium backup images is that you can mount them and then browse and restore individual files. Pretty handy.
 

Dice

Neophyte Sage
Joined
Dec 11, 2015
Messages
1,214
@zoomzoom I think you should consider posting your suggestion for windows backups as a resource. However, at its present format there is very little "FreeNAS" content. That - could be fixed by suggesting a dataset/subdataset structure (involving anything from storing prepared ISOs to the 'incoming data'), compression levels, quota management and suggestions for snapshot intervals.

This would be a very useful resource. I'm sure many would be grateful.
(Could drop a PM for some input/error proofing - testing)
 

zoomzoom

Neophyte Sage
Joined
Sep 6, 2015
Messages
671
@Dice Will do, thanks! =]
I'm sure everything you say is true. It's just that I was burned once about 17 years ago when I depended on Microsoft's backup scheme and I've been wary ever since. I'm sure their system is much more reliable these days.

Once nice thing about the Macrium backup images is that you can mount them and then browse and restore individual files. Pretty handy.
Provided one always uses /checkintegrity /verify, it's impossible for a WIM/ESD to become corrupted. As for File Backup, it's essentially a constant non-archive, non-compression Rsync/Robocopy job, where every X hours a copy of the files are copied to a remote location [NAS or external drive]. Backed up files are assigned a UTC time and date, which is used by File -> Properties -> Previous Versions, which can be viewed in the screenshot, with the below demonstrating the file naming in the FileHistory directory. FileHistory is not a substitute for ESD/WIM backups and vice versa.
Code:
PS Microsoft.PowerShell.Core\FileSystem::\\FreeNAS\Backup\FileHistory\Win10Pro\FRACTALS\Data\D\Files\Documents\Microsoft\Office\Outlook> cmd
  Microsoft Windows [Version 10.0.15063]

C:\Windows>dir /o:n \\FreeNAS\Backup\FileHistory\Win10Pro\FRACTALS\Data\D\Files\Documents\Microsoft\Office\Outlook
  Volume in drive \\Fractals\Backup is Backup

Directory of \\FreeNAS\Backup\FileHistory\Win10Pro\FRACTALS\Data\D\Files\Documents\Microsoft\Office\Outlook

2017.06.03  21:03	<DIR>			 .
2017.05.01  18:22	<DIR>			 ..
2017.05.30  23:48	<DIR>			 Archived
2017.04.30  10:39	<DIR>			 EasCache
2015.10.23  05:36		   271,360	Email (2016_03_16 18_01_40 UTC).pst
2015.10.23  05:36		   271,360	Email (2016_05_27 10_36_15 UTC).pst
2015.10.23  05:36		   271,360	Email (2016_06_14 16_31_56 UTC).pst
2015.10.23  05:36		   271,360	Email (2016_07_24 18_32_47 UTC).pst
2015.10.23  05:36		   271,360	Email (2016_10_02 15_33_50 UTC).pst
2015.10.23  05:36		   271,360	Email (2017_04_30 15_09_31 UTC).pst
2017.04.30  13:25	   200,286,208	Exchange (2017_04_30 18_26_01 UTC).ost
2017.04.30  13:36	   200,286,208	Exchange (2017_04_30 18_39_36 UTC).ost
2017.05.01  11:52	   216,965,120	Exchange (2017_05_01 23_14_22 UTC).bak
2017.05.01  11:56		   101,729	Exchange (2017_05_01 23_14_22 UTC).log
2017.05.01  21:38	   183,607,296	Exchange (2017_05_02 02_44_36 UTC).ost
2017.05.29  18:34	   183,607,296	Exchange (2017_05_30 02_15_16 UTC).ost
2017.06.03  21:00	   183,607,296	Exchange (2017_06_04 02_01_50 UTC).ost
2017.05.01  11:53	   233,644,032	Exchange_2 (2017_05_01 23_14_22 UTC).bak
2017.05.01  11:55	   250,322,944	Exchange3 (2017_05_01 23_14_22 UTC).bak
2009.03.10  22:00			 1,436	extend (2016_03_16 18_01_40 UTC).dat
2009.03.10  22:00			 1,436	extend (2016_05_27 10_36_15 UTC).dat
2009.03.10  22:00			 1,436	extend (2016_06_14 16_31_56 UTC).dat
2009.03.10  22:00			 1,436	extend (2016_07_24 18_32_47 UTC).dat
2009.03.10  22:00			 1,436	extend (2016_10_02 15_33_50 UTC).dat
2009.03.10  22:00			 1,436	extend (2017_04_30 15_09_31 UTC).dat
2011.02.28  10:00		87,376,896	Outlook (2016_03_16 18_01_40 UTC).bak
2011.02.28  10:09			79,428	Outlook (2016_03_16 18_01_40 UTC).log
2016.03.16  13:01	   477,447,168	Outlook (2016_03_16 18_01_40 UTC).pst
2016.03.22  12:01	   477,447,168	Outlook (2016_03_22 17_01_45 UTC).pst
2016.03.27  01:34	   621,437,952	Outlook (2016_03_27 06_37_40 UTC).pst
2016.04.07  02:46	   621,437,952	Outlook (2016_04_07 07_50_28 UTC).pst
2016.04.10  20:31	   621,437,952	Outlook (2016_04_11 01_29_18 UTC).pst
2016.04.16  06:08	   642,008,064	Outlook (2016_04_16 11_05_29 UTC).pst
2016.04.21  23:12	   662,578,176	Outlook (2016_04_22 04_12_29 UTC).pst
2011.02.28  10:00		87,376,896	Outlook (2016_05_27 10_36_15 UTC).bak
2011.02.28  10:09			79,428	Outlook (2016_05_27 10_36_15 UTC).log
2016.05.27  03:48	   178,799,616	Outlook (2016_05_27 10_36_15 UTC).pst
2011.02.28  10:00		87,376,896	Outlook (2016_06_14 16_31_56 UTC).bak
2011.02.28  10:09			79,428	Outlook (2016_06_14 16_31_56 UTC).log
2011.02.28  10:00		87,376,896	Outlook (2016_07_24 18_32_47 UTC).bak
2011.02.28  10:09			79,428	Outlook (2016_07_24 18_32_47 UTC).log
2016.09.26  00:57	   812,663,808	Outlook (2016_09_26 06_01_39 UTC).pst
2011.02.28  10:00		87,376,896	Outlook (2016_10_02 15_33_50 UTC).bak
2011.02.28  10:09			79,428	Outlook (2016_10_02 15_33_50 UTC).log
2011.02.28  10:00		87,376,896	Outlook (2017_04_30 15_09_31 UTC).bak
2011.02.28  10:09			79,428	Outlook (2017_04_30 15_09_31 UTC).log
2017.05.01  11:54		   227,364	Outlook (2017_05_01 23_14_22 UTC).log
2017.05.11  05:21	 1,017,857,024	Outlook (2017_05_11 10_26_40 UTC).pst
2017.05.22  00:45	 1,038,427,136	Outlook (2017_05_22 05_47_07 UTC).pst
2017.05.29  18:33	 1,038,427,136	Outlook (2017_05_30 02_15_16 UTC).pst
2009.03.10  22:50			 1,298	Outlook.sharing.xml (2016_03_16 18_01_40 UTC).obi
2009.03.10  22:50			 1,298	Outlook.sharing.xml (2016_05_27 10_36_15 UTC).obi
2009.03.10  22:50			 1,298	Outlook.sharing.xml (2016_06_14 16_31_56 UTC).obi
2009.03.10  22:50			 1,298	Outlook.sharing.xml (2016_07_24 18_32_47 UTC).obi
2009.03.10  22:50			 1,298	Outlook.sharing.xml (2016_10_02 15_33_50 UTC).obi
2009.03.10  22:50			 1,298	Outlook.sharing.xml (2017_04_30 15_09_31 UTC).obi
2013.12.17  10:44			   261	Outlook.xml (2016_03_16 18_01_40 UTC).kfl
2013.12.17  10:44			   261	Outlook.xml (2016_05_27 10_36_15 UTC).kfl
2013.12.17  10:44			   261	Outlook.xml (2016_06_14 16_31_56 UTC).kfl
2013.12.17  10:44			   261	Outlook.xml (2016_07_24 18_32_47 UTC).kfl
2013.12.17  10:44			   261	Outlook.xml (2016_10_02 15_33_50 UTC).kfl
2013.12.17  10:44			   261	Outlook.xml (2017_04_30 15_09_31 UTC).kfl
2017.05.01  11:52	 1,203,495,936	Outlook_2017.05.01 (2017_05_01 23_14_22 UTC).bak
2017.04.30  10:38	<DIR>			 RoamCache
2017.04.30  10:38	<DIR>			 Rules (Exported)
2017.04.30  10:38	<DIR>			 Settings

 

Attachments

Last edited:

Spearfoot

He of the long foot
Moderator
Joined
May 13, 2015
Messages
2,266
@Dice Will do, thanks! =]

Provided one always uses /checkintegrity /verify, it's impossible for a WIM/ESD to become corrupted. As for File Backup, it's essentially a constant non-archive, non-compression Rsync/Robocopy job, where every X hours a copy of the files are copied to a remote location [NAS or external drive]. Backed up files are assigned a UTC time and date, which is used by File -> Properties -> Previous Versions, which can be viewed in the screenshot, with the below demonstrating the file naming in the FileHistory directory. FileHistory is not a substitute for ESD/WIM backups and vice versa.
Code:
PS Microsoft.PowerShell.Core\FileSystem::\Fractals\Backup\FileHistory\Win10Pro\James\ALIENFRACTALS\Data\D\JW0914\Documents\Microsoft\Office\Outlook> cmd
  Microsoft Windows [Version 10.0.15063]

C:\Windows>dir /o:n \\Fractals\Backup\FileHistory\Win10Pro\James\ALIENFRACTALS\Data\D\JW0914\Documents\Microsoft\Office\Outlook
  Volume in drive \\Fractals\Backup is Backup

Directory of \\FreeNAS\Backup\FileHistory\Win10Pro\FRACTALS\Data\D\Files\Documents\Microsoft\Office\Outlook

2017.06.03  21:03	<DIR>			 .
2017.05.01  18:22	<DIR>			 ..
2017.05.30  23:48	<DIR>			 Archived
2017.04.30  10:39	<DIR>			 EasCache
2015.10.23  05:36		   271,360	Email (2016_03_16 18_01_40 UTC).pst
2015.10.23  05:36		   271,360	Email (2016_05_27 10_36_15 UTC).pst
2015.10.23  05:36		   271,360	Email (2016_06_14 16_31_56 UTC).pst
2015.10.23  05:36		   271,360	Email (2016_07_24 18_32_47 UTC).pst
2015.10.23  05:36		   271,360	Email (2016_10_02 15_33_50 UTC).pst
2015.10.23  05:36		   271,360	Email (2017_04_30 15_09_31 UTC).pst
2017.04.30  13:25	   200,286,208	Exchange (2017_04_30 18_26_01 UTC).ost
2017.04.30  13:36	   200,286,208	Exchange (2017_04_30 18_39_36 UTC).ost
2017.05.01  11:52	   216,965,120	Exchange (2017_05_01 23_14_22 UTC).bak
2017.05.01  11:56		   101,729	Exchange (2017_05_01 23_14_22 UTC).log
2017.05.01  21:38	   183,607,296	Exchange (2017_05_02 02_44_36 UTC).ost
2017.05.29  18:34	   183,607,296	Exchange (2017_05_30 02_15_16 UTC).ost
2017.06.03  21:00	   183,607,296	Exchange (2017_06_04 02_01_50 UTC).ost
2017.05.01  11:53	   233,644,032	Exchange_2 (2017_05_01 23_14_22 UTC).bak
2017.05.01  11:55	   250,322,944	Exchange3 (2017_05_01 23_14_22 UTC).bak
2009.03.10  22:00			 1,436	extend (2016_03_16 18_01_40 UTC).dat
2009.03.10  22:00			 1,436	extend (2016_05_27 10_36_15 UTC).dat
2009.03.10  22:00			 1,436	extend (2016_06_14 16_31_56 UTC).dat
2009.03.10  22:00			 1,436	extend (2016_07_24 18_32_47 UTC).dat
2009.03.10  22:00			 1,436	extend (2016_10_02 15_33_50 UTC).dat
2009.03.10  22:00			 1,436	extend (2017_04_30 15_09_31 UTC).dat
2011.02.28  10:00		87,376,896	Outlook (2016_03_16 18_01_40 UTC).bak
2011.02.28  10:09			79,428	Outlook (2016_03_16 18_01_40 UTC).log
2016.03.16  13:01	   477,447,168	Outlook (2016_03_16 18_01_40 UTC).pst
2016.03.22  12:01	   477,447,168	Outlook (2016_03_22 17_01_45 UTC).pst
2016.03.27  01:34	   621,437,952	Outlook (2016_03_27 06_37_40 UTC).pst
2016.04.07  02:46	   621,437,952	Outlook (2016_04_07 07_50_28 UTC).pst
2016.04.10  20:31	   621,437,952	Outlook (2016_04_11 01_29_18 UTC).pst
2016.04.16  06:08	   642,008,064	Outlook (2016_04_16 11_05_29 UTC).pst
2016.04.21  23:12	   662,578,176	Outlook (2016_04_22 04_12_29 UTC).pst
2011.02.28  10:00		87,376,896	Outlook (2016_05_27 10_36_15 UTC).bak
2011.02.28  10:09			79,428	Outlook (2016_05_27 10_36_15 UTC).log
2016.05.27  03:48	   178,799,616	Outlook (2016_05_27 10_36_15 UTC).pst
2011.02.28  10:00		87,376,896	Outlook (2016_06_14 16_31_56 UTC).bak
2011.02.28  10:09			79,428	Outlook (2016_06_14 16_31_56 UTC).log
2011.02.28  10:00		87,376,896	Outlook (2016_07_24 18_32_47 UTC).bak
2011.02.28  10:09			79,428	Outlook (2016_07_24 18_32_47 UTC).log
2016.09.26  00:57	   812,663,808	Outlook (2016_09_26 06_01_39 UTC).pst
2011.02.28  10:00		87,376,896	Outlook (2016_10_02 15_33_50 UTC).bak
2011.02.28  10:09			79,428	Outlook (2016_10_02 15_33_50 UTC).log
2011.02.28  10:00		87,376,896	Outlook (2017_04_30 15_09_31 UTC).bak
2011.02.28  10:09			79,428	Outlook (2017_04_30 15_09_31 UTC).log
2017.05.01  11:54		   227,364	Outlook (2017_05_01 23_14_22 UTC).log
2017.05.11  05:21	 1,017,857,024	Outlook (2017_05_11 10_26_40 UTC).pst
2017.05.22  00:45	 1,038,427,136	Outlook (2017_05_22 05_47_07 UTC).pst
2017.05.29  18:33	 1,038,427,136	Outlook (2017_05_30 02_15_16 UTC).pst
2009.03.10  22:50			 1,298	Outlook.sharing.xml (2016_03_16 18_01_40 UTC).obi
2009.03.10  22:50			 1,298	Outlook.sharing.xml (2016_05_27 10_36_15 UTC).obi
2009.03.10  22:50			 1,298	Outlook.sharing.xml (2016_06_14 16_31_56 UTC).obi
2009.03.10  22:50			 1,298	Outlook.sharing.xml (2016_07_24 18_32_47 UTC).obi
2009.03.10  22:50			 1,298	Outlook.sharing.xml (2016_10_02 15_33_50 UTC).obi
2009.03.10  22:50			 1,298	Outlook.sharing.xml (2017_04_30 15_09_31 UTC).obi
2013.12.17  10:44			   261	Outlook.xml (2016_03_16 18_01_40 UTC).kfl
2013.12.17  10:44			   261	Outlook.xml (2016_05_27 10_36_15 UTC).kfl
2013.12.17  10:44			   261	Outlook.xml (2016_06_14 16_31_56 UTC).kfl
2013.12.17  10:44			   261	Outlook.xml (2016_07_24 18_32_47 UTC).kfl
2013.12.17  10:44			   261	Outlook.xml (2016_10_02 15_33_50 UTC).kfl
2013.12.17  10:44			   261	Outlook.xml (2017_04_30 15_09_31 UTC).kfl
2017.05.01  11:52	 1,203,495,936	Outlook_2017.05.01 (2017_05_01 23_14_22 UTC).bak
2017.04.30  10:38	<DIR>			 RoamCache
2017.04.30  10:38	<DIR>			 Rules (Exported)
2017.04.30  10:38	<DIR>			 Settings

Is all of this available for Windows 7?
 

zoomzoom

Neophyte Sage
Joined
Sep 6, 2015
Messages
671
Is all of this available for Windows 7?
It is, but you would use ImageX instead of DISM. See ImageX man on TechNet.

As to FileHistory, that is as well and if it's not under the Control Panel\System and Security\File History, it should be under Control Panel\System and Security
 
Last edited:

Ericloewe

Not-very-passive-but-aggressive
Moderator
Joined
Feb 15, 2014
Messages
17,019
The bad news is that rumor has it that File History is getting canned later this year.
 

Robert Trevellyan

Pony Wrangler
Joined
May 16, 2014
Messages
3,778
it's always baffled me why people choose 3rd Party products
I've set up Windows native backup for several clients. The problem I see most often is silent failure. I don't consider an Action Center notification sufficient to warn a typical user that their backup isn't working.
I'm sure their system is much more reliable these days.
Not in my experience.
 

zoomzoom

Neophyte Sage
Joined
Sep 6, 2015
Messages
671
The bad news is that rumor has it that File History is getting canned later this year.
That would be a bummer for a lot of users, especially if it's not replaced with anything as simple to configure. I wonder what they're going to do with the File Properties -> Previous Versions tab, as that's the main way in which FileHistory is meant to be utilized. You can utilize it to restore entire directories/partitions, but it's meant for the granular, per file usage.

What FileHistory does can still be somewhat accomplished quite easily with a Robocopy Job added to Task Scheduler and set to run at boot, however one would obviously not be able to utilize the Previous Versions tab.
I've set up Windows native backup for several clients. The problem I see most often is silent failure. I don't consider an Action Center notification sufficient to warn a typical user that their backup isn't working.
If you're referring to FileHistory as "native backup", that wasn't what I was referring to. Windows has always provided native backup capabilities to WIM/ESD images via ImageX prior to Win8 and DISM after, of which can't silently fail, as any issue reports to the DISM log (C:\Windows\Logs\DISM\dism.log), as well as multiple Event logs. It's also literally impossible for a WIM/ESD image to become corrupted as long as one always uses /CheckIntegrity /Verify.
  • I personally always recommend running all user directories on a separate partition (not the entire User folder, just individual folders, which can be moved via File Properties - Location), then creating a Task to run once a week to backup the User partition to external storage (mine goes to one of my FreeNAS Backup shares), and since WIM/ESD images only copy in a new file if a file in the previous image has been changed, they stay quite small in size (for example, my OS partition is ~175GBytes in size, while my backup ESD, which contains 5 images of the system partition, is ~60GBytes).
    • Each WIM/ESD index is a full backup image, not a differential or incremental, so lets say you have a system partition WIM/ESD with a single image in it and will be appending a new image to it, the WIM/ESD is likely to only increase a few GB since most of the files on the System Partition won't have changed. Each additional image will utilize a file in a prior index's database if that file hasn't changed (verified via hashing), allowing for an extremely efficient size to data contained ratio.
  • I prefer full partition backups, with a separate user partition since you can't image the system partition while booted to Windows, however you can also image just folders, allowing one to image C:\Users\%username% without offlining to WinRE to take the image, and for it to be run from Task Scheduler.
In regards to FileHistory, any errors will also be logged to the Event logs at \Applications and Services Logs\Microsoft\Windows\FileHistory-core & FileHistory-engine
 
Last edited:

Ericloewe

Not-very-passive-but-aggressive
Moderator
Joined
Feb 15, 2014
Messages
17,019
I wonder what they're going to do with the File Properties -> Previous Versions tab, as that's the main way in which FileHistory is meant to be utilized.
It's going nowhere, because it's used for NTFS shadow copies, SMB previous versions, and whatever ReFS calls snapshots.
 
Status
Not open for further replies.
Top