Move root disk to new server

Hi,
I need to do an installation where I have identical hardware at both sites and create the installation at one site and take the disk to the other site. Question: Do I need to do anything special for the OS to come up properly?

thanks.

Should work fine.

yeah, should be fine, just do a reconfiguration reboot on the second site to be sure.

Thanks. To thicken the issue, I'm running VxVM. I guess I'll need to install the VxVM license at the new site. Do I install the license at the ok prompt prior to the first boot -r command?

No, the root disk will be an encapsulated UFS filesystem, and will boot. You should boot and then apply the license.

Actually, thinking about this further is could be best to unencasulate the disk before moving it and reencapsuleate it at the new site.

storage is involved. will that blow up the storage?

Maybe you should post some more info - your original question wasn't very informative as far as the many things you have going on. You stated everything was identical and then afterwards mentioned VxVM - is the root partition controlled by Veritas? What do you mean by storage is involved? You stated you were moving "the disk".

Post the OS and version
Post the Veritas VM version
Post the hardware information
Post any other relevant information on what you are trying to accomplish.

Sorry for the leaking details.
V240 and a Storedge 3310
solaris 8 , Vxvm 3.5
root disk encalsulated and mirrored, 7 other disks in another dg.

I want to move all these disks into another v240 and 3310.

Thanks again.

Having read your last reply I have a few further questions.

  1. You mean volumes not disk, don't you? Or is it 7 LUNs?
  2. Are these volumes mirrored in veritas?
  3. Do you mean to move the volumes physically or logical? (ie is it the disks in the array or is it the volumes or is it that you want to move the existing 3310 to another 240?
    3(a) or is it just a new root disk any you want to import the existing volumes on the 3310 to the new root disk?

I guess what it really comes down to is, are you trying to clone the existing setup?

StorEdge 3310 JBOD without RAID Controller or a RAID Controller based one ?

there are 7 more disks. 3 are mirrored with a hot spare.
it is more less a clone. i can't build at the site these disks will reside. i will physically move all the disks from the V240 and 3310 and fly the disk half way around the world, and install the disks in a new v240 and 3310.

no hardware raid.

In a sentence, that probably won't work.

I will reply in a little while in more detail with a possible alternative strategy for you to explore. One more question that come to mind now though is, is the 3310 in single or dual bus configuration? If you are unsure about this, then did you need to edit sd.conf when installing?

it is in a dual bus config. I haven't installed yet. This is in the planning stage of how to do a new install of os,db,app on a server that is currently in use. i look forward to your reply. :slight_smile:

Sorry for the delay I got called away to other things after my last post.

I'm just doing up the full reply now.

On think to note is that this assumes that the arrays are configured with the same number of LUNs.

Obviously given the amount of information in this I can't suppy you will all of the command to do all of these tasks in one post, but it should get you pointed in the right direction.

  1. Stop any databases you have running on your system.
  2. Detach the mirrors of each of your volumes
  3. Dump the inactive mirrors of your data volumes to tape
  4. Shudown and remove the 2nd mirror of the root disk or dump it to tape
5. Detach mirrors
6. Restore root disk to detached mirror of the root disk \(or replace it with the disk you removed from the first machine\)
7. Create data volumes on the detached mirror and restore from tape
8 Reboot to single user mode using the \(currrently detached\) 2nd mirror
9.Apply the new veritas lincense & reboot again using the 2nd mirror
10. If every thing is working remirror using the 2nd mirror as the master

Note that using this approach there is no downtime on the target system until \#8

Another approach would be to use Veritas NetBackup to achieve most of this.

sry for reading that post late,
:eek: :eek:
but:

with veritas you bought a very good developed volumemanager, there is no need to detach mirrors or volumes in VxVM! if you really have the same hardware, you only need to put the "old" things in the new one.

in a v240 there is a card which is called the "System Configuration Card" (SCC) where the HOSTID is stored (hostid and nvram settings). you need to put the old card in the new mashine to provide the right HOSTID to your VxVM license.

in theory you could put in those disk in any order... that'S a feature of VxVM... when the kernel starts a demon (vxconfigd) looks at all attatched disks and reads the privat region on the disk to see which diskgroup and which volume (data in public region) configuration is on the disk [manual command would be: "vxdctl enable"] that's a big different to SDS/LVM because it handles the volumes with local databases (metadb) but VxVM stores the information on each disk. that's the reason for the logical split of the disk into privat and public regions.
###
by the way: there are also feature for deporting and importing. take a look at the command vxdg {deport|import]. to see all diskgroups not only the imported use that command: "vxdisk -o alldgs list"
###
the dual way to the disks should be enable afterwards with the veritas DMP. enable it for the disks. (could be done with the "vxdiskadm" cli interface or with the cli command "vxdmpadm") i'm not sure if DMP will work if there are no controllers in the 3310 just a jbot. take a look at the instructions in the "Enabling VERITAS DMP" section of the Sun StorEdge 3000 Family Installation, Operation, and Service Manual on docs.sun.com.

anyway. the idea with the backup should not be ignored for safety reason :wink: but it should work with the normal disk&SCC replacement.. :wink:

greetings pressy

All true Pressy, with the following qualifiers:

True, but in that case why not just bring the whole hardware hardware setup? That too would be easier. There may also be licensing issuse here. As a Veritas (and Sun) OEM supplier I know that we cannot do this when installing for external customers.

In theory yes, in practice with the 3310 you cannot, unless it is a JBOD. In which case it can be done this way. It cannot be done in a cotrolled bases 3310 as a global replacement of disks would require rebuilding of the logical drives, wiping all the information, also insering the disks in any order would not work in the 3310 as the logical drives are configures based on the physical position of the disks in the array.

This is what I use and why I at first didn't consider the JBODs, we only use them as for expansion on controller based 3310s. And the reason I said a direct swap probably wouldn't work.

In single bus mode DMP configuration can be done on a JBOD, but since he is using dual bus it's not an option.

It also give hardware independence, you could happily move from a 3510 to any other array by just adding the drivers.

VirginiaSA, read Pressy's reply in detail, it will work if you are using JBODs with no controller. On the other hand, if you really want to take the physical swap approach, it might be easier just shipping he whole lot to where it's going and swap the two systems.

Well I guess pressy is right. come to find out, it is a JODB and single controller mode. 3310 has one controller for each side of the chassie.

I'm more confised now after this.

Single bus or single controller? If it has a controller it is not a JBOD, and pressy's way will not work. A single controller 3310 is simply that, one controller for the entire array using two SCSI channels. If there are two controllers on the array than it is dual controller using four SCSI channels.

Basically which of these does the back of it look like, and for the controllers if it is the top one it looks like, the simplest is how many com ports does it have?