It depends on how you did the backup. If you used the DBSTORE parameter then
the whole DB was stored and you can restore it al with no ill effects. If
you restore just certain datasets you run a number of risks. Firstly your
root file's record count may differ from the dataset's count. Secondly
related masters may not reflect the data of the restored detail dataset.
Thirdly some masters have more than one path. If the master changed because
of the secondary path and you restore the master based on the primary path
then you've got trouble.

For these reasons it has always been my practice to do a DBSTORE even on
partials.

----- Original Message -----
From: "Rich Trapp" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Tuesday, August 08, 2000 5:14 PM
Subject: [HP3000-L] TURBOSTORE question...


> Gang,
>   Ok, I feel ignorant w/o a box to play with...I guess humility is good
for
> me. (no comments Art!)
>
>   Some of my cohorts are asking if a partial backup will store only the
> datasets that have been modified, or if it will store the entire database.
>
>    We're working on some recovery plans and we're wondering if restoring
the
> latest partial over the latest full will cause the database to be
> inconsistent.  Doesn't seem likely even if only rootfile and datasets that
> have changed are stored...everything should be consistent (right?).
>
> RAT
>
> _______________________________________________________________________
>  Rich Trapp "RAT"
>  Managed Business Solutions   [log in to unmask]   http://www.mbsnav.com
>  Assigned to Design Automation Support at Agilent Technologies
>  Telnet or 970-679-2221 [log in to unmask]  Loveland, CO USA
>
> _______________________________________________________________________
>