Salta al contenuto principale

Backups Fail After Deleting Snapshot - Failed to rename file '.tmp...xml'

Thread solved

Over the past couple of days, we've come across this issue.

Backups will run and the backup file will be created, but when it gets to the deleting snapshot step, the process hangs and eventually fails.  The snapshot is successfully deleted in VMware.

The log contains the following (I've blanked some stuff out with zzzzz):

Error 0x135003d: Command has failed. Command=Deleting snapshot; tenantID=00000000-0000-0000-0000-000000000000
| trace level: error
| channel: tol-activity#zzzzz
| line: 0x4a8728dc8a1c9583
| file: e:/226/enterprise/common/tol/gating_activity.cpp:221
| function: OnCompleted
| $module: service_process_lxa64_10330
|
| error 0x20b0008: Failed to rename file '.tmp.zzzzz.Daily_Backup_-_zzzzz.xml' to 'Daily_Backup_-_zzzzz.xml'.
| line: 0x93ddf24cf210e756
| file: e:/226/enterprise/mms/metainfo/impl/metainfo_layout.cpp:127
| function: RenameStream
| $module: disk_bundle_lxa64_10330
|
| error 0x40009: Error occurred while renaming the file.
| line: 0x3d9ea26f1bfdf218
| file: E:/226/core/file/unix/posixsp.cpp:922
| function: Rename
| path1: /tmp/.mnt_net_J51KYp/.tmp.zzzzz.Daily_Backup_-_zzzzz.xml
| path2: /tmp/.mnt_net_J51KYp/Daily_Backup_-_zzzzz.xml
| $module: disk_bundle_lxa64_10330
|
| error 0xfff1: Resource temporarily unavailable
| line: 0xbd28fdbd64edb911
| file: e:/226/core/common/error.cpp:339
| function: AddPosixError
| code: 0xb
| $module: disk_bundle_lxa64_10330

We've tried restarting the vCenter Server.  We've tried restarting the network location the backups (and XML files) are stored at.  We've tried restarting the Aconix Backup Appliance.

In fact, several backup plans don't have an XML file at all, and they only have stray ".tmp..." versions.

No changes were made recently, and Monday's backups ran fine, but Tuesday's and today's are failing.  Any ideas? 

Thanks.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 22
Commenti: 3800

Hi Brian,

The error is unrelated to snapshot deletion process - this error should first appear higher in the backup log file, but it's also appended to the last message in the log (which is "snapshot deletion event") to have the full stack, even though the error itself is not related.

The error in your case is referring to access to backup location: the network backup locations are accessed as mount points ("/tmp/.mnt_net_J51KYp/" is a mount point on appliance which refers to network share) on the share. And the root cause is in the specifics of shares access from Linux (from within appliance), but the details of it should be investigated separately with our support team involved (remember to collect system report). There could be some traces from mout points left or issues with share mounting or issues with share status or something similar.

Thank you.