Mike Resseler wrote:
But I would like to know what your business case is for sending the log files over with a backup copy job. In most of designs, the first backup is the short term one (e.g. 7 days) and in that case log files are important. But the BCJ to a secondary repository or location is mostly for some longer period and therefore I have enough with the daily SQL backup.
How do you see this? (I always like to hear business reasons, requirements etc... for other designs...
Sure. We actually keep the same retention in all of our sites (28 daily backup jobs) then we have backup copy jobs running the same retention offsite (28 daily) ie SiteA > SiteB, SiteA > Site C, SiteB > SiteA, SiteC > SiteA.
We could use something like SAN replication but that would increase our storage costs and also open up the failure domain, we are quite happy with the way the backup copy jobs work it's just that it would be nice to get the VLBs included in the copy jobs. We don't offer log backup via Veeam to our IaaS clients currently due to the fact we would need to copy the entire Backup Job Chain offsite to meet our onsite/offsite requirements.