You have to get it out of the data center you’re in. In the case of a storage system or backup server failure, and especially a natural disaster like a fire or flood, having your files backed up won’t mean anything if they’re onsite, they’ll just be lost as well. If you’re looking for protection, you want to go offsite. It’s a strategy to employ for rapid recovery of large datasets when working on a project. Nick explained that onsite backup isn’t as much for retention or protection. ETL is a heavy piece of work, and if something goes wrong, I don’t want to have to spend a lot of time starting over.” For example, if my ETL process fails during the Load stage, I want to recover my database quickly to the point in the process just prior to the Load. Organizations supporting databases with a high data change rate will often employ an onsite backup strategy for quick recovery in the event of a failure. “Onsite backup is generally part of a two-fold strategy used to ensure rapid access to point in time data that takes longer to retrieve offsite. So, when is it good to stay onsite? Nick explains: I spoke with our Director of Infrastructure Nick Lumsden about the reasons why someone may want onsite versus offsite backup, and vice versa, to try clarifying the muddy waters of backup and recovery. Trying to parse through which one fits best into your disaster recovery plan can be very difficult, and often for a result that isn’t ideal. There are many backup and recovery options out there some onsite, some offsite.

Offsite personal backup