ROLLFORWARD only works if you have a valid log, but that doesn't apply in
your case.
RESTORE DB  restores the DB back to the point the backup was taken; you
shouldn't need the ROLLFORWARD capability in a controlled situation.

I have moved an ADSM data base from one ADSM NT server to another this way.
I did a BACKUP DB.
Then I installed ADSM on the new machine, configured the DB to the right
size.
Then I copied the devconfig and volhist to the new machine,
then DSMSERV RESTORE DB worked like a champ!
***************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
***************************************************************



> -----Original Message-----
> From: Mapes, Mark [SMTP:MWM4 AT PGE DOT COM]
> Sent: Friday, October 30, 1998 4:30 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: LOADDB fails
>
> Richard,
>
> it is my understanding that the RESTORE DB only works if you have a valid
> "log".  Since I am moving to a new machine with new disks, I thought my
> only
> option was the DUMPDB/LOADDB.  Have you tried doing a bare-metal restore?
>
> Mark
>
> > ----------
> > From:         Richard Sims[SMTP:rbs AT BU DOT EDU]
> > Reply To:     ADSM: Dist Stor Manager
> > Sent:         Friday, October 30, 1998 1:07PM
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > Subject:      Re: LOADDB fails
> >
> > I don't know why the LOADDB fails; but DUMPDB/LOADDB is basically
> archaic:
> > you should be using BACKUP DB and DSMSERV RESTORE DB for such
> operations.
> > DUMPDB/LOADDB are part of a salvage utility that was a stop gap solution
> > for ADSMv1 until the database backup and recovery functions could be
> added
> > in ADSM version 2.
> >     Richard Sims, BU
> >