Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

OpenVMS Decnet + backup command

 
geir_2
Super Advisor

OpenVMS Decnet + backup command

Hi,

 

I want to transfer an image ($backup/image) from one server to another. I have tried different commands without . success.

 

$backup/image/ignore=interlock 1.80"username password"::dka100 user.bck/save

The error message indicate that it's an illegal backup device.

 

Since the source server have no space to store the image locally I want to run the backup command from one server to antorher. We use Decnet Phase 4+. Hope someone could give me some usefull hints. Thanks:

9 REPLIES 9
Volker Halle
Honored Contributor

Re: OpenVMS Decnet + backup command

Geir,

 

please show the complete command and error message (using cut & paste - if possible):

 

The correct command would be:

 

$ backup/image/ignore=interlock 1.80"username password"::dka100_user.bck/save

 

Your original command included a SPACE character in the output saveset parameter. This could have led to the error message about an invalid device.

 

Volker.

Richard Brodie_1
Honored Contributor

Re: OpenVMS Decnet + backup command

The saveset has to be on the remote node: you can push a sequential file over DECNET but you can't rummage around in the innards of a remote disk.

Volker Halle
Honored Contributor

Re: OpenVMS Decnet + backup command

Geir,

 

sorry I've overlooked the missing input device specifier in your command example. So a correct BACKUP command would look like this:

 

$ backup/image/ignore=interlock dka100: 1.80"username password"::user.bck/save

 

The input disk MUST be a local disk, but the output saveset can be on a remote node.

 

Volker.

geir_2
Super Advisor

Re: OpenVMS Decnet + backup command

Hi,

 

Thanks for all answers.   I try to copy a image file from one server to another . Each time I try to execute the command I got an error message. The command I run is following:

 

$backup mka500:osws99.bck/save 1.99"system password"::dka100:osws99.bck

 

osws99.bck is a image file.

 

The tapedevice is mounted with the foreign command

Rgds

Geir

 

Maybe it's not possible to move a bck file from one server to another with the backup command.

Hoff
Honored Contributor

Re: OpenVMS Decnet + backup command

A saveset specification is the only portion of the BACKUP input and output parameters that's permitted to be on a remote (DECnet FAL connected) host.

 

You're trying to reverse this pattern, and place the saveset locally and to then restore the files remotely, or to copy the file remotely.  That won't work, as BACKUP would have to open a gazillion files over the network, and that was viewed as problematic by the folks that built BACKUP.

 

You can read the examples in the BACKUP on-line HELP text for typical commands. 

 

Looking at the specifics of your question, this particular question has arisen fairly regularly over the years, where you don't have a tape drive on the target system that is compatible with the media, and where you don't have a scratch disk local to the tape drive you do have.  You can temporarily move the tape drive to the target system, or free up some storage locally, or you can cluster the hosts (if you have licenses), or you can temporarily transfer some disk storage from the target system over to the system with the tape drive.  

 

You can potentially also try to MOUNT the tape native, and attempt to COPY the saveset from tape to disk, then transfer the saveset to the remote host for restoration.  That isn't entirely reliable and won't work for multi-volume savesets, and HP/Compaq/DEC offered the Saveset Manager tool to perform that operation more reliably.

 

The best solution is acquiring the additional hardware necessary; additional used or new tape drives, or that could be more storage on the systems, or some shelves of disk drives that (with the proper care around quescing the SCSI buses) can be swapped around.

 

Best?  Get yourself a tape drive.  That'll make backups on the remote server easier and faster, too.

 

And FWIW, using /IGNORE=INTERLOCK is a recipe for silent data loss.