Hi Lars,
300 TB, not bad!
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.
Thanks!
300 TB, not bad!
Maybe it will be.Would Veeam SQL plugin be my saviour?
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.
What about a backup copy job to a remote site?How to handle large Dataset in archive sense? to put it offsite/tape?
Thanks!
Statistics: Posted by PetrM — Feb 04, 2025 11:25 pm




