Setup Mirroring for the first time - Large DB

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi, I have a 500GB database I need to mirror across a 100MB WAN, I have
tested mirroring smaller databases without issue but these DB's were not in
use, my issue is this is a very important production DB and is in constant
use so while the backup and copy to the mirror server happens (20 hour
process) things will get out of sync, I found the below:

Read below from
http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/dbm_best_pract.mspx#EAMAE

Initial Synchronization Between Principal and Mirror:
Prior to establishing the database mirroring session, the database must be
restored on the mirror server, and be in the Restoring state. The most common
way to achieve this is to take an online backup of the database on the
principal, copy the backup to the mirror server, and restore it on the mirror
server with the option to apply further transaction logs.
Depending on the size of the database and the distance between the two
servers, it can take a long time to copy the backup and restore it on the
mirror server. During this time, it is possible that the principal database
has produced several transaction log backups. If the principal produces lots
of transaction log backups, you need a way to copy all the transaction log
backups and apply them on the mirror. If you don’t want to bother copying and
applying so many transaction log backups on the mirror, you can suspend
transaction log backups on the principal until the database on the mirror
server is restored and the database mirroring session is established. After
the database mirroring session is established, resume transaction log backups
on the principal. One thing to note in this approach is that during the time
that transaction log backups are suspended, the log file can grow; you need
to plan for enough disk space to account for the growth of the log file.

My question is not being a DBA and assuming suspending is the easiest for me
to do how do I actually suspend it? I've searched but cannot find anything
specific that tells me, btw it's SQL 2005 Std.

Thanks in advance for any help.

Mike
.

Relevant Pages

  • Re: replication
    ... mode, when a session begins, the mirror server synchronizes the mirror ... database with the principal database as quickly as possible. ... substantial if the principal server is under a heavy work load or the ...
    (comp.databases.ms-sqlserver)
  • RE: Database Mirroring or Log Shipping?
    ... Log Shipping nothing but moving tlog from Primary to Secondary once restored ... "Because the mirror database is in a recovering state, ... snapshots are not an option for us b/c we have SQL 2005 STD. ...
    (microsoft.public.sqlserver.replication)
  • RE: Database Mirroring or Log Shipping?
    ... "Because the mirror database is in a recovering state, ... snapshots are not an option for us b/c we have SQL 2005 STD. ... Maybe Log Shipping is an alternative, but thought that I read that Log ...
    (microsoft.public.sqlserver.replication)
  • RE: Database Mirroring or Log Shipping?
    ... I used SSMS to configure the Log Shipping in 2005 and it seems to get the ... Josh Blair (hfdev) ... "Because the mirror database is in a recovering state, ...
    (microsoft.public.sqlserver.replication)
  • Re: The remote copy of database is not recovered far enough to enable database mirroring.
    ... How about taking a up to date transactional log backup from the primary and restore it in norecovery mode to the mirror database and then finalize the setting up your database mirroring operation? ... on my mirror server, I then received the error "The remote copy of ...
    (microsoft.public.sqlserver.replication)