Disaster Recovery plan for SQL server

Hi,
We plan to implement Disaster Recovery plan and system
for SQL 2000 server and databases. SQL server is
connected in headquarter network. Recovery SQL server
will stay on remote location (site) and it must have the
most recent copy of SQL production databases.
SQL server has 2 databases. Each database has about 2-3
GB of data. We can expect that database will grow
significantly in the future (10 Gb and more). Databases
accept about 2 MB of data per day. Connection between
headquarter and remote location will probably be on high-
speed WAN (10 Mb/s or more). At any disaster event, we
can loose data for about last 1 hour (maximum 1 hour, not
more anyway)
What is the best solution for implementing Disaster
Recovery?
Backup, restore with STANDBY server on remote location
(with frequently created transaction log backups)?
Or SQL database replication (transaction replication)?
Thanks in advance for help
MilanDefinitely Standby Server with Log Shipping.
Theres lots of info in SQL Books Online and it is offered as a feature with
SQL Enterprise Edition.
--
Regards,
Mandar Naik
This posting is provided AS IS with no warranties, and confers no rights.
"Milan Ojstersek" <milan.ojstersek@.hermes-plus.si> wrote in message
news:087a01c33f07$3e84d700$a301280a@.phx.gbl...
> Hi,
> We plan to implement Disaster Recovery plan and system
> for SQL 2000 server and databases. SQL server is
> connected in headquarter network. Recovery SQL server
> will stay on remote location (site) and it must have the
> most recent copy of SQL production databases.
> SQL server has 2 databases. Each database has about 2-3
> GB of data. We can expect that database will grow
> significantly in the future (10 Gb and more). Databases
> accept about 2 MB of data per day. Connection between
> headquarter and remote location will probably be on high-
> speed WAN (10 Mb/s or more). At any disaster event, we
> can loose data for about last 1 hour (maximum 1 hour, not
> more anyway)
> What is the best solution for implementing Disaster
> Recovery?
> Backup, restore with STANDBY server on remote location
> (with frequently created transaction log backups)?
> Or SQL database replication (transaction replication)?
> Thanks in advance for help
> Milan
>|||I prefer Log Shipping.
"Milan Ojstersek" <milan.ojstersek@.hermes-plus.si> wrote in message
news:087a01c33f07$3e84d700$a301280a@.phx.gbl...
> Hi,
> We plan to implement Disaster Recovery plan and system
> for SQL 2000 server and databases. SQL server is
> connected in headquarter network. Recovery SQL server
> will stay on remote location (site) and it must have the
> most recent copy of SQL production databases.
> SQL server has 2 databases. Each database has about 2-3
> GB of data. We can expect that database will grow
> significantly in the future (10 Gb and more). Databases
> accept about 2 MB of data per day. Connection between
> headquarter and remote location will probably be on high-
> speed WAN (10 Mb/s or more). At any disaster event, we
> can loose data for about last 1 hour (maximum 1 hour, not
> more anyway)
> What is the best solution for implementing Disaster
> Recovery?
> Backup, restore with STANDBY server on remote location
> (with frequently created transaction log backups)?
> Or SQL database replication (transaction replication)?
> Thanks in advance for help
> Milan
>