Salta al contenuto principale

Cheers Acronis......Not

Thread needs solution

I have been using nonstop backup as this has been a good friend to me and my style of PC use & backup (music home-studio). When TIH2012 came along I went straight for it. Big mistake, not only did NSB not continue on the existing NSB, after many hours of churning, the relevant folder (Time Explorer Storage) was a total of 0 Bytes.

Pity really since my RAID0 array chose that day to die. Some time was spent with one's cheeks firmly clenched... Long story short, I recovered my data but not thanks to Acronis, but rather a fluke temporary reinstatement of the array. That moment decided that I should now run two backup disks and rotate them weekly.

Once the second backup was complete, I wiped all traces of TIH and reinstalled. No sooner complete I set about updating the NSB of one backup hard drive. Several hours later.... 0 bytes and no backup; 2012 was uninstalled and I was not happy.

I reinstated TIH2011 and all was well: well for a week or two. Then Acronis kindly updated TIH 2011. Ah I thought, perhaps a good time to try 2012 again but first I'll just complete a nonstop run on 2011. Oh... - since updating 2011, NSB is broken. It just sits there twiddling its cursor indefinitely. To be sure I left it overnight and then forgot about it, buried under a heap of other windows. Nearly 20 hours later it's still sat there, drawing circles in pixels. I had to kill the task in the end. I tried a reboot - and a reinstall, nada.

What's going wrong? Is there a disgruntled programmer in the office spiking the coffee with LSD or something? I rely on the security of TIH to keep irreplaceable material safe but my confidence is taking a hard knock right now. Oh - please don't suggest the cloud as a safety net, I have TB's of data and a lowly (rural) broadband connection.

Oh well, time to wipe away r6942 and go backwards yet again. Perhaps someone could tell me when it's safe to use up to date Acronis software again?

0 Users found this helpful

Nigel,

NSB is a different technology. There is no validation, no individual backup files, no retention rules,...

To fix things, you can delete your backup task, then try to uninstall, use the clean up utility to remove remnants, and reinstll.

If your objective is to protect irreplaceable data, you should be paranoid about:
- diversifying your backup locations: rotates your disks, take a disk offsite,
- diversifying your backup schemes: disk and partition backup are the ATI foundation, they rarely fail. NSB is fine but less control. Do one AND the other. I use ATI only for daily disk images, but weekly Windows 7 images as well.
- diversifying your backup technology: for things like big files that are compressed in nature and rarely change, a simple sync software that verifies what it copies is as good as it gets to have a redunant backup. I use Syncback because it features retention rules on versions. For small files that change often (eg Quicken), I add an online backup.