Article Content King

You are viewing: EDB Recovery In Case of Recovery Storage Group Failure
By Axel Culver

EDB Recovery In Case of Recovery Storage Group Failure

Articles - Computers - Data-Recovery - View Article



Publish this article

Recovery Storage Group or RSG is the most significant administrator friendly characteristic of Microsoft Exchange Server, which allows you to mount a second copy of Exchange mailbox store on same computer as original mailbox store (database) or on another computer that is in same administrative group. It helps you to recover mailboxes without installing and configuring separate EDB Recovery computer.

In Exchange Server 2000 and earlier versions, you need to configure separate Microsoft Active Directory service on recovery service when you want to mount other copy of production Exchange Server database. With RSG feature in MS Exchange Server 2003, you do not need to have separate Exchange Server. After creating RSG and you add database to it, you can restore either restore online or copy offline database files. To extract data from recovered database in RSG, use Exmerge.exe (Microsoft Exchange Mailbox Merge Wizard).

In order to use RSG, the Active Directory topology of Exchange Server must be intact and in same state when database copy was created. The Recovery Storage Group feature isn't intended for use in the disaster recovery planning, which includes multiple servers and storage groups. This features is helpful in following situations:

1.Logical information in the Active Directory about storage group and containing mailboxes is unchanged and intact.
2.You need to retrieve data from single mailbox, single database, or a group of databases in single storage group.

The Exchange Server Information Store Service automatically redirects all Exchange Server Repair processes to Recovery Storage Group. In case if the database, which is selected for restore operation is not present, restore operation gets terminated and the following events logged into Application Event Log:
Event Type: Error
Event Source: ESE BACKUP
Event Category: Callback
Event ID: 904
Computer: EXCHANGE
Description: Information Store (4000) Callback function call ErrESECBRestoreGetDestination ended with error 0xC7FE1F42 Database not found.

In such situations, the restoration can not complete successfully and thus data database remains inaccessible. These circumstances might occur due to corruption to the EDB file. Severe corruption might cause serious data loss situations and require EDB Recovery to be fixed.

Recovery is potential through powerful and effective third party Exchange Server Recovery software. These applications use efficient scanning mechanisms to methodically scan the EDB file and extract all of its objects. These EDB Recovery Tools are completely easy and safe to use.

Stellar Phoenix Mailbox Exchange Recovery is the most effective and powerful Recover EDB tool to repair and restore corrupt EDB file in most of the cases. It works well with Exchange Server 2003, 2000 and 5.5. This software is compatible with Microsoft Windows 2003, XP and 2000.

See All articles From Author

Axel Culver has passion for writing Technical article. He is right now writing articles related to Product like EDB Recovery and EDB Recovery Tool. He is a professional writer and has written many technical articles, press relaese, blogs and journals.

Article Source : http://www.articlecontentking.com

Tags: edb recovery edb recovery software edb recover tool recover edb file recover corrupt edb file Exchange Server Recovery Outlook Mailbox recovery recover .edb database files Outlook express mail recovery.

Word Count Appx. : 422 | Article Views 828 Published 07-09-2009


Related articles
Hard Drive Recovery Is Not For the Faint of Heart
By: Tom Stabler | 29-06-2009
I went to work and during lunch I purchased a new hard drive. When I got home I told my wife that everything was under control. I installed the new hard drive and using my most recent backups (six months old) and the recovery disks, I was able to get & (read entire article)
Data Recovery
By: Russell Phillips | 05-11-2008
Memory storage has witnessed a technological revolution in the last few years, from the big sized floppy disks that allowed nothing over a mere megabyte of data to the gigabytes that we can easily store on a Flash today. (read entire article)
Logical Corruption and Bad Page Error in Exchange Server Database
By: Axel Culver | 25-10-2009

Logical corruption in Microsoft Exchange Server database (EDB) is very problematic and quite difficult to identify and repair than physical damage. The administrators and users are generally unaware of logical corruption to EDB file.

(read entire article)
Data Recovery and Your Computer
By: Clive Haman | 11-12-2009

Data recovery for your computer

(read entire article)
Boot Sector Corruption and File Loss Due to Power Off/Shutdown in Windows
By: Richard Dawson | 06-10-2009

Sometimes you may face boot sector corruption issues on a Windows NT-based operating system computer, if you've installed the operating system on a FAT file system formatted partition. In such situations, the computer might not start properly, when you (read entire article)

How to Recover Data From a Failed Hard Drive
By: Stephen Drummonsy | 09-05-2010

This article will help you to recover hard drive data before it is too late.

(read entire article)
Easy way for removing duplicate Outlook contacts
By: mac nicolson | 04-10-2010

Contacts imported to PST file results in duplicity of contact information. But duplicate Outlook contacts are easy to remove from PST file using manual methods. Also, there is an efficient tool to remove duplicate contacts in much easier way.

(read entire article)
The Fix Computer Problems Virus Scan Guide
By: Bryon Zirker | 20-12-2009

Downsides to ineffective repairs and loading the OS new include having...

(read entire article)
Exchange Server 2000 and 2003 Databases Dismount due to Exhaustion of
By: Axel Culver | 29-12-2009

Exchange Server supports transaction logging and numbers them sequentially. It starts naming them from E nn 00001.log and goes on till E nnffff0.log, where nn represents the storage group number.

(read entire article)