|
 CII
Carbon
CII
Carbon Hit by Hurricane Katrina.
CII is back in business after corporate site fails!
Hurricane Katrina forced CII
to evacuate their New Orleans area corporate office. Their backup
generator worked perfectly, until it ran out of gas 12 hours later.
The UPS systems worked flawlessly until the batteries drained.
When the storm passed it was clear that CII would not be returning
to business as normal at their main office. While employees were
being directed to an alternate company site located further inland,
their Oracle standby database was ready and waiting for activation.
Within minutes, CII was able to have a viable production database
up and running. Their business information was safe and intact
ready to continue business.
Don’t get caught with your database down! The cost to setup
and maintain a standby database is minimal compared to the cost if
your business can’t invoice customers, pay invoices, or ship
products.
Standby databases.. cheap
backup or cheap insurance!
If you have been running your ERP system
for more than a year or two chances are your database contains
millions of records and transactions that are now worth more
to the organization than the cost to set it up was in the beginning.
That's big buck$. Your basic back up to tape, while important
to do, does not necessarily mean rapid recovery.
Who: CII
Carbon located outside of New Orleans, LA. IT contact is Peter
Crosby.
Why: Implemented an Oracle
Standby database to protect the investment made in putting data
into the database and the ability to fail over to another server
should the primary server fail.
What: Using a combination
of Oracle Standard Edition (8.1.6) and a set of NT batch files
eNSYNC implemented an easily managed Oracle failover solution.
The standby database wakes up twice per day and imports any outstanding
archive logs. It then shuts down the database and waits for the
next wake event. The import process generally takes less than
5 minutes. To complete the process, CII Carbon will ship the
standby database server to one of their remote facilities. The
archive logs will then be moved over the WAN.
In summary, the new standby database met the goals and needs of the client.
Everyone knew what was expected from the very beginning and good communication
between the client, consultant, and sales staff helped make the project a success.
When: The project was
started on a Tuesday morning and the database was setup, configured,
and tested by Thursday afternoon. As part of the project, the
IT staff was trained on the use of Oracle (installation, configuration,
tuning, etc...) and was involved with hands on tasks in implementing
the fail over solution.
-----Original
Message-----
From: Peter Crosby [mailto:PCrosby@CIICarbon.com] Sent: Thursday, April 10,
2003 8:01 AM
To: Alan Clark (E-mail)
Subject: Oracle Standby update
Hi Alan,
I just wanted to share some good news about our standby server.
We had an outage of our T1 to our remote location that lasted for about 24hrs
due to a main Sprint fiber being cut. When the T1 came back on, the standby
process picked back up where it left off like nothing ever happened (I didn't
have to do anything to get it back going). I was very happy with the results.
I also corrected a problem we had while trying to compile new modifications
for ROSS and place them into our training system. They were getting a message "could
not connect to database". It turned that they were trying to compile for
our old "train" database. I recognized it right away and made the
necessary corrections to the batch file that does the compiling at it worked.
My training time with you is paying off and I was excited that I was able to
see and correct this problem without having to call. YAHOO!!!
<<...>> Peter S. Crosby <<...>>
|
