Version 3 Error - "object that no longer exists"

[jbc]

Just upgraded (per the instructions in the release notes).

Trying to run old (from v2) jobs, or creating a new job, I'm getting continual failures with the message:

"Initializing source
The request refers to an object that no longer exists or has never existed."

Any thoughts? I am not opposed to doing a fresh install (as opposed to an upgrade), since I have to mod each job anyways.

Thanks,
Jason

[Gostev]

Hello Jason - have not heard about similar issues so far, so unfortunately I cannot give you a quick answer here. Of course, fresh install will be fastest way to address this, since it is likely some kind of upgrade problem. Alternatively you could send us all logs and so we can figure out exactly what's going on - this will just take a bit longer.

[cmillsgd]

We have just upgraded to 3.1 from 2.0 and encountered the same problem. We did a clean install and other VM's in the same job are being backed up successfully.

The problem has not been solved by creating a new job specifically for the problem VM. We have also cloned the VM and run it on a different host and the problem is still present.

Thanks for any help.

[Gostev]

Courtney, have you tried to do this ?

[cmillsgd]

Thanks, that has enabled me to run one-off backups for the VM's that were causing problems.

The 2 licences have are now allocated to 2 ESX servers. I did notice before I revoked the licences that one was allocated to an ESX host and the other to the vCenter server. Is the change I've made likely to affect the original backup? Do I need to recreate the jobs from scratch?

Thanks

[Gostev]

Courtney, no you do not need to re-create anything. It will not affect the original backup.

[cmillsgd]

Revoking the licences worked for an adhoc backup of a single VM last night. But the normal scheduled backup tonight for 3 VM's failed with the same error - "Initializing source The request refers to an object that no longer exists or has never existed."

Creating a new job for multiple or single VM's also fails.

[Gostev]

Strange... please work with our support to troubleshoot.

[cmillsgd]

This issue has been resolved by ensuring VM's are selected for backup from the vCenter node rather than that of an ESX host.

[Ben Milligan]

Big thanks for posting the confirmation of the resolution Courtney!