Do you know the status of your backups?

Even backups through Veeam or VMWare may not give you the protection you are expecting when you need to restore your data.

SQL Server backups require special handling.

One of our customers thought they had backups in hand, until they had a ransomware attack. We have been approached by WAY too many customers looking for help with insufficient backups. Each database consists of at least two files and a backup of only file one leaves you vulnerable to data loss. Traditional backup options may not be configured to help you recover all your data nor restore quickly.

Get the most recent backup history from your database with our free report. It will help you verify your backups are setup correctly or identify if changes are needed. If you can access SQL Server Management Studio, you can run the report.


Get our free Database Backup Report

Instructions

  1. Click Get The Report below and download the file.
  2. Unzip the file to preferred location.
  3. Open SQL Server Management Services (SSMS) and connect to SQL Server.
  4. Right click on the instance.
  5. Choose Reports > Custom Reports.
  6. Navigate to where the file was downloaded and select.
  7. Click Run on message.
  8. Review your report.

Are you seeing red?

Don’t get angry…let us help.

Common Backup Issues

  • Backups are on the same server as the database. If the disks on the database backup go down, so do your backups.
  • Databases are in simple recovery mode, but should be in full recover mode. Most backups are taken once per day. Do you need to keep the data in between backups? If so, you probably need to change your recovery model and implement log backups.

Are your backups not where they need to be? Do you need help?

  • Purchase a service below
  • Meet with us and discuss your RPO
  • When your backup location is ready, we’ll create the backups for you
  • You can then use the free report to check on them as frequently as you would like

We leverage community proven scripts to help ensure your backups are there when you need them. You can even be notified if there is an issue with a backup.

Does the recovery model matter?

The recovery model matters if your data changes and you need to restore those changes. The term is Recovery Point Objective (RPO) and it describes what is going to be in the restored data. If you can only lose 15 minutes of data, your RPO is 15 minutes. Test systems might have an RPO of one week. There are a variety of different reasons which influence your RPO; however, the frequency and type of backup is influenced by your RPO. This is why recovery model matters.

One-Time Setup Help

$399

  • - Discussion on your recovery needs
  • - Implement the backup process
  • - Verify backups function properly
  • - Provide training
Get Started
On-going Backup Support

$150 /month

  • - Monthly Service
  • - SQL Server backups available locally and offsite
  • - Stored in Azure blob storage
  • - Very Secure
  • - Ongoing monitoring of the backup process
  • - Your team can request a backup at any time
Get Started

Frequently Asked Questions

  • Why does my backup location look like a code?

    This normally means you are writing to tape or a network location using third party software. You will need to verify with your software the location of your backups.

  • I use Veeam or VMWare for backups. Isn't that enough?

    If it is set up correctly, these types of backups can be sufficient; however, we normally see they are not correctly configured and leave you vulnerable. We recommend taking SQL Server backups AND Veeam/VMWare backups to eliminate the chance of issues when you need to restore.

  • Why use SQL Server backups?

    As long as you have a backup file, the database can be restored–sure there are rare exceptions to this; however, a backup file reduces the reliance on other software to restore data.

  • My Differential backup is from the past.

    There are many different backup options and we don’t consider differential backups mandatory, so we only suggest you review your plan if the differential backup is more than 30 days old.

Fix your backups.

Get out of the red.


The real cost of data loss

Like insurance, backups are a cost we spend hoping we won’t have to use it. Luckily backups are not all or nothing, but they aren’t free.

Neither is data loss
Verizon’s annual data breach investigation report indicates the cost to business for ‘small’ amounts of data loss average $25,000 per incident.  Calculating data loss varies from organization to organization, but when data is unavailable–especially unplanned unavailability, two general areas to consider include lost productivity and lost sales. Think about what downtime will cost you and it doesn’t take long to recognize you lose more than data when your data is unavailable.
Ransomware attacks cause an average of 16.2 days of downtime
96% of business experienced an outage in a 3-year period
“The true cost of the data breach was much higher than what we projected.”
Data breaches are becoming more common; however, data loss can occur by hardware failure, theft, lost, negligence, malware and even accidently destroyed.
Businesses can significantly mitigate the impact and cost of data loss with a data backup solution. As a enterprise level tool, SQL Server requires special attention.
One-Time Setup Help

$399

  • - Discussion on your recovery needs
  • - Implement the backup process
  • - Verify backups function properly
  • - Provide training
Get Started
On-going Backup Support

$150 /month

  • - Monthly Service
  • - SQL Server backups available locally and offsite
  • - Stored in Azure blob storage
  • - Very Secure
  • - Ongoing monitoring of the backup process
  • - Your team can request a backup at any time
Get Started
I feel much more comfortable knowing SQL Data Partners helped set up my backups correctly.
Kyu Cho - Printing Center USA
I can finally have a use case for cloud services–Backups!
Jim O'Shea - Maracle

Found a bug or issue with our report? Let us know.

Listen to our SQL Server maintenance episodes.

Our SQL podcast keeps you easily informed and entertained.

Episode 252: The Cumulative Update Dilemma

 Episode 252: The Cumulative Update Dilemma 720 540 Carlos L Chacon

Episode 236: Database Monitoring with SQL Sentry

 Episode 236: Database Monitoring with SQL Sentry 560 420 Carlos L Chacon

RPO and RTO

 RPO and RTO 560 420 Carlos L Chacon

Episode 230: Recovery Time Objective & Recovery Point Objective

 Episode 230: Recovery Time Objective & Recovery Point Objective 560 420 Carlos L Chacon
Episode 172: Power BI Monitoring

Episode 172: Power BI Monitoring

 Episode 172: Power BI Monitoring 560 420 Carlos L Chacon
Episode 163: Very Large Databases

Episode 163: Very Large Databases

 Episode 163: Very Large Databases 560 420 Carlos L Chacon
Episode 133: Shrinking Files

Episode 133: Shrinking Files

 Episode 133: Shrinking Files 560 420 Carlos L Chacon
Episode 112: Keeping up with patching

Episode 112: Keeping up with patching

 Episode 112: Keeping up with patching 560 420 Carlos L Chacon
Episode 102: Monitoring Availability Groups

Episode 102: Monitoring Availability Groups

 Episode 102: Monitoring Availability Groups 560 420 Carlos L Chacon
Episode 90: DBCC CheckDB

Episode 90: DBCC CheckDB

 Episode 90: DBCC CheckDB 560 420 Carlos L Chacon
Episode 04: Advanced Backup Techniques with Tim Radney

Episode 04: Advanced Backup Techniques with Tim Radney

 Episode 04: Advanced Backup Techniques with Tim Radney 560 420 Carlos L Chacon
Episode 03: Backup and Recovery

Episode 03: Backup and Recovery

 Episode 03: Backup and Recovery 560 420 Carlos L Chacon

Backup History

 Backup History 560 420 Carlos L Chacon

The Importance of Backups

 The Importance of Backups 560 420 Carlos L Chacon
Back to top