Hi guys,
We have 8 VM's replicating to our DR site and i recently received a warning about low disk space on one of the datastores. After further investigation i noticed that all 8 VMs have a XXX.vmdk and a XXX_working.vmdk file which are both exactly the same size. Do i really need both and what causes this issue (if infact it is an issue?).
Cheers guys.
-
Jeff8247
- Novice
- Posts: 3
- Liked: never
- Joined: Dec 09, 2009 11:17 pm
- Full Name: Jeff S
- Contact:
-
Vitaliy S.
- VP, Product Management
- Posts: 27405
- Liked: 2806 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Replication jobs
Hello Jeff,
Actually, XXX_working.vmdk is the descriptor file, that is created and used while replicating to ESXi host. I believe you see the same size, because you use Datastore Browser for that, which merges descriptors and actual flat disks by default. If you try to browse using FastSCP that is built-in Veeam Backup and Replication you'll see the actual size of the file.
Thank you!
Actually, XXX_working.vmdk is the descriptor file, that is created and used while replicating to ESXi host. I believe you see the same size, because you use Datastore Browser for that, which merges descriptors and actual flat disks by default. If you try to browse using FastSCP that is built-in Veeam Backup and Replication you'll see the actual size of the file.
Thank you!
Who is online
Users browsing this forum: Baidu [Spider], Semrush [Bot] and 47 guests