I make sure to pick some from the newest restore point, some from the middle of the chain, and some from the oldest available. Myself, I do a test restore if a few random files every now and then. I know it's probably impractical to do a test restore of everything you have on account of time and storage limitations. The offsite datacenter was just implemented when I left the company, so I dint know what the testing schedule there was.īetween this and the occasional need for a file restored for a user, we were confident in the backups. This restore was used to update and wipe clean their test and development environment, so it wasn't a completely regular schedule depending on that was going on at the time. ![]() Every six months to a year, we did a test restore of everything from local storage. Every month, we did a test restore of a few random files (both from recent recovery points and also older ones). Even with something like this, I would to test restores.Īs an example, a client I had in the past had Veeam backups locally, and a replication to an offsite datacenter. Some products (like Veeam) have a function where it boots up your virtual machine from the backup, tests that it functions, shuts it down, and emails you the report. ![]() Backups are not a "set it and forget it" product and of you treat it that way you run bigger risk of being burned. If any company or product ceases to exist or function when I need it, I have two others on which I can rely.Īs to ensuring reliability, the only reliable way to test backup integrity is to do test restores as often as you feel you need to. ![]() Thus, now I use Arq to my storage server locally, Backblaze for cloud storage, and a straight up regular file copy to a couple of offline drives. The product never failed me, but as you know the company sort of pulled the rug out from under me on that one. I used to just use CrashPlan for everything (personally) and trust it 100%. Tl dr: Do test restores, and use more than one backup methodology.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |