Backing up and restoring Zimbra (Open Source Version): Difference between revisions

No edit summary
 
Line 3: Line 3:


== Backing Up ==
== Backing Up ==
It is always good practice to backup your copy of Zimbra in the event of unforeseen circumstances.
It is always good practice to backup your copy of Zimbra in the event  
Since all of the components to operate Zimbra are stored in the Zimbra folder itself, you can simply copy the folder and past it at another location.
of unforeseen circumstances.
 
Since all of the components to operate Zimbra are stored in the Zimbra  
folder itself, you can simply copy the folder and past it at another location.


You may want to use:
You may want to use:
Line 10: Line 13:
>zmcontrol stop
>zmcontrol stop


to prevent changes to any Zimbra databases during the copy processes. If you get some kind of error, you may want to make sure that Zimbra has completly stopped by running:
to prevent changes to any Zimbra databases during the copy processes. If you get  
some kind of error, you may want to make sure that Zimbra has completly stopped  
by running:
 
>ps auxww | grep zimbra
>ps auxww | grep zimbra
and kill any left over processes such as the log.
and kill any left over processes such as the log.


Copy Command: cp -r /opt/zimbra [location path]
Copy Command: cp -r /opt/zimbra [location path]
'''WARNING''': Make sure that the copy location has enough space to support your backup copy (ie the tmp folder probably isn't the best locaiton).
'''WARNING''': Make sure that the copy location has enough space to support your  
backup copy (ie the tmp folder probably isn't the best locaiton).

Revision as of 04:42, 29 March 2006

If you wish to have a more automated backup feature, you should try the [Network Version of Zimbra.]


Backing Up

It is always good practice to backup your copy of Zimbra in the event of unforeseen circumstances.

Since all of the components to operate Zimbra are stored in the Zimbra folder itself, you can simply copy the folder and past it at another location.

You may want to use: >su zimbra >zmcontrol stop

to prevent changes to any Zimbra databases during the copy processes. If you get some kind of error, you may want to make sure that Zimbra has completly stopped by running:

>ps auxww | grep zimbra and kill any left over processes such as the log.

Copy Command: cp -r /opt/zimbra [location path] WARNING: Make sure that the copy location has enough space to support your backup copy (ie the tmp folder probably isn't the best locaiton).

Jump to: navigation, search