BUS MS Exchange Issues - Revision history

Jamii: /* See Also */

2018-05-03T19:37:22Z

Cheeks: /* File size of SystemState.bkf not correct */

2011-11-16T20:10:26Z

File size of SystemState.bkf not correct

← Older revision		Revision as of 14:10, 16 November 2011
Line 25:		Line 25:

	Although this is not an official recommendation from Microsoft, this key will get recreated after the machine is restarted.		Although this is not an official recommendation from Microsoft, this key will get recreated after the machine is restarted.

			===Circular Logging===
			If you get an error like this:
			CExBackup::backupService:HrESEBackupSetup: Error Number 0xc800020e:
			An incremental backup cannot be performed when circular logging is enabled.

			In the Exchange admin thing, check that the properties for Exchange Storage Group and turn off circular logging. Note the circular logging is on by default in SBS.

			After turning off circular logging, restart the "Microsoft Exchange Information Store" service. Then perform a Full Backup of the MS Exchange server.

	==Exchange 2010==		==Exchange 2010==

Cheeks: /* File size of SystemState.bkf not correct */

2010-12-21T23:07:16Z

File size of SystemState.bkf not correct

← Older revision		Revision as of 17:07, 21 December 2010
Line 25:		Line 25:

	Although this is not an official recommendation from Microsoft, this key will get recreated after the machine is restarted.		Although this is not an official recommendation from Microsoft, this key will get recreated after the machine is restarted.

			==Exchange 2010==
			* Exchange 2010 requires the latest hotfix be applied to bring the BUS client up to version 5.5.7.4. You can download it here: ftp://ftp.swcp.com/pub/bus/hotfix_5574/ Download both the '''obm-win-5574-hotfix.zip''' and '''README''' files. Follow the instructions in the README to apply the update.

	==See Also==		==See Also==
	[[Category: BUS]]		[[Category: BUS]]
	[[Category: MS Exchange]]		[[Category: MS Exchange]]

Cheeks at 19:49, 7 November 2008

2008-11-07T19:49:15Z

@@ Line 15: / Line 15: @@
 If you get an error that looks like '''No *.stm found for database 'ServerX\Microsoft Information Store\First Storage Group\Mailbox Store (ServerX)' ''', this suggests that the .stm file on server may have been corrupted or found missing. To resolve this error, please perform a Full MS Exchange backup manually via OBM.
 [[Category: BUS]]
 [[Category: MS Exchange]]

Cheeks at 23:26, 22 October 2008

2008-10-22T23:26:00Z

← Older revision		Revision as of 17:26, 22 October 2008
Line 11:		Line 11:

	Alternatively, instead of backing up transaction logs during the weekdays, you can consider doing Full Exchange Database backup on a daily basis with the In-File Delta option enabled. This should avoid interference from other backup software while keeping the amount of upload data to a minimum.		Alternatively, instead of backing up transaction logs during the weekdays, you can consider doing Full Exchange Database backup on a daily basis with the In-File Delta option enabled. This should avoid interference from other backup software while keeping the amount of upload data to a minimum.

			===No *.stm found===
			If you get an error that looks like '''No *.stm found for database 'ServerX\Microsoft Information Store\First Storage Group\Mailbox Store (ServerX)' ''', this suggests that the .stm file on server may have been corrupted or found missing. To resolve this error, please perform a Full MS Exchange backup manually via OBM.

	[[Category: BUS]]		[[Category: BUS]]
	[[Category: MS Exchange]]		[[Category: MS Exchange]]

Cheeks: /* Expected log sequence 'xxx' but found 'SERVERNAME\Microsoft Information Store\First Storage Group\E000xxx.log' */

2008-06-24T20:25:11Z

Expected log sequence 'xxx' but found 'SERVERNAME\Microsoft Information Store\First Storage Group\E000xxx.log'

← Older revision		Revision as of 14:25, 24 June 2008
Line 10:		Line 10:
	To resolve this problem, you need to deactivate all other backup software that is operating on MS Exchange, and then you need to perform a Full MS Exchange database backup manually via OBM.		To resolve this problem, you need to deactivate all other backup software that is operating on MS Exchange, and then you need to perform a Full MS Exchange database backup manually via OBM.

	Alternatively, instead of backing up transaction logs during the weekdays, you can consider doing Full Exchange Database backup on a daily basis with the In-File Delta option enabled. This should avoid interference from other backup software while keeping the amount of upload data to ~~minimal~~.		Alternatively, instead of backing up transaction logs during the weekdays, you can consider doing Full Exchange Database backup on a daily basis with the In-File Delta option enabled. This should avoid interference from other backup software while keeping the amount of upload data to a minimum.

	[[Category: BUS]]		[[Category: BUS]]
	[[Category: MS Exchange]]		[[Category: MS Exchange]]

Cheeks at 19:50, 24 June 2008

2008-06-24T19:50:13Z

← Older revision		Revision as of 13:50, 24 June 2008
Line 1:		Line 1:
	There are two approaches to backing up Exchange: (a) the traditional approach of backing up the files which comprise Exchange and the message store or (b) "brick-level" backup of individual mailboxes and contact databases. Currently the SWCP BUS only supports the traditional method. "Brick-level" backups may be supported in a future version.		There are two approaches to backing up Exchange: (a) the traditional approach of backing up the files which comprise Exchange and the message store or (b) "brick-level" backup of individual mailboxes and contact databases. Currently the SWCP BUS only supports the traditional method. "Brick-level" backups may be supported in a future version.


			==Common Exchange Backup Problems==
			Here are some common errors encountered when doing Exchange backups and how to resolve them.

	===Expected log sequence 'xxx' but found 'SERVERNAME\Microsoft Information Store\First Storage Group\E000xxx.log'===		===Expected log sequence 'xxx' but found 'SERVERNAME\Microsoft Information Store\First Storage Group\E000xxx.log'===

Cheeks: /* BUS And Microsoft Exchange */

2008-06-24T19:49:29Z

BUS And Microsoft Exchange

← Older revision		Revision as of 13:49, 24 June 2008
Line 1:		Line 1:
	=BUS ~~And Microsoft Exchange=~~		There are two approaches to backing up Exchange: (a) the traditional approach of backing up the files which comprise Exchange and the message store or (b) "brick-level" backup of individual mailboxes and contact databases. Currently the SWCP BUS only supports the traditional method. "Brick-level" backups may be supported in a future version.


	===Expected log sequence 'xxx' but found 'SERVERNAME\Microsoft Information Store\First Storage Group\E000xxx.log'===		===Expected log sequence 'xxx' but found 'SERVERNAME\Microsoft Information Store\First Storage Group\E000xxx.log'===

Cheeks at 19:47, 24 June 2008

2008-06-24T19:47:45Z

← Older revision		Revision as of 13:47, 24 June 2008
Line 1:		Line 1:
			=BUS And Microsoft Exchange=

	===Expected log sequence 'xxx' but found 'SERVERNAME\Microsoft Information Store\First Storage Group\E000xxx.log'===		===Expected log sequence 'xxx' but found 'SERVERNAME\Microsoft Information Store\First Storage Group\E000xxx.log'===
	This error occurs when the log sequence of MS Exchange was altered by other backup software, e.g. NTBackup. Thus when OBM next performs a MS Exchange backup, the Exchange log sequence would not match the one that it is expecting. With the broken sequence, the Exchange server cannot be restored to its latest state.		This error occurs when the log sequence of MS Exchange was altered by other backup software, e.g. NTBackup. Thus when OBM next performs a MS Exchange backup, the Exchange log sequence would not match the one that it is expecting. With the broken sequence, the Exchange server cannot be restored to its latest state.

Cheeks at 19:47, 24 June 2008

2008-06-24T19:47:24Z

← Older revision		Revision as of 13:47, 24 June 2008
Line 5:		Line 5:

	Alternatively, instead of backing up transaction logs during the weekdays, you can consider doing Full Exchange Database backup on a daily basis with the In-File Delta option enabled. This should avoid interference from other backup software while keeping the amount of upload data to minimal.		Alternatively, instead of backing up transaction logs during the weekdays, you can consider doing Full Exchange Database backup on a daily basis with the In-File Delta option enabled. This should avoid interference from other backup software while keeping the amount of upload data to minimal.

			[[Category: BUS]]
			[[Category: MS Exchange]]

← Older revision		Revision as of 13:37, 3 May 2018
Line 40:		Line 40:
	==See Also==		==See Also==
	[[Category: BUS]]		[[Category: BUS]]
	~~[[Category: MS Exchange]]~~