Sponsored Content
Operating Systems AIX Migrating LUNs to new storage array Post 303038794 by eckertd on Friday 13th of September 2019 10:07:26 AM
Old 09-13-2019
One thing I would add would be before importing the DG, have the storage team tell you what queue_depth you should be using and set accordingly

Code:
# chdev -l hdisknn -a queue_depth=#

If you've already imported, you can still run the above, but append "-P" to the end. This will make the change in the ODM (CuDv, I believe) and the settings will be applied next reboot.
 

6 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Storage array question

We just purchased a MOD30 disk array strage system. We have 15 drives and 2 hot spares. We're running a database app with 8 data sets. I'm trying to get the best i/o speed out of my disk configuration. Right now I have 3 raid5 arrays setup. This seems to offer the same performance as having the... (1 Reply)
Discussion started by: ncmurf00
1 Replies

2. Filesystems, Disks and Memory

how can I monitoring the LUNs in HP storage

Hi, How can i monitoring the LUN in HP Storage with korn shells? I would like to have a shell can monitoring the LUN, VGs, lvols and raw devices. Jesus (3 Replies)
Discussion started by: jgutierrez29
3 Replies

3. Solaris

storage array simulator

hi i haven't much experience in solaris. I would like to know about storage. how to configure,how it is working etc....can i get any simulator for doing these work? plaese send me the link . please help me advance thanks to all (2 Replies)
Discussion started by: sijocg
2 Replies

4. HP-UX

HP Storage Array

hi I need to check status and configure HP Storage Array device. HP Storageworks P2000 Please suggest (0 Replies)
Discussion started by: anand87
0 Replies

5. UNIX for Advanced & Expert Users

VxVM breaking mirror for migrating storage

We are in the process of migrating storage from one array to another. I know the commands I would use in LVM but I am not very familiar with VxVM. The goal is to attach the new LUNs from the new array and add them to the disk group. Then mirror the data online to these new LUNs using VxVM... (4 Replies)
Discussion started by: keelba
4 Replies

6. Red Hat

Migrating an Oracle database storage - REDHAT4

e have a RHEL4 server with an Oracle 10 ( RAC ) are migrating storage bank records. The copy is made by the storage they make a copy of the level of disk all blocks are copied and the file permissions. Problems we had Initially the Cluster service was not rising due to absence of OCR disks... (0 Replies)
Discussion started by: fausto.ncc1701
0 Replies
VGIMPORT(8)						      System Manager's Manual						       VGIMPORT(8)

NAME
vgimport - make volume groups known to the system SYNOPSIS
vgimport [-d|--debug] [-f|--force] [-h|--help] [-v|--verbose] VolumeGroupName PhysicalVolumePath [PhysicalVolumePath...] DESCRIPTION
vgimport allows you to make a volume group known to the system which has previously been exported (see vgexport(8) ) on this or another system. OPTIONS -d, --debug Enables additional debugging output (if compiled with DEBUG). -f, --force Force import of volume group even though it is not flagged exported. This option allows the importing of volume groups from broken systems. -h, --help Print a usage message on standard output and exit successfully. -v, --verbose Display verbose runtime information about vgimport's activities. Examples "vgimport myvg /dev/sd[b-h]5" tries to make new volume group "myvg" known to the system. The previously exported volume group (see vgex- port(8) ) resides on disk partitions "/dev/sdb5" to "/dev/sdh5". DIAGNOSTICS
vgimport returns an exit code of 0 for success and > 0 for error: 1 no volume group name on command line 2 invalid volume group name 3 no physical volume(s) on command line 4 volume group already exists 5 physical volume occurs mutiple times on command line 6 invalid physical volume name 7 error reading physical volume 8 physical volume is not exported 9 error reallocating memory 10 error allocating memory 11 no valid physical volumes found 12 physical volume belongs to a different exported volume group 13 wrong number of physical volumes 14 error reading VGDA from disk(s) 15 VGDA is inconsistent 16 invalid logical volume count 17 error getting a free volume group number 18 error writing VGDA to physical volumes 19 error creating VGDA in kernel 20 error inserting volume group into lvmtab 21 error doing backup of VGDA to disk 22 error storing VGDA in lvmtab 23 not enough free logical volume manager block specials available 95 driver/module not in kernel 96 invalid I/O protocol version 97 error locking logical volume manager 98 invalid lvmtab (run vgscan(8)) 99 invalid command line Example "vgimport this_import /dev/sdk3 /dev/sdj4" tries to import a volume group contained on both partitions. The volume group this_import may not already exit. You have to specify all physical volumes belonging to the exported volume group. See also lvm(8), lvcreate(8) AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com> Heinz Mauelshagen LVM TOOLS VGIMPORT(8)
All times are GMT -4. The time now is 04:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy