[BETA] [HPE] Restored VM's service plan

[dcolpitts]

Just curious why when I restore a full VM, a new custom service plan named "veeam-custom-service-plan" is created, when the original VM was using the original pre-defined "2 CPU, 8GB Memory" service plan, and how this will affected VMs if I were restoring one that has "2 CPU, 8GB" and then one that has "4 CPU, 16GB Memory", or if I were restoring both at the same time?

dcc

[PTide]

Hi,

Great question! @cody.ault might know something about that.

Thanks!

[cody.ault]

Hey,

I'll check into the naming and why we're creating a new service plan but we will set the VM back with the original settings (CPU/Memory), even if there are more than one VM restored. If you notice that's not what's happening, please let us know while I check on the behavior.

[cody.ault]

So, regarding the Veeam-custom-service-plan: This is used when you restore to a new location. Each service plan has a numerical ID and they don't always match across VME environments so there's a possibility that the ID for "2 CPU, 8GB" in one environment could have a different ID in another environment. Restore to original location will pick the same ID as before, whereas restore to new location just creates a new service plan and specifies the parameters to match the restored machine.

[dcolpitts]

Ok - let me test a restore in a few. A "2CPU, 8GB" VM, then a "4CPU, 16GB" VM and we'll confirm they don't screw each other up.