It's more than just the mentioned file that's missing, other files are missing too.
-rw------- 1 root root 15.5G Oct 19 2019 SRVDC01_0-000001-delta.vmdk
-rw------- 1 root root 322 Sep 9 2019 SRVDC01_0-000001.vmdk
-rw------- 1 root root 46.9G Mar 10 10:50 SRVDC01_0-000002-delta.vmdk --> missing: SRVDC01_0-000002.vmdk
-rw------- 1 root root 60.0G Sep 4 2019 SRVDC01_0-flat.vmdk
-rw------- 1 root root 552 Aug 13 2019 SRVDC01_0.vmdk
-rw------- 1 root root 17.3G Oct 19 2019 SRVDC01_1-000001-delta.vmdk
-rw------- 1 root root 323 Sep 9 2019 SRVDC01_1-000001.vmdk
-rw------- 1 root root 303.0G Mar 10 10:50 SRVDC01_1-000002-delta.vmdk --> missing: SRVDC01_1-000002.vmdk
-rw------- 1 root root 330 Mar 14 11:29 SRVDC01_1-000003.vmdk (Corrupt FILE)
-rw------- 1 root root 500.0G Sep 4 2019 SRVDC01_1-flat.vmdk
-rw------- 1 root root 554 Aug 13 2019 SRVDC01_1.vmdk
To find out what may be possible, please download all of the small the descriptor .vmdk files (the ones without delta, or flat in their names) as well as the VM's .vmx, and .vmsd file, compress/zip these files, and attach the .zip archive to your next reply.
You may want to use e.g. WinSCP for the downloads, since the datastore browser hides these small files.
Also describe what you've tried so far!
Another question: The VM's name suggests that it is a domain controller. Is this the only DC, or do you have other DC's in your environment? I'm asking because bringing a DC back online with old data, can cause serious issues in the Active Directory.
André