Renaming Sites

[Paul Johnston]

Hello All,

I have three sites that we use for our Production sites and three for our

Test sites.   I wish to rename them to more appopriate names.

Is there a simple / easy method of renaming the sites .

I assume that I will probably have to rename them separately or one after the other.

Would it be necessary to incur  site / process downtime. ?

Any suggestions. ?

PauL

Topic

[garry r fisher]

Hi Paul,

It is quite easy but messy. It will involve downtime.

Stop the existing site(s) – all process must be down

Copy your existing sites

Rename the copies to your new names

Edit the server.ini to match your new site names

Start your new sites

Delete the old site directories

If anyone knows of a more elegant solution then please tell.

Regards

Garry

[Paul Johnston]

Gary ,

I appreciate your response . As you can see it is the only response.

I was hoping for an easier or elegant method as you say but I guess it must be the only way.

I forgot to mention that we are using an HPUX 11i server with 3.8.1P

Thanks for your attention.

Paul

[garry r fisher]

Paul,

Attached is a zip file with a perl script called iSiteCopy. This is a cut down version of hcirootcopy and takes two parameters – a source site name and a destination site name i.e.

iSiteCopy garry paul

Will copy the site ‘garry’ from the CURRENT root to a site called ‘paul’ again in the CURRENT root.

The script should be copied to HCIROOT/bin and shoud berun from the HCIROOT directory.

I’ve tested it on Windows and it works fine – as it uses the original hcirootcopy it should work on any platform.

Any problems come back to me.

Regards

Garry

PS Unable to add attachment – I’ll email it to you.

[David Harrison]

Garry,

Sounds useful. Could you email it to me as well please.

Dave

[Keith McLeod]

I tar up my sites that I wish to rename.  I perfrom an hcisiteinit with the new site name.  I then copy my tar file to the new site directory.  I then untar the tar file.  I have not taken my site down as of yet.  I then edit the NetConfig file to make any necessary changes by using search and replace to rename processes or groups to conform to your new naming convention.  I also do this for monitor default view and any alerts in the default alert file to conform to new name.  May alos need to check tclprocs that may have hard coded paths.

One the modifications are complete, I would then stop the old site and start the new site.

[Bala Pisupati]

we are moving from 5.2 to 5.5 on different boxes, 5.2 was in aix and we are moving to 5.5 on a Redhat linux 4.0. (vmware). How do I use hcirootcopy in this senario when it is two different boxes.

[Max Drown (Infor)]

Could you email me a copy of that script (iSiteCopy) as well?

-- Max Drown (Infor)

[Hongle Sun]

Garry,

Could you email it to me as well please.

hosun@tegh.on.ca

Thanks

[Russ Ross]

Bala in answereing your question

Code:

we are moving from 5.2 to 5.5 on different boxes, 5.2 was in aix and we are moving to 5.5 on a Redhat linux 4.0. (vmware). How do I use hcirootcopy in this senario when it is two different boxes.

I have done something similar that might work for you.

I migrated from QDX 5.2 on an AIX 5.2 server to QDX 5.6 on a different AIX 5.3 server.

What I did was to make my QDX5.2 file system exportable as read only to my new server.

Then on my new server I did a NFS mount of the read only QDX5.2 filesystem/directories that physically reside on the old server so they look like they are on my new server that I’m upgrading to QDX5.6.

Then I was able to run hcirootcopy to migrate a site from QDX5.2 to QDX5.6 on my new box.

This also is a bit safer than upgrading on the same server in place since the NFS mounted files are read only so I can’t accidently step on what is actively running while I’m working on the upgrade.

Russ Ross
RussRoss318@gmail.com

[Russ Ross]

Bala:

Here are some notes about exporting a file system I found that might help you; plus it shows how I was able to test out the cloverleaf license file without having to fail-over or having cloverleaf running on my fail-over box.

Code:

***** How to NFS mount and do hcilictest

   on mdahub7
   —————–
   smitty nfs
   network file systems
   add directory to export list (mount now option)

   on mdahub6
   ——————
   showmount -e mdahub7

   mount mdahub7:/upgrade /upgrade
   mount mdahub7:/upgrade /sites

   hcilictest
   umount /upgrade
   umount /sites

   on mdahub7
   ———-
   smitty nfs
   network file systems
   remove directory to export list (mount now option)

   on mdahub6
   ——————
   showmount -e mdahub7

Here is how my current NFS mounts show up on my test server mdahub4 to help complete the picture (mdahub10 is the old server and mdahub4 is the new server)

Code:

(mdahub4:hci) /upgrade/scripts > df -kI
Filesystem    1024-blocks      Used      Free %Used Mounted on
/dev/hd4           262144     68656    193488   27% /
/dev/hd2          3145728   1939516   1206212   62% /usr
/dev/hd9var        786432     47848    738584    7% /var
/dev/hd3           524288     44132    480156    9% /tmp
/dev/hd1          1048576    504224    544352   49% /home
/proc                   –         –         –    –  /proc
/dev/hd10opt       262144    188784     73360   73% /opt
/dev/fslv00        262144       368    261776    1% /perfman
/dev/fslv01        524288       704    523584    1% /logs
/dev/fslv02       2097152    870108   1227044   42% /usr/sys/inst.images
/dev/fslv03      10485760      2764  10482996    1% /work4
/dev/san00        5242880     11756   5231124    1% /ftp
/dev/fslv05      41943040    438564  41504476    2% /data
/dev/fslv06      10485760     42936  10442824    1% /hcitest
/dev/fslv07      20971520    185076  20786444    1% /sites
/dev/fslv08      20971520   1524256  19447264    8% /upgrade
/dev/fslv09      10485760     42900  10442860    1% /oldmsgs
/dev/fslv04       1048576       504   1048072    1% /backup_logs
mdahub10:/data    20971520   9182880  11788640   44% /nfs/data
mdahub10:/sites    20971520   9712492  11259028   47% /nfs/sites
mdahub10:/upgrade    20971520   2483616  18487904   12% /nfs/upgrade
(mdahub4:hci) /upgrade/scripts >

Here is a script I used to do the NFS mounts on my new test server:

Code:

#!/usr/bin/ksh

if [[ “`echo $MDA_UPDIR`” = “” ]]; then
   export MDA_UPDIR=/upgrade
fi

me=`whoami`

if [ “$me” != “root” ]; then
   echo “$0 must be run as root”
   exit 1
fi

echo “”

showmount -e mdahub10

echo “”

mount   mdahub10:/data      /nfs/data
mount   mdahub10:/sites     /nfs/sites
mount   mdahub10:/upgrade   /nfs/upgrade

echo “”

df -kI

echo “”

Then I use symbolic links to make things show up logically where they are expected to be located.

Here is an illustration of the /quovadx directory on my new server to make 5.2 appear in the right place (see below)

Code:

(mdahub4:hci) /quovadx > ls -al
total 8
drwxrwxr-x    3 hci      staff           256 Sep 09 13:17 .
drwxrwxr-x   18 hci      staff          4096 Sep 09 13:24 ..
lrwxrwxrwx    1 hci      staff            33 Sep 09 13:15 qdx5.2 -> /nfs/upgrade/quovadx_aix5L/qdx5.2
drwxrwxr-x    3 hci      staff           256 Apr 25 2008  qdx5.6
(mdahub4:hci) /quovadx >

Russ Ross
RussRoss318@gmail.com

[Author]

Replies