This is not in any way critique or something similar, just the point-of-view from "the other side" of the fence regarding the feature to always save the last backup of a server.
I come from a background working with legacy backup solutions for almost 10 years (CA ArcServe, HP DataProtector, Veritas/Symantec BackupExec, Legato Networker) when I started with Veeam in 2011-2012, using version 6. For me, keeping that last backup was a nuisance and against how I saw backups. If one removes a server from all backup jobs, that to me meant it was a dead system and nothing should be kept once retention had expired. The backup self-cleaned and purged no longer needed data. Yes, there were instances when a system needed to be saved outside of backups, but that was an archive task, not a backup. So special considerations was taken for that system. This applies even more in a virtual environment, where VMs comes and goes at much higher rates than physical servers ever did.
Three scenarios one might consider the differences between and how to deal with: backup, archive, and disaster recovery. Each one has its own requirements, many shared, but also many unique.
Again, in no way saying what is right or wrong, just food for thought.![:wink:]( "Wink")
I come from a background working with legacy backup solutions for almost 10 years (CA ArcServe, HP DataProtector, Veritas/Symantec BackupExec, Legato Networker) when I started with Veeam in 2011-2012, using version 6. For me, keeping that last backup was a nuisance and against how I saw backups. If one removes a server from all backup jobs, that to me meant it was a dead system and nothing should be kept once retention had expired. The backup self-cleaned and purged no longer needed data. Yes, there were instances when a system needed to be saved outside of backups, but that was an archive task, not a backup. So special considerations was taken for that system. This applies even more in a virtual environment, where VMs comes and goes at much higher rates than physical servers ever did.
Three scenarios one might consider the differences between and how to deal with: backup, archive, and disaster recovery. Each one has its own requirements, many shared, but also many unique.
Again, in no way saying what is right or wrong, just food for thought.
Statistics: Posted by Matts N — Jun 30, 2025 9:25 am
