RE: Automating Informix Database Environment Restore
Well, I was just able to go into dbaccess on a development secondary server,
and it allowed me to "create temp table test001 ... with no log". Two
things that may be necessary:
(1) make sure you have some temp dbspaces set up and defined in DBSPACETEMP
in your ONCONFIG file (NOTE: this *probably* is NOT necessary, since I
believe that HDR disable the temp dbspaces on a secondary server);
(2) this is probably the key: make sure that the applications that are
creating the temporary tables on the "inquiry-only" server do so using the
"with no log" clause, whether they build the temp tables implicitly (select
... into temp xxx with no log) or explicitly (create temp table xxx ... with
no log).
Try using #2 first -- that's probably all you'll need.
BTW, to minimize impact on your primary server, use asynchronous updating
(DRINTERVAL >= 0).
HTH
Paul Mosser
-----Original Message-----
From: jhimschoot@CroweChizek.Com [mailto:jhimschoot@CroweChizek.Com]
Sent: Friday, October 29, 1999 1:34 PM
To: mosserp@WellsFargo.COM
Cc: informix-list@iiug.org
Subject: RE: Automating Informix Database Environment Restore
Yes, we can make the servers identical in every aspect. However, the
inquiry-only user's application that runs, which is setup to only perform
inquiries and reporting, creates temporary tables on the fly. From what I
have read about HDR, the secondary server's data is read-only. Can I get
around this issue somehow? Thanks, Jim.
|--------+----------------------->
| | mosserp@Wells|
| | Fargo.COM |
| | |
| | 10/29/1999 |
| | 12:14 PM |
| | |
|--------+----------------------->
>--------------------------------------------------------|
| |
| To: James A Himschoot/SB/CroweChizek/US |
| cc: informix-list@iiug.org |
| Subject: RE: Automating Informix Database |
| Environment Restore |
>--------------------------------------------------------|
Are the production server and the inquiry-only server identical? If they
are close enough in configuration (OS version, Informix version, disk
layout, etc.), then I would *highly* recommend that you look at
high-availability data replication (HDR). This is exactly the type of
setup
that HDR is intended for. We use HDR on some very critical 24x7 production
servers, and the overhead impact is very minimal. Now, if you were
thinking
of using Enterprise Replication, aka ER or CDR, then the overhead is
*substantially* more than that of HDR. Look into HDR. I'm pretty sure
that
it's available in the NT version. It's extremely easy to set up and
administer. Check out chapters 25 and 26 in the 7.3 Admin Guide.
HTH,
Paul Mosser
Wells Fargo & Co.
-----Original Message-----
From: jhimschoot@CroweChizek.Com [mailto:jhimschoot@CroweChizek.Com]
Sent: Friday, October 29, 1999 8:14 AM
To: informix-list@iiug.org
Subject: Automating Informix Database Environment Restore
Our IDS V7.3.TC3 NT4 (RAID5) environment is setup to perform a nightly
level 0 Informix backup to a disk-file which is then saved to tape via 3rd
party backup software. Transaction logs are continuously copied to tape
throughout the day.
I would like to create, and automate a procedure that daily restores the
level 0 backup onto another inquiry-only server. By the way, replication
has been ruled out as an option due to the negative aspects placed upon the
production server. Some thoughts would be to first perform a manual
initial Informix db environment load from the production server's level 0
backup on the inquiry-only server. From that point forward, I would want
to automate a procedure to execute the same reload daily. This process
might include copying the level 0 backup (currently 7+ GB) across the
network to the inquiry-only server at night, and executing a scheduled
UNIX-type of script (utilizing ONTAPE or ONBAR?). Is this possible to
automate? If so, how? Any examples, or other ideas would be very helpful
since I am relatively new to the Informix environment. I can be reached at
jhimschoot@crowechizek.com. Thanks for your time.