Seeding is the
process of making a complete copy of the source database file. Once the database file has been copied,
the asynchronous log file shipping can start. The database can either be manually copied, or copied
with the Update-StorageGroupCopy cmdlet.
The following cmdlets are necessary for seeding:
??‘ Suspend-StorageGroupCopy
??‘ Update-StorageGroupCopy
??‘ Resume-StorageGroupCopy
??‘ Get-StorageGroupCopyStatus
??‘ Get-StorageGroup
Chapter 12: Working with Continuous Replication
347
Seeding can also be required under the following conditions:
??‘ Initial seed
??‘ Offline defragmentation was run against the source database
??‘ Database divergence as a result of failover
??‘ The LCR or CCR copy is corrupt
??‘ Server loss
The process for seeding is the same for LCR, CCR, and SCR. First, Suspend-StorageGroupCopy stops
any current log replication. This step may not be necessary for a first - time seed.
Suspend-StorageGroupCopy -Identity < StorageGroupIdParameter >
[-DomainController < Fqdn > ] [-SuspendComment < String > ] [-WhatIf < Boolean > ]
[-Confirm < Boolean > ]
The SuspendComment is an optional string used for commenting on why the storage group was
suspended. Even though this is an optional parameter, it is a good idea to use it. For example, after a
disaster recovery the suspend comment in the event log can help pinpoint when tasks were done.
Pages:
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492