No subject

Thu Oct 13 11:38:50 EDT 2022

sure
       they are running well.

       Then testing whether RT will run there, I'll do a dummy setup. Just
install
       the same version of RT as I have on the old system. If it installs
fine, then
       try accessing it (with the root user) and clicking a few things here
and there
       just to make sure they are working. If you see much success, then I
guess it's
       time to blow it away (rm -rf rt2 directory)

Step2: Setup up your aliases (for the rt e-mail addresses) on the new
server. Don't
       Don't fire the MTA up as yet.

Step3: Backup your rt directory (cd /opt && tar -cZf rt2.tgz rt2) and move
it to
       the new server (same destination) and extract it. That way you have
preserved
       all permissions. You even have all your customizations intact. On the
new server
       extract your rt2 to the correct location (tar zxvf rt2.tgz).

Step3: Backup your rt2 database and move it over. (substitute your real
values for RT_USER
       and RT_USER_PASS)

       `mysqldump --opt rt2 > backup-rt2.sql`

       Move backup-rt2.sql to the new server.
       Login to the new server as root, create the rt2 database.

       `mysqladmin create rt2`

       Setup the correct permissions for your RT_USER; something like

       GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, INDEX ON rt2.* TO
RT_USER at localhost IDENTIFIED by 'RT_USER_PASS';
       flush privileges;

       NB: Please verify the granted perms by login to my sql and doing this
query:

       show grants for RT_USER at localhost;

       You can then restore the tables and the data back into MySQL with:

       mysql database < backup-file.sql

Step5: If I haven't missed something, then it's time to fire up all
applications and see if your RT is
        up and running.

As a side note: Life would be easier if you were to RETIRE the old server.
You could just
move the old disk onto the new server or create the new server from the old
disk. If both
disks are ATA (say), [This is from FreeBSD's point because I am not familiar
with linux],
I'd do a minimal install on the new disk (reflecting similar partitions on
old disk), then
mount the new disk into the old machine and write all data from old disk
into new disk.
After that, all I've have to do is change a few params on fstab and rc.conf
on the new disk,
mount it on the new machine and boot it up.

I create a new partition with  the necessary slices. I mount them on my old
system /mnt/newsystem. 
Write the new using the old rather than copy the old on top of a temporary
new.

Off the top of my head I would type the command line:

# dump 0af - / | ( cd /mnt ; restore -rf - )
# dump 0af - /var | ( cd /mnt/var ; restore -rf - )
# dump 0af - /usr | ( cd /mnt/usr ; restore -rf - )

5) edit and change your /etc/fstab file to reflect the new changes, save it,
move the
   new disk into the new server and reboot!

Donate the old server to charity!

Just my $ 0.02

        cheers
       - wash 
+----------------------------------+----------------------------------------
-+
Odhiambo Washington, wash at wananchi.com	. WANANCHI ONLINE LTD (Nairobi, KE)
|
http://ns2.wananchi.com/~wash/		. 1ere Etage, Loita Hse, Loita St.,
|
GSM: (+254) 722 743 223			. # 10286, 00100 NAIROBI
|
+---------------------------------+-----------------------------------------
-+
"Oh My God! They killed init! You Bastards!"  
						 --from a /. post

 "The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from all
computers." 

------_=_NextPart_001_01C28734.E4C28E40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [rt-users] RE: Moving RT2.0.13 from 1 server to =
another</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>The rt directory has been copied over from the =
production server.  The following error shows up when I try to =
restart apache on my new server:</FONT></P>

<P><FONT SIZE=3D2>Variable "$m" is not imported at =
/usr/local/rt/bin/webmux.pl line 94.</FONT>
<BR><FONT SIZE=3D2>[Thu Nov  7 22:08:33 2002] [error] Global =
symbol "$m" requires explicit package name at =
/usr/local/rt/bin/webmux.pl line 94.</FONT></P>

<P><FONT SIZE=3D2>Compilation failed in require at (eval 6) line =
1.</FONT>
</P>

<P><FONT SIZE=3D2>Syntax error on line 1077 of =
/usr/local/www/conf/httpd.conf:</FONT>
<BR><FONT SIZE=3D2>Global symbol "$m" requires explicit =
package name at /usr/local/rt/bin/webmux.pl line 94.</FONT>
<BR><FONT SIZE=3D2>Compilation failed in require at (eval 6) line =
1.</FONT>
</P>

<P><FONT SIZE=3D2>Any ideas????</FONT>
</P>

<P><FONT SIZE=3D2>Thanks</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Gororo, Hillary </FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, November 06, 2002 10:32 AM</FONT>
<BR><FONT SIZE=3D2>To: 'Odhiambo Washington'</FONT>
<BR><FONT SIZE=3D2>Cc: rt-users at lists.fsck.com</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [rt-users] RE: Moving RT2.0.13 from 1 =
server to another</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi,</FONT>
</P>

What I actually want to run is RT 2.0.14 on the new =
server.  My current production server is running RT 2.0.13.  =
I am looking for a way to migrate the mysql database from my production =
server (RT 2.0.13) to my new server (RT 2.0.14).

And I am looking for a way to migrate (upgrade) my =
current RT2 directory from the RT2.0.13 server to the RT 2.0.14 server. =
That way I do not have to redo my config's on the new server. =

<P><FONT SIZE=3D2>Is there an easy way of doing this?????</FONT>
</P>

<P><FONT SIZE=3D2>Thanks </FONT>
<BR><FONT SIZE=3D2>Hillary</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>  </FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Odhiambo Washington [<A =
HREF=3D"mailto:wash at wananchi.biz">mailto:wash at wananchi.biz</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, August 30, 2002 3:48 AM</FONT>
<BR><FONT SIZE=3D2>To: Gororo, Hillary</FONT>
<BR><FONT SIZE=3D2>Cc: rt-users at lists.fsck.com</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [rt-users] RE: Moving RT2.0.13 from 1 =
server to another</FONT>
</P>
<BR>

* Gororo, Hillary <HGororo at chartercom.com> =
[20020830 01:20]: wrote:
 > Hi Everyone,
 > I am new to the list, we just recently =
purchased a new server and so I am
 > preparing to move RT2 from one server to =
another.  What steps do I need to
 > perform?. I understand from scanning through =
the archives that I will need
 > to backup my current RT and load it on the new =
server.  Do I need a fresh
 > install on the new server? and also which =
directories/files do I need to
 > backup, How do I backup these files and how do =
I load the files onto the new
 > server.
 >

From the top of my head (untested)
 Step1: Ensure the new system has all the =
prerequisites for RT.
        I'll setup the =
Web Server, MySQL server (and even the MTA) and make sure
        they are =
running well.
   
        Then testing =
whether RT will run there, I'll do a dummy setup. Just install
        the same =
version of RT as I have on the old system. If it installs fine, =
then
        try accessing =
it (with the root user) and clicking a few things here and there
        just to make =
sure they are working. If you see much success, then I guess =
it's
        time to blow it =
away (rm -rf rt2 directory)

Step2: Setup up your aliases (for the rt e-mail =
addresses) on the new server. Don't
        Don't fire the =
MTA up as yet.

Step3: Backup your rt directory (cd /opt && =
tar -cZf rt2.tgz rt2) and move it to
        the new server =
(same destination) and extract it. That way you have preserved
        all =
permissions. You even have all your customizations intact. On the new =
server
        extract your =
rt2 to the correct location (tar zxvf rt2.tgz).

Step3: Backup your rt2 database and move it over. =
(substitute your real values for RT_USER
        and =
RT_USER_PASS)

<P><FONT SIZE=3D2>       `mysqldump --opt =
rt2 > backup-rt2.sql`</FONT>
</P>

<P><FONT SIZE=3D2>       Move =
backup-rt2.sql to the new server.</FONT>
<BR><FONT SIZE=3D2>       Login to the =
new server as root, create the rt2 database.</FONT>
<BR><FONT SIZE=3D2>       </FONT>
<BR><FONT SIZE=3D2>       `mysqladmin =
create rt2`</FONT>
</P>

<P><FONT SIZE=3D2>       Setup the =
correct permissions for your RT_USER; something like</FONT>
<BR><FONT SIZE=3D2>       </FONT>
<BR><FONT SIZE=3D2>       GRANT SELECT, =
INSERT, UPDATE, DELETE, CREATE, INDEX ON rt2.* TO RT_USER at localhost =
IDENTIFIED by 'RT_USER_PASS';</FONT>
<BR><FONT SIZE=3D2>       flush =
privileges;</FONT>
</P>

<P><FONT SIZE=3D2>       NB: Please =
verify the granted perms by login to my sql and doing this =
query:</FONT>
</P>

<P><FONT SIZE=3D2>       show grants for =
RT_USER at localhost;</FONT>
<BR><FONT SIZE=3D2>       </FONT>
<BR><FONT SIZE=3D2>       You can then =
restore the tables and the data back into MySQL with:</FONT>
</P>

<P><FONT SIZE=3D2>       mysql database =
< backup-file.sql</FONT>
</P>

<P><FONT SIZE=3D2>Step5: If I haven't missed something, then it's time =
to fire up all applications and see if your RT is</FONT>
<BR><FONT SIZE=3D2>        up and =
running.</FONT>
</P>
<BR>
<BR>

As a side note: Life would be easier if you were to =
RETIRE the old server. You could just
 move the old disk onto the new server or create the =
new server from the old disk. If both
 disks are ATA (say), [This is from FreeBSD's point =
because I am not familiar with linux],
 I'd do a minimal install on the new disk (reflecting =
similar partitions on old disk), then
 mount the new disk into the old machine and write =
all data from old disk into new disk.
 After that, all I've have to do is change a few =
params on fstab and rc.conf on the new disk,
 mount it on the new machine and boot it up.

I create a new partition with  the necessary =
slices. I mount them on my old
 system /mnt/newsystem. 
 Write the new using the old rather than copy the old =
on top of a temporary new.

<P><FONT SIZE=3D2>Off the top of my head I would type the command =
line:</FONT>
</P>

<P><FONT SIZE=3D2># dump 0af - / | ( cd /mnt ; restore -rf - )</FONT>
<BR><FONT SIZE=3D2># dump 0af - /var | ( cd /mnt/var ; restore -rf - =
)</FONT>
<BR><FONT SIZE=3D2># dump 0af - /usr | ( cd /mnt/usr ; restore -rf - =
)</FONT>
<BR><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2>5) edit and change your /etc/fstab file to reflect =
the new changes, save it, move the</FONT>
<BR><FONT SIZE=3D2>   new disk into the new server and =
reboot!</FONT>
</P>

<P><FONT SIZE=3D2>Donate the old server to charity!</FONT>
</P>

<P><FONT SIZE=3D2>Just my $ 0.02</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>        =
cheers</FONT>
<BR><FONT SIZE=3D2>       - wash </FONT>
<BR><FONT =
SIZE=3D2>+----------------------------------+---------------------------=
--------------+</FONT>
<BR><FONT SIZE=3D2>Odhiambo Washington, wash at wananchi.com  . =
WANANCHI ONLINE LTD (Nairobi, KE)  |</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://ns2.wananchi.com/~wash/" =
TARGET=3D"_blank">http://ns2.wananchi.com/~wash/</A>  =
        . 1ere Etage, Loita Hse, =
Loita St.,  |</FONT>
<BR><FONT SIZE=3D2>GSM: (+254) 722 743 223 =
        =
        . # 10286, 00100 =
NAIROBI          &nbsp=
;  |</FONT>
<BR><FONT =
SIZE=3D2>+---------------------------------+----------------------------=
--------------+</FONT>
<BR><FONT SIZE=3D2>"Oh My God! They killed init! You =
Bastards!"  </FONT>
<BR>        =
        =
        =
        =
        =
        <FONT SIZE=3D2> --from =
a /. post</FONT>
</P>
<BR>

"The information transmitted is intended =
only for the person or entity to which it is addressed and may contain =
confidential and/or privileged material. Any review, retransmission, =
dissemination or other use of, or taking of any action in reliance =
upon, this information by persons or entities other than the intended =
recipient is prohibited. If you received this in error, please contact =
the sender and delete the material from all computers." =

</BODY>
</HTML>
------_=_NextPart_001_01C28734.E4C28E40--