| Hot Standby Schemes [message #75156] |
Tue, 02 April 2002 07:23  |
Mike Barnes
Messages: 1
Registered: April 2002
|
Junior Member |
|
|
For this new redundant production environment we are configuring, we were going to use dataguard to hot copy the database. In performing a test installation, the implementation of Dataguard appears to require archived log files to go to two places at once, and Standard Edition allows only one. There is no other documentation we can find that insists on the enterprise edition tho. Are you aware of any such restriction? Since we run a tight ship, the very large license cost of upgrading to the enterprise edition just for dataguard is prohibitive. Here are a couple of options we are considering:
1) Make a copy of the Production
Database (standard edition) on each server, and copy archived files as they
appear. Apply them on some schedule, like nightly. Possibly we could get
this down to a nightly operation. When the production server breaks, apply
all the accumulated log files, and restart the database on the backup
machine. The down time depends on two major items: detection of "down" and
the time to apply all the daily accumulated redo; perhaps an hour or two.
In Microsoft land this approach is called "log shipping".
2) buy Shareplex from Quest Software; still expensive, but less than upgrading
to the enterprise edition.
Do you have any other wisdom on workable standby schemes?
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
