20.12.8 Troubleshooting Backup and Restore Problems

This section describes common backup and restore problems and their solutions.

• Problem: msprobe restarts everything during a long imsrestore during message store migration. This can also happen with imsbackup, imsimport, or any processing intensive utility.

• Solution: When imsrestore or any processing intensive operation takes significantly more system resources than normal, and continues doing so longer than the msprobe interval, there may be a temporary backlog of DB transaction log files to be cleared. If there are more files than specified in local.store.maxlog, then msprobe may erroneously restart all the processes during a restore. To prevent this from happening, disable msprobe during the imsrestore.

• Problem: When I do an restore of a folder or INBOX using imsrestore or imsasm, it appends all the messages in that folder onto the current folder. This results in multiple copies of the messages in that folder.

  Solution: Make sure the -i flag of imsrestore is not set in the imsasm script.

• Problem: I want to do an incremental backup of just new messages added in a mail folder, but when I try, the entire folder gets backed up. How do I just back up the new messages?

  Solution: Set the -d datetime flag on imsbackup. This will backup messages stored from the specified date and time to the present. The default is to backup all messages regardless of their dates.