Hi Mecki,
  In our case, the ADSM server directory is not part of the root volume
group, so that a mksysb won't grab it.  We also time our operations so th=
at
the volume history file backup contains a reference to our nightly full
backup of the ADSM database, and mksysb just isn't a good fit.

  The actual message we get is "/dev/rmt1.1 fsf 2 failed: There is an inp=
ut
or output error.", which results from the AIX command "mt -f /dev/rmt1.1 =
fsf
2".  The mt command is used used to get past the tape label.  I gather th=
at
either an EOF or EOT mark is not being written by the ADSM "label volume"
command.

Thanks,
Jim

> ----------
> From:         Mecki M.[SMTP:RMESCHON AT DE.IBM DOT COM]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Tuesday, January 04, 2000 3:40 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Difference between dsmlabel and internal "label volume"
> commands
>
> Hi Jim,
>
> the process we use for backing up those (and a few more) files is to le=
t
> ADSM
> point
> to rootvg-filesystems for those files and we get them with the
> mksysb-tape.
>
> This is under AIX.
>
> The tapes we're using are especially for this purpose and not labelled =
for
> ADSM-needs.
>
> The drive is the 8mm-unit, defined as a manual drive to ADSM as mt0 and=
 to
> AIX
> as rmt0.
> The state is changed via rmdev/mkdev-command and an access to that driv=
e
> fails
> if
> it is in use by the other system, but having scheduled the operations n=
o
> failures occured.
>
> As far as I do not know on which System and Hardware you are, nor do I
> know more
> about the error-messages you get during re-labelling your volumes, I ho=
pe
> that
> this
> Information is useful for you.
>
> Regards
>      Meck=EF
>