Re: Restore to test env

Cosmo Lee wrote: [SNIP] > And that's another issue. If restoring w/ `ontape` you're going to have to > have almost all the ONCONFIG parameters the same in your development DB. > This can be a great: HASSLE. > > This brings up another issue: how will you restore from `ontape` (or other > archive utility) if you need to restore an Online instance with the same > name already running. I don't know the answer to this. Maybe someone else > has an answer. I don't know if the archive utilites are specific regarding > the DBSERVERNAME. Could you restore from an `ontape` archive to a DBSERVER > w/ a different name??? Two issues for ontape: 1) Not all of the ONCONFIG parameters need to be the same only those that affect disk layout such as ROOTNAME, ROOTPATH, ROOTOFFSET, ROOTSIZE, PHYSDBS, PHYSFILE, LOGFILES, & LOGSIZE. Shared memory and connection parameters (like BUFFERS, NUMAIOVPS, PHYSBUFF, SHMVIRTSIZE, etc) do not need to be the same. Indeed we run production with 28 CPU VPs and 120 AIO VPs and 20 NET CPs and 200,000 -> 400,000 BUFFERS and must reduce both AIO VPs and the number of BUFFERS (to 20,000) in order to restore an archive because it takes so long to connect the ~200 oninit processes to that much shared memory that ontape times out and aborts waiting for the engine to initialize. 2) You ABSOLUTELY can restore to a different DBSERVERNAME and SERVERNUM with ontape. I do this frequently to recover from major crashes or to sync a server and it's backup (I'm doing a restore to another machine tonight in fact). We have 2-5 machines running the same databases and do not back up all machines every time so if a machine crashes the most recent archive may be from another machine. Art S. Kagel