Continuous virtual standby is set up for a specific server in the AppAssure deployment. When logging into the Core UI, failed export jobs are presented on the main page with the following error message:
"Failed to enqueue continuous export of 'AgentName' to 'ExportDirectory' at 'C:\FilePath'. Reason: Unable to start the export. AmountGB of free space is additionally required on C:\FilePath"
In the AppRecovery Logs, the following even will be found:
DEBUG 2014-06-10T16:10:06 [94] - Replay.Core.Implementation.Export.Validation.MachineSettings.VirtualMachineFreeSpaceValidatorBase () Total required space for current export: 1.25 TB. Available on target: 1.21 TB ERROR 2014-06-10T16:10:06 [94] - Events.Export.ExportEnqueueFailedEvent () Failed to enqueue continuous export of 'AgentName' to 'ExportDirectory' at 'C:\FilePath'. Reason: Unable to start the export. AmountGB of free space is additionally required on C:\FilePath
When the export destination, whether locally or remote, has ran out of free space the exports will fail. A few scenerios can cause this:
•Users using the storage to store large files without knowledge of the volume they are writing too
•Verify that the storage medium does have enough storage space by checking its availability through its properties
•An old export was once set up, but then removed from the UI. The originial files were never deleted and is using up storage space
•The exported machine is larger than anticipated
NOTE: Virtual Standby free space calculation is (Base + Largest incremental) * 1.1 when calculating necessary freespace
Verify that there is enough storage to write the export to the specified file path.
Delete any older files, older virtual exports, and verify that there are no hidden files taking up valuable space.
Expand the destination storage size to accommodate the exports appropriately.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center