I have multiple lines in the dsmserv.opt file for volhistory and devconfig.
All of them specify the full path of where I want the devconfig and
volhistory files created.
(You can specify these parms as many times as you want.)
That way I always have multiple copies on different physical disks, and ADSM
keeps them current.
I don't even have to do the BACKUP DEVCONFIG or BACKUP VOLHIST!

> -----Original Message-----
> From: Richard Sims [SMTP:rbs AT BU DOT EDU]
> Sent: Wednesday, April 21, 1999 2:13 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Backups of DEVICE CONFIG data and VOLUME HIST data
>
> >Im running daily full backups of the database with BACKUP DB  and want to
> run
> >similar BACKUP DEVCONFIG and BACKUP VOLHIST for each server
>
> You could simply have an external cron job or the like copy the file at
> the operating system level, as another approach.  ADSM naturally always
> keeps the file current, so you can grab an image whenever you'd like.
>     Richard Sims, BU