TruCluster
cancel
Showing results for 
Search instead for 
Did you mean: 

Migrating disk from a server in a tru64 cluster to non-clustered server

Telia BackOffice
Valued Contributor

Migrating disk from a server in a tru64 cluster to non-clustered server

Hi There

We have a GS160 server called basix which once was part of a tru64 cluser. We would like to migrate all disks to another alpha server called niki. We have umounted the filesystem on basix and presented the disk to niki. We can not access the disk though:

niki># showfdmn domain_dsk55c

bs_bfdmn_activate: can't open log for domain 'domain_dsk55c',

tag = 0xfffffff7.0x0: E_CANT_FIND_LOG_END (-1077)

showfdmn: unable to get info for domain 'domain_dsk55c'

showfdmn: error = E_CANT_FIND_LOG_END (-1077)

On basix the device is still locked to basix, which is the culprit:

thosan@basix|pts/2:/etc/fdmns$ sudo drdmgr -v /dev/disk/dsk851c



View of Data from member basix (Member 2) as of 2009-03-04:12:08:58

Device Name: dsk851c
Hardware ID: 1519
Device Type: Direct Access O Disk
Device Status: OK
Number of Servers: 1
Server Name: basix
Server State: Server
Access Member Name: basix
Open Partition Mask: 0
Statistics for Client Member: basix
Client Connection Status: Connected
Number of Read Operations: 3456
Number of Write Operations: 228
Number of Bytes Read: 124977152
Number of Bytes Written: 2867200

Is there any way to get the disk from basix to niki without getting niki into the cluster or removing the disk from cluster control?

BR Thomas
2 REPLIES
Ivan Ferreira
Honored Contributor

Re: Migrating disk from a server in a tru64 cluster to non-clustered server

Normally, the disk will be marked with a SCSI key that will prevent from mount it on a non-cluster node.

You should try removing the SCSI reservation key.

Attached is the procedure.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Telia BackOffice
Valued Contributor

Re: Migrating disk from a server in a tru64 cluster to non-clustered server

We hired a consultant that cloned our server (which booted from LAN), allowing us to setup a cluster, swinging the service over to the new server and closing down the old one.

Took him 4-5 hours.