Koozali.org: home of the SME Server
Obsolete Releases => SME Server 8.x => Topic started by: jim7jim on October 25, 2014, 08:28:49 PM
-
Using SME 8.1. Using Workstation backup with Windows file server as target. Been working well for months. Recently the backups started failing. I've done some research on DAR but can't find anything about what to do when db is corrupted. I'm getting the emails below to the admin account. I tried to setup a brand new Workstation backup from scratch to start with a new full backup but it failed as well. Does anyone know how I can start from scratch? Can I delete the existing backups and dar-catalog? TIA
1st email:
==================================
DAILY BACKUP TO WORKSTATION REPORT
==================================
Backup of <server name removed> started at Sat Oct 25 10:00:05 2014
Backup of mysql databases has been done
Mounting backup shared directory <mount dir removed>
Using set number 2 of 2
Attempt full backup
Backup temp directory /mnt/smb/tmp_dir/<server name removed> is mounted and is writable
Backup base file name is full-201410251000
Starting the backup with a timeout of : 28770 seconds
--------------------------------------------
345024 inode(s) saved
including 2352 hard link(s) treated
0 inode(s) changed at the moment of the backup and could not be saved properly
0 byte(s) have been wasted in the archive to resave changing files
0 inode(s) not saved (no inode/file change)
0 inode(s) failed to be saved (filesystem error)
262 inode(s) ignored (excluded by filters)
0 inode(s) recorded as deleted from reference backup
--------------------------------------------
Total number of inode(s) considered: 345286
--------------------------------------------
EA saved for 0 inode(s)
--------------------------------------------
Moving backup files to target directory /mnt/smb/<server name removed>/set2
Updating catalog
*** No backup allowed or error during backup ***
Failed to delete set 7 from catalog.
2nd email:
Corrupted database :Not enough data to initialize storage field
Corrupted database :Not enough data to initialize storage field
Failed to delete set 7 from catalog.
Backup terminated: backup failed - status: 7424
-
Sorry to hear that. If it is all default backup etc. and not contrib related, then I would file a bug report.
1. Dev's scan bugzilla
2. Backup is a serious thing
guest
ps. There are already some reports with "Backup terminated: backup failed - status: 7424"
-
Take a look here, if any of these tweaks is useful for you:
http://forums.contribs.org/index.php/topic,49556.msg247797.html#msg247797 (http://forums.contribs.org/index.php/topic,49556.msg247797.html#msg247797) .----->
http://alan.lamielle.net/2009/09/03/windows-7-nonpaged-pool-srv-error-2017 (http://alan.lamielle.net/2009/09/03/windows-7-nonpaged-pool-srv-error-2017)
http://social.technet.microsoft.com/Forums/windows/en-US/909a5f0f-73b0-4a52-a594-0d7f80f0c7df/error-while-mounting-windows-7-shared-on-linuxsamba (http://social.technet.microsoft.com/Forums/windows/en-US/909a5f0f-73b0-4a52-a594-0d7f80f0c7df/error-while-mounting-windows-7-shared-on-linuxsamba)
http://hardforum.com/showthread.php?p=1032714322 (http://hardforum.com/showthread.php?p=1032714322)
Any WindowsUpdate may have "fired" your shares ?
Nicola
-
When you say:
I tried to setup a brand new Workstation backup from scratch to start with a new full backup but it failed as well
What was the backup config for the new backup
Did you rename the destination shared dir of the old backup destination as well before attempting the new backup
Did you check the /mnt/smb dir on the server and delete any part backup that may be still evident?
What is the size of the backup?
-
Thanks for the suggestions. After renaming the destination folder and deleting all the existing backups, I now have a passing backup.
Cheers! :pint: