SAN migration

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Faster way: SAN hd to SAN hd copying

hi! i got a rhel 6.3 host that already have an xfs filesystem mounted from a SAN (let's call it SAN-1) whose size is 9TB. i will be receiving another SAN (let's call it SAN-2) storage of 15TB size. this new addition is physically on another SAN storage. SAN-1 is on a Pillar storage while the new...

2. 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...

3. 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!

4. 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...

5. 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...

6. 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.

7. 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....

8. HP-UX

SAN Migration of HP-UX hosts

Hello gurus, I am a SAN Admin - not very familiar with the HPUX administration - so need help with the steps in regards to the migration I need to do at my client place. Environment: Migrating from CX4 to VMAX - using OR/Hot Pull. Here are the steps I have put together - HPUX gurus please...

9. AIX

IBM SAN TO SAN Mirroring

Has anyone tried SAN to SAN mirroring on IBM DS SAN Storage. DS5020 mentions Enhanced Remote Mirror to multi-LUN applications I wonder if Oracle High availibility can be setup using Remote Mirror option of SAN ?

10. 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...

LEARN ABOUT HPUX

st_ats_enabled

st_ats_enabled(5)						     OBSOLETED							 st_ats_enabled(5)

NAME

       st_ats_enabled - determine whether to reserve a tape device on open (OBSOLETED)

VALUES

   Default
   Allowed values
       or

   Recommended values
DESCRIPTION

       Note: this tunable is obsoleted and has been renamed to beginning with release HP-UX 11i v3.

       This  tunable  notifies	the stape or estape driver whether it needs to reserve a tape device on open and subsequently release it on close.
       When this tunable is on the stape or estape driver will attempt to reserve any tape device on open.  The driver	has  a	few  tape  devices
       flagged	as  suitable  devices  for  this functionality including DLT 8000, DLT 7000, STK 9840, HP Ultrium, and others.	DDS drives are not
       flagged for this functionality.

       The tunable allows the safe sharing of tape devices in multinode configurations like MC/ServiceGuard's Advanced Tape  Sharing.	The  auto-
       matic  reserve  and  release protects the tape device from being accessed from multiple nodes which would corrupt a backup.  If the reserve
       portion of the stape or estape driver's open routine fails, a status of is returned.

   Who Is Expected to Change This Tunable?
       Anyone.

   Restrictions on Changing
       Changes to this tunable take effect immediately and are used during the next open or close.

   When Should the Tunable Be Turned On?
       This tunable should be turned on if the system will be used in an MC/ServiceGuard Advanced Tape Sharing configuration or the user wants the
       stape or estape driver to use automatic reserve or release on open and close for multinode manageability.

   What Are the Side Effects of Turning the Tunable On?
       A  reserve is sent to the tape device by the stape or estape driver on open and a release is sent on close.  No other initiator or HBA will
       be able to access the tape device while it is opened on another initiator or HBA.

   When Should the Tunable Be Turned Off?
       This tunable should be turned off for any SAN tape sharing solution configuration other than ATS.  Most multinode backup applications  (for
       example, Omniback) manage device reservation themselves and any interference by the stape or estape driver may produce problems.  This tun-
       able should also be turned off for any multiplatform SAN configuration to keep tape access across platforms more uniform.

   What Are the Side Effects of Turning the Tunable Off?
       Unauthorized access from another initiator might interfere with any current tape operation.

   What Other Tunables Should Be Changed at the Same Time?
       None.

WARNINGS

       All HP-UX kernel tunable parameters are release specific.  This parameter may be removed or have its meaning changed in future releases	of
       HP-UX.

       Installation  of  optional  kernel  software, from HP or other vendors, may cause changes to tunable parameter values.  After installation,
       some tunable parameters may no longer be at the default or recommended values.  For information about the effects of installation  on  tun-
       able  values,  consult  the documentation for the kernel software being installed.  For information about optional kernel software that was
       factory installed on your system, see at

AUTHOR

       was developed by HP.

SEE ALSO

       st_ats_enable(5), scsi_tape(7), scsimgr_estape(7).

							     Tunable Kernel Parameters						 st_ats_enabled(5)

HP-UX