Aller au contenu principal

Entire PC backup to QNAP stalls consistently

Thread needs solution

I am trying to use Acronis True Image 2017 to do an "Entire PC" backup to a QNAP NAS. 

The transfer begins and reproducibily creates a file that increases in size until it reaches exactly 12,967,936 at which point it stalls and no longer transfers. 

I'm not sure if this is an Acronis problem or a QNAP problem. 

Any suggestions on how to troubleshoot this?

thanks!

0 Users found this helpful

Grab the MVP log viewer which is linked below in this post.  Use it to check some of the most current service.logs as it might shed some light on the issue. You can also upload some of the recent service.logs here for additional review.

I'm not sure if that 12,967,936 is MB or KB, but I'm going to assume MB.  If that is true, then that would be 12.967936 TB of data and I suspect you may be running out of space on the NAS.  

If you are using "entire pc" you may be backing up much more than you intend to and running out space on the NAS in the process.  I would suggest that you reconfigure a NEW backup, making sure to use "disks and paritions" and only select the backup disk(s) you truly intend to backup.  Then use Windows to determine how much space is actively in use on that disk and compare that to how much space is actually available on the NAS and make sure that it would fit.

Even if space is not an issue, 13TB of backup is HUGE to do in one job.  You could very well be overwhelming the CPU and available memory on the NAS if attempting to backup up that much data in one go.  Or, you could be overwhelming your network equipment (switches or home router) as the router may be running out of CPU or memory resources at some point in such a large file transfer. 

Hopefully the logs will point you in the right direction...

Thanks for the quick response. I will try the log viewer. 

Those numbers were KB, rather than MB, so it is not a space issue. I successfully saved a 110GB subfolder off of the same drive using "Files and Folders" as a source rather than "Entire PC", so it seems to be partially working. 

I'll keep trying, maybe let it try overnight and see what happens. 

 

Roger that.  You may want to run chkdsk /f /r against your source drive as well.  If there are dirty/bad sectors on the disk, that could cause a full disk backup to fail (where a copy would not).  Particularly, becuase the bad/dirty sector lives somewhere else on the drive (A windows or system folder, the bootloader partition or a recovery partition).  

Unfortunately, chkdsk may still not chck those other paritions if they are not assigned a drive letter.  You can assign one using the Windows installer advanced menu command prompt and diskpart.  Or, probably easier, you can run something like Seatools or WD Data lifeguard on the drive instead.

WD Data Lifeguard Diagnostic for Windows

SeaTools for Windows from (http://www.seagate.com/support/downloads/seatools/