When you consider what is actually done by the maintenance process, e.g. hard deletion of any relevant messages and mailboxes and recovery of white space, I'd say backing up a cleanly re-jigged (technical term!) database is probably a good thing.
I've not personally heard of the online maintenance causing any database problems. If I had, then you could argue that backing it up before maintenance would be better. If you had, say, severe database problems that resulted in the dreaded -1018 error, then both the online maintenance and backup procedure would reveal this problem, so it wouldn't matter which way round you did them. Neil -----Original Message----- From: STACKHOUSE, TODD -CONT(DYN) [mailto:[EMAIL PROTECTED]] Posted At: 16 January 2002 13:03 Posted To: Sunbelt Exchange List Conversation: backup/db maintenance "best practices Subject: backup/db maintenance "best practices Currently, we run the IS maintenance (defaults) after doing our nightly backup. Is there any benefit to running the maintenance before the backup? List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual to whom it is addressed. Any view or opinions presented are solely those of the author and do not necessarily represent those of Silversands, or any of its subsidiary companies. If you have received this email in error, please contact our Support Desk immediately by telephone on 01202-360000 or via email at [EMAIL PROTECTED] ********************************************************************** List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
