Specify NEWLABEL when using HiDRO DUP to copy Linux disk
search cancel

Specify NEWLABEL when using HiDRO DUP to copy Linux disk

book

Article ID: 263824

calendar_today

Updated On:

Products

VM:Backup High-Speed Disaster Recovery Option (HiDRO)

Issue/Introduction

We have a E000 disk on a Linux server that we are trying to copy to another Linux server.

Using command: DUP UNIT E000 USER (LINUXA) TO UNIT E000 USER (LINUXB) (IVORG UND OVORG UND

After trying to use the disk on LINUXB, it won't activate it.

Noting that VMSECURE DUPMDISK worked.

 

Environment

HiDRO release 2.8

Cause

The issue here is that the VOLSER is somehow used as a factor in the encryption, or when the new VOLSER is stored on the target it is not encrypted.

 

Resolution

Need to specify the NEWLABEL option.

Specify NEWLAB (VOL ORIG) on the DUP.

 

For more information, see the NEWLABel Option DUPlicate Operation, documented at:

https://techdocs.broadcom.com/us/en/ca-mainframe-software/traditional-management/ca-vm-backup-for-z-vm-hidro-component/2-8/command-reference/duplicate-operation/local-options-for-duplicate-operations/newlabel-option-duplicate-operation.html

 

Additional Information

Able to see the label in plain-text on both the input and output volumes. When they did not match, they failed to become active after the server booted.

When they did match (using NEWLABEL), there was no issue which is an indication the (original) VOLSER must be involved in the encryption process.