Can you post the output of the script, I might spot something...
did you run the INSTALL option? this looks like you are wanting to crypt the archive but don't have a passwd file for it yet.
I see there are quite a few people still using this script, and there are some bugs that need killing, and the code need a lot of cleaning, and spring is in the air (well almost anyway...) :o !!
So here it is - CALL FOR ENHANCEMENT REQUESTS !!
Anyone need something that the script don't do at the moment?
Anyone going to share there fixes, to rid the script of a bug or two?
Thanks for your fast reply.
I have used the --INSTALL option
Here is the log
I have checked the file in /etc/zmbac/ with the name noread and its empty.Quote:
Full Backup started at: 11:27
No old backups found
Setting date & version Marker into /opt/zimbra/DATE_VERSION.txt
Doing a hotsync of /opt/zimbra/ to /srv/backup/sync/
sync went ok
Stopping the Zimbra server
Deactivated zimbra's cronjobs
Zimbra server has stopped
kill any left over zimbra procs
Nothing to kill
Doing a fast cold sync...
sync went ok
Reinstated zimbra's cronjobs
Zimbra has started
Service down time was - Hr:0 Min:2 Sec:44
Running A hack... This one to check and start Stats subsystem
Hack not needed Stats seems to be running fine...
All services are running
Writing a full backup called:
in: /srv/backup/dars/ with file sizes of max: 4395M
Thanks for your help.
In the install part of the script there is a option to generate that password for you in that file.
In fact all you have to do is to put a password in that file... then it should work.
All the install part does is creates a password in the following manner:
The easy one liner to do this would be (this is with defaults in script settings):Code:
~$ openssl rand -base64 48 [ enter ]
Hope that helps you out !Code:
openssl rand -base64 48 -out /etc/zmbac/noread
Thanks for sharing this script. It's rather big comparing with others, but very useful and well commented.
Hello once again,
At the end of backup i got this error,
./zmbac.sh: line 890: /srv/backup/dars/Backuplist-13-March-2009.txt.gz: Permission denied
Can this be related to email sending?
re: Call for enhancements :)
a) Backup management e.g. keep 'x' days/weeks of backup files then auto-delete
b) Backup options e.g. nightly full backup. Many of us have small installs where this is perfectly feasible
c) Optional daily 'success' reports (for the paranoid)
d) Weekly summary report
e) Target storage location info in report e.g. available disk% free
f) Report alert if available target space is less than x% free
g) Support for CentOS install as well as Ubuntu
h) Official version control.. put some #comments at the top of the script
i) Restore options!
j) Status indications in the report, e.g. step 1 / 6 complete (v. useful when running a manual full backup from the command line)
k) Simplify the script - FULL and DIFF sections are essentially the same, use a variable to differentiate which option instead of giving me double the opportunity to stuff-up custom tweaks :D
l) Post the new script to a new thread, this one's getting a bit long!
I'm happy to test changes if you need willing victims.
How do I use the backup if it needed? (which method to restore?)
Cheers for the suggestions, I will get down to coding asap!