[Info-vax] Backup TK50 tapes

[supervinx]

> Um, BACKUP /PHYSICAL does that.  BACKUP /PHYSICAL is the rough VMS
> equivalent of dd, and it can be used to create a physical saveset.  But
> that's a pile of work, with a pile of gear, and arguably unnecessary if
> there's a network here.
>
I'm unable to use BACKUP /PHY with a tape as first argument.
Where am I wrong ?

$ backup/physical MUA0: duc1:
%BACKUP-F-MOUNTFOR, DUC1:[SYSMGR]*.*;* must be mounted /FOREIGN

$ mount /foreign duc1:
%MOUNT-I-MOUNTED, TEMP mounted on _SVXVAX$DUC1:

$ backup/physical MUA0: duc1:
%MOUNT-I-MOUNTED, CDD mounted on _SVXVAX$MUA0:
%BACKUP-F-NONPHYSET, nonphysical save set supplied to physical operation
OK, the tape contains normal savesets...

$ backup/physical MUA0: duc1:xxx.bck
%BACKUP-F-PHYFILSPE, /PHYSICAL specification must have only device name
OK, I've understood..

$ backup/physical MUA0: duc1:xxx.bck/save
%BACKUP-F-ONEF11DEV, both input and output must not be save sets
That's right, tapefiles are treated as savesets...

What's the right syntax ?

 

> 
> Install the available LD kit from Jur's digiater.nl site, and then use
> LD to create and connect a disk image on OpenVMS VAX, INITIALIZE the LD
> disk image, then MOUNT that disk image, then load the disk image
> with.... stuff... ...whatever... then DISMOUNT, then LD disconnect the
> LD device, then transfer the disk image via network to the simh host
> box, specify the disk image as the target device (device type RAUSER) in
> the simh initialization, boot OpenVMS VAX, and MOUNT your disk image,
> and off you go...
> 
But how to create bootable images from bootable tapes ?
I.e, for bootable tapes I want an image like tapedd one...

-- 
                                 _            
 ___ _   _ _ __   ___ _ ____   _(_)_ __ __  __
/ __| | | | '_ \ / _ \ '__\ \ / / | '_ \\ \/ /
\__ \ |_| | |_) |  __/ |   \ V /| | | | |>  < 
|___/\__,_| .__/ \___|_|    \_/ |_|_| |_/_/\_\
          |_|