Feature request: Preserve Guest Processing settings during a VM move to another Backup Job

[iDeNt_5]

Good morning,

I'm not sure if it was never requested before, but I'd like to ask if is it possible to preserve the Guest Processing settings during a VM move to another Backup Job, since this is set to default upon each VM move, unless a per-tag or per-folder selection is already specified.

Thanks.

[david.domask]

Hi iDeNt_5,

Request is understood; currently it's by design, the Guest Processing settings are part of the original job, not the VM, but we can certainly consider the request as it makes sense.

Can I ask, is this a frequent process for you or the situation is more of a "one-off" that resulted in a surprise when the guest processing settings weren't copied as well? If it's frequent, what's the use case for the frequent moving between jobs?

[iDeNt_5]

Hi David,

I was already aware of this behavior, but since currently I'm migrating more than 60VMs (most of them one per time) to a new BJ that points to another BCK Repo, I have to remember at the end of each BCK chain move to put an hand on the Guest Processing section of the target BJ.

Since it's possible that this feature will be used again in the future with this customer environment, I consider my request relevant just to avoiding to remember every time to change that manually.

Thanks.