The problem is caused by VMware system, when Core is trying to write to the repository location, which is beyond the size of VMDK and there's no more free space on the datastore.
For example: repository was created as 13TB on the thin-provisioned 11.5TB VMDK.
There are 2 possible resolutions:
1) increase datastore size, so it'll be bigger than provisioned repository disk in guest OS. Then shut down Core VM and resize the VMDK appropriately.
2) if datastore cannot be grown, then use failback/failover to another Core server (even temporarily), then recreate VM Core's repository as thick-provisioned and less than free datastore size, before replicating data back. https://support.quest.com/rapid-recovery/kb/267207/how-to-perform-failover-failback-replication-for-various-reasons
Important: sudden Core VM powerdowns can be detrimental and may cause repository corruption
© ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center