Skip to main content

Solution for Exchange 2007 CCR Database copy status that becomes suspended

 Exchange 2007 CCR Database copy status becomes “suspended”

Due to various reasons your CCR replication could get stopped and your Database copy status becomes “suspended”. Even though Active Database is online and working normal,
This Article will help you to manually seed the passive database and re-start your CCR replication and to change the copy status to “Healthy”
In this scenario I have my Active CCR node call “Node A” and passive node call “Node B”, and my Exchange virtual server name is “EgyEngDotCom
Assume that your current status of the CCR copy is “suspended” if not you can use the following command to suspend the replication.

1. Suspend-StorageGroupCopy -Identity: “
Example : Suspend-StorageGroupCopy -Identity: “EgyEngDotCom\First Storage Group”

If you check your exchange management console you will see the status changed to “suspended”

2. Remove database files, all log files, and checkpoint files from the passive node.
Delete *.log, *.jrs, *.chk, and the .edb files from the configured directories (logs directory, the system files directory, and the directory hosting the database file).

3. On the passive node run the following command to seed the passive database using command shell

Update-StorageGroupCopy -Identity:
Example : Update-StorageGroupCopy -Identity: “EgyEngDotCom\First Storage Group”

You will see a progress bar similar to the following image

4. Once its finishes you can use following cmdlet command to resume the replication

Resume-StorageGroupCopy -Identity:\
Example : Resume-StorageGroupCopy -Identity: “EgyEngDotCom\First Storage Group”

Seeding is required under the following conditions:
- When a new passive node is introduced into a cluster continuous replication (CCR) environment and the first log file of the production storage group is not available.
- After a failover occurs in which data is lost as a result of the now passive copy having become diverged and unrecoverable.
- When the system has detected a corrupted log file that cannot be replayed into the passive copy.
- After an offline defragmentation of either copy of the database occurs.
- After a page scrubbing of the active copy of a database occurs, and you want to propagate the changes to the passive copy.
- After the log generation sequence for the storage group has been reset back to 1.


Popular posts from this blog

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu

Unlock the VMware VM vmdk file

  Unlock the VMware VM vmdk file Kill -9 PID Sometimes a file or set of files in a VMFS become locked and any attempts to edit them or delete will give a device or resource busy error, even though the vm associated with the files is not running. If the vm is running then you would need to stop the vm to manipulate the files. If you know that the vm is stopped then you need to find the ESX server that has the files locked and then stop the process that is locking the file(s). 1. Logon to the ESX host where the VM was last known to be running. 2.  vmkfstools -D /vmfs/volumes/path/to/file  to dump information on the file into /var/log/vmkernel 3.  less /var/log/vmkernel  and scroll to the bottom, you will see output like below: a. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)FS3: 130: <START vmware-16.log> b. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)Lock [type 10c00001 offset 30439424 v 21, hb offset 4154368 c. Nov 29 15:49:17 vm22 vmkernel: gen 664