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

how to do this !

SOLVED
Go to solution
SCC_2
Frequent Advisor

how to do this !

Hello,
I install a new HD for my micro vax 3100 model 90 v5.5.2, is a seagate scsi drive, after I boot up the system, I can mount the disk like example

Mount/system/noquota dka100: backup

That's no problem. I am trying to do a image backup from other disk drive to that one, but the system ask me to dism the drive and mount it under mount/fore dka100: that's no problem to do that too. But when I abort the process or after finish, I can't get into that drive. No matter what I do, the system say wrong label.

I am going to init. the drive again and start it over again. Is there any way I can copy or from a backup to copy all files over to that new drive and during the process it will also create a new dir. example
I want to copy a file from dka400:[test]test.dat to dka100:[test]
but on dka100: there is no dka100:[test] setup
Or I have to use backup tapes data to backup to that HD.

Thanks !
SCC
8 REPLIES
Dale A. Marcy
Trusted Contributor

Re: how to do this !

SCC,

You did not show the backup command that you were using, but I suspect the image backup caused the label of the DKA100 to be changed to the same value as your original drive (DKA400?). You can specify /NoInitialize on the output side to not overwrite the label of the output disk. You can use back to create the directories as you requested in the end part of your question, but if you want to move ACLs with the directory, you have to perform an extra task. To move with ACLs in tact, do the following:

$ backup dka400:[000000]test.dir dka100:[000000]test.dir
$ backup dka400:[test]test.dat;* dka100:[*]*.*;*

In the above, if you want to retain the original owner, add /by_owner=original to the end of both lines.

If you would like further assistance, please provide example of backup command you are using.
Bojan Nemec
Honored Contributor

Re: how to do this !

SCC,

If you want to do an image backup, do it as you did:

$ MOUNT/FOREIGN destination_drive
$ BACKUP/IMAGE source_drive destination_drive

Then mount the drive private:

$ MOUNT/OVER=ID destination_drive

The destination_drive label will be displayed. You cant have two drives with the same label mounted system wide, so probably you want to change the drive label with:

$ SET VOLUME/LABEL=new_label destination_drive

Now you can dismount the drive and mount it system wide with MOUNT/SYSTEM.

Bojan
SCC_2
Frequent Advisor

Re: how to do this !

Thank ! this is what I try to do start from scratch

$ init dka100: backup
$ mount/fore dka100:
$ backup/log/image/ign=(lab,inter) mka0: dka100:

( it start copying the the files at this point ) then I ctrl-Y to kill it. then type
$ set def dka100:[000000]
$ dir
return will error
%direct-e-openin, error opening dka100:[000000]*.*;* as input -system-f-devforeign device is mount foreign

Then I dismount the dka100:
$ dism dka100:
after that I can't mount the disk another more, error say incorrect volume label

scc
William Webb_2
Frequent Advisor

Re: how to do this !

If you kill your image backup, the target disk is still mounted /FOREIGN, which is not FILES-11, so you cannot do a DIR command on it.

A DIR command will not work until the backup has finished and you dismount the volume and then remount it FILES-11.

HTH,

WWWebb
Dale A. Marcy
Trusted Contributor
Solution

Re: how to do this !

SCC,

Change your backup command to the following and it should leave your label alone:

$ backup/log/image/ign=(lab,inter) mka0: dka100:/NoInitialize

If that qualifier is not added, it will initialize with the label of the disk in the backup save set on the tape. The other thing you could do is the Mount/Over=Id dka100 and VMS will tell you the value of the disk label after the backup operation. As stated in other responses, you must dismount the disk from the Mount/Foreign and mount it again before it can be accessed with the directory command.
Jan van den Ende
Honored Contributor

Re: how to do this !

SCC,

Several issues together:

$ init dka100: backup
$ mount/fore dka100:
$ backup/log/image/ign=(lab,inter) mka0: dka100:

-- whatever was the label of the original disk before backinh-up to tape, will now be the label of dka0: as well.
To prevent that, add /NOINIT to the backup command


Then I dismount the dka100:
$ dism dka100:
after that I can't mount the disk another more, error say incorrect volume label


Yes, you changed the label to that of the original disk (the one that was taped).

And if it is on the same system, then trying to mount is systemwide as well (with the label taken from the tape) then you get "Another device with same label already exists.
Another reason to BACKUP/NOINIT.

hth,

Proost.

Have one on me.

jpe


... then I ctrl-Y to kill it.

BACKUP (and certainly /IMAGE) does have to do some complex housekeeping functionality as well.
If you do not let it run to completion, (and you DID interrupt it!) then the output disk will not be consistent,
Don't rust yours pelled jacker to fine doll missed aches.
Bojan Nemec
Honored Contributor

Re: how to do this !

SCC,

You should not abort image backup with ctrl-Y. You must wait until the whole disk is copied. If you abort the backup, you will receive an inconsistent volume which can not be mounted.

After dismounting the disk, mount it private with MOUNT/OVER=ID. This will tell you the device label. If another disk has the same label you should change it with SET VOLUME/LABEL while the disk is private mounted.

If you want to copy only some files and then interupt the backup process you can not use the /IMAGE qualifier. Use this command:

$ BACKUP MKA0: DKA100:[*...]/OWNER=ORIGINAL

Bojan
Willem Grooters
Honored Contributor

Re: how to do this !

IMHO, interrupting an image backup will leave your backup useless, si the only feasable thing to do with the target medium is to INIT it again and redo the excercise.

Im not sure on your second question.
I suppose you have:

DKA400:[test]test.dat
DKA100:[000000] - without test.dir

and want to end up to have:

DKA100:[test]test.dat

I would use the simple approach:

$ CREATE/DIRECTORY DKA100:[TEST]
$ COPY DKA400:[TEST]TEST.DAT DKA100:[TEST]

or, if DKA400 containsa a backup saveset:

$ CREATE/DIRECTORY DKA100:[TEST]
$ BACKUP/SELECT=[TEST]TEST.DAT DKA400:/SAVE_SET DKA100:[TEST]

Willem Grooters
OpenVMS Developer & System Manager