Cant remove old checkpoints that have already been merged. They still show up in Hyper-V manager

BlackJack11
BlackJack11 used Ask the Experts™
on
Hello

I have a exchange 2013 server as a VM in Hyper-V, Server 2012R2, that I had a issue with several months ago. My Backup Exec 16 -the full version was backing it up and by default it creates a checkpoint to speedup the backup (this can be disabled and I have now). The issue was several more checkpoints 4 of them were created possibly by backup errors and I started to loose drive space. Well I worked with Microsoft to roll all the checkpoints in the right order in to one .VHDX and all I have is one file now with no checkpoints which is how I want it. I don't like using checkpoints for obvious reasons, better to have a good backup or an export than create a differencing disk.

My issue is that in hyper-v manager 2 of the old checkpoints are still listed and I cant get rid of them See pics.

This is causing a Issue with backup exec were I cant do a virtual based backup because Backup exec thinks the exchange VHDK is corrupted.
I can do a agent backup but this is not the best way to backup exchange.

I still have the old checkpoints saved, but like I said they have been already rolled in so I don't want to put them back where hyper-v can find them, and have the delete checkpoint roll them in again. Seems like that would cause a problem.

Its almost like I have some old configuration data some were in Hyper-V

Any ideas on how to get rid of these old checkpoints?

Old checkpoints
cant delete
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Alex AppletonBusiness Technology Analyst

Commented:
Best way to do it is to create a new checkpoint, then export the checkpoint to a location.  Once exported you can re-import the VM as a new VM.  Its a bit of work to do, but your VM config is corrupted so this is the only way that I have found work for this.

Author

Commented:
Thanks Alex for you input

Can you tell me why I should create a new checkpoint? Since that will be linked to the existing parent .VHDX file.

Why not just stop the VM export it. Delete the server from the Hyper-V manager and create a new VM with all the same parameters and then attach the exported disk.

Or how about create a 2nd VM with a different name, no drive, then stop the first VM detach the drive and then attach the exchange drive to the new VM. does that make any sense? Any downside you can see?

Thanks
Business Technology Analyst
Commented:
You would have to import the VM Configuration files, otherwise the guest OS is going to think there was a major hardware change and you would have to reconfigure network adapters and possibly re-activate the OS.  When you import the VM there's none of that to worry about.

I like exporting the checkpoint to ensure I have a good application-consistent copy of the VM.  You could technically shut it down and export the VM as an alternative as well.

Author

Commented:
I know what you mean I have had to migrate VMs from 2008 to 2008r2 to 2012r2  in that order by just copying the drives and attaching them to new VMs its a process but it works.

the real problem with exchange is if the config changes the virtual nics change and all the exchange services wort start and the server takes like 45min to boot to a logon.

Thanks for your input.

I might just start by  copying  the drive to a test server. And see if it works well as a new VM

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial