--cvVnyQ+4j833TQvp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Ian_Fehring AT national.com DOT au <Ian_Fehring AT national.com DOT au> 
[2005-08-05 12:=
28]:
> David,
>=20
> We do a similar thing with our Master server using SRDF to replicate the
> our DR site.
>=20
> For DR Testing, we split our SRDF link (to stop replication) and mount our
> DR disks to our DR master server. We then do a 'hostname
> prod_master_server_name" to change the name of the DR server to be the sa=
me
> as our production host. We DO NOT change the IP address on the DR server.
>=20
> We can then start up the DR master server and point clients to it to test
> restores and/or backups. By doing this, we continue to have the Production
> master server running performing backups etc, but can also test that our =
DR
> master server can start correctly and with the production data (at the
> point in time of the SRDF split)
>=20
> The procedure that we have for a Real DR is very similar, except we
> obviously do not need to manually stop the SRDF replication.

We are doing the same thing and it works great. The only reason anyone
=66rom the backup group has to be there at all is in case something goes
horribly wrong and the master needs to be built from scratch. I'm
actually at our DR site as I type this using exactly this type of
replication.

--=20
David Rock
david AT graniteweb DOT com

--cvVnyQ+4j833TQvp
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFC8udoMrO4/Yb/xwYRAvzaAKCApMpif0zxnISRbBLu5//5iruxswCfXlHC
LwxbkB8URqVttXk8g7GDOww=
=zdax
-----END PGP SIGNATURE-----

--cvVnyQ+4j833TQvp--