SQL Backup.

[1dna]

Hello,

we have around 11 sql (MS) cluster and still growing,

Currently design i so-fort:

1) Dump Databases to backup server
2) Backup job picks daily op.
3) Copy job: Pick up backup and put it offsite
4) Tapejob puts it monthly out on a tape
5) S3-Immutable incoming soon (not relevant here)

We have 3 Large hp Servers, for storing the backups temp, (Datasize is around - 300TB rough estimates - not hyper active bases but a massive unstrucuture size)

This design has grown hopeless to secure in a proper manor - so im hoping there is someone in here who might want to share their design.

Typically we need to save data 90 day, 12 month and some years - so im trying to consider what my options is in veeam to make this design a bit more robust in the future

Question: Would Veeam SQL plugin be my saviour?
Question: How to handle large Dataset in archive sense? to put it offsite/tape?

Lowest amount of jobs possible

[PetrM]

Hi Lars,

300 TB, not bad!

Would Veeam SQL plugin be my saviour?

Maybe it will be.

The plug-in for Microsoft SQL Server has no built-in GFS mechanism (as you mentioned above "90 days, 12 months, and some years"), and backup to tape is currently not supported. However, both of these requests are likely the most important ones on our roadmap, nevertheless, I cannot share any timelines.

For GFS retention, I can propose two workarounds:
1. Change the plug-in configuration on a schedule to create GFS full backups. There are two options: change the repository or change the customerServerName parameter in the veeam_config.xml. Please let me know if this would work for you, and I can share the instructions.
2. Run image-level backups in Copy-only mode to avoid breaking the backup chain maintained by the plug-in.

How to handle large Dataset in archive sense? to put it offsite/tape?

What about a backup copy job to a remote site?

Thanks!