Difference between revisions of "Changing Backup directory and General Information"

(New page: '''Default Backup Information''' Backing up the Zimbra server on a regular basis can help you quickly restore your mail service, if an unexpected crash occurs. The backup process writes a...)
 
 
(13 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
{{Archive}}{{Unsupported}}
 +
 
'''Default Backup Information'''
 
'''Default Backup Information'''
  
 
Backing up the Zimbra server on a regular basis can help you quickly restore your mail service, if an unexpected crash occurs. The backup process writes a consistent snapshot of mailboxes to a designated backup directory.
 
Backing up the Zimbra server on a regular basis can help you quickly restore your mail service, if an unexpected crash occurs. The backup process writes a consistent snapshot of mailboxes to a designated backup directory.
 
  
 
   * Zimbra mailboxes can be restored from the following:
 
   * Zimbra mailboxes can be restored from the following:
Line 13: Line 14:
 
   * Redo logs that contains current and archived transactions processed by the Zimbra server since the last incremental backup
 
   * Redo logs that contains current and archived transactions processed by the Zimbra server since the last incremental backup
  
   * crontab -l
+
   * crontab -l -- Default Crontab of Zimbra user.
 +
 
 +
    0 1 * * 6 /opt/zimbra/bin/zmbackup -f -a all
  
0 1 * * 6 /opt/zimbra/bin/zmbackup -f -a all
+
    0 1 * * 0-5 /opt/zimbra/bin/zmbackup -i -a all
0 1 * * 0-5 /opt/zimbra/bin/zmbackup -i -a all
 
0 0 * * * /opt/zimbra/bin/zmbackup -del 1m
 
  
  * Default Backup Directory:
+
    0 0 * * * /opt/zimbra/bin/zmbackup -del 1m
  
   * /opt/zimbra/backup
+
   * Default Backup Directory: /opt/zimbra/backup
 +
 
 +
=== Changing the backup directory ===
  
 
'''Why To Change the Path'''
 
'''Why To Change the Path'''
Line 28: Line 31:
 
   * Storage issues, lesser space on the local disk for large deployments.
 
   * Storage issues, lesser space on the local disk for large deployments.
 
   * Take Backups of Multi-Install Zimbra Server to a single place/server on different directories.
 
   * Take Backups of Multi-Install Zimbra Server to a single place/server on different directories.
 +
  * You can use NFS also to store the backup on a different location.
 +
 +
'''How to Change - New Method:'''
 +
 +
zmprov gacf zimbraBackupTarget
 +
 +
The default is : /opt/zimbra/backup
 +
 +
To change modify the config:
 +
 +
zmprov mcf zimbraBackupTarget /path/to/new/target
 +
 +
'''Do a Flush Cache on the Config:'''
 +
 +
zmprov fc config
 +
 +
As of 4.5.6 the backup tab in the admin console allows for setting:
 +
 +
zimbraBackupTarget
 +
 +
zimbraBackupReportEmailSubjectPrefix
 +
 +
zimbraBackupReportEmailSender
 +
 +
zimbraBackupReportEmailRecipients
 +
 +
(These attributes can also be set with zmprov)
  
'''How to Change'''
+
They we're added in RFE: http://bugzilla.zimbra.com/show_bug.cgi?id=12442
 +
 
 +
'''How to Change - Old Method:'''
  
 
   * You can edit the backup cronjob and specify a different backup location using the -t switch.  
 
   * You can edit the backup cronjob and specify a different backup location using the -t switch.  
  
'''Steps'''
+
Steps:
  
 
   * su - zimbra
 
   * su - zimbra
  
   * crontab -l | grep zmbackup
+
   * crontab -e
  
 
   * 0 1 * * 6 /opt/zimbra/bin/zmbackup -f -a all -t </path/to/new target>
 
   * 0 1 * * 6 /opt/zimbra/bin/zmbackup -f -a all -t </path/to/new target>
Line 45: Line 77:
 
   * 0 0 * * * /opt/zimbra/bin/zmbackup -del 1m  
 
   * 0 0 * * * /opt/zimbra/bin/zmbackup -del 1m  
  
   * Bug "http://bugzilla.zimbra.com/show_bug.cgi?id=7112" would address specifying a  
+
  * Save the file [Esc :wq].
 +
 +
  * You can also use Symlinks to define new Backup Paths.
 +
 
 +
  * These changes won't survive an upgrade.
 +
 
 +
'''Notes'''
 +
 
 +
  * If you want to take backups of Multi-Server install of Zimbra (Ldap (Zimbra-1), Mailstore (Zimbra-2), Logger (Zimbra-3))
 +
    to a Single backup server the backup directories should be different for each server.
 +
 
 +
  * Eg:- On the backup server something like:- /path/backup/zimbra-1/, /path/backup/zimbra-2/, and /path/backup/zimbra-3/.
 +
 
 +
  * The -t option should be specified for zmbackup -del also.
 +
 
 +
   * Bug http://bugzilla.zimbra.com/show_bug.cgi?id=7112 would address specifying a  
 
     different backup target as part of the zmschedulebackup utility.
 
     different backup target as part of the zmschedulebackup utility.
  
  * These changes won't survive an upgrade.
+
 
 +
{{Article Footer|unknown|7/13/2007}}
 +
 
 +
[[Category:Backup and Restore]]

Latest revision as of 14:59, 24 March 2015


Default Backup Information

Backing up the Zimbra server on a regular basis can help you quickly restore your mail service, if an unexpected crash occurs. The backup process writes a consistent snapshot of mailboxes to a designated backup directory.

 * Zimbra mailboxes can be restored from the following:
 * Full backup files that contains all the information needed to restore mailboxes
 * Incremental backup files that contains the LDAP directory server files and all the redo log 
   transactions written since the last backup
 * Redo logs that contains current and archived transactions processed by the Zimbra server since the last incremental backup
 * crontab -l  -- Default Crontab of Zimbra user.
   0 1 * * 6 /opt/zimbra/bin/zmbackup -f -a all
   0 1 * * 0-5 /opt/zimbra/bin/zmbackup -i -a all
   0 0 * * * /opt/zimbra/bin/zmbackup -del 1m
 * Default Backup Directory: /opt/zimbra/backup

Changing the backup directory

Why To Change the Path

 * To move the backups to a safer place [SAN, Netapp Appliance]
 * Storage issues, lesser space on the local disk for large deployments.
 * Take Backups of Multi-Install Zimbra Server to a single place/server on different directories.
 * You can use NFS also to store the backup on a different location.

How to Change - New Method:

zmprov gacf zimbraBackupTarget

The default is : /opt/zimbra/backup

To change modify the config:

zmprov mcf zimbraBackupTarget /path/to/new/target

Do a Flush Cache on the Config:

zmprov fc config

As of 4.5.6 the backup tab in the admin console allows for setting:

zimbraBackupTarget

zimbraBackupReportEmailSubjectPrefix

zimbraBackupReportEmailSender

zimbraBackupReportEmailRecipients

(These attributes can also be set with zmprov)

They we're added in RFE: http://bugzilla.zimbra.com/show_bug.cgi?id=12442

How to Change - Old Method:

 * You can edit the backup cronjob and specify a different backup location using the -t switch. 

Steps:

 * su - zimbra
 * crontab -e
 * 0 1 * * 6 /opt/zimbra/bin/zmbackup -f -a all -t </path/to/new target>
 * 0 1 * * 0-5 /opt/zimbra/bin/zmbackup -i -a all -t </path/to/new target>
 * 0 0 * * * /opt/zimbra/bin/zmbackup -del 1m 
 * Save the file [Esc :wq].

 * You can also use Symlinks to define new Backup Paths.
 * These changes won't survive an upgrade.

Notes

 * If you want to take backups of Multi-Server install of Zimbra (Ldap (Zimbra-1), Mailstore (Zimbra-2), Logger (Zimbra-3)) 
    to a Single backup server the backup directories should be different for each server.
 * Eg:- On the backup server something like:- /path/backup/zimbra-1/, /path/backup/zimbra-2/, and /path/backup/zimbra-3/. 
 * The -t option should be specified for zmbackup -del also.
 * Bug http://bugzilla.zimbra.com/show_bug.cgi?id=7112 would address specifying a 
   different backup target as part of the zmschedulebackup utility.


Verified Against: unknown Date Created: 7/13/2007
Article ID: https://wiki.zimbra.com/index.php?title=Changing_Backup_directory_and_General_Information Date Modified: 2015-03-24



Try Zimbra

Try Zimbra Collaboration with a 60-day free trial.
Get it now »

Want to get involved?

You can contribute in the Community, Wiki, Code, or development of Zimlets.
Find out more. »

Looking for a Video?

Visit our YouTube channel to get the latest webinars, technology news, product overviews, and so much more.
Go to the YouTube channel »

Jump to: navigation, search