How much space is required for client side deduplication?
We are running BE 2012 on a 3600 R2 appliance. When attempting to run a backup of SQL located on a vm, it fails with the following error:
Storage device "Appliance_Dedupe_BACKUP:3" reported an error on a request to write a media location identifier (file mark).
A device attached to the system is not functioning.
Veng-sql2-backupVENRetailWindows_V-6.1.7601_SP-1.0_PL-0x2_SU-0x110_PT-0x3 - An unknown error has occurred.
However, more importantly, the backup job seems to completely bring down the vm. In discussion with vmware, it appears as though local disk space on the vm is expanding during the backup, and since the disk is configured as thin, it automatically expands causing the entire datastore to fill up, bringing the vm down and preventing it from starting up again until space is freed up. We were able to bring the vm back by moving the vswp file to another datastore.
So my question is, does this sound like a problem with insufficient space required for client side dedupe? How can we determine how much space is required for this? When checking the Backup Exec AOFO Store folder on the vm, it's empty, which I understand automatically cleans up after a reboot. Since this occured on a production server, we can't rerun the backup until we know for sure what caused the issue.