Server stops 2 hours after backup

[joe_louis]

I am running the backup script labelled "A Simple Shell Script Method like above, but with rsync over ssh" from http://wiki.zimbra.com/wiki/Open_Source_Edition_Backup_Procedure. every time it runs on a install that i did, It will stop 2 hours afterwards. I have multiple servers running and it only happens to the one. They all have the same software as the one having the issue. The only difference between all of them is the amount of email per user and the number of users. I have installed the latest patches for zimbra 7.1.1 and Centos on this server. Looking through the logs doesn't show anything either other then entries stop when this occurs. any help in figuring out where the issue is would be much appreciated.

[joe_louis]

Any help out there?

[soba@ukw.edu.pl]

Originally Posted by joe_louis

Any help out there?

the best backup:

cp -R /opt/zimbra /other

[joe_louis]

Thank you, Unfortunatley, I need to be able to set this up as a cron job that runs nightly. That command is the jist of what i am doing though. The diffrence is i am only syncing all the changes instead of everything.

[soba@ukw.edu.pl]

Do you using any LVM structure? You can use several backup procedures. Maybe your Zimbra is stopped because of restrictions on the server? During the data backup process can consume a lot of resources.

I am kidding with this: cp-R / opt / Zimbra / other
Probably best to use a virtual environment for ZImbra backup (VMware / Oracle).

[joe_louis]

They server completes the backup properly. During the backup, it does stop the server to make sure it catches anything that might not have been accessible at the time. Then it starts it up with "service zimbra start". 2 hours after it completes this part is roughly when it stops responding.

[soba@ukw.edu.pl]

The fact that the backup was done correctly does not mean that over time you will not break any process in the system.

What kind of backup do you use? (LVM/ other method?) Mybe you don't have enough memory (LVM needs a lot of memory during heavy operations in the file system). You may have a system bug also.

[joe_louis]

I agree that i may have a system bug. This only happens when the backup is ran through cron. I can run it all day long from the command line. the server won't stop then. That is why i am mentioning the backup script that i use. I am using rsync for this.

[soba@ukw.edu.pl]

Maybe you have a zombie process after the backup finished?
Check your system status - like top or ps aux

[soba@ukw.edu.pl]

And check your crontab shell (bash / sh).