One-server-only System & configuration backup copies

[Poweruser]

#MOD: Split from original discussion (File Copy to Backup Server not available anymore)

Please consider a one-server-only System instead of a complex setting.
Veeam forget´s these use-cases often :-(

[Mildur]

Hi Poweruser,

Is your comment related to Bostjan’s question? If not, please clarify your request and I’ll move your comment to a dedicated (or similar) topic.

Also, maybe I’m misunderstanding, but how would a “single-server-only” setup benefit from a File Copy job if there’s no other system to copy the configuration backup to? Since this topic is about the missing “File Copy to Backup Server”.

Best,
Fabian

[Poweruser]

Yes, and no. In general both applies.
This is just one use-case of the general use-case one-host-only.

A single server device with a single tape drive - let it be called VirtualMachineHost (Including VBR).
This device holds n Hyper-V instances.

This is the SMB use-case which is very important and classical.
veeam does not care about and adds more and more hard locks which are unnecessary or over-engineered.

[Mildur]

Hi Poweruser,

I’m still having trouble understanding how the other topic relates to your comment, which is why I split your posts into a new topic. We don’t want to derail the original discussion with unrelated feedback.

The other topic was about two machines: one backup server and one offsite repository server, and File Copy jobs that no longer work with the backup server as the source. This can be solved by changing the workflow direction—copy from the backup server to the offsite repository.

Can you please elaborate why File Copy jobs on a “single-server-only” backup system are useful for your use case? If the server dies, you will lose all configuration backups, no matter how many copies you have on local disks.

Or is your request to have a copy on tape? That can be done with File to Tape jobs.

If your request is a “backup copy” of configuration backups to an SMB share, then I can add a note to the existing feature request topic and discuss it again in one of our next PM meetings.

Best,
Fabian

[Poweruser]

First: Tape is used
Second: Multiple HDDs are used, so a HDD crash of the VMs may be recovered through the other HDD.
Third: If something inside the VM was changed or deleted, it can be pushed back quickly from local backup.

Tape is slow and maybe unrealiable, but off-site. so it is just an last-resort emergency option.
Normally HDDs fail, and not whole devices including all HDDs, so in most cases this is very quick.

My proposal was, that Veeam should respect the use-case one-backup-server including repo, Hyper-V Host, VMs, Tapedrive, and everything else.
It should be considered as the normal smallest SMB use-case so development should obey not to lose this setting someday more and more by softlocks.