v.Eremin wrote:Hi, Magnus,
Please, see explanations provided above about the reasons why backup of VM with independent virtual disks outputs warning, instead of error.
masonit wrote:And that Gostev laughs at this as it is no big deal... ...
Vitaliy S. wrote:Nothing has changed, but as a workaround for now, you can use a nicely formatted report to assess every VM configuration (not only for independent disks, but for pRDMs and other potential issues) that is available in the free version of Veeam ONE.
v.Eremin wrote:Information about vSphere infrastructure is retrieved by Veeam ONE directly from vSphere. Thanks.
masonit wrote:Does Veeam One retrieve this information from Veeam or from Vmware? Ok then Veeam One is not a good option for us.
Gostev wrote:Perhaps we can find some middle ground, for example the warning is only displayed when the VM is backed up for the very first time (first full backup). This way, the change will not affect any existing jobs.
My proposed solution will solve the dynamic container issue. Each time the new VM falls into the job's scope, we will warn ONCE (during the very first full backup) that it has some unsupported disk types. And you will never see this warning again for that particular VM, at least until it has a change in virtual disks configuration.
This also means you will not get any warnings on your existing jobs after upgrade, because all those VMs already have full backups created at least once
ramnefors wrote:As this is intended how do I get back the v7 behavior, i.e. no warning?
Users browsing this forum: No registered users and 1 guest