New to all of this and just want to confirm before I do this.
A veeam Copy from and to the server of the main OS disk has left me a nice mess saying redo logs are corrupt when i power on the machine. I did this while the VM was running, the process seemed to have shut down the VM which freaked me out and I tried to power it back on while the backup was still running as it was been used elsewhere. it did not power on so i left the backup to complete.
To note, i have not created any snapshots, the backup is now showing many ctk, sesparse and extra vmdk files which look like some type of snapshot?
I believe the issue is due to free space on my 2x 5TB drives that are full and I believe it's tried to make "snapshots" on these data stores which have no space.
Option 1 - easier? rebuild the OS disk and manually remove the VMNAME-000001.vmdk ctk and sparse ect files and just use the base vmdk of the 2x 5TB disks?
option 2 can i increase the space on the data store temporarily or move the snapshot files to another temp drive, let it do what it has to and then consolidate or remove these files?
Here is the file list of one of the 5TB drives
-rw------- 1 root root 4761048 Oct 1 18:56 CentOS-Core_1-000001-ctk.vmdk
-rw------- 1 root root 19657654272 Oct 1 18:59 CentOS-Core_1-000001-sesparse.vmdk
-rw------- 1 root root 396 Oct 1 18:33 CentOS-Core_1-000001.vmdk
-rw------- 1 root root 4761048 Oct 1 19:53 CentOS-Core_1-000002-ctk.vmdk
-rw------- 1 root root 19657654272 Oct 1 19:53 CentOS-Core_1-000002-sesparse.vmdk
-rw------- 1 root root 403 Oct 1 19:53 CentOS-Core_1-000002.vmdk
-rw------- 1 root root 4761048 Oct 1 22:32 CentOS-Core_1-000003-ctk.vmdk
-rw------- 1 root root 19657654272 Oct 1 22:32 CentOS-Core_1-000003-sesparse.vmdk
-rw------- 1 root root 403 Oct 1 19:53 CentOS-Core_1-000003.vmdk
-rw------- 1 root root 4761048 Oct 1 18:33 CentOS-Core_1-ctk.vmdk
-rw------- 1 root root 4991782789120 Oct 1 15:37 CentOS-Core_1-flat.vmdk
-rw------- 1 root root 522 Oct 1 18:33 CentOS-Core_1.vmdk
Any help would be greatly appreciated!
