VMware Data Recovery error – Trouble writing files, error -1020 (Sharing violation)
Sometimes you came out in a trouble when your VDR backup does report an error.
Trouble writing files, error -1020 (Sharing violation)
And when you manually trigger the backup it fails with the following error:
The destination is not available for a backup job. Please ensure the destination has been formatted and there is enough space.
There is a solution I found in this VMware KB article. This error happenings when VDR has been quit not properly and the locked file in the deduplication store has been left there. So you just have to look for the store.lck file in the folder which is found in /VMwareDataRecovery/BackupStore/store.lck.
Then if you’re sure that no other instances of VDR deduplication store, delete the lock folder.
After deleting the lock folder, VDR can complete operations as expected. Note that you must not delete this folder if other instances of Data Recovery are using the deduplication store, otherwise a corruption may occur.
More on VMware Data Recovery:
- VDR connectivity and divers troubleshooting
- VMware Data Recovery 2.0 – the upgrade process from earlier version
- Troubleshooting tool for VDR
- VDR plugin do not connect to VDR appliance
- How-to enable verbose logging in VDR – VMware Data Recovery
- If you’re trying to use Windows CIFS with VDR
- How to fix damaged restore points in VDR
- Using VMware Data Recovery without vCenter?
- VDR appliance not mounting automatically the backup destination after reboot
- VDR – how to get a log bundle before you call the support
- How-to update VDR to 1.2
- Do you want to see a little magic?
- VDR backup fail error – this post
- VMware Data Recovery – a tool for Easy backups of your Virtual Infrastructure
- VMware VDR – vSphere Data Recovery – part 3 – Restore Your Data
- VMware Data Recovery – your first backup – part 2 video
- VMware Data Recovery – install and configure video- part1
- Data recovery – new GUI backup tool present in vSphere 4