VMware Cloud Community
ezimmerm
Enthusiast
Enthusiast
Jump to solution

VCB left a snapshot....afraid to delete it. Snapshot question for all you guru's.

I have about 15 or so machines being backed up via VCB.

I noted this morning that the backups had not been actually backing up data for about a week on half of the machines. I finally traced the problem back to a VM that has a snapshot that was left behind by VCB about a week ago.

It appears VCB didn't clean up properly after a backup and is now preventing the rest of the machines from finishing.

When I go into snapshot manager....it shows the following:

  1. -panther

  2. -VCB-Backup (Created Nov.15th)

  3. You are hear

What do I need to do so I do not loose any data. Since this hasn't been creating my backup I cannot afford to loose anything.

I did try searching the forum but since this happens to be a fairly important server (of course....) I need to be absolutely sure before I pull the trigger on anything.

I know that the snapshot contains a delta file of all changes since last week ...from what I can find I think I need to actually power down the machine and then click remove? That should write all changes permanently to disk and keep all the work that has been done for the last week?

Thanks for the help in advance!

EZ

Tags (4)
0 Kudos
1 Solution

Accepted Solutions
sbeaver
Leadership
Leadership
Jump to solution

I have seen this before and it is a funky error. The best bet is to shutdown and apply the snap so you do not loose any data

Steve Beaver

VMTN Forum Moderator

*Virtualization is a journey, not a project.*

Steve Beaver
VMware Communities User Moderator
VMware vExpert 2009 - 2020
VMware NSX vExpert - 2019 - 2020
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: [www.virtualizationpractice.com/blog|http://www.virtualizationpractice.com/blog/]
Come follow me on twitter http://www.twitter.com/sbeaver

**The Cloud is a journey, not a project.**

View solution in original post

0 Kudos
3 Replies
sbeaver
Leadership
Leadership
Jump to solution

I have seen this before and it is a funky error. The best bet is to shutdown and apply the snap so you do not loose any data

Steve Beaver

VMTN Forum Moderator

*Virtualization is a journey, not a project.*

Steve Beaver
VMware Communities User Moderator
VMware vExpert 2009 - 2020
VMware NSX vExpert - 2019 - 2020
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: [www.virtualizationpractice.com/blog|http://www.virtualizationpractice.com/blog/]
Come follow me on twitter http://www.twitter.com/sbeaver

**The Cloud is a journey, not a project.**
0 Kudos
uslacker99
Expert
Expert
Jump to solution

You can go ahead and delete the snapshot. It would be safe to do that.

ezimmerm
Enthusiast
Enthusiast
Jump to solution

Thanks for the help. I think last time this happen I must have hit revert rather then remove and deleted my data (ugghh).

I would think that VMware could come up with better terminology then Delete since that sounds...not so good.

Thanks again!

-Erik

0 Kudos