VMS need to unbind bind volumes

[Howard_24]

I received a backup tape of a bind disk volume and I need to restore it to a single disk. I have seach the notes and they say that it can be done if you use /noinit with backup/image. I have tried this, but it still complained about the number of device in the output specifications.

I used the following command:

backup/image/noinit mka400:test.bck/sav dkd100:

Does anyone have any other way to do this?
I'm using OpenVMS 8.2 and the tape is an image backup from a 6.1-H3 bind disk set.

Thanks,

Howard

[Hoff]

Forget /IMAGE, unless you want to create and use LD logical disk driver or other such to recreate the numbers of members previously present in the bound-violume set. The massively brute-force equivalent would be the use of a RAID controller, and presenting disk volumes that way.

For details on using LD, see http://64.223.189.234/node/28
or various other LD-related documents posted around the 'net.

Why? /IMAGE preserves the file id, and one of the constituent fields of the file id contains the bound-volume volume number, and in aggregate this means BACKUP needs multiple output volumes to preserve the id.

The easiest way is to restore this saveset is using /SELECT; to perform a file-oriented restoration of the content of the saveset. This is the generic sequence used to reconstitute a bound-volume set

If this disk is a bootable device (system disk), you'll end up reconstituting the directory links; to perform the same sequence used to reconstruct a non-/IMAGE disk back into a bootable system disk. Bootable bound-volume disks are not supported and not reliable (as an ECO or an upgrade can easily cause key pieces of the bootstrap to end up on a disk other than the first volume, and to fail), but I've certainly seen MOUNT /BIND used to bind system disks; to configure a bound and (usually) bootable disk this way.

[Howard_24]

Thanks for the reply. I have tried to do it without the /image but it doesn't build the directory stucture correctly. I couldn't tell but it didn't look like /select would build the directory stucture either. I have a raid controller in the box and I have partition the disks that's why I'm running into the problem. The system the tape is coming from had the bind volume and I'm trying to only use one larger partiton on the raid controller, but I need to keep the structure of the disk.

I would like to restore and keep the directories and the file layout the same as the orignial disks.

Howard

[The Brit]

Try this (I think this is what Hoff is suggesting):

$ backup/NoInit/select=[*...]*.* mka400:test.bck/sav dkd100:[*...]*.*

Dave

Add "/Log" to verify that it is creating the necessary directory structure.

Also, since you are specifying /NoInit, you must make sure the disk in initialized manually before starting, the disk should be mounted normally, (not foreign).

Dave.

[Louis in Michigan]

To avoid using the /IMAGE qualifier, but to get everything back into the original directory tree, use the following BACKUP command for the restore:

"BACKUP save_set_device:save_set_file_spec.ext /SAVE_SET new_mounted_disk:[000000...]*.*;* /EXCLUDE=[000000]*.SYS;* /BY_OWNER=ORIGINAL /LOG"

This assumes a non-system disk save-set and will not restore any *.sys;* files that may be in the top-level directory ([000000]).

The target disk must be inited and mounted (not mounted foreign) before the restore operation.

If the save set is on a tape then you may wish to use the "/REWIND" qualifier. If the save set is on a disk then you will want to include the directory in the save set file specification.

[Robert Gezelter]

Howard,

I concur with Hoff's comments.

It would be helpful to do a BACKUP/LIST of the saveset and post the command used for the BACKUP to the forum. Then the way in which the saveset was generated would be definitively known, rather than a subject for speculation.

I would try using /SELECT also. The /NOINIT is also called for.

The precise error message would also be helpful. In nearly thirty years of system management (and being an advocate of using bound volumes where appropriate), I have not seen a situation that could not be resolved.

- Bob Gezelter, http://www.rlgsc.com

[Jan van den Ende]

Howard,

How much control/influence do you have over the SAN?

If sufficient, (and assuming suuficient temporary SAN space), (have) export(ed) the number and size of the original bound volumes, and restore /IMAGE the backup to a replica of the bound volume set.
Create a new volume big enough to hold the entire ensemble.
Now, use BACKUP to copy /own=orig the volume set to the new volume.
If satisfied with the result, destroy the volume set and give those volumes back to SAN management.

hth

Proost.

Have one on me.

jpe

[Jan van den Ende]

sorry,

forgot one thing:
IF there are (file- or directory-) aliases involved, you will have to recreate those by hand on the copy disk later on. Ib that case, carefully read the HELP on SET FILE/ENTER.

succes!

Proost.

Have one on me.

jpe