Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: Sharif George on September 23, 2003, 11:57:42 AM
-
I am having serious problems with my backup regime, I need help (mental as well as technical)
I have just tried to manually perform a backup to w/s using Adv Backup/Restore and got this error message
__________MESSAGE STARTS___________________________
Content-type: text/html
Software error:
Error occurred while deleting old mysql dumps.
For help, please send mail to the webmaster (admin@gimmehelp.com), giving this error message and the time and date of the error.
________MESSAGE ENDS_______________________________
Now The automatic backup to W/s wont start, the manual backup won't start and the tape backup hates my Travan Drive. I have this problem also on another system (that doesn't have a tape drive). This is meant to backup to w/s and then we dump it onto a DVD.
Anyone got any suggestions on either of these two probs. I am running 5.6 with updates.
Thanks y'all
MR Slunk
"Nice town I'll Take It"
-
well. i can't give you the technical advice you need. for your mental state use this: http://www.internet-pharmacy-rx.com/prozac.html ;-)
-
run the prebackup and postbackup events at command line and see if that dumps and removes the mysql.dump
/sbin/e-smith/signal-event pre-backup
/sbin/e-smith/signal-event post-backup
check in /home/e-smith/db/mysql (5.6) as you go.
In fact check first - should be empty - if not try removing it "manually" first
rob
-
Rob
thank you it "worked" I manually ran the lines as suggested and they "successfully" deleted the log file then ran the backup again and it worked (phew)
Thanks Rob
and if there is anything I can ever do to help let me know
Sharif
-
Hi everybody...
I'm having the same problem with dmc-mitel-adv-backup-restore-0.0.1-5.noarch.rpm and e-smith 5.6 with lastest updates applied.
I follow Rob Wellesley's recommendations, and also look at /home/e-smith/db/mysql and it's empty (wasn't empty before doing the signal-event stuff). I'm having the same error.
I'll really appreciate any help about this problem.
tnx,
Jarkor
[%sig%]
-
I also try restarting the server, but the same occurs.
regards,
Jarkor