chris_gardner
Contributor
Contributor

VCB doesn't like existing snapshots?

Initially (right or wrong) I thought it'd be a good idea to snap machines before handing them off to users. I'd create an "Initial Build" snap. The snap would stay there forever. I'm also using VCB to back up on a file level.

I've noticed that VCB consistently fails more often on the machines with snaps than ones without. It'll do the VCB snap then fail to mount. No "renew disk" message in VC, no error messages in Event Viewer -- it'll just sit there forever and then time out.

As a test, I removed the "Initial Build" snap on a machine (I had a backup) and did a file-level VCB. Works fine.

Maybe I'm violating best practices by leaving snaps on the machine. But aside from this, does VCB just not like when you have snaps on the box? Does it have to reconstruct the changes between the current snap and the initial (I'm a relative VMware neophyte so I'm still learning how this works). Should the recommendations be "don't leave snaps on the machine if you intend to use VCB"?

0 Kudos
2 Replies
jonathanp
Expert
Expert

VCB does not support existing snapshot...

you can create a template after first install instead of a snapshot..

Jon

0 Kudos
chris_gardner
Contributor
Contributor

VCB does not support existing snapshot...

Interesting. Is that in the documentation anywhere?

0 Kudos