Hello all,
I went in Snapshot manager and deleted the snapshot in hopes of merging the files back into one as it states it should. However the operation appears to have failed saying it could not delete the file and not there are no snapshots in the GUI. However when I go into the VMDK folder I do still see the incremental snapshots of the disk. (-s001, -s002)
I cannot simply delete these as I would lose the data so is there a way now to manually merge these files together so as to not lose my data. I have turned off AutoProtect snapshots and the VM still appears to be creating them as well.
The is workstation Pro 14 running under windows 10 pro.
I really only wanted a snapshot of the system drive and not all the data drives so chalk that up to learning but I need to get my data drives back into on simple VMDK. Also note that these data disks are using physical disks the entire disk. So like my N, R and P drive
anyone know how to merge these files back and then actually stop snapshots. I have unchecked the box for automatic snapshots and the GUI shows AutoProtect is disabled now.
thank you
Problem solved.
Reason for the problem: a bug in WS 14 that allows Autoprotect on VMs with physical disks.
This is a very stupid and dangerous bug that should be fixed as soon as possible.
Files named name-s001.vmdk and name-s002.vmdk are not snapshots - they are parts of a split growing vmdk.
The file name.vmdk describes the path to all the associated slices.
Please provide a list of all the files in the directory.
I will provide the list at the end of this post. However it doesn't make sense that the file that is growing is the physical drive and it is taking up space on my C drive. see the list below as the physical drive 6 near the end of this list that is the file that is getting huge.
Volume in drive C is C_Win_VMware_Workstation
Volume Serial Number is AA62-C062
Directory of C:\Users\pappa\Documents\Virtual Machines\MRD
05/02/2018 07:00 AM <DIR> .
05/02/2018 07:00 AM <DIR> ..
05/01/2018 01:15 PM 4,294,967,296 564d434c-71d0-c6ad-5275-6534ca11644b.vmem
05/01/2018 01:15 PM <DIR> 564d434c-71d0-c6ad-5275-6534ca11644b.vmem.lck
11/08/2017 02:44 PM <DIR> caches
05/02/2018 07:00 AM 0 list.txt
05/01/2018 01:06 PM 1,667,956,736 MRD-000001-s001.vmdk
05/01/2018 01:06 PM 2,094,858,240 MRD-000001-s002.vmdk
05/01/2018 01:06 PM 4,009,689,088 MRD-000001-s003.vmdk
05/01/2018 01:06 PM 3,852,075,008 MRD-000001-s004.vmdk
05/01/2018 01:06 PM 1,891,237,888 MRD-000001-s005.vmdk
05/01/2018 01:06 PM 15,073,280 MRD-000001-s006.vmdk
05/01/2018 01:06 PM 23,527,424 MRD-000001-s007.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s008.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s009.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s010.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s011.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s012.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s013.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s014.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s015.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s016.vmdk
05/01/2018 01:06 PM 13,893,632 MRD-000001-s017.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s018.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s019.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s020.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s021.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s022.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s023.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s024.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s025.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s026.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s027.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s028.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s029.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s030.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s031.vmdk
04/30/2018 03:41 PM 1,245,184 MRD-000001-s032.vmdk
05/01/2018 01:16 PM 2,268 MRD-000001.vmdk
05/01/2018 01:15 PM <DIR> MRD-000001.vmdk.lck
04/30/2018 03:41 PM 1,078,853,632 MRD-000002-s001.vmdk
04/30/2018 03:41 PM 533,987,328 MRD-000002-s002.vmdk
04/30/2018 03:41 PM 1,909,850,112 MRD-000002-s003.vmdk
04/30/2018 03:41 PM 5,522,849,792 MRD-000002-s004.vmdk
04/30/2018 03:41 PM 2,734,489,600 MRD-000002-s005.vmdk
04/30/2018 03:41 PM 514,981,888 MRD-000002-s006.vmdk
04/30/2018 03:41 PM 47,644,672 MRD-000002-s007.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s008.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s009.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s010.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s011.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s012.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s013.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s014.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s015.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s016.vmdk
04/30/2018 03:41 PM 34,668,544 MRD-000002-s017.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s018.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s019.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s020.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s021.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s022.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s023.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s024.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s025.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s026.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s027.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s028.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s029.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s030.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s031.vmdk
04/28/2018 07:29 PM 1,245,184 MRD-000002-s032.vmdk
04/29/2018 04:16 PM 2,268 MRD-000002.vmdk
05/01/2018 01:15 PM <DIR> MRD-000002.vmdk.lck
04/28/2018 08:37 PM 1,412,038,656 MRD-000003-s001.vmdk
04/28/2018 08:37 PM 766,836,736 MRD-000003-s002.vmdk
04/28/2018 08:37 PM 4,329,701,376 MRD-000003-s003.vmdk
04/28/2018 08:37 PM 3,556,638,720 MRD-000003-s004.vmdk
04/28/2018 08:37 PM 2,225,864,704 MRD-000003-s005.vmdk
04/28/2018 08:37 PM 51,642,368 MRD-000003-s006.vmdk
04/28/2018 08:29 PM 70,516,736 MRD-000003-s007.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s008.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s009.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s010.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s011.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s012.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s013.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s014.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s015.vmdk
04/25/2018 07:26 PM 40,304,640 MRD-000003-s016.vmdk
04/28/2018 08:37 PM 1,139,802,112 MRD-000003-s017.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s018.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s019.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s020.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s021.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s022.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s023.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s024.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s025.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s026.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s027.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s028.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s029.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s030.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s031.vmdk
04/24/2018 07:13 PM 1,245,184 MRD-000003-s032.vmdk
04/28/2018 08:37 PM 2,261 MRD-000003.vmdk
05/01/2018 01:15 PM <DIR> MRD-000003.vmdk.lck
02/04/2018 04:44 PM 4,294,967,296 MRD-9f6e48f4.vmem
02/04/2018 10:00 PM <DIR> MRD-9f6e48f4.vmem.lck
04/24/2018 07:18 PM 10,067,574,784 MRD-s001.vmdk
04/24/2018 07:19 PM 9,869,262,848 MRD-s002.vmdk
04/24/2018 07:22 PM 10,067,574,784 MRD-s003.vmdk
04/24/2018 07:25 PM 10,067,574,784 MRD-s004.vmdk
04/24/2018 07:28 PM 10,067,574,784 MRD-s005.vmdk
04/24/2018 07:29 PM 6,700,990,464 MRD-s006.vmdk
04/24/2018 07:29 PM 8,785,821,696 MRD-s007.vmdk
04/05/2018 08:46 AM 10,067,574,784 MRD-s008.vmdk
04/05/2018 08:46 AM 10,067,574,784 MRD-s009.vmdk
04/05/2018 08:46 AM 10,067,574,784 MRD-s010.vmdk
04/05/2018 08:46 AM 10,067,574,784 MRD-s011.vmdk
04/05/2018 08:46 AM 10,067,574,784 MRD-s012.vmdk
04/05/2018 08:46 AM 10,067,574,784 MRD-s013.vmdk
04/05/2018 08:46 AM 10,067,574,784 MRD-s014.vmdk
04/05/2018 08:46 AM 10,067,574,784 MRD-s015.vmdk
04/05/2018 08:46 AM 1,407,451,136 MRD-s016.vmdk
04/24/2018 07:32 PM 9,771,352,064 MRD-s017.vmdk
04/05/2018 08:46 AM 10,067,574,784 MRD-s018.vmdk
04/05/2018 08:46 AM 10,067,574,784 MRD-s019.vmdk
04/05/2018 08:46 AM 10,067,574,784 MRD-s020.vmdk
04/05/2018 08:46 AM 10,067,574,784 MRD-s021.vmdk
04/05/2018 08:46 AM 10,067,574,784 MRD-s022.vmdk
04/05/2018 08:46 AM 10,067,574,784 MRD-s023.vmdk
04/05/2018 08:46 AM 2,350,514,176 MRD-s024.vmdk
11/07/2017 04:30 PM 1,245,184 MRD-s025.vmdk
11/07/2017 04:30 PM 1,245,184 MRD-s026.vmdk
11/07/2017 04:30 PM 1,245,184 MRD-s027.vmdk
11/07/2017 04:30 PM 1,245,184 MRD-s028.vmdk
11/07/2017 04:30 PM 1,245,184 MRD-s029.vmdk
11/07/2017 04:30 PM 1,245,184 MRD-s030.vmdk
11/07/2017 04:30 PM 1,245,184 MRD-s031.vmdk
11/08/2017 02:09 PM 1,376,256 MRD-s032.vmdk
04/30/2018 03:44 PM 4,294,967,296 MRD-Snapshot11.vmem
04/30/2018 03:44 PM 4,022,112 MRD-Snapshot11.vmsn
05/01/2018 01:06 PM 270,840 MRD.nvram
04/24/2018 07:36 PM 2,248 MRD.vmdk
05/01/2018 01:15 PM <DIR> MRD.vmdk.lck
04/30/2018 03:44 PM 677 MRD.vmsd
05/01/2018 02:01 PM 4,789 MRD.vmx
05/01/2018 01:12 PM <DIR> MRD.vmx.lck
12/31/2017 03:04 PM 3,469 MRD.vmxf
04/28/2018 07:29 PM 256,031,522,816 Physical Hard Disk6-000001-s001.vmdk
04/28/2018 07:29 PM 82,970,214,400 Physical Hard Disk6-000001-s002.vmdk
04/28/2018 08:38 PM 570 Physical Hard Disk6-000001.vmdk
05/01/2018 01:15 PM <DIR> Physical Hard Disk6-000001.vmdk.lck
04/30/2018 03:41 PM 300,993,544,192 Physical Hard Disk6-000002-s001.vmdk
04/30/2018 03:41 PM 151,023,779,840 Physical Hard Disk6-000002-s002.vmdk
04/29/2018 04:17 PM 400 Physical Hard Disk6-000002.vmdk
05/01/2018 01:15 PM <DIR> Physical Hard Disk6-000002.vmdk.lck
04/29/2018 04:15 PM 237,709,754,368 Physical Hard Disk6-000003-s001.vmdk
04/27/2018 08:14 PM 5,562,040,320 Physical Hard Disk6-000003-s002.vmdk
04/28/2018 08:38 PM 393 Physical Hard Disk6-000003.vmdk
05/01/2018 01:15 PM <DIR> Physical Hard Disk6-000003.vmdk.lck
05/01/2018 01:06 PM 143,467,020,288 Physical Hard Disk6-000004-s001.vmdk
05/01/2018 01:06 PM 40,110,456,832 Physical Hard Disk6-000004-s002.vmdk
05/01/2018 01:19 PM 400 Physical Hard Disk6-000004.vmdk
05/01/2018 01:15 PM <DIR> Physical Hard Disk6-000004.vmdk.lck
04/26/2018 07:52 PM 742 Physical Hard Disk6.vmdk
05/01/2018 01:15 PM <DIR> Physical Hard Disk6.vmdk.lck
05/01/2018 01:06 PM 1,613,150 vmware-0.log
04/29/2018 08:40 AM 3,217,834 vmware-1.log
04/24/2018 07:41 PM 455,582 vmware-2.log
05/02/2018 06:54 AM 475,536 vmware.log
05/01/2018 01:06 PM 4,673 vprintproxy-0.log
04/29/2018 08:40 AM 4,413 vprintproxy-1.log
04/24/2018 07:41 PM 4,676 vprintproxy-2.log
05/01/2018 01:15 PM 4,415 vprintproxy.log
162 File(s) 1,490,502,550,676 bytes
15 Dir(s) 409,041,100,800 bytes free
Wow - you use snapshots for physical disks ???
Do you do this intentionally or by accident ?
Handling snapshots for physical disks is tricky and can be dangerous.
If you want - call me via skype so that we can arrange a Teamviewersession and do this together.
Ulli.
@Continuum Great series by the way. Yeah it was by accident I only wanted to snapshot the C drive and leave all other drives alone. Now I know so I would love the help to merge these back in and make sure it is turned off. I am in the Pacific Time zone so let me know what time you want to get together and help me work this out and I would love the help. Tried to message just you and it gave me a red x with no explanation.
@Continuum Great series by the way. Yeah it was by accident I only wanted to snapshot the C drive and leave all other drives alone. Now I know so I would love the help to merge these back in and make sure it is turned off. I am in the Pacific Time zone so let me know what time you want to get together and help me work this out and I would love the help. Tried to message just you and it gave me a red x with no explanation.
Hi Randall
Merging the content of the snapshots of the physical disks can in some cases destroy the content of the physical disks.
To decide wether we have one of those delicate cases I need to know some details.
- which guestOS is installed in your VM ?
- which hostOS is installed on the host
- does the hostOS see the physical disks.
A safe scenario would look for example like this:
- guestOS is Windows
- hostOS is Linux
- hostOS has not mounted the physical disks.
In this scenario merging the content of the snapshots to the phys. disks would be safe.
A dangerous scenario would look like this:
- guestOS is Windows
- hostOS is Windows
- hostOS uses the phys. disks when the VM is not in use.
In this scenario merging the content of the snapshots could destroy the filesystem on the disks.
As already suggested I would prefer to handle this problem via skype + teamviewer.
My skype name is "sanbarrow"
Regards Ulli
Problem solved.
Reason for the problem: a bug in WS 14 that allows Autoprotect on VMs with physical disks.
This is a very stupid and dangerous bug that should be fixed as soon as possible.