Re: How to deploy a 24hrs , 7 days a week kind of database environment?

In article <01be0700$d9dd3560$b8ce2aca_at_mis1-184.yas.com.sg>, sunwong_at_yas.com.sg says...

>This is a first time that our company are deploying a 24hrs , 7 days a week
>kind of database environment.
>Can anyone pls tell me what type of strategies shall I use in order not to
>have any downtime?

When do you propose to do system maintenance/upgrades?

>What are the recommended backup strategies?

You need to do hot backups (ie backup the database without taking it down). If it is possible to run three-way mirrors you can detach one of the mirrors to take a cold dump of the OS, however attaching & detaching mirrors may mean your system has to go down briefly (depends on the OS and volume management software).

If you are serious about 7x24 you also need a hot standby machine with an automatic failover system. A failover system also allows you to do upgrades etc as you can switch users onto the failover machine whilst working on the original. Again, a 100% 24x7 service probably requires _two_ standby machines so that you can keep at least one online all the time...

>Can Oracle running on NT server have this type of reliability?

Oracle can, but I'd be surprised if you can run a big system on NT for more than 24 minutes without it falling over. Unix bigots of the world unite.....

Cheers
Martin

--
Martin Rapier, Database Administrator
Corporate Information & Computing Services. University of Sheffield Tel 0114 222 1137 The opinions expressed here may be those of my employer, or they may not. http://rhino.shef.ac.uk:3001/mr-home/ Received on Tue Nov 03 1998 - 06:35:18 CST