إضغط لتفاصيل الإعلانات



Results 1 to 2 of 2
Share
  1. #1
    Join Date
    Nov 2007
    Location
    Arab world!
    Posts
    6,169
    Blog Entries
    4
    Rep Power
    10

    Arrow 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.
    Last edited by Mohamed Fouad; 25-07-2010 at 07:37 PM.


  2. Facebook Comments - تعليقـك على الفيس بوك يسعدنا ويطور مجهوداتنـا


  3. Forum Ads:

  4. Forum Ads:

    اضفط هنا لمعرفة تفاصيل الإعلانات بالموقع


  5. Forum Ads:

    -->

  6. #2
    Join Date
    Jan 2008
    Location
    Egypt
    Posts
    3,946
    Blog Entries
    1
    Rep Power
    16

Similar Threads

  1. Replies: 0
    Last Post: 05-05-2011, 12:31 PM
  2. Replies: 0
    Last Post: 26-12-2010, 06:31 PM
  3. Replies: 0
    Last Post: 07-12-2010, 09:14 PM
  4. Database Availability Group (DAG) - Exchange 2010
    By Mohamed Fouad in forum Microsoft
    Replies: 2
    Last Post: 23-08-2010, 11:31 AM
  5. Replies: 2
    Last Post: 21-05-2010, 03:54 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

أقسام المنتدى

الروابط النصية

تابع جروبنا على الفيس بوك

صفحة Egypt Engineers على الفيس بوك

تابعنا على linkedin

جروبنا على الياهو جروب