02-21-2008
migrate complete OS from v240 to v440
We are concluding development of a new application on a v240 and would like to migrate the entire Solaris10 OS on the v240 to a v440 that is currently live with Solaris 9.
The steps outlined in my head are as follows:
1) Flash archive the v440 and v240 and store the flar file on a different server.
2) Flash install on the v440 from the v240 flar.
Now, I'm not sure what needs to be done next to get all the devices up to date. Do I need to boot into single user mode and delete the /dev directory and run devfsadm? What else needs to be done?
Thanks.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I trying to jumpstart SunFire V240 Solaris 10, 2006_01. All the jumpstart files on jumpstart install and boot server are ok (tested on another machine Sun Ultra 10). But this system comes out with: "The file just loaded does not appear to be executable." after "boot net - install" and setting... (0 Replies)
Discussion started by: jump
0 Replies
2. Solaris
Hello all,
This is probably a commonly asked question, but it has me stumped.
I have a V440 which upon bootup gives me the option of getting into ALOM with #. I don't have the ALOM password so I want to re-install Solaris 10.
When connected to the Management serial interface (on the PCI... (3 Replies)
Discussion started by: juanj
3 Replies
3. UNIX for Dummies Questions & Answers
Hi,
Does anyone know how to make BASH provide a list of possible completions on the first tab, and then start cycling through the possibilites on the next tab?
Right now this is what I have in my .bashrc:
bind "set show-all-if-ambiguous on"
bind \\C-o:menu-complete
This allows... (0 Replies)
Discussion started by: Mithu
0 Replies
4. Solaris
Hi,
we are having one sun v240 server, now this server is performing very slow,
checked using top, iostat and vmstat commands, output is looking normal, but the performance is very slow and generating more traffic in network,
how can we resolve this.
Regards
RJS (5 Replies)
Discussion started by: rajasekg
5 Replies
5. Solaris
I recently acquired a server for home use. Currently, I'm running a V210. I was wondering of a way to basically swap hard drives into the V440.
I would like to avoid reinstall on the V440 for many reasons.
Currently on the V440, when I try to boot up it forces itself into System Maintenance... (1 Reply)
Discussion started by: adelsin
1 Replies
6. Solaris
I'm currently trying to move a perfectly find harddrive from a V210 to a V440. From what I can tell, the disk labeling a bit different, (V210 is c1t0d0 and V440 is c0t0d0). My question is, what all do I have to change to get the V440 to boot off of this with very little complications. Right now, it... (21 Replies)
Discussion started by: adelsin
21 Replies
7. Solaris
hallo anybody know how to set alom mail alerty server with yahoomail ?
thank u?where i can find mail server address for yahoomail?thank (1 Reply)
Discussion started by: yanto85
1 Replies
8. Solaris
had a v240 pre-configured and running the OS and alom, for about 3 months good, no issues.
All of sudden, I can't see the IP address of the OS and the alom..
There is nothing wrong with thet network...
I suspect the ALOM crashed and/or something bad happened to it..
Is there anyway... (3 Replies)
Discussion started by: ppchu99
3 Replies
9. Solaris
We have a v240 running Solaris 10, and an application that I don't want to go through the pain of reinstalling on a new system right now.
Can I just move those disks to a v440 for an easy upgrade?
At first I thought the idea was laughable, but then I started thinking that they are both Ultra... (9 Replies)
Discussion started by: lyle
9 Replies
10. Solaris
Hey guys,
I recently replaced the heatsinks on two different V240's. Repasted and replaced them myself. After attempting to bring them back up, there was no display coming from the KVM. I figured it was a matter of environment in OBP and attempted to get to the OK prompt from the... (20 Replies)
Discussion started by: DanielSluder
20 Replies
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)