Info: Restore Failed With Exit Code 64
Helpful error message when attempting an Expert restore today - pulling back an inadvertently deleted file from last nights backup created with Microlite BackupEdge
What it actually meant to say was :
Info: Restore Failed - unable to create directory in restore location.
If you try to restore without selecting Flat Restore AND if a file with the same name as the folder you're attempting to restore exists in the Restore To: path, you'll get this error.
Showing posts with label microlite edgemenu linux. Show all posts
Showing posts with label microlite edgemenu linux. Show all posts
Tuesday, 23 October 2012
Thursday, 7 July 2011
A nice exciting new error in Microlite BackupEdge today.
af token exists before mount
Got this error in edgemenu when we attempted to access a usb disk which was setup as an attached file system af0, using a file system partition fsp0.
Turned out that once again there were left over files in the mount point:
/usr/lib/edge/system/mnt/af0
Moved the .edge_af file to /tmp and it's all working again now!
I wish the firm would make the change to using the smartdrive method, it's certainly less problematic in my experience.
Wednesday, 13 October 2010
AF Unmount Command Failed / AF Token File Missing
Using Microlite BackupEDGE getting the following error:
Command was: "umount /usr/lib/edge/system/mnt/af0"
Reason is AF Unmount Command Failed
Setup all looks OK in edgemenu - default resource is:
fsp!fsp0 (/fsp0) (Directory Resource)
Using USB HDD as backup media, which can be mounted and unmounted without problems.
Found that the backup was actually going into the directory mentioned in the unmount command. There shouldn't be anything in that folder. Removed the contents and ran the scheduled backup.
New error :
Generic System Error
Reason is AF Token File Missing
Initialised the media - didn't help.
Make sure af0 is empty still.
Rebooted - errors gone, backup ran through OK.
Strange!
-update-
seems that removing the following file will negate the need to reboot and is likely the whole cause of the problem - this file is used to track the mount status. It gets 'mounted' even though the device isn't mounted, then it never attempts to mount and creates the backup in the folder, rather than the USB drive.
/usr/lib/edge/system/locks/af0.lck
You DO still need to initialise the media.
Command was: "umount /usr/lib/edge/system/mnt/af0"
Reason is AF Unmount Command Failed
Setup all looks OK in edgemenu - default resource is:
fsp!fsp0 (/fsp0) (Directory Resource)
Using USB HDD as backup media, which can be mounted and unmounted without problems.
Found that the backup was actually going into the directory mentioned in the unmount command. There shouldn't be anything in that folder. Removed the contents and ran the scheduled backup.
New error :
Generic System Error
Reason is AF Token File Missing
Initialised the media - didn't help.
Make sure af0 is empty still.
Rebooted - errors gone, backup ran through OK.
Strange!
-update-
seems that removing the following file will negate the need to reboot and is likely the whole cause of the problem - this file is used to track the mount status. It gets 'mounted' even though the device isn't mounted, then it never attempts to mount and creates the backup in the folder, rather than the USB drive.
/usr/lib/edge/system/locks/af0.lck
You DO still need to initialise the media.
Subscribe to:
Posts (Atom)