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.

Comments

Post a Comment

Popular posts from this blog

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...
Post a Comment
Read more

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.
Post a Comment
Read more

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...
Post a Comment
Read more