Exchange Disaster Recovery, Mailbox store not mounting,
This is'nt urgent as its on a duplicate test lab.
Its also on totally differant hardware to the original.
Ive setup a duplicated 2003 domain with a mix of 2003 standard and 2003 Standard R2 exactly as is on the live network onto a test lab, I used a system state backup etc to mimmick the test domain, seized the fsmo roles imported all the GPOs etc all works perfectly and all DCs and the same IP on all the DC's/DHCP/DNS servers setup with the same netbios everything has the same paths.
The only thing that is differant is the servers/hardware is totally differant along with the fact that this test domain is not connected to the web so apart from the MS Service packs being installed there are no MS Updates installed as is on the live domain. THIS MAY WELL BE PART OF MY PROBLEM NOT SURE.
Exchange
Ive imported the live exchange server info store via a usb drive,
used ntbackup to then restore only the mailbox store ont the test labs exchange server which is setup identical to the original exchange, ie info store has the same path etc.
It failed the 1st time which was no surprise, so Ive since ran
eseutil /mh
this shows it was a dirty shutdown,
I then ran
eseutil /p
This then leaves it in a clean shutdown,
I then ran
eseutil /d
not so sure if this actually completes correctly the defrag as it shows 100% in approx 15 seconds flat even though the stores ( recovery/ and main store are both offline).
I then try to remount and receive the following which believe me when I say Ive tried countless fixes Ive got a sneaking feeling its to do with the incorrect e000.logs but I could be mistaken their which is why Im asking on here.
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Description: Error 0xfffff745 starting database "First Storage Group\Mailbox Store (MAIL1)" on the Microsoft Exchange Information Store. Failed to attach to Jet DB.
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Description: Error 0xfffff745 starting Storage Group /DC=COM/DC=COMPANY/CN=CONF
Ive tried this fix with no joy
http://www.innovativetechnologyconcepts.com/Exchange_Server_Error_0xffff745.htm
I tried running isinteg but it gave an error indicating I was inputting the incorrect syntax which I was sure I was doing it correct as I was correct according to all the MS white papers, I cant give you that exact error at the moment as Im running another eseutil /p at the moment on a differant exchange backup which Ive imported from backup but off the same live exchange server just to see if it was the bkf that was corrupt.
ANY SUGGESTIONS WELCOME
AS APART FROM THIS IVE GOT A PERFECTLY SETUP TEST LAB MIMMICKING EXACTLY THE LIVE DOMAIN, ITS JUST MOUNTING WHICH IS CAUSING ME PROBLEMS.
Im using the recovery storage group option, to recover
Its also on totally differant hardware to the original.
Ive setup a duplicated 2003 domain with a mix of 2003 standard and 2003 Standard R2 exactly as is on the live network onto a test lab, I used a system state backup etc to mimmick the test domain, seized the fsmo roles imported all the GPOs etc all works perfectly and all DCs and the same IP on all the DC's/DHCP/DNS servers setup with the same netbios everything has the same paths.
The only thing that is differant is the servers/hardware is totally differant along with the fact that this test domain is not connected to the web so apart from the MS Service packs being installed there are no MS Updates installed as is on the live domain. THIS MAY WELL BE PART OF MY PROBLEM NOT SURE.
Exchange
Ive imported the live exchange server info store via a usb drive,
used ntbackup to then restore only the mailbox store ont the test labs exchange server which is setup identical to the original exchange, ie info store has the same path etc.
It failed the 1st time which was no surprise, so Ive since ran
eseutil /mh
this shows it was a dirty shutdown,
I then ran
eseutil /p
This then leaves it in a clean shutdown,
I then ran
eseutil /d
not so sure if this actually completes correctly the defrag as it shows 100% in approx 15 seconds flat even though the stores ( recovery/ and main store are both offline).
I then try to remount and receive the following which believe me when I say Ive tried countless fixes Ive got a sneaking feeling its to do with the incorrect e000.logs but I could be mistaken their which is why Im asking on here.
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Description: Error 0xfffff745 starting database "First Storage Group\Mailbox Store (MAIL1)" on the Microsoft Exchange Information Store. Failed to attach to Jet DB.
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Description: Error 0xfffff745 starting Storage Group /DC=COM/DC=COMPANY/CN=CONF
Ive tried this fix with no joy
http://www.innovativetechnologyconcepts.com/Exchange_Server_Error_0xffff745.htm
I tried running isinteg but it gave an error indicating I was inputting the incorrect syntax which I was sure I was doing it correct as I was correct according to all the MS white papers, I cant give you that exact error at the moment as Im running another eseutil /p at the moment on a differant exchange backup which Ive imported from backup but off the same live exchange server just to see if it was the bkf that was corrupt.
ANY SUGGESTIONS WELCOME
AS APART FROM THIS IVE GOT A PERFECTLY SETUP TEST LAB MIMMICKING EXACTLY THE LIVE DOMAIN, ITS JUST MOUNTING WHICH IS CAUSING ME PROBLEMS.
Im using the recovery storage group option, to recover
rakeshmiglani
did you remove the logs after /p and /d were run?
ASKER
To be honest I ve tried that many options its all starting to become a blur.
But it should be completed shortly the eseutil /p
so after the /d
I will make sure the logs are cleared will come back to you in approx 1hour ish.
But it should be completed shortly the eseutil /p
so after the /d
I will make sure the logs are cleared will come back to you in approx 1hour ish.
ASKER
Eseutil /p and /d have finnished however the problem now is that it is stripping out all the data from the edb, by that I mean the edb started out as 15gig but now ends up at 2meg believe it or not.
and will not mount of course.
below is the output from eseutil.
Unfortunately I missed part of the initial
eseutil /mh
but the rest is there. Im now in the process of copying another BKF backup of the original live exchange over to a USB H/D to copy over to the test exchange to then restore that, however Im not sure why eseutil /p is stripping it away completely.
**************************
cbDbPage: 4096
dbtime: 44553267 (0-44553267)
State: Dirty Shutdown
Log Required: 11915-11915
Streaming File: Yes
Shadowed: Yes
Last Objid: 29236
Scrub Dbtime: 0 (0-0)
Scrub Date: 00/00/1900 00:00:00
Repair Count: 0
Repair Date: 00/00/1900 00:00:00
Last Consistent: (0x2E8B,13FE,8F) 01/06/2007 15:50:19
Last Attach: (0x2E8B,1406,3C) 01/06/2007 15:54:09
Last Detach: (0x0,0,0) 00/00/1900 00:00:00
Dbid: 2
Log Signature: Create time:11/23/2005 16:47:17 Rand:205379 Computer:
OS Version: (5.2.3790 SP 1)
Previous Full Backup:
Log Gen: 11872-11877 (0x2e60-0x2e65)
Mark: (0x2E64,20BE,176)
Mark: 01/05/2007 23:13:21
Current Incremental Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Current Full Backup:
Log Gen: 11915-0 (0x2e8b-0x0)
Mark: (0x2E8B,148B,A4)
Mark: 01/06/2007 15:57:48
Current snapshot backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
cpgUpgrade55Format: 0
cpgUpgradeFreePages: 0
cpgUpgradeSpaceMapPages: 0
Patch Current Full Backup:
Log Gen: 11915-11915 (0x2e8b-0x2e8b)
Mark: (0x2E8B,148B,A4)
Mark: 01/06/2007 15:57:48
Operation completed successfully in 1.31 seconds.
C:\Program Files\Exchsrvr\bin>eseutil
age Group\
Usage Error: Invalid mode.
Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.
DESCRIPTION: Maintenance utilities for Microsoft(R) Exchange Server databases.
MODES OF OPERATION:
Defragmentation: ESEUTIL /d <database name> [options]
Recovery: ESEUTIL /r <logfile base name> [options]
Integrity: ESEUTIL /g <database name> [options]
File Dump: ESEUTIL /m[mode-modifier] <filename>
Repair: ESEUTIL /p <database name> [options]
Restore: ESEUTIL /c[mode-modifier] <path name> [options]
Checksum: ESEUTIL /k <file name> [options]
Copy File: ESEUTIL /y <source file> [options]
<<<<< Press a key for more help >>>>>
D=Defragmentation, R=Recovery, G=Integrity, M=File Dump, P=Repair, C=Restore, K=
Checksum, Y=Copy File
=>
C:\Program Files\Exchsrvr\bin>eseutil
rage Group\mailbox store (exchange2)0.edb"
Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating REPAIR mode...
Database: C:\Program Files\Exchsrvr\Recovery Storage Group\mailbox store
(exchange2)0.edb
Streaming File: C:\Program Files\Exchsrvr\Recovery Storage Group\mailbox store
(exchange2)0.STM
Temp. Database: TEMPREPAIR2820.EDB
Checking database integrity.
The database is not up-to-date. This operation may find that
this database is corrupt because data from the log files has
yet to be placed in the database.
To ensure the database is up-to-date please use the 'Recovery' operation.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
Scanning the database catalog.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Rebuilding MSysObjects.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Rebuilding MSysObjectsShadow from MSysObjects.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Checking the database.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Scanning the database.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Repairing damaged tables.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Repair completed. Database corruption has been repaired!
Note:
It is recommended that you immediately perform a full backup
of this database. If you restore a backup made before the
repair, the database will be rolled back to the state
it was in at the time of that backup.
Operation completed successfully with 595 (JET_wrnDatabaseRepaired, Database cor
ruption has been repaired) after 14089.703 seconds.
C:\Program Files\Exchsrvr\bin>eseutil
rage Group\mailbox store (exchange2)0.edb"
Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating DEFRAGMENTATION mode...
Database: C:\Program Files\Exchsrvr\Recovery Storage Group\mailbox s
tore (exchange2)0.edb
Streaming File: C:\Program Files\Exchsrvr\Recovery Storage Group\mailbox s
tore (exchange2)0.STM
Temp. Database: TEMPDFRG3740.EDB
Temp. Streaming File: TEMPDFRG3740.STM
Defragmentation Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Moving 'TEMPDFRG3740.EDB' to 'C:\Program Files\Exchsrvr\Recovery Storage Group\M
ailbox Store (EXCHANGE2)0.edb'... DONE!
Moving 'TEMPDFRG3740.STM' to 'C:\Program Files\Exchsrvr\Recovery Storage Group\M
ailbox Store (EXCHANGE2)0.stm'... DONE!
Note:
It is recommended that you immediately perform a full backup
of this database. If you restore a backup made before the
defragmentation, the database will be rolled back to the state
it was in at the time of that backup.
Operation completed successfully in 6.907 seconds.
C:\Program Files\Exchsrvr\bin>eseutil
orage Group\mailbox store (exchange2)0.edb"
Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating FILE DUMP mode...
Database: C:\Program Files\Exchsrvr\Recovery Storage Group\mailbox stor
e (exchange2)0.edb
File Type: Database
Format ulMagic: 0x89abcdef
Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,9
Engine ulVersion: 0x620,9
Created ulVersion: 0x620,9
DB Signature: Create time:02/28/2007 13:34:28 Rand:165996586 Computer:
cbDbPage: 4096
dbtime: 723 (0-723)
State: Clean Shutdown
Log Required: 0-0
Streaming File: Yes
Shadowed: Yes
Last Objid: 7
Scrub Dbtime: 0 (0-0)
Scrub Date: 00/00/1900 00:00:00
Repair Count: 0
Repair Date: 00/00/1900 00:00:00
Last Consistent: (0x0,0,0) 02/28/2007 13:34:30
Last Attach: (0x0,0,0) 02/28/2007 13:34:30
Last Detach: (0x0,0,0) 02/28/2007 13:34:30
Dbid: 2
Log Signature: Create time:00/00/1900 00:00:00 Rand:0 Computer:
OS Version: (5.2.3790 SP 1)
Previous Full Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Current Incremental Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Current Full Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Current snapshot backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
cpgUpgrade55Format: 0
cpgUpgradeFreePages: 0
cpgUpgradeSpaceMapPages: 0
Operation completed successfully in 1.47 seconds.
C:\Program Files\Exchsrvr\bin>eseutil
rage Group\mailbox store (exchange2)0.edb"
Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating INTEGRITY mode...
Database: C:\Program Files\Exchsrvr\Recovery Storage Group\mailbox store
(exchange2)0.edb
Streaming File: C:\Program Files\Exchsrvr\Recovery Storage Group\mailbox store
(exchange2)0.STM
Temp. Database: TEMPINTEG3868.EDB
Checking database integrity.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Integrity check successful.
Operation completed successfully in 4.63 seconds.
C:\Program Files\Exchsrvr\bin>
and will not mount of course.
below is the output from eseutil.
Unfortunately I missed part of the initial
eseutil /mh
but the rest is there. Im now in the process of copying another BKF backup of the original live exchange over to a USB H/D to copy over to the test exchange to then restore that, however Im not sure why eseutil /p is stripping it away completely.
**************************
cbDbPage: 4096
dbtime: 44553267 (0-44553267)
State: Dirty Shutdown
Log Required: 11915-11915
Streaming File: Yes
Shadowed: Yes
Last Objid: 29236
Scrub Dbtime: 0 (0-0)
Scrub Date: 00/00/1900 00:00:00
Repair Count: 0
Repair Date: 00/00/1900 00:00:00
Last Consistent: (0x2E8B,13FE,8F) 01/06/2007 15:50:19
Last Attach: (0x2E8B,1406,3C) 01/06/2007 15:54:09
Last Detach: (0x0,0,0) 00/00/1900 00:00:00
Dbid: 2
Log Signature: Create time:11/23/2005 16:47:17 Rand:205379 Computer:
OS Version: (5.2.3790 SP 1)
Previous Full Backup:
Log Gen: 11872-11877 (0x2e60-0x2e65)
Mark: (0x2E64,20BE,176)
Mark: 01/05/2007 23:13:21
Current Incremental Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Current Full Backup:
Log Gen: 11915-0 (0x2e8b-0x0)
Mark: (0x2E8B,148B,A4)
Mark: 01/06/2007 15:57:48
Current snapshot backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
cpgUpgrade55Format: 0
cpgUpgradeFreePages: 0
cpgUpgradeSpaceMapPages: 0
Patch Current Full Backup:
Log Gen: 11915-11915 (0x2e8b-0x2e8b)
Mark: (0x2E8B,148B,A4)
Mark: 01/06/2007 15:57:48
Operation completed successfully in 1.31 seconds.
C:\Program Files\Exchsrvr\bin>eseutil
age Group\
Usage Error: Invalid mode.
Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.
DESCRIPTION: Maintenance utilities for Microsoft(R) Exchange Server databases.
MODES OF OPERATION:
Defragmentation: ESEUTIL /d <database name> [options]
Recovery: ESEUTIL /r <logfile base name> [options]
Integrity: ESEUTIL /g <database name> [options]
File Dump: ESEUTIL /m[mode-modifier] <filename>
Repair: ESEUTIL /p <database name> [options]
Restore: ESEUTIL /c[mode-modifier] <path name> [options]
Checksum: ESEUTIL /k <file name> [options]
Copy File: ESEUTIL /y <source file> [options]
<<<<< Press a key for more help >>>>>
D=Defragmentation, R=Recovery, G=Integrity, M=File Dump, P=Repair, C=Restore, K=
Checksum, Y=Copy File
=>
C:\Program Files\Exchsrvr\bin>eseutil
rage Group\mailbox store (exchange2)0.edb"
Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating REPAIR mode...
Database: C:\Program Files\Exchsrvr\Recovery Storage Group\mailbox store
(exchange2)0.edb
Streaming File: C:\Program Files\Exchsrvr\Recovery Storage Group\mailbox store
(exchange2)0.STM
Temp. Database: TEMPREPAIR2820.EDB
Checking database integrity.
The database is not up-to-date. This operation may find that
this database is corrupt because data from the log files has
yet to be placed in the database.
To ensure the database is up-to-date please use the 'Recovery' operation.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
Scanning the database catalog.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Rebuilding MSysObjects.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Rebuilding MSysObjectsShadow from MSysObjects.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Checking the database.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Scanning the database.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Repairing damaged tables.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Repair completed. Database corruption has been repaired!
Note:
It is recommended that you immediately perform a full backup
of this database. If you restore a backup made before the
repair, the database will be rolled back to the state
it was in at the time of that backup.
Operation completed successfully with 595 (JET_wrnDatabaseRepaired, Database cor
ruption has been repaired) after 14089.703 seconds.
C:\Program Files\Exchsrvr\bin>eseutil
rage Group\mailbox store (exchange2)0.edb"
Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating DEFRAGMENTATION mode...
Database: C:\Program Files\Exchsrvr\Recovery Storage Group\mailbox s
tore (exchange2)0.edb
Streaming File: C:\Program Files\Exchsrvr\Recovery Storage Group\mailbox s
tore (exchange2)0.STM
Temp. Database: TEMPDFRG3740.EDB
Temp. Streaming File: TEMPDFRG3740.STM
Defragmentation Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Moving 'TEMPDFRG3740.EDB' to 'C:\Program Files\Exchsrvr\Recovery Storage Group\M
ailbox Store (EXCHANGE2)0.edb'... DONE!
Moving 'TEMPDFRG3740.STM' to 'C:\Program Files\Exchsrvr\Recovery Storage Group\M
ailbox Store (EXCHANGE2)0.stm'... DONE!
Note:
It is recommended that you immediately perform a full backup
of this database. If you restore a backup made before the
defragmentation, the database will be rolled back to the state
it was in at the time of that backup.
Operation completed successfully in 6.907 seconds.
C:\Program Files\Exchsrvr\bin>eseutil
orage Group\mailbox store (exchange2)0.edb"
Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating FILE DUMP mode...
Database: C:\Program Files\Exchsrvr\Recovery Storage Group\mailbox stor
e (exchange2)0.edb
File Type: Database
Format ulMagic: 0x89abcdef
Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,9
Engine ulVersion: 0x620,9
Created ulVersion: 0x620,9
DB Signature: Create time:02/28/2007 13:34:28 Rand:165996586 Computer:
cbDbPage: 4096
dbtime: 723 (0-723)
State: Clean Shutdown
Log Required: 0-0
Streaming File: Yes
Shadowed: Yes
Last Objid: 7
Scrub Dbtime: 0 (0-0)
Scrub Date: 00/00/1900 00:00:00
Repair Count: 0
Repair Date: 00/00/1900 00:00:00
Last Consistent: (0x0,0,0) 02/28/2007 13:34:30
Last Attach: (0x0,0,0) 02/28/2007 13:34:30
Last Detach: (0x0,0,0) 02/28/2007 13:34:30
Dbid: 2
Log Signature: Create time:00/00/1900 00:00:00 Rand:0 Computer:
OS Version: (5.2.3790 SP 1)
Previous Full Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Current Incremental Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Current Full Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Current snapshot backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
cpgUpgrade55Format: 0
cpgUpgradeFreePages: 0
cpgUpgradeSpaceMapPages: 0
Operation completed successfully in 1.47 seconds.
C:\Program Files\Exchsrvr\bin>eseutil
rage Group\mailbox store (exchange2)0.edb"
Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating INTEGRITY mode...
Database: C:\Program Files\Exchsrvr\Recovery Storage Group\mailbox store
(exchange2)0.edb
Streaming File: C:\Program Files\Exchsrvr\Recovery Storage Group\mailbox store
(exchange2)0.STM
Temp. Database: TEMPINTEG3868.EDB
Checking database integrity.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
..........................
Integrity check successful.
Operation completed successfully in 4.63 seconds.
C:\Program Files\Exchsrvr\bin>
how are you doing the restore?
are you restoring it to a recovery storage group or the mailbox store on this server?
are you restoring it to a recovery storage group or the mailbox store on this server?
ASKER
Recovery storage group
after restoring run eseutil as it never mounts after the restore.
Thats where it rips the edb right back to a couple of meg as oppose to 15 gig
Just waiting for the new bkf to copy across at the moment from the usb with a differant backup of the live exchange.
can try any way you suggest as Ive exhausted all avenues I think
after restoring run eseutil as it never mounts after the restore.
Thats where it rips the edb right back to a couple of meg as oppose to 15 gig
Just waiting for the new bkf to copy across at the moment from the usb with a differant backup of the live exchange.
can try any way you suggest as Ive exhausted all avenues I think
is this an online backup that you are trying to restore?
if yes then are you using ntbackup to restore this bkf file?
if yes to ntbackup then what options do you select while doing the restore?
if yes then are you using ntbackup to restore this bkf file?
if yes to ntbackup then what options do you select while doing the restore?
ASKER
Sorry I could'nt come back to you earlier;
To restore the mailbox store to the Recover Group using NTBACKUP
1 Tick this DB can be overwritten by a restore on Recovery Mailbox store
2 Dismount Recovery Mailbox Store
3 Now run NTBACKUP
4 In NTBACKUP using restore wizard
Select Mailbox store to be retored
Leave unticked Log files
5 Set Temp location for log and patch files, ie: C:\Temp
6 Tick Last restore set (log file replay will start after this restore completes)
Leave unticked Mount mailbox store after restore
It never mounts after the restore in the Recovery Group so no point trying in the main mailbox store.
After restore completes I then run eseutil /mh which shows dirty shutdown so then run /p and /d
This is where its being stripping out the data.
At the moment I have another BKF waiting to be restored so will now try your suggestion.
To restore the mailbox store to the Recover Group using NTBACKUP
1 Tick this DB can be overwritten by a restore on Recovery Mailbox store
2 Dismount Recovery Mailbox Store
3 Now run NTBACKUP
4 In NTBACKUP using restore wizard
Select Mailbox store to be retored
Leave unticked Log files
5 Set Temp location for log and patch files, ie: C:\Temp
6 Tick Last restore set (log file replay will start after this restore completes)
Leave unticked Mount mailbox store after restore
It never mounts after the restore in the Recovery Group so no point trying in the main mailbox store.
After restore completes I then run eseutil /mh which shows dirty shutdown so then run /p and /d
This is where its being stripping out the data.
At the moment I have another BKF waiting to be restored so will now try your suggestion.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ive had enough of messing with NTBACKUP,
Im going to install Veritas on the test lab and copy across one of the veritas Online backups from the live exchange server as Ive had enough of this.
Each time I get the DB into a clean state and check its file size after running eseutil /p the db file size is the correct original size, I reboot and its still the correct size,
the very instant I use eseutil /d I loose the db, by that I mean it shrinks down to apprx 1mb.
eseutil /p is running one last time at the moment while I start installing veritas etc, after eseutil /p has completed and if eseutil /mh shows the db in a clean state as it always does I will at that point try to mount it, if it mounts great, if not I'll give the veritas backups a crack.
Im going to install Veritas on the test lab and copy across one of the veritas Online backups from the live exchange server as Ive had enough of this.
Each time I get the DB into a clean state and check its file size after running eseutil /p the db file size is the correct original size, I reboot and its still the correct size,
the very instant I use eseutil /d I loose the db, by that I mean it shrinks down to apprx 1mb.
eseutil /p is running one last time at the moment while I start installing veritas etc, after eseutil /p has completed and if eseutil /mh shows the db in a clean state as it always does I will at that point try to mount it, if it mounts great, if not I'll give the veritas backups a crack.
ASKER
Working now with Veritas,
I assume the previous 2 sets of NTBACKUP bkfs for some strange reason were corrupt and could not be recovered using eseutil /p
(strange).
I used Veritas 10D and bang first attempt both stores mounted Priv n Pub.
Why have I got NTBACKUP and veritas both backing up exchange at differant times (hmmm good question, but ntbackup was setup here years ago by whoever was here before me and Ive just scheduled veritas to backup exchange outside ntbackups time slot,
time I guess I turned ntbackup off altogether as I personnally backup the entire domain using veritas).
Sorry for not getting back to you earlier but as this is a testlab obviously it dosent take priority.
Now its time to start testing various scenario's.
Thanks for your comments.
Roy
I assume the previous 2 sets of NTBACKUP bkfs for some strange reason were corrupt and could not be recovered using eseutil /p
(strange).
I used Veritas 10D and bang first attempt both stores mounted Priv n Pub.
Why have I got NTBACKUP and veritas both backing up exchange at differant times (hmmm good question, but ntbackup was setup here years ago by whoever was here before me and Ive just scheduled veritas to backup exchange outside ntbackups time slot,
time I guess I turned ntbackup off altogether as I personnally backup the entire domain using veritas).
Sorry for not getting back to you earlier but as this is a testlab obviously it dosent take priority.
Now its time to start testing various scenario's.
Thanks for your comments.
Roy