SAN Migration of HP-UX hosts Post: 302738995

10 More Discussions You Might Find Interesting

1. HP-UX

SAN migration

Hi, I'm going to be involved in a migration of SAN islands to one big SAN. I've not worked with SANs before and I'm not sure how to approach this. I suspect the disk devices on the HP servers are going to change, when the EVA's and servers are plugged into this new Cisco 9509 switch. Any...

2. Solaris

Thoughts/experiences of SAN attaching V880 to EMC SAN

Hi everyone, I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN? At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the...

3. AIX

aix tcp wrappers hosts.allow hosts.deny?

hi all just installed the netsec.options.tcpwrapper from expansion pack, which used to be a rpm, for my aix 6.1 test box. it is so unpredictable. i set up the hosts.deny as suggested for all and allow the sshd for specific ip addresses/hostnames. the tcpdchk says the hosts allowed and...

4. Solaris

Need Help On Solaris Cluster Steps For San Migration

I am going to do a SAN Array migration and need the sequence of steps required on the Solaris cluster before moving the old array luns to new array luns. Here are the steps and I need info on the bold points:( I might even be wrong on the sequence of steps please correct me if I am wrong) 1....

5. AIX

SAN Migration

Hi all, We are migrating our SAN storage from HSV360 to 3PAR. The system runs aix 6.1 version with HACMP. Please let me know what are requirements from OS side and how are the data copied to the new disks.

6. HP-UX

SAN Migration question

Hi, I am very new to HP-UX, and we're going to be doing a SAN migration. We're going to take down the machine, and zone it to the new SAN. My question is, will the device names change and will that interfere with the LVM? If the new disks come in with different device names, how would I...

7. Red Hat

Volume group not activated at boot after SAN migration

I have an IBM blade running RHEL 5.4 server, connected to two Hitachi SANs using common fibre cards & Brocade switches. It has two volume groups made from old SAN LUNs. The old SAN needs to be retired so we allocated LUNs from the new SAN, discovered the LUNs as multipath disks (4 paths) and grew...

8. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much!

9. Solaris

How to identify if disk is attached to SAN and assist in migration.?

I am working on VM host and collecting data to identify the type of storage attached to the server which will be migrated to VNX. it has one ldom created on it luxadm probe output --- No Network Array enclosures found in /dev/es Found Fibre Channel device(s): Node...

10. Solaris

How to copy a tar file on a series of remote hosts and untar it on those hosts?

Am trying to copy a tar file onto a series of remote hosts and untar it at the destination. Need to do this without having to do multiple ssh. Actions to perform within a single ssh session via shell script - copy a file - untar at destination (remote host) OS : Linux RHEL6

LEARN ABOUT HPUX

pvck

pvck(1M)																  pvck(1M)

NAME

       pvck - check or repair a physical volume in LVM volume group

SYNOPSIS

       pv_path

       pv_path

DESCRIPTION

       This command is supported for arguments belonging to volume groups version 1.0.	Attempting this command with arguments belonging to volume
       groups version 2.0 or higher will result in an error.

       Note: Currently is only capable of detecting bad checksums caused by a forward system migration	after  a  backward  system  migration.	It
       should not be used in other situations.

       The command examines and repairs LVM data structures on a raw disk (pv_path) in a volume group.

   Options and Arguments
       recognizes the following options and arguments.

	      Repair problems found.

	      Report, but do not repair problems.

	      pv_path	The raw device path name of a physical volume.

RETURN VALUE

       returns the following values

	      Either no problems were found or all problems were corrected.

	      Unable to repair.

EXAMPLES

       Examine LVM checksums on without modifying anything:

       Repair LVM checksums on if necessary:

WARNINGS

       should only be run on a device whose volume group has not been activated.

       is designed to repair the root device or devices while the system is booted in maintenance mode ("", see hpux(1M) on PA-RISC systems).

AUTHOR

       was developed by HP.

SEE ALSO

       intro(7), lvm(7).

																	  pvck(1M)