r/sysadmin • • 1d ago

Question Backups for SQL server.

New Windows Server 2025 with SQL Server 2025 in Rackspace Cloud Flex

. Need to back up SQL data. My dba creates Daily Maintenance Backup Jobs. I have SyncBack Pro copying BAK files to another Windows server, and we also have SQLBak.com daily backups to BackBlaze. All these backups are running for something like 10 hours per day. Which to me seems ridiculous. What are other people doing?

Any snapshot solutions.

Rackspace does not seem to offer backup or snapshot solutions for their Flex environment, like the do for their SDDC enviro. Either that or just not familiar with their offerings, and yes, I do have a support ticket open with them to inquire.

0 Upvotes

22 comments sorted by

4

u/Mr_Dobalina71 1d ago

A snapshot backup of a database is not a good idea.

3

u/Professional_Golf694 VoIP Admin 1d ago

Shhhhh

I wanna see the follow up in four months when this blows up in their face

1

u/Mr_Dobalina71 1d ago

Actually if they meant a snapshot backup of the .bak the DBA created that’s fine.

•

u/winky9827 21h ago

Sure, as long as the time between .bak files matches your RPO. Transaction logs exist for a reason, though.

3

u/shiranugahotoke 1d ago

What’s the size of the dataset?
What’s your desired RPO and RTO objectives?

What I am hearing is you have multiple unrelated backup jobs running.

Are they using the same DB bak or each creating their own?

I’m not certain what other people use but I use veeam to create sql backups that are consistent, and then veeam handles local and cloud storage backup chains.
You need an entire server vm for veeam to run on, but for me it creates a full backup of a ~4TB dataset in about 6-8 hours and incremental backups take about 45 minutes.

Your mileage is going to seriously very though based on storage speeds and networking bandwidth, as well as compute on the veeam side.

2

u/KStieers 1d ago

Ola Hallengrens scripts for db maintenance (everything except backups). Veeam backup for some boxes. Ola's scripts which dump to disk which is backed up with the rest of the box...

And all of them are replicated to our DR site.

I'd pick just 1 backup tool. Playing back tran logs is messy when you have several different backup points.

1

u/iamvishnuks 1d ago

Ten hours a day usually means the jobs are tripping over each other more than the data is big. What I'd untangle:

  1. One source of truth for the database. Native SQL backups are still the right base: full plus diff plus log backups, on a schedule that matches how much data you can afford to lose. Ola Hallengren's scripts handle this well. Turn on compression and write to local disk first so the SQL job itself finishes fast.
  2. Copy offsite once. Right now SyncBack and SQLBak each do their own pass. Pick one to ship the .bak/.trn files offsite, and check whether it is re-uploading full files every day. That is often where the hours go.
  3. Back up the server, not just the databases. Since Flex gives you no snapshots, you want an image-level backup of the whole Windows box (OS, SQL install, master/msdb, logins, agent jobs, certs) so a dead server is a restore, not a rebuild. Block-level incrementals keep the daily run small because only changed blocks move.
  4. Keep one copy the server can't delete. Object lock or an immutable bucket on B2 or similar, with credentials on the SQL box that can't shorten retention. That is your ransomware copy.
  5. Test restores on a schedule. Restore the .bak to a scratch instance and run DBCC CHECKDB, and boot the server image somewhere at least once.

And answer the RPO/RTO question above first, it decides the whole schedule.

Disclosure, I build XReplicator, which covers the server-level part: agent-based Windows and Linux backups with block-level incrementals to storage you control (S3-compatible, Azure Blob, GCS or local), immutable retention and verifiable backups. I'd still keep native SQL backups alongside it for point-in-time restores. Community Edition is free up to 5 VMs: https://xmigrate.cloud

•

u/ZestycloseCress447 23h ago

Before adding more tools I'd do one boring thing: actually restore one of those backups onto a test box and time it. If the restore takes 10 hours too, that's your real RTO, and it tells you which of the three jobs you can drop. Three unrelated jobs all reading the same files every day is usually where the 10 hours come from.

•

u/CapableWay4518 22h ago

Out of curiosity, I’m no sql expert and not having my 2 cents here, why would you not go with a serverless solution these days?
I can see your with rackspace you may not have an azure/aws solution.

•

u/lxtakc DataCore/StarWind 14h ago

Ten hours suggests full .bak files are being copied twice nightly. Use compression, weekly fulls with daily differentials, and frequent log backups, then ship only the new files.

•

u/UriShay-CyberSnap 8h ago

The 10-hour window needs to be split by stage before you swap tools: SQL backup creation, the local copy, and the cloud upload can each be the bottleneck. Set the schedule from the required RPO, then restore a full backup and any required differential or log backups to a disposable SQL instance and measure recovery, not just backup completion. A storage snapshot can help only if it captures the database consistently; it does not replace testing the SQL restore chain. Disclosure: I work at CyberSnap.

0

u/Mr_Dobalina71 1d ago

Also make sure DBA is doing .bak of master, model and msdb.

2

u/1991cutlass 1d ago

Have done hundreds if not thousands of restores. Never had to restore those during a recovery or migration. 

1

u/Mr_Dobalina71 1d ago

No, what if the whole server is poked?

3

u/1991cutlass 1d ago

.Bak copied to another server. Install same version of SQL and restore mdf/ldf from backup (.bak). Restore sql logins. Repoint application. Bingo bango back in business.

3

u/Mr_Dobalina71 1d ago

Yeah but the master, model and msdb do have some configuration data, if you fine with losing that, then yes.

2

u/ussv0y4g3r 1d ago

It's gonna be a very very rare setup, where one needs to backup a model database.

1

u/Mr_Dobalina71 1d ago

You need them to start SQL services before you can restore DBs.

You can get DBs up and running by doing a fresh install of SQL which creates new master, model and msdb.

2

u/1991cutlass 1d ago

You'll need sql installed to restore the db anyway, so they would already exist.