Hello,
I'm wondering how many people are running nightly differential SQL backups due to the shear size of their databases. We are at about 1/2 TB in size running CPS.
If so, is this working well for you?
Have you tried a disaster recovery from it?
Do you think GE will support you with this configuration?
Our primary concern is to reduce our backup times because they cut into our clinic open hours.
We are wondering about the nightly "Update Statistics" SQL job which GE has us running. This job takes a full 3 hours to run every night which cuts deeply into SQL performance when running.
I don't think GE supports anything other than a full backup.
I do have a secondary backup which I could use instead, using Appassure. That backup is less invasive and I can do it during business hours with the agentless option.
I would only take a chance with a SQL differential if I had another backup to fall back on. Due mainly to GE's support policy.
You could, however, adjust the backup time to occur earlier. Just make sure you change the other jobs as well so they don't run simultaneously. This would only help you if you aren't a 24/7 shop
Mike Zavolas
Tallahassee Neurological Clinic
We do volume snaps from our nimble storage to get hourly backups of the volume. Also the added flash performance helps out with how long it takes to export the files nightly.
We then use Nimble replication of the volumes to send our data off site for DR purposes.
We still do a full backup every night but also do a log backup every 5 minutes. We also have a script that automatically creates the sql restore script with each log backup so restores are easy.
I've encouraged GE to split their nightly job into its individual parts. Check DB, Backup and Update Stats. That would allow us to better time everything. I'd also like to see something a little less aggressive then a blanket 15% every day on the stats. For now though we stick with the GE Job with the addition of log backups. We just have fast enough storage the impact isn't that bad.
Using the built-in compression option for backups saves time and space.
I replaced the GE backup command with a command that use the Ola Hallengren backup scripts (free).
https://ola.hallengren.com/sql-server-backup.html
Storage snapshots are generally not a recommended backup strategy for databases. Does your nimble snapshot quiesce your database? If it is oracle then the answer is almost for sure, no.
I can't speak for GE support; however, differential backups are a 100% supported way to support your system. The suggestion to start the job earlier is a good one; however, you don't want to go outside of your maintenance window.
At your size, you may need to consider modifying the disk structure somewhat--faster disks would be nice, but ensuring your log file and data file are on different LUNS--not just drive letters, is a first step. Your backup should also be going to a different drive or network location.
Again, I can't speak from the GE support perspective, but you might try changing the update statistics portion of the plan to just run once a week. If you notice things getting sluggish, change it back.
Our database is 650GB. I do full backups on the 2nd and 4th Sundays, Differentials every night and 5 minute transaction log backups. I also have log shipping configured to our DR site.
I'm actually do a presentation at CHUG on this if you are interested.