Aller au contenu principal

VMProtect 9 - Best Practices for Virtual Server Backup Tasks

Thread needs solution

Is it better to create individual backup tasks for each server or one task to backup all servers?

Separate tasks seems to make more sense. If one backup fails, the others may succeed. Also I can see that each server is being backed up, without editing the task.

What are the benefits of backing up all servers under one task?

If I create one task to backup the Esxi host, if a server is added will it backup the additional server without needing to re-create the task?

Does VMprotect create different TIB files for each server if all are under one task? Haven't looked at this yet?

Thanks,

Bill

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi William,

Please see my comments inline:

William Meyer wrote:
Is it better to create individual backup tasks for each server or one task to backup all servers?

Separate tasks seems to make more sense. If one backup fails, the others may succeed. Also I can see that each server is being backed up, without editing the task.

What are the benefits of backing up all servers under one task?

When you back up multiple machines within the same task - they are all put into the same archive and this enables deduplication between the machines. If you back up each machine into a separate archive (in separate tasks) then there is no deduplication performed and this is less efficient.

Note that when you back up multiple machines within one task then even if 1 machine fails in the middle - its backup will be re-tried in the end of the task (once the other machines are processed). You can check the corresponding option under Backup Options->Error Handling->Re-try failed VM processing.

William Meyer wrote:
If I create one task to backup the Esxi host, if a server is added will it backup the additional server without needing to re-create the task?

If you select a dynamic group of machines on the 1st step (entire Host, entire resource pool or vApp) then all new elements which appear in this group later will be backed up. There is no need to re-configure the backup task. NOTE however that when you select all VMs under group individually - it won't be considered as dynamic group (new VMs in this group won't be backed up automatically), therefore the right way is to select the dynamic group (resource pool/host/vApp) on left side and drag it entirely to right.

William Meyer wrote:
Does VMprotect create different TIB files for each server if all are under one task? Haven't looked at this yet?

All VMs are backed up into the same archive, which can be a single .tib file (default "Single file for all backups" archive type or so-called "always-incremental") or a set of .tib files ("Multiple files for backups" archive type).

William Meyer wrote:
Thanks,

Bill

Thank you.
--
Best regards,
Vasily
Acronis Virtualization Program Manager