-
Title
Backup fails with 'Error Message: 2129 - can't write -
Description
A backup of a VM(s) fail with error message 2129 - can't write.....
-
Cause
-
Resolution
POSSIBLE RESOLUTIONS:
Cause 1: Backups over a WAN are failing
RESOLUTION:
If the backup is over a WAN this is not supported with vranger currently.
Cause 2: Compression enabled for the repository drive itself ( please note this does not refer to having compression on or off for the vranger job itself )
RESOLUTION:
Microsoft recommends to not use NTFS compression on servers or on volumes that have high I/O (read/write operations on the repository)
http://support.microsoft.com/kb/251186
Browse to the repository in windows explorer and right click on the repository drive and choose properties turn off Windows disk compression.
Cause 3: Other Backup Vendor processes or agents overlapping with vRanger backups.
RESOLUTION:
A possible cause of this is that another backup agent could be backing up the repository and the overlap will cause the vRanger backup to fail. Schedule the repository backup in such a way that it does not overlap with vRanger backups.
Cause 4: Repository is full and or has run out of space
RESOLUTION:
A possible cause of this is that the repository in question has become full look into possibly deleting some older savepoints or free up enough space to allow backups to continue.
Cause 5: Too many concurrent backups per repository
RESOLUTION:
Lower number of concurrent backups allowed per repository in vranger this is done by selecting
tools | options | my jobs | configuration
Cause 6: Improper Repository Path Creation\ Definition
RESOLUTION:
1. In vRanger Gui select My Repositories
2. Right click on repository and choose properties
3. Check to make sure that server is defined as \\servername\vrangershare and not \\servername\C$\vrangershare
Cause 7: Permissions on the Repository Share via Windows NTFS
RESOLUTION:
1. Ensure that the vRanger user had Full Control permissions set on the Share being used as your respository destination.
2. Ensure that the vRanger user has Full Control permissions set at the NTFS level.
Cause 8: Hung metadata.exe Files on vRanger Server
RESOLUTION:
On Ranger server in the Task Manager there are multiple metadata.exe processes. Metadata.exe normally appears in the Task Manager for a few seconds, when GlobalManifest, savepoint Manifest or VmConfig is being written. If jobs appear to be stuck in queue or hung using windows task manager on the vranger server kill all metadata.exe processes that are running. Confirm that GlobalManifest is not locked by opening up the file in Wordpad.
Then restart the services in the following order.
1. Stop the vRanger FLR and API services
2. Restart the vRanger service
3. Start the vRanger API service
4. Start the vRanger FLR serviceCause 9: Server Hosting Repository running low on resources
RESOLUTION:
Server hosting repository is running low on resources reboot the server hosting the repository(s)
Cause 10: Corruption between vRanger Database and contents of Repository for job with multiple vm's
RESOLUTION:
Exclude the failing vm(s) from the backup job and create a new job for the excluded vm(s).