ontape restore question
Question: when restoring with ontape to a second instance, must the temp dbspaces match the source? Art Kagel explained that ontape rewrites the reserved pages with the original chunk layout, so paths/offsets can change but chunk sizes cannot — the temp chunks must exist and be at least as large as on the source, even though only header pages are written. John Miller noted ontape -r -D can selectively restore only chosen dbspaces. A follow-up "ran out of space" failure was attributed to needing to count chunk offsets in the space required, and to not having done a cold restore of the root dbspace first.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Does the temp space need to be the same on between 2 instances to do an ontape
restore? (I know the rest of the dbspaces need to be, but I was wondering if
temp needed to be)
Jonathon Wyza
CX & CBORD System Administrator
CX Programmer/Analyst
Administrative Computing
Bethel College
(574)-257-3381
AIM: Iamwyza
jonathon.wyza@bethelcollege.edu<mailto:jonathon.wyza@bethelcollege.edu>
==============================
SLES 11x64 & IDS 11.50.FC6
"Don't document the problem, fix it."
- Atli Björgvin Oddsson
Remember that when ontape does a restore the reserved pages will be written
containing the paths and sizes of the original chunks/dbspaces from the
source server. You can change the paths and offsets during a restore, but
not the chunk sizes, so yes, the chunks for the temp dbspaces have to exist
and have to be at least as large as they were on the original server, even
though nothing will be restored to them except the dbspace and chunk header
pages.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
IIUG Board of Directors (art@iiug.org)
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Advanced DataTools, the IIUG, nor any other
organization with which I am associated either explicitly, implicitly, or by
inference. Neither do those opinions reflect those of other individuals
affiliated with any entity with which I am affiliated nor those of the
entities themselves.
On Tue, Aug 31, 2010 at 3:08 PM, Wyza, Jonathon <wyzaj@bethelcollege.edu>wrote:
> Does the temp space need to be the same on between 2 instances to do an
> ontape> restore? (I know the rest of the dbspaces need to be, but I was wondering
> if
> temp needed to be)
>
> Jonathon Wyza
> CX & CBORD System Administrator
> CX Programmer/Analyst
> Administrative Computing
> Bethel College
> (574)-257-3381
> AIM: Iamwyza
> jonathon.wyza@bethelcollege.edu<mailto:jonathon.wyza@bethelcollege.edu>
> ==============================
> SLES 11x64 & IDS 11.50.FC6
>
> "Don't document the problem, fix it."
> - Atli Björgvin Oddsson
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--0016e64355bcea7de8048f238a61
While it is not widely used, ontape has the ability to selectively rest=
ore
dbspaces using
the -D option. I would suggest listed only the dbspaces you require t=
o
restore, and the other
dbspaces will be skipped.
John F. Miller III
STSM, Support Architect
miller3@us.ibm.com
503-578-5645
IBM Informix Dynamic Server (IDS)
ids-bounces@iiug.org wrote on 08/31/2010 12:08:32 PM:
> From:
>
> "Wyza, Jonathon" <wyzaj@bethelcollege.edu>
>
> To:
>
> ids@iiug.org
>
> Date:
>
> 08/31/2010 12:09 PM
>
> Subject:
>
> ontape restore question [21088]
>
> Sent by:
>
> ids-bounces@iiug.org
>
> Does the temp space need to be the same on between 2 instances to doa=
n
ontape> restore? (I know the rest of the dbspaces need to be, but I was wonde=
ring
if
> temp needed to be)
>
> Jonathon Wyza
> CX & CBORD System Administrator
> CX Programmer/Analyst
> Administrative Computing
> Bethel College
> (574)-257-3381
> AIM: Iamwyza
> jonathon.wyza@bethelcollege.edu<mailto:jonathon.wyza@bethelcollege.ed=
u>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
> SLES 11x64 & IDS 11.50.FC6
>
> "Don't document the problem, fix it."
> - Atli Bj=F6rgvin Oddsson
>
>
>
***********************************************************************=
********
> Forum Note: Use "Reply" to post a response in the discussion forum.=
>=
Do the chunks to be the same size, or is "at least as big" good enough?
We just tried to perform an 'ontape -r -D dbspace' and it failed because the
chunk ran out of space. The restore DB chunk is exactly the same size as the
production chunk. Why/How could it run out of space during a restore?
Thanks,
Michael Hoffman
When you start the restore, you should get a printout of the dbspaces
and chunks. There will be sizes, offsets and paths. You must have
this space (and do not forget to add in offsets).
A chunk with a 500MB offset which is 1GB in size will take 1.5GB in
filesystem space. The archive will verify that it can write to the last
page in each chunk (i.e. the page at 1.5GB into the device) before
continuing.
John F. Miller III
STSM, Embedability Architect
miller3@us.ibm.com
503-578-5645
IBM Informix Dynamic Server (IDS)
ids-bounces@iiug.org wrote on 09/16/2010 10:30:15 AM:
> From:
>
> "MICHAEL HOFFMAN" <mrh@panix.com>
>
> To:
>
> ids@iiug.org
>
> Date:
>
> 09/16/2010 10:31 AM
>
> Subject:
>
> Re: ontape restore question [21325]
>
> Sent by:
>
> ids-bounces@iiug.org
>
> Do the chunks to be the same size, or is "at least as big" good enough?
>
> We just tried to perform an 'ontape -r -D dbspace' and it failed because
the
> chunk ran out of space. The restore DB chunk is exactly the same size as
the
> production chunk. Why/How could it run out of space during a restore?
>
> Thanks,
> Michael Hoffman
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
Thanks Much, John! I think the problem lies in that the Production DBA didn't perform a cold restore of the ROOTDB before trying to restore the single dbspace. Thanks, Michael On Thu, Sep 16, 2010 at 11:48 AM, John Miller iii <miller3@us.ibm.com> wrote: When you start the restore, you should get a printout of the dbspaces and chunks. There will be sizes, offsets and paths. You must have this space (and do not forget to add in offsets). A chunk with a 500MB offset which is 1GB in size will take 1.5GB in filesystem space. The archive will verify that it can write to the last page in each chunk (i.e. the page at 1.5GB into the device) before continuing. John F. Miller III STSM, Embedability Architect miller3@us.ibm.com 503-578-5645 IBM Informix Dynamic Server (IDS) ids-bounces@iiug.org wrote on 09/16/2010 10:30:15 AM: