catalog failure after backup
I have 3 types of backups scheduled to run automatically: daily, monthly and yearly. Each type of backup goes to a different drive. I keep 4 weeks worth of daily backups (full on Sunday, incremental on other days). I have 6 monthly sets - full backup on the first of the month, and 3 sets of yearly backups.
I was concerned about being "infected" by one of the viruses that encrypt your online data and demand a ransom. I feared that, since my backups are on the same machine, I could be left with both my original data and my backups encrypted. To solve the problem, I created command files to change the drive status from online to offline and back again, using diskpart. When the backup started, I could run a pre-backup command to change the needed disk from offline to online, with a similar process to make it offline when the process ends. Unfortunately, this doesn't quite work. When you change a disk from online to offline and back again, something changes and Acronis cannot catalog the backup. I have rebuilt the catalog and tried different things, but once the disk goes offline and then online, it doesn't work.
Any suggestions? Thanks in advance.
It works fine if I don't run the post-command, but that makes it useless. My intention was to have the backups offline except when they are running. One would normally expect something called a "post command" to run AFTER the process had finished and cataloging is part of the process.
Hello Rich,
The catalog operation indexes the backup to enable search in the data view. That is really its only purpose. Building this index is done right after the backup operation, but is not really considered part of the backup operation since all the data is backed up and fully restorable without the catalog.
I see two ways to work around this issue:
- If you don't need to search your backups for specific files (i.e. you know where your files are located in the images), you can simplt disable the catalog.
- You can schedule the post-command via the Windows task scheduler to run at a time that takes into account the cataloging operation.
I have taken your situation into account for future versions and we will look into making some sort of post-all-operations command that runs when the agent becomes idle.