Difference between revisions of "Ajcody-Disaster-Recovery-Specific-Notes"

m (Bugs Filed That Might Apply)
m (Bugs Filed That Might Apply)
Line 15: Line 15:
Please see: [[Network_Edition_Disaster_Recovery#Restoring_to_the_new_server]]
Please see: [[Network_Edition_Disaster_Recovery#Restoring_to_the_new_server]]
=====Bugs Filed That Might Apply=====
* "Improve zmrestore & zmrestoreoffline performance"
** http://bugzilla.zimbra.com/show_bug.cgi?id=33606
*** Large mailstores will probably see this as a performance issue when doing the zmrestoreoffline step. In other words, it's taking forever.
* "accounts.xml file dependency needed for zmrestore"
** http://bugzilla.zimbra.com/show_bug.cgi?id=30979
* "Expand restore recovery documentation to include multi-server configurations"
** http://bugzilla.zimbra.com/show_bug.cgi?id=24894
'''Please add your votes to this RFE!'''
* "Disaster recovery through server to server sync (beta)"
** http://bugzilla.zimbra.com/show_bug.cgi?id=11423
====What To Do Or Check====
====What To Do Or Check====

Revision as of 17:16, 16 June 2009

Attention.png - This article is NOT official Zimbra documentation. It is a user contribution and may include unsupported customizations, references, suggestions, or information.

Disaster Recovery Specific Notes

Actual Disaster Recovery Specific Notes Homepage

Please see: Ajcody-Disaster-Recovery-Specific-Notes

My Disaster Recovery Failed

Main Reference

Please see: Network_Edition_Disaster_Recovery#Restoring_to_the_new_server

What To Do Or Check

Time Issues

First, make sure your TIME is set right! See Time_Zones_in_ZCS#The_server_OS

Authentication Password Issues

Though I'm still investigating why this is happening for our customers, the root issues seem to be resolved by the following. Some of the auth errors will be logged to /var/log/zimbra.log and /opt/zimbra/log/mailbox.log

Put the output of this command in a text file:

zmlocalconfig -s | grep password

These should match what's in /opt/zimbra/conf/localconfig.xml

Now, compare the passwords with what is in your restore. Put in your path of the restore specific directory.

vi /opt/zimbra/backup/sessions/YOUR_DIR/sys/localconfig.xml

Do a /password or the full variable in vi to see what the old passwords are. You'll need to adjust the following below. Remember to copy a backup.

cp /opt/zimbra/conf/localconfig.xml /opt/zimbra/conf/localconfig.xml.DR
accounts.xml file - restore error

mailbox.log or restore command will output errors about

  • accounts don't actually get restore though restore command appears to completed without error.
zimbra@xxxx:~/log$ zmrestore -all -rf
Error occurred: invalid request: invalid account email address: ll
zimbra@xxxx:~/log$ zmrestore -a bdavis@XXXXXXX.com -rf
Error occurred: no such account: Account ID for bdavis@XXXXXXXXX.com not found in backup
  • no such session backup label errors
com.zimbra.cs.backup.BackupServiceException: backup full-20080920.050014.406 not found: 
/opt/zimbra/backup/sessions/full-20080920.050014.406 not found ExceptionId:main:1222811246316:7615eea74222489d

If your missing the /opt/zimbra/backup/accounts.xml file, grab it from your saved backup directory or from the backup session your using (/opt/zimbra/backup/sessions/full-XXXXXX/sessions.xml). If you need/want to change the referenced session label in the accounts.xml file - just vi it and use the global search and replace string (:%s/search_string/replacement_string/g).

Errors about mysql or ldap not running

This will most likely be encounter if you have to adjust some items in regards to the restore command not working. Run or confirm the following:

su - zimbra
zmconvertctl stop
mysql.server start
ldap start
zmconvertctl start

Then try the restore command again.

Jump to: navigation, search