S
Stephanie Seney
Guest
I can accept that, however the issue that occurred was on the day/night of the backup on 6/12 - not after that time. While the progress backups were executing on the VM machine, the VM SAN ran out of disk space. This happened apparently during the progress backups. When the VM ran out of space, it apparently "suspends" operations. The whole server was thus "unavailable" the following morning. Our SA increased the space needed by the VM snapshots, and then the server(s) were available. Once the our DB server was "awakened", the progress backups completed - along with the varifies - as seen in my initial post. However, it appears that because the VM ran out of space during the backup of this DB - that apparently corrupted the progress backup, yet, the immediate prorest verify passes didn't detect that corruption. My concern is that if we were to script the restore, if the initial verify shows it was GOOD, but something undetected by progress backup verify does happen and the CRC is thrown, how long before the restore attempt is aborted because of the CRC errors? In this case, I was "monitoring" the restore in part...and just killed the script since it seemed like all it would do is continue with the CRC error until the disk space of the restore location was filled up. I'm not saying that the CRC error is not "legit" because it was....and I can attribute it to the VM disk space issue on the day of the backup, yet, the verify pass didn't catch that it was corrupted. We create full progress backups nightly that reside on disk. I will be attempting to restore them again today to the special testing location - so that I can do some time tests of how long a DB change on our LIVE DBs will take, for a project to be installed next week. This special restore script would not be used daily - just on an as needed case. I was hoping to be able to run it right after the DB backups complete (and they are up in MU mode ready for the following day), but if the restore hangs if any CRC issue happens...I'm not going to since I'm not comfortable now with the verify pass.
Continue reading...
Continue reading...