migrate from ssa to san

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

Removing Faulty Disk SSA

Hi Experts, I have configured A D40 Array. There is an faulty disk which is not part of an raid volume but shows fault in the diagnostics. pdisk15 U0.1-P1-I1/Q1-W40AA83CC2400D SSA160 Physical Disk Drive ( MB) Is there a way to stop this...

3. AIX

Procedure for removing SSA array

Hi All, What's the proper procedure for removing SSA arrays? Is the procedure like these? - rmdev ssa disk - physical turn off the ssa - cfgmgr There's no more filesystem or logical volume on it. It's just pdisk and hdisk. Thanks in advance, itik

4. AIX

mirroring ssa to san

Hi guys, I'd like to share my migration/mirroring of ssa to san. No downtime for users, probably I/O performance. here's the step: 1 After the lun had been carved on the SAN and the connections had been done on AIX fiber card 2 “lspv” and look for the new SAN hdisk? on the bottom, say...

5. Linux

Howto clone/migrate a volume in the SAN

Dear Srs, I have a Linux server (linux01) booting from SAN with a volume in a Nexsan SATAbeast storage array (san01). The disk/volume has four ext3 partitions, total size is near to 400GB, but only 20-30GB are in use. I need to move this disk/volume to another Nexsan SATAbeast storage array...

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

7. AIX

Problem with a SSA drive

I've a problem with an IBM StorageWorks - Seagate SSA drive, model ST373453LC (IBM P/N 24P3733, Type S53D073, 72,8 GB 15K - USCSI 4 - 320 SSA). I bought this disk used but working; it came from an unknown IBM SSA storage array. I've removed the SCA - SSA adapter (IBM 18P3051 - 001 - R0) and i tried...

8. AIX

updating ssa

I am in the process of updating ssa adapters, drives and enclosures and wanted to know if there are any caveats that anyone would like to share. The documentation is not very clear on the ordering of the updates. Any tips would be appreciated.

9. AIX

ssa performances

Helo: We updated form AIX 4.3.3 to AIX 5.1-7 and after this we spent more than double time in read from external disks. Aparently the ssa cards microcode is at last level and all the ptf and apars are instaled. Out backups expent more than double time, but curiously in read only, if we write in...

10. AIX

RS6000 SSA Raid question

Hi Can I add disks on the fly to extend the capacity of an existing RAID 5 volume? It's created on a 4P Advanced SSA Raid Adapter. I need to extend a volume group, so I figured it would be easiest to extend the "physical disk" which is a RAID5 volume. Thanks.

LEARN ABOUT DEBIAN

vzmigrate

vzmigrate(8)							    Containers							      vzmigrate(8)

NAME

       vzmigrate - migrate a container between two OpenVZ servers

SYNOPSIS

       vzmigrate [-r|--remove-area yes|no] [--ssh=ssh_options] [--rsync=rsync_options] [--keep-dst] [--online] [-v] destination_address CTID

DESCRIPTION

       This  utility  is  used	to  migrate  a container from one (source) Hardware Node (HN) to another (destination) HN. The utility can migrate
       either stopped or running container. For a stopped container, simple CT private area transfer is  performed  (rsync(1)  is  used  for  file
       transfer). For running containers, migration may be offline (default) or online.

       This  program uses ssh as a transport layer. You will need to put ssh public key to destination node and be able to connect to node without
       entering password.

OPTIONS

       -r, --remove-area yes | no
	      Whether to remove a container area on source HN for the successfully migrated container. Default is yes.

       --ssh=options
	      Additional options that will be passed to ssh while establishing connection to destination HN.

       --rsync=options
	      Additional options that will be passed to rsync(8).  You may add options like -z to enable data compression  if  you  are  migrating
	      over a slow link.

       --keep-dst
	      Do  not  clean  synced  destination container private area in case of some error. It makes sense to use this option on big container
	      migration to avoid syncing container private area again in case some error (on container	stop  for  example)  occurs  during  first
	      migration attempt.

       --online
	      Perform  online (zero-downtime) migration: during the migration the container hangs for a while and after the migration it continues
	      working as though nothing has happened.

       -v     Verbose mode. Causes vzmigrate to print debugging messages about its progress.  Multiple -v options  increase  the  verbosity.   The
	      maximum is 3.

EXAMPLES

       Migration of CT 101 to 192.168.1.130 with downtime:

	  vzmigrate 192.168.1.130 101

       Online migration of CT 102 to 192.168.1.130:

	  vzmigrate --online 192.168.1.130 102

EXIT STATUS

       0 EXIT_OK
	      Command completed successfully.

       1 EXIT_USAGE
	      Bad command line options.

       2 EXIT_VE_STOPPED
	      Container is stopped.

       4 EXIT_CONNECT
	      Can't connect to destination (source) HN.

       6 EXIT_COPY
	      Container private area copying/moving failed.

       7 EXIT_VE_START
	      Can't start or restore destination CT.

       8 EXIT_VE_STOP
	      Can't stop or checkpoint source CT.

       9 EXIT_EXISTS
	      Container already exists on destination HN.

       10 EXIT_NOTEXIST
	      Container does not exists on source HN.

       12 EXIT_IP_INUSE
	      You attempt to migrate CT which IP address(es) are already in use on the destination node.

       13 EXIT_QUOTA
	      Operation with CT quota failed.

SEE ALSO

       rsync(1).

COPYRIGHT

       Copyright (C) 2001-2010, Parallels, Inc. Licensed under GNU GPL.

OpenVZ								    28 Jun 2011 						      vzmigrate(8)

AIX