mysterious .avhd's

we not use hyper-v snapshots in our environment reason have couple of disks have .avhd's. blib under disk information in settings tab says there snapshot there no snapshots in snapshot section. these servers setup , not touched other monthly updates , daily backups. thing can think of perhaps maybe there issue host based backup option backup exec? have 1 server being backed via cluster backing .vhd 1 not seem issue. others backed through agent installed on vm itself. 

the main thing looking correct way merge these drives. additional vhd's attached vm data. tonight going try merge user directory folder redirected documents company sized 400gigs. when want merge pull hyper-v manager, edit disk , browse newest avhd , hit merge? need shut down our file/print server in order since not c drive? need disconnect drive before , if alter configuration , cause merge fail?

sorry questions, new hyper-v , none of covered in class since snapshots without being listed in manager not supposed happen believe.

through forums on time have seen multiple cases of folks taking snapshots , deleting them.

thus resulting in mysterious avhd files.

avhd extension specific msft hyper-v snapshot.  no other applications or backup products make them.

regardless of policy - has happened other folks in forum.  (historically popular reason integrator didn't merge snapshot properly).

in cases, safest way merge snapshot files - 1) delete snapshot in hyper-v manager (sounds done in case) 2) power off vm 3) wait avhd merged. 4) power on vm.

you can see status of merge processes in far right of middle pane of hyper-v manager.  , errors in event logs under applications , services, microsoft, hyper-v-*

---

brian ehlert
http://itproctology.blogspot.com
learn. apply. repeat.
disclaimer: attempting change of own free will.

Windows Server  >  Hyper-V