05-06-2014
Hi Gull04
I am not sure how to check about how are they attached. I am just in the learning phase. if you tell me what details you need in specifi , i can provide them to you.
Hi Robin,
We havnt started the migration yet hence the disks are not added.
I was wondering whether i need to upgrade firware or hba level for this. should i change the mpio?
Also the rootvg doesnt need to be touched right? they are SCsi disks.
so i suppose its only the dataVg that needs to be migrated.
So when its a cluster environment do i need to make any changes in the hacmp configuration after the migrations?
Thanks in advance!
10 More Discussions You Might Find Interesting
1. HP-UX
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... (0 Replies)
Discussion started by: Hils
0 Replies
2. Solaris
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... (2 Replies)
Discussion started by: si_linux
2 Replies
3. AIX
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 ? (1 Reply)
Discussion started by: filosophizer
1 Replies
4. HP-UX
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... (5 Replies)
Discussion started by: jps460
5 Replies
5. Solaris
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.... (0 Replies)
Discussion started by: sunshinedeepu
0 Replies
6. HP-UX
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... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
7. Red Hat
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... (4 Replies)
Discussion started by: rbatte1
4 Replies
8. AIX
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 Replies)
Discussion started by: BG_JrAdmin
4 Replies
9. Solaris
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... (7 Replies)
Discussion started by: kpatel786
7 Replies
10. Filesystems, Disks and Memory
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... (6 Replies)
Discussion started by: rino19ny
6 Replies
LEARN ABOUT SUNOS
asupgrade
asupgrade(1m) Application Server Utility asupgrade(1m)
NAME
asupgrade - migrates the configuration of a previously installed Sun Java System Application Server
SYNOPSIS
asupgrade [-c | --console] [-V --version] [-h | --help]-s | -source applicationserver7.x_installation -t --target application-
server8.x_installation [-d | --domain domain_name -n | --nsspwdfile NSS_password_filepath -j | --jkspwdfile JKS_password_filepath -p |
--capwdfile CA_password_filepath]
Use the asupgrade utility to migrate the server configration and its persisted state, J2EE services, and deployed J2EE applications. The
configuration of an installed Sun Java System Application Server 7 is migrated to the Sun Java System Application Server 8 Application
Server installation. If the domain contains information about a deployed application and the installed application components do not agree
with the configuration information, the configuration is migrated as is without any attempt to reconfigure the incorrect configurations.
asupgrade migrates the configuration and deployed applications of a previous version of the Application Server; however, the runtime bina-
ries of the server are not updated. Database migrations or conversions are beyond the scope of the asupgrade command.
Only those instances that do not use the Sun Java System Web Server specific features will be upgraded seamlessly. Configration files
related to HTTP path, CGI bin, SHTML, and NSAPI plugins will not be upgraded.
The upgrade process can also be initiated automatically at installation time using the Upgrade checkbox in the Application Server install-
er. After completion of the upgrade, use the Application Server 7 Uninstaller to remove the previous version of the Application Server.
Application archives (.ear) and component archives (.jar, .war, .rar) that are deployed in the Application Server 7 environment do not
require any modification to run on Application Server 8. However applications and components deployed in the source server are repackaged
into new J2EE archives in the target server's autodeploy directory and are deployed upon server startup. Applications that do not deploy
successfully, must use Migrationtool (asmigrate) on the application and then manually redeploy the application.
You must specify the source and target directories for the upgrade. If the upgrade includes certificates, you must also provide the pass-
words for the source PKCS12 file and the target JKS keyfile for each domain that contains certificates to be migrated. Since Application
Server 7 uses a different certificate store format (NSS) than Application Server 8 (JSSE), the migration keys and certificates are con-
verted to the new format. Upon successful upgrade, an upgrate report is generated listing successfully migrated items along with a list of
the items that could not be migrated.
OPTIONS
-c --console launches the upgrade command line utility.
-V--version displays the version of the UpgradeTool.
-h--help displays the arguments for launching the UpgradeTool.
-s--source identifies the installation directory for Sun Java System Application Server 7.
-t--target identifies the installation directory for Sun Java System Application Server 8.
-d--domain identifies the destination domain name for the migrated certificates.
-n--nsspwdfile identifies the path to the NSS password file.
-j--jkspwdfile identifies the path to the JKS password file.
-p--capwdfile identifies the path to the CA certificate password file.
EXAMPLES
Example 1: Using asupgrade
example% upgrade -s /home/sunas7 -t /home/sunas8
SEE ALSO
asmigrate(1M)
Sun Java System Application Server March 2004 asupgrade(1m)