Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.ms-sqlserver > #1573

Re: Database Mirroring (resynching the database every time a mirror is broken)

Cross-posted to 4 groups.

Show all headers | View raw

On 2011-01-31, Query Builder <querybuilder@gmail.com> wrote:
> I use Database mirroring extensively in my disaster recovery site. I
> have my primary site and DR site in different geographical location.
> So far the mirroring is been  stable and does the job without any
> manual intervention. We have implemented TDE and I am able to set the
> mirroring with the certs installed on both primary and DR.
>
> But now I have a situation that my database backups have grown to be
> big because of the TDE.. The issue I have is the need to resynch the
> database each time I had to do a DR Drill to take the standby DB out
> of mirror or database maintenance such as adding a file group to the
> db, etc... It takes me a day to get the backups copied over or ship to
> the DR site.
>
> Just wondering how people who deal with VLDB's with situations like
> this. Is there a way for me to do a planed DR Drill but to minimize
> the downtime of being without the DR site for a long period of time?
>
> Any advise would greatly be appreciated..
>
> Thanks in advance..
> Aravin Rajendra.

at the recovery-site have a readable hot-standby and for the drill 
use snapshot copy of it

this means the disks at the recovery site need to be big enough for
two copies of the database.

-- 
⚂⚃ 100% natural

Back to comp.databases.ms-sqlserver | Previous | Next | Find similar

Thread

Re: Database Mirroring (resynching the database every time a mirror is broken) Jasen Betts <jasen@xnet.co.nz> - 2011-01-31 10:09 +0000

csiph-web