a quick question:

i added a disk storage unit to test a backup to disk.  i then wanted to
change the frag size from 2gig to 500meg.  a second backup created a file
size of 1.3 gig before i realized the change didn't take effect and i
terminated the job.  i then deleted the disk storage unit and created
another with a different name but pointing to the same unix mount point.
when a backup job starts, the job just queues up and doesn't write to the
disk.  i did change the job to backup to the new disk storage name.  the
bpsched log shows:

12:30:31 [25432] <4> connected_peer: Connection from host bacchus,
10.205.xx.xxx, on non-reserved port 60536
12:30:31 [25432] <2> nb_is_valid_server: checking if bacchus is a valid
server
12:30:31 [25432] <4> process_request: VSMInit() failed for stunit change: 2d
12:30:31 [25432] <2> stunit_db: ?
12:30:31 [25432] <4> db_logstrec: label=*NULL* media type=0 (Disk) density=0
(qscsi)
12:30:31 [25432] <4> db_logstrec:  robotype=0 (?) robonum=0 concurrent
jobs=0 impx=0 mmpx=0
12:30:31 [25432] <4> db_logstrec:  odo=0 host=*NULL* path=*NULL*
12:30:31 [25432] <4> db_logstrec:  last_reread_stunit=0 max frag size =0
ndmp_attach_host: *NULL*
12:30:31 [25432] <2> stunit_db: Q_STUNITGET
12:30:31 [25432] <2> stunit_get: ?
12:30:31 [25432] <2> get_stunit_list: ?
12:30:31 [25432] <2> get_stunit: ?
12:30:31 [25432] <2> get_stunit: STUNIT fas_disk2 0 bacchus 0 -1 -1 2 0
/nb_disk1/storage1 1 1 2000 *NULL*
12:30:31 [25432] <2> get_stunit: ?
12:30:31 [25432] <2> get_stunit: MD5 digest line
12:30:31 [25432] <2> get_stunit: myfgetline() NULL
12:30:32 [25432] <4> bpdbm: request complete: exit status 0

do i need to stop and re-start media manager processes?  i didn't when i
added the disk storage unit.  also, our dba's are restoring a database from
a 2nd media server so i don't know if re-starting media manager on this
master/media server would effect them, so i haven't done it yet.  are there
any other logs to look through?  any help is appreciated.

thanks,
jerald iverson
unix sysadm