Veritas mirroring question

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat Veritas mirroring question
# 1  
Old 08-09-2012
Veritas mirroring question

Hi all, I'm fairly new to Veritas on Linux machines and have a disk group with 64 disks that we are migrating to 64 new disks. This means I'll be mirroring the old to the new. So my question is this - is there a way to mirror a specific volume to a range of disks as opposed to listing each disk by name?

example: vxassist -g dg1 mirror vol1 disk_dg65 - disk_dg128 ???

I'm hoping there is so I don't have to type or copy 64 disk names. Any help would be greatly appreciated!
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Question on Veritas file system..

Hi, I am on Solaris 10 server which is running Veritas. It's E420 server with two drives. I don't know much about Veritas. The other guy who works on this, on vacation this week. :-) Any way, looks like I have hard drive issue on the server. When I do iostat -E. I see this. sd0... (4 Replies)
Discussion started by: samnyc
4 Replies

2. Solaris

Help with mirroring rootdisk under veritas and boot from the mirror

Hi All, We are using Solaris 10 x86, and Veritas Storage Foundation Software version 6.0.1 and faced the following issues after mirroring and during boot from mirror. 1) VTOC has been changed after mirroring the rootdisk with this command - " /opt/VRTS/bin/vxrootmir <disk to be mirrored>".... (0 Replies)
Discussion started by: mprasamsa
0 Replies

3. Solaris

Undo the Veritas mirroring and update from Solaris 8 to Solaris 10

Hi all I wish to undo the mirroring for root and update the Solaris version from 8 to 10. Since i am lack of knowledge and experience on this, hope you all can help me double check the step and correct me. Existing disk groups details root@leo # vxdg list NAME STATE ID... (3 Replies)
Discussion started by: SmartAntz
3 Replies

4. Solaris

Quick question about mirroring

Hello! I have setup root mirror (d0) and swap mirror (d1) with 2 sub mirrors each Right now when I run metastat | grep -i progress it is resyncing but when I do an echo | format, I don't get the md info I also changed the information in /etc/vfstab after the mirrors sync...... (8 Replies)
Discussion started by: Keepcase
8 Replies

5. Solaris

Veritas Storage Question

How do you get the total size of the LUNS currently online on a Solaris 10 server running Symantec Storage Foundation? (2 Replies)
Discussion started by: soupbone38
2 Replies

6. UNIX for Advanced & Expert Users

Mirroring and Clustering with Veritas

Can anybody help me how to mirror the solaris 10 step-by-step with veritas. Have two disks. Then how can I cluster with veritas (1 Reply)
Discussion started by: karole
1 Replies

7. Solaris

Veritas root disk mirroring

Hi there, My task is to replace the two 73 G disks with two 143 G disks , which has vxvm 4.1 running on it. I would like to know whether the steps iam following are correct. 1. Break the sub-disks, plexes of the root mirror. 2. Remove the sub-disks,plexes of the root mirror. 3. Remove one of... (10 Replies)
Discussion started by: Jartan
10 Replies

8. UNIX for Dummies Questions & Answers

Veritas Question

Can someone tell me what command it is to list the disk in a specified disk group. I dont want to see disks in all groups, just the disk in a specified group. (2 Replies)
Discussion started by: TRUEST
2 Replies

9. UNIX for Dummies Questions & Answers

Question about this veritas command

vxdg -g mktdg adddisk mktdg02=c0b0t3d0 i know this command adds c0b0t3d0 to the disk group mktdg but what i dont know is what the significance of mktdg02 is. i mean, what is it? what does it stand for?? (1 Reply)
Discussion started by: TRUEST
1 Replies
Login or Register to Ask a Question
vxdiskadd(1M)															     vxdiskadd(1M)

NAME
vxdiskadd - add one or more disks for use with Veritas Volume Manager SYNOPSIS
vxdiskadd disk_address_pattern_list DESCRIPTION
The vxdiskadd utility configures disks for use by Veritas Volume Manager (VxVM). Disks must already have been formatted. vxdiskadd prompts the user for a disk group name and disk name for the disks. If no disk group name specified, the disks will be left as unassigned replacement disks for future use. A new disk group may be created that will become the disks' disk group. If a disk group is specified for the disks, the user is prompted for whether the disks should be designated as spares for the disk group. For new disks, all space on the disk becomes free space in the disk's disk group. vxdiskadd interactively allows initialization to be done for all the disks specified or allows the user to ask to make the decision for each disk individually. One or more disks may be specified with a disk_address_pattern_list. The basic form of a disk address is c#t#d#. Any leading portion of this address may be specified to indicate that all disks that match that leading portion should be used. For example c2t0 may be used to specify all disks on controller 2, target 0. More than one disk address or address pattern may be specified on the command line. In case of enclosure-based names, the disk address will be of the form enclosurename_diskno. The enclosurename indicates that all disks in the specified enclosure are used. For example, emc1_ is used to specify all disks in the enclosure emc1. The word all may be used to specify all disks on the system. Disk address names relate directly to device node names in the /dev/dmp and /dev/rdmp directories. Here are more examples: all: all disks c3 c4t2: all disks on controller 3 and controller 4, target 2 c3t4d2: a single disk (in the c#t#d# naming scheme) xyz_0 : a single disk (in the enclosure based naming scheme) xyz_ : all disks on the enclosure whose name is xyz The files /etc/vx/cntrls.exclude, /etc/vx/disks.exclude and /etc/vx/enclr.exclude may be used to exclude controllers or disks from use by vxdiskadd. Each line of cntrls.exclude specifies the address of a controller to exclude, for example, c2. Each line of disks.exclude spec- ifies a disk to exclude, for example, c0t3d0. Each line of enclr.exclude specifies the name of an enclosure to exclude, for example, enc0. All courses of action that do not involve clear failure conditions require prompts from the user, with defaults supplied as appropriate. Help is made available at every prompt. Entering ? in response to a prompt displays a context-sensitive help message. OPERATIONS
Reconnecting a drive that was temporarily inaccessible This situation is detected automatically by noting that the specified drive has a disk ID that matches a disk media record with no currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes referring the disk are restarted. This reattach action is performed by calling the vxrecover utility. Initialization of a disk with reserved regions Initialization of the disk is performed by calling vxdisksetup. Adding a disk to an existing disk group This operation can be performed independently of the initialization of the disk drive. The operation adds the disk to the group so that its storage is added to the free space pool in that disk group. The vxassist utility can subsequently allocate from that free space. Creation of new disk groups in which to import a new disk If disks are added that are required to be put into a disk group that does not exist, the option of creating the disk group is offered. Hardware-Specific Note Some environments provide guidelines to optimize VxVM's interaction with intelligent storage systems. If these guidelines are present, VxVM follows the guidelines when adding disks to disk groups. If the operation fails due to these guideline(s), you are prompted to use the force option. The force option ignores any such storage-specific guidelines. FILES
/etc/vx/cntrls.exclude Specifies the address of controllers to exclude from vxdiskadd operations. /etc/vx/disks.exclude Specifies the address of disks to exclude from vxdiskadd operations. /etc/vx/enclr.exclude Specifies the address of enclosures to exclude from vxdiskadd operations. NOTES
EFI disks cannot be added to a disk group that is compatible with the Cross-platform Data Sharing (CDS) feature, nor can they be formatted as CDS disks. SEE ALSO
vxassist(1M), vxdisk(1M), vxdiskadm(1M), vxdisksetup(1M), vxintro(1M), vxrecover(1M) VxVM 5.0.31.1 24 Mar 2008 vxdiskadd(1M)