2019 > 2020 upgrade PCs have incomplete .tibx backups. Need both volsnap and fltrsrv registry entries
Steve Smith wrote:Paul, in this case the NAS is a PC running Windows Home Server 2011 which is not an area that I have any experience with either. I have never seen these types of issues with my Synology NAS for my own backups across my home network.
Slight misunderstanding, my current WHS2011 server backs up the Win 7 PCs, but cannot handle Win 10, so I am trying to use Acronis to migrate to my new HP ML310E Gen 8 server running Win10
I have a second different HP Microserver Gen 8 running Win10 and 2020 backup to this has exactly the same problems.
Acronis has used VSS for some years before 2019, so why should .tib backup when .tibx doesn't
Mustang wrote:Thanks Steve, I guess I missed that about Windows Home Server 2011. Maybe Bob (Enchantech) can help. However, I think it's complicated by the fact this is a Windows 7 system. Windows 7 isn't very good at remembering network credentials.
Above, I explained WHS2011 is not involved in this other than backups to this have worked seamlessly for years but now I need Win 10 support.
2020 doesn't run reliably and it is supposed to be Win 7 compatible, so surely I can rightly expect Acronis 2020 to handle any limitations - and does for .tib backups?
Well' you don't seem to getting to where you want to be. I have two suggestion at this point. If I were you, I would do both.
1. Steve developed a modification to change a task from creating files of the tibx format to the tib format. You can try that to see if indeed the tibx format is causing your problems. Steve can help you with that.
2. It's time to try another backup solution. I would use Macrium Reflect Free. You can install it in Windows 7 along side True Image. There will be no conflict. Having more than one backup solution is a good idea (not putting all your eggs in one basket).
See forum topic: How to create a Disk backup as .tib (not .tibx) which will create a new backup task using the older .tib format in the Windows ATI 2020 or 2021 GUI.
Steve Smith wrote:See forum topic: How to create a Disk backup as .tib (not .tibx) which will create a new backup task using the older .tib format in the Windows ATI 2020 or 2021 GUI.
Thanks Steve, I'll give that a try
First question: How do I set 'Backup Later' ?
Mustang wrote:...It's time to try another backup solution. I would use Macrium Reflect Free. You can install it in Windows 7 along side True Image. There will be no conflict. Having more than one backup solution is a good idea (not putting all your eggs in one basket).
Thanks for the hint, I will try it out.
Looking at their web page, It was not instantly obvious whether Macrium is PC or Server based, so can you help?
Macrium Free is PC based no serve needed.
thomasjk wrote:Macrium Free is PC based no serve needed.
If Macrium turns out suitable, then the features of the paid-for versions would be needed, so can you advise what I would need for 4 PCs backing up to a Win 10 server?
I wouldn't think you'd need a server license if you are only back up to the server and not backing up the server. They sell the Home edition in a 4 pack for $139.
To be safe, you should ask the Macrium sales team exactly what you should buy. I see a popup flag in the lower right corner of their website for asking sales questions.
Mustang wrote:I wouldn't think you'd need a server license if you are only back up to the server and not backing up the server. They sell the Home edition in a 4 pack for $139.
To be safe, you should ask the Macrium sales team exactly what you should buy. I see a popup flag in the lower right corner of their website for asking sales questions.
I'm running Macrium now and it looks like it is working.
However I hit the Hide button on the backup progress GUI (as there is not a 'minimise' button) and I cannot find how to get it back to see if it completed. Can you help?
Update, I finally found out how to un-hide on the Macrium forum as it was not present / obvious in the manual. Setting and saving backups seem to very easy in the GUI, rather than following the over complex user guide.
Will update further in the morning when the first backs and incrementals show be complete.
Macrium Full + 1 Incremental backup have now run seamlessly whilst Acronis backups continue to fail.
Event Viewer has shown no system errors, whilst the same Application errors have continued, so I have turned off all Acronis backups and will recheck tomorrow.
If errors disappear, it seems to prove Acronis is the root problem, especially as Macrium also uses VSS and has tools to log and fix VSS errors, so they must be conscious of potential problems with VSS.
W Thomas Phillips wrote:Macrium Full + 1 Incremental backup have now run seamlessly whilst Acronis backups continue to fail.
Event Viewer has shown no system errors, whilst the same Application errors have continued, so I have turned off all Acronis backups and will recheck tomorrow.
If errors disappear, it will likely prove Acronis is the root problem, especially as Macrium also uses VSS and has tools to log and fix VSS errors, so they must be conscious of potential problems with VSS.
That's good news. I hope things continue to work well for you.
Mustang wrote:That's good news. I hope things continue to work well for you.
I switched off all Acronis backups, while leaving the trial Macrium one running, and since then have seen no Event errors. I think that is conclusive proof that the fault lies with 2020.
My one remaining problem is that I cannot get Macrium restore media to access the network. Checked all the drivers that were requested were available during the recovery build process, although Ethernet driver was not on the list, and booting up the media indicates that the network is set up. When it opens I cannot access the network either though the Explorer links or typing the UNC. Any ideas?
Try mapping a network shared folder as a drive letter from a command window in the recovery environment.
net use Y: \\ComputerName\SharedFolder /user:\UserName password
or
net use Y: \\IP_Address\SharedFolder /user:\UserName password
For more help with Macrium questions you should be using the Macrium forum.
Duplicate post
Mustang wrote:Try mapping a network shared folder as a drive letter from a command window in the recovery environment.
net use Y: \\ComputerName\SharedFolder /user:\UserName password
or
net use Y: \\IP_Address\SharedFolder /user:\UserName password
For more help with Macrium questions you should be using the Macrium forum.
Thanks Paul, sadly a trial Macrium license does not include forum access.
However I did start seeing Macrium VSS errors when I enabled the 'Verify Backup' option, whilst I also check Events on my WHS2011 (which I thought was clean) and it too showed I've had VSS errors for years.
I have used DrivePool for many years (instead of RAID) for folder mirroring and asking about these problems, they said it does not support VSS and large files may indeed show errors, so this could be the root cause.
I did look online and virtuallt all apps do not support VSS and have talk of VSS errors in their forums, so do you know any other Win 10 file / folder mirroring app that I might try to see if this helps the problem?
Mustang wrote:Try mapping a network shared folder as a drive letter from a command window in the recovery environment.
net use Y: \\ComputerName\SharedFolder /user:\UserName password
or
net use Y: \\IP_Address\SharedFolder /user:\UserName password
For more help with Macrium questions you should be using the Macrium forum.
Thanks Paul,
I'm now seeing VSS errors whatever I use, so I talked to Stablebit, whose folder duplication app I use on the server, and they said that it does not support VSS, so that may be the root cause of many of my troubles.
I'm thinking of using Storage Spaces instead on my server as I'd expect it not to have VSS issues, so what do you think?
W Thomas Phillips said:
I'm thinking of using Storage Spaces instead on my server as I'd expect it not to have VSS issues, so what do you think?
You should be able to find success with VSS and Storage Spaces on your server using either an NTFS or an ReFS filesystem.
Have a read of the link below for some great info on using Shadow Storage with Storage Spaces
Enchantech wrote:You should be able to find success with VSS and Storage Spaces on your server using either an NTFS or an ReFS filesystem.
Have a read of the link below for some great info on using Shadow Storage with Storage Spaces
Thanks. The link looks rather complex for my limited knowldege, but is Shadow Storage not just part of what Storage Spaces does?
There is little Microsoft documentation on Storage Spaces, so is there not a default for setting for Shadow storage that that is set for each disk and/or simply increases as disks are added?
Storage Spaces is Microsoft's version of what's called a Software Raid where multiple drives are arranged by software to appear as a single storage disk or more correctly a storage pool. The storage pool typically keeps copies of your data in a mirror image on more than one disk of the storage pool. So if a disk fails that disk can be replaced and the pool made healthy again without data loss. This is different than Shadow Storage.
For VSS, Windows is able to work with the Storage Spaces software to allocate disk space for Shadow Copy purposes. When the filesystem used is NTFS for Storage Spaces the disk space should show up in the System Protection tab of System Properties thus it can be configured for VSS Shadow Storage. The reason for the complexity of the link answer I supplied is that in that example the ReFS filesystem was used for Storage Spaces rather than NTFS.
There are advantages to using ReFS with Network Attached Storage systems or Virtualized workloads via implementation of Storage Spaces Direct. Using ReFS with regular Storage Spaces is suitable for shared storage arrangements such as data servers or SAS enclosures.
You can learn more about ReFS Here
Enchantech wrote:Storage Spaces is Microsoft's version of what's called a Software Raid where multiple drives are arranged by software to appear as a single storage disk or more correctly a storage pool. The storage pool typically keeps copies of your data in a mirror image on more than one disk of the storage pool. So if a disk fails that disk can be replaced and the pool made healthy again without data loss. This is different than Shadow Storage.
For VSS, Windows is able to work with the Storage Spaces software to allocate disk space for Shadow Copy purposes. When the filesystem used is NTFS for Storage Spaces the disk space should show up in the System Protection tab of System Properties thus it can be configured for VSS Shadow Storage. The reason for the complexity of the link answer I supplied is that in that example the ReFS filesystem was used for Storage Spaces rather than NTFS.
There are advantages to using ReFS with Network Attached Storage systems or Virtualized workloads via implementation of Storage Spaces Direct. Using ReFS with regular Storage Spaces is suitable for shared storage arrangements such as data servers or SAS enclosures.
You can learn more about ReFS Here
Helpful, thanks. I understand that Microsoft are not developing ReFS in the future and I am not using Storage Spaces direct but am using the Win 10 version on a single server, so do I still need to manually configure Shadow Storage or is it automatically handled in my setup?
Is there a link somewhere (user guide?) from Microsoft on Storage Spaces?