Turbostore is supposed store all sets in a database unless the
;PARTIALDB option is specified.  I believe that the default is ";FULLDB"
if you did not request ;PARTIALDB.

I don't like items as critical as the backup to be left up in the air,
so I'd always specify ;FULLDB even on the partial.

Have you timed how long your partials are taking --- and what files are
being stored.  Now days with the large capacity DDS and DLT drives, it
is often easier to just do a fullbackup every night  --- UNLESS you have
one of those VERY LARGE databases.

Out of synch datasets can be a real bear, not necessarily the end of the
world, if it is just the automatic masters that are out of synch.  Those
can be rebuilt with Adager or DBGENERAL,  but having detail sets mixed
up from differnt tapes -- is a disaster.

Rich Trapp wrote:
>
> 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
>
> _______________________________________________________________________