IT Administrators and MSPs will often backup systems using their software package of choice. But what happens when they overlook the SQL Backup toolset built into Microsoft SQL? They are missing out on the additional protection that can offer in a highly critical database. It is always best to not have all of your eggs in one backup methodology. This backup should also be stored on separate hardware so that neither a hardware nor software issue could impact your second backup option.
IT Administrators and MSPs will often backup systems using their software package of choice. But what happens when they overlook the SQL Backup toolset built into Microsoft SQL? IT Administrators may not have setup SQL backup jobs during a new software install but in most cases the software vendor is expecting IT Department to manage that job moving forward. When the vendor comes calling for a database to be restored or recovered they will place the blame straight onto the IT department if their database cannot be recovered. The software vendor probably even outlines that backups are a responsibility of the IT department once the software is installed in their contract with the customer. Take the time to make sure you manage not only your own backups but the vendor expected SQL backups to ensure you are always protecting a client or companies data.
SQL 2005 and above has a very consistent setup of emailing out the reports. This is really useful to make it easy for an administrator to check their SQL backups via email.
If you want to centralize your backups and monitor all from one source check out wwwbackupradar.com. We’ve also created a document that outlines the entire setup process at the link below: