no LTR possibility in MIRROR COPY JOB, no SMART copy either
-
Hi,
I'm trying to get together homogeneous backup copies for client VMs that have backup copy option on our side.
First of all, there is no LTR options possible in MIRROR COPY jobs. the only way to have more points in the backup copy is to get a longer retention in mirror copy job schedule than the source job schedule.
Could we get LTR options also in mirror copy job ?Second point, mirror copy job is either all VMs from remote, or manually selected VMs, no possibility of "SMART" selection by tags.
I'd like to be able to TAG VMs with client_name/backupcopy_option to autoselect the concerned VMs
If you could get these demands in future dev, would be great
Thanks in advance.
-
and I noticed a "bug?" with mirror copy job ?
Even if I only manually select one VM out of the 7 that are on the remote, they are "checked" by the job, but excluded by the job filter
on the remote, all 7 VMs folders are created, but only the copied VM contains data
the copy is OK for the selected VM, but why check and create the other VMs/folders ?
-
Question for @Bastien-Nollet or @florent
-
Hi @Pilow,
We plan to make LTR available also for mirror backups and metadata backups in the future, but we didn't have the time to do it yet.
Smart mode on mirror incremental backups would be a bit tricky to do, as it would require us to handle incomplete chains of backups, for cases when a tag is removed from a VM and then added back. We might still implement it in the future, though.
About the bug you noticed about VMs showing in backup log despite being excluded, I think it was intentional at some point, but now it would make sense to remove it. Thanks for the feedback, we'll change this.
-
@Bastien-Nollet I'm not a big fan of the way it is implemented right now : when you make a mirror copy, it first duplicate all the points then prune to the desired retention
but if you keep this way of handling mirror copies, it has the advantage of not needing to handle incomplete chains ?
