What kind of setup is this? A cluster or have you somehow connected two non-clustered nodes to the same storage?
---------- Post updated 2010-04-03 at 12:01 AM ---------- Previous update was 2010-04-02 at 11:58 PM ----------
Also can you post the output of:
Code:
vxdg -o alldgs list
Hello,
Thanks for reply.
This is a single machine (v440) connected via scsi cable to only ESM on storedge D2. Other scsi port is terminated using LVD/SE terminator. No cluster software on the v440 as well as no such intention.
Code:
vxdg -o alldgs list
VxVM vxdg ERROR V-5-1-776 Option alldgs not recognized, recognized options are:
failfast - set the failfast timeout for the disk (msec)
verify - verifies that the specified disk group task can be performed
without violating any storage-specific guidelines,
but does not perform the task
override - performs the disk group task and ignores any
storage-specific guidelines
remove - removes the objects involved in a move/split/join from
thisdiskgroup
complete - perform recovery by retrying original operation
clean - clear any move/split/join-related internal flags
expand - select additional objects that reside on same disks
dgtype - select dg type (private, shared, san)
clearreserve - clear reservations before import
groupreserve - import with group reserve
listreserve - show group reserve information with list command
ejectkey - eject host membership
dgid - need to use dgid for the dg to be initialized
selectcp - Select cp on this disk
site - Site based import
noreonline - Don't reonline disks
coordinator - dg disks reserved as coordinator disks
site - disk group site name
tag - disk group tag name[=value]
source - disk group tag source
useclonedev - import clone disks
updateid - update ids when importing clone disks
addmirror - Add mirror on the new site
rmmirror - Remove mirror on the site being removed
overridessb - Override SSB on reattaching a disk/site
alldisks - Reattach a site only if all disks are online
autotagging - Autotaging for newly added disks
Hi,
Can anybody provide me Pointers to Practice tests or any Material to prepare for Brainbench certification in Unix Shell Scripting? Also how good is this Certification for UNIX programmers. Is it worth it? I'm planning to take this certification in 2 weeks. Kindly let me know all the pros... (0 Replies)
Dear Gurus,
I have encountered a C question, which I thought of sharing with you.
This question was asked by one of my technical training staff...Though my training was over I'm still thinking of a solution for this..
Write a C program to do a small task(lets say just simply printing a "Hello... (34 Replies)
Hi Gurus,
To the Brain Teaser, if I add another condition, say the executable should not be altered, how the program should be altered? (no perl please, purely C). I forgot to mention this condition my staff had mentioned. ( forgot then and got now :D )
The program executed the first time... (4 Replies)
Hello!
I am working on an application which reads environmental instruments which have serial ports. The application requires a serial port to be present to talk to the device (i.e. /dev/ttyS0 ). In some instances the environmental devices will be 100's of yards away from the computer, so a... (5 Replies)
A global group of scientists are spending the next ten years and a billion dollars to try and develop a computer simulation of the brain:
https://www.humanbrainproject.eu/
I always found it fascinating that the brain can understand itself. This almost sounds like in a few years the computer... (0 Replies)
Discussion started by: figaro
0 Replies
LEARN ABOUT HPUX
vgmove
vgmove(1M)vgmove(1M)NAME
vgmove - move data from an old set of disks in a volume group to a new set of disks
SYNOPSIS
autobackup] diskmapfile vg_name
autobackup] diskfile diskmapfile vg_name
DESCRIPTION
The command migrates data from the existing set of disks in a volume group to a new set of disks. After the command completes successfully,
the new set of disks will belong to the same volume group. The command is intended to migrate data on a volume group from old storage to
new storage. The diskmapfile specifies the list of source disks to move data from, and the list of destination disks to move data to. The
user may choose to list only a subset of the existing physical volumes in the volume group that need to be migrated to a new set of disks.
The format of the diskmapfile file is shown below:
source_pv_1 destination_pv_1_1 destination_pv_1_2 ....
source_pv_2 destination_pv_2_1 destination_pv_2_2 ....
....
source_pv_n destination_pv_n_1 destination_pv_n_2 ....
If a destination disk is not already part of the volume group, it will be added using see vgextend(1M). Upon successful completion of the
source disk will be automatically removed from the volume group using see vgreduce(1M).
After successful migration, the destination disks are added to the LVM configuration files; namely, or The source disks along with their
alternate links are removed from the LVM configuration files.
A sample diskmapfile is shown below:
/dev/disk/disk1 /dev/disk/disk51 /dev/disk/disk52
/dev/disk/disk2 /dev/disk/disk51
/dev/disk/disk3 /dev/disk/disk53
The diskmapfile can be manually created, or it can be automatically generated using the diskfile and diskmapfile options. The argument
diskfile contains a list of destination disks, one per line such as the sample file below:
/dev/disk/disk51
/dev/disk/disk52
/dev/disk/disk53
When the option is given, reads a list of destination disks from diskfile, generates the source to destination mapping, and saves it to
diskmapfile.
The volume group must be activated before running the command. If the command is interrupted before it completes, the volume group is in
the same state it was at the beginning of the command. The migration can be continued by running the command with the same options and
disk mapping file.
Options and Arguments
The command recognizes the following options and arguments:
vg_name The path name of the volume group.
Set automatic backup for this invocation of
autobackup can have one of the following values:
Automatically back up configuration changes made to the volume group.
This is the default.
After this command executes, the command is executed for the volume group; see vgcfgbackup(1M).
Do not back up configuration changes this time.
Specify the name of the file containing the
source to destination disk mapping. If the option is also given, will generate the disk mapping and save it to
this filename. (Note that if the diskmapfile already exists, the file will be overwritten). Otherwise, will
perform the data migration using this diskmapfile.
Specify the name of the file containing the
list of destination disks. This option is used with the option to generate the diskmapfile.
When the option is used, no volume group data is moved.
Preview the actions to be taken but do not
move any volume group data.
Shared Volume Group Considerations
For volume group version 1.0 and 2.0, cannot be used if the volume group is activated in shared mode. For volume groups version 2.1 (or
higher), can be performed when activated in either shared, exclusive, or standalone mode.
Note that the daemon must be running on all the nodes sharing a volume group activated in shared mode. See lvmpud(1M).
When a node wants to share the volume group, the user must first execute a if physical volumes were moved in or out of the volume group at
the time the volume group was not activated on that node.
LVM shared mode is currently only available in Serviceguard clusters.
EXTERNAL INFLUENCES
Environment Variables
determines the language in which messages are displayed.
If is not specified or is null, it defaults to "C" (see lang(5)).
If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)).
EXAMPLES
Move data in volume group from to After the migration, remove from the volume group:
Generate a source to destination disk map file for where the destination disks are and
SEE ALSO lvmpud(1M), pvmove(1M), vgcfgbackup(1M), vgcfgrestore(1M), vgextend(1M), vgreduce(1M), intro(7), lvm(7).
vgmove(1M)
04-02-2010
