Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ms-sqlserver > #1573
| Path | csiph.com!eeepc.pasdenom.info!news.pasdenom.info!news.dougwise.org!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!194.25.134.126.MISMATCH!newsfeed01.sul.t-online.de!t-online.de!netnews.web.de!news.sub.net!wieslauf.sub.de!.POSTED!reversiblemaps.ath.cx!not-for-mail |
|---|---|
| From | Jasen Betts <jasen@xnet.co.nz> |
| Newsgroups | comp.databases.ms-sqlserver, microsoft.public.sqlserver.programming, comp.databases, microsoft.public.sqlserver.server |
| Subject | Re: Database Mirroring (resynching the database every time a mirror is broken) |
| Date | 31 Jan 2011 10:09:11 GMT |
| Organization | Dis (not Dat) Organisation |
| Lines | 31 |
| Message-ID | <ii61o7$j16$4@reversiblemaps.ath.cx> (permalink) |
| References | <a2c043d5-0358-447e-a3ea-7c8629257648@k7g2000yqj.googlegroups.com> |
| NNTP-Posting-Host | W9Wpu3kNUd3W5T9yO21/BQ.user.wieslauf.sub.de |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset=UTF-8 |
| Content-Transfer-Encoding | 8bit |
| X-Complaints-To | usenet@wieslauf.sub.de |
| NNTP-Posting-Date | Mon, 31 Jan 2011 10:30:48 +0000 (UTC) |
| User-Agent | slrn/pre1.0.0-18 (Linux) |
| X-Notice | Filtered by postfilter v. 0.8.1 |
| X-Face | ?)Aw4rXwN5u0~$nqKj`xPz>xHCwgi^q+^?Ri*+R(&uv2=E1Q0Zk(>h!~o2ID@6{uf8s;a +M[5[U[QT7xFN%^gR"=tuJw%TXXR'Fp~W;(T"1(739R%m0Yyyv*gkGoPA.$b,D.w:z+<'"=-lVT?6 {T?=R^:W5g|E2#EhjKCa+nt":4b}dU7GYB*HBxn&Td$@f%.kl^:7X8rQWd[NTc"P"u6nkisze/Q;8 "9Z{peQF,w)7UjV$c|RO/mQW/NMgWfr5*$-Z%u46"/00mx-,\R'fLPe.)^ |
| Cancel-Lock | sha1:5OXQU+E1CEKLv4ujwOZ10ORbbQQ= |
| Xref | csiph.com comp.databases.ms-sqlserver:1573 comp.databases:442 |
Cross-posted to 4 groups.
Show key headers only | 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
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