Stuck in nonstop hell
I have deleted a Nonstop backup from my list of backups. Sadly, it won't go away. Nor can I edit the now supposedly dead backup. Throws up an error:
Event code: 0x0064028A+0x01030008+0x01030001
The Acronis Support Center tells me that:
"There is no information about this error available now. You can use the links below to search for any additional information that might be available."
How can I tell TI2017 to forget about this backup so that I can create a new version?
I want to do this because this backup is really a Nonstop pain. It was throwing up errors every day.
It took time to track those inscrutable errors down to the Nonstop backup. Strangely, it recovered if I went to the back settings, paused the backup and then resumed it. But that is another matter.
I have done a "Repair" on the installation but that has not helped.
I've spent a few hours looking around here and in the KnowledgeBase. Nothing comes to mind.
Any thoughts?
Excellent. Something to start with.
Yes, script still there.
Deleted. Now gone from TI2017 too.
Fingers crossed that I can build a new backup that doesn't fall over every day.
Much appreciated.
I cant' really speak for NSB stability - I've never used it - it's one of the more troublesome backup schemes mentioned in the forums and I think it's a mix of systems not being able to keep up with the constant changes., but also, people aren't really aware of some of the other gotchas's... particulalry when it relates to open databases (even Outlook PST's) as they often get missed because they are open in memory and not saved to disk so NSB is not capturing those changes anyway.
Also, all your daily "NSB"'s get consolicated into a single one each day at midnight so you cant' really recover to those multiple restore points once the consolidation occurs each day. Really NSB only helps you that same day, up to 11:59PM, then you only have a single restore point for any day prior to the current one as soon as 12:00AM comes around.
I would personally recommend using frequent incrementals if you have such an email or database backup need -perhaps hourly. Set up a backup scheme of 1 full and 23 hourly incrementals to capture an hourly backup - preferably just for the necessary folders that needs such a backup scheme (instead of trying to backup your entier system this frequently - you can always make other backup tasks for full system, certain folders, etc). Also for any open database, some of your backups should try to include a backup when the database is not open either. SQL and Oracle have their own database backup method too. Use those for your primary restore and then use Acronis to backup, the backup in case you lose the drive that those database backups are housed on.
I get what it's inteneded for, but think that NSB is actually a less capable backup plan than one would really expect. You're never going to capture all open database changes (PST's, SQL, Oracle), using NSB. If you need to backup email, leave it on the server and use IMAP with archiving (standard in Gmail and some other mail applications). If you still need local email backups, it's really not goign to capture every email as they come in - using timed incrementals and backign up the database when it's not in use (from time to time) will help ensure you can recover email with minimal loss of data.
I have seen all of the whines about nonstop backup. My take is that if Acronis offers a feature, it should work.
You don't know my own regime, so I can forgive you for not realising that I have other procedures in place to deal with the drawbacks that you highlight.
Rather than an essay on why I am a misguided twerp, all I really needed was help to fix a problem.
For the time being at least, I now have it sorted out, for which thanks.
Sadly, my experience over the years with True Image is that none of it really works as expected, which is why I have those other routines in place.
To give just one example of how useless ATI can be, what help is an error message that says no more than "Oops"? Not even a hint as to which of my libraries of backups failed. Hopeless.
Michael,
Nothing was directed at you personally - just relaying my personal thoughts on NSB and the caveats that many aren't aware of so that they can make an informed decision about the scheme if they're considering it.
Again, I don't personally use NSB so I can't speak to it's reliability and/or what issues may some users may see (or not). NSB rarely seems to come up in the forums these days, so hopefully stability is better in current releases. There are a number of reasons why any backup scheme can fail though. No idea why the trouble showed up on your particular machine, but am glad the information I provided helped you to be able to remove the existing NSB backup so you can try again.