Re: Level - 0 Restore problems
Short answer --> it depends.
Long answer -->
No problem with OnBar. Just have to bring the ixbar file, the $ONCONFIG
file (maybe), and the oncfg... file over, shut down the instance and do a
cold restore.
The nasty piece is the Storage Manager.
With ISM -- very tough/impossible -- ISM uses the machine name as the client
name and is only intended to perform local backup/restores. Would have to
change machine name and copy ISM catalog files from original machine. --
easier to just use ontape.....
With ADSM -- a piece of cake (dry & chewy, but not too hard) -- Set the
virtualnode name, authorize cross-machine access to the production client,
hold your breath, and run it.
OmniBack is similar.
Have not tried other Storage Managers, but the bottom line for any of them
is that you need the ability to specify the client name and maybe grant
access.
HTH,
Doug
<Stephen_Murray@agsea.com> wrote in message
news:8j02j8$161$1@news.xmission.com...
>
> We use ontape to regularly duplicate production systems to separate test
> machines for development/testing/QA, etc. Is it possible to take an onbar
> backup created on host A and restore it to host B (assuming all the
> necessary disk devices and links are set up to accommodate all the chunks
> contained in the backup)?
>
> Thanks,
>
> Steve Murray, Senior DBA
> Assocated Grocers, Inc
> Seattle, WA
>
>
>
>
>
> "Art S. Kagel" <kagel@bloomberg.net> on 06/13/2000 06:21:56 AM
>
> Please respond to kagel@bloomberg.net
>
> To: informix-list@iiug.org
> cc: (bcc: Stephen Murray/AGInc)
> Subject: Re: Level - 0 Restore problems
>
>
>
>
> Note: Some recipients have been dropped due to syntax errors.
> Please refer to the "$AdditionalHeaders" item for the complete headers.
>
>
>
> Watawinona@aol.com wrote:
> >
> > Mark,
> >
> > we could talk in deep, dark tones about why a level 0 from one machine
to
> > another is not a good idea. And many a newbie tries that now and then,
> and
> > fails just as the idiots before him.
> >
> > There are other, more suitable tools designed just for that purpose. So
> use
> > them. And don't wolf about things you don't know anything about.
>
> Sorry Nona, there is nothing inherently BAD or 'bad idea' about restoring
> from one machine to another. Indeed I depend on that capability to
> maintain a sane backup strategy in the face of servers that take over 24
> hours to archive. We archive sister machines on a rotating schedule so
> that
> I always have a current level 0 from one and level 0 plus level 1 from the
> other. I keep the disk layouts compatible (I try to keep them identical
> but that never seems to work) so that I can restore one set to the other
> machine if that is the faster solution holding the two tape set restore in
> reserve in case the tapes turn out to be bad. This has worked for me and
> for my predecessor for eight years and I'm still working here!
>
> The problem is that the disk layouts have to be compatible, which is easy
> if you are running only one instance per machine, meaning all devices are
> the same size or if larger on one system that the instance ONLY utilizes
> the smaller size on both systems letting the difference go to waste.
>
> Mark is right, and obviously one word to you was not sufficient so here
> were a few hundred. Your one liners are not useful or helpful and, unless
> appended or prepended to a functional answer, neither appreciated nor
cute.
>
> Art S. Kagel
>
>
>
>
>
>