Migration Strategy and Executable Task List

DRAFT
UMBC
15 May 2006
Prepared by Bryan Brown, Dayspring Systems, LLC. & Nick Yeates

Migration Overview

In order to complete the transition from the UMBC Sun Solaris/Oracle Para-Docs appli-ance (UMBC-PD-SUN) to the UMBC Fedora Core 4/Postgresql Para-Docs appliance (UMBC-PD-FC4), all of the data, including the Para-Docs database, stored document files, and custom scripts, must be transferred from UMBC-PD-SUN to UMBC-PD-FC4. Once the operational files have been transferred, both appliances must be reconfigured to respond to new domain names and exhaustively tested to ensure full functionality.

Migration Priorities

Complete the migration within the time specified (19 May 2006, 9 p.m. to 22 May 2006, 7 a.m.).
Ensure the integrity of all UMBC data.
Replicate all functionality of the existing PD installation on the new appliance.
Perform any necessary maintenance on new appliance.
Ensure a measurable system speed increase.

UMBC Migration Task List

Login to gsdocs.umbc.edu using appropriate credentials. These credentials are available from Nick Yeates and Dayspring Systems.
```
sudo bash
```
This command will move the user into superuser mode, allowing execution of privileged commands and access to restricted directories.
Turn off login functionality of users (making sure they cannot login from myUMBC also)

cd /afs/umbc.edu/users/g/s/gsdocs/home/ora2pg

```
perl ora2pg.pl
```
This directory contains the Perl script that will perform the conversion of the data-base information from Oracle to Postgresql. This script will take a significant amount of time to run. The previous export of the Para-Docs database on the Sun server was over 1GB in size. The output file is named output.sql.
Note chmod & chown settings on gsdocs-prd.umbc.edu:/home/support
Create correct chmod & chown settings if needed on gsdocs-prd.umbc.edu:/home/support
```
scp ./output.sql support@gsdocs-prd.umbc.edu:/home/support
```
This command will move the database output file from the Sun server to the FC4 server.
Create old chmod & chown settings from before on gsdocs-prd.umbc.edu:/home/support
Exit and exit again
Login to gsdocs-prd.umbc.edu using appropriate credentials
```
cd /home/support
```
```
su root
```
```
pg_dump paradocsimport > /pd.dmp
pg_dump paradocs > /pd2.dmp
```
These two commands will backup the existing Para-Docs databases on the FC4server. Although there is no need to preserve the data on the FC4 server, maintaining a backup may allow for more effective configuration and testing.
```
dropdb paradocs
```
This Postgresql command is used to drop an existing database. This is necessary to clear the way for the new import data from the Sun server.
```
createdb paradocs
```
This Postgresql command is used to add a database. This database will be completely blank and will be populated with data from the output.sql file transferred from the Sun server.
```
psql paradocs < /home/support/output.sql
```
This Postgresql command will parse the SQL file generated from the database on the Sun server and add the data to the Paradocs DB.
```
Edit /etc/odbc.ini
```
This file points the ODBC calls in the PHP code to the correct data. Under the heading [PARADOCS], the attribute database must be changed from paradocsimport to paradocs. This will associate the ODBC pointer with the correct Postgresql database (the one now containing the Para-Docs DB data).
```
/sbin/service postgresql restart
```
This command will flush any cached data and break any persistent connections to the database, forcing them to be renewed.
```
/sbin/service httpd restart
```
This command will restart the Apache web server.
Perform testing via PD Explorer web interface. This testing will confirm database functionality, including logins, queries, workflow, etc. The links to the files will return “file not found” errors until the document files are migrated to the FC4 server.

Moving repository/PDF data from UMBC-PD-SUN to UMBC-PD-FC4

mv /usr/local/data/repository /usr/local/data/repositoryold

mkdir /usr/local/data/repository
mkdir /usr/local/data/repository/gsapp

Note chmod & chown settings on /usr/local/data/repository and /usr/local/data/repository/gsapp

chmod 777 /usr/local/data/repository
chmod 777 /usr/local/data/repository/gsapp

```
chown support.support /usr/local/data/repository
```
This will allow data to be copied directly to the target directory via SCP.
```
mv /var/www/html/pd_search pd_searchold
```
```
mkdir /var/www/html/pd_search
```
```
chmod 755 /var/www/html/pd_search
```
```
chown support.support /var/www/html/pd_search
```
This will allow data to be copied directly to the target directory via SCP.
Exit and logout
Login to gsdocs.umbc.edu with proper credentials
```
sudo bash
```

scp -r /apps/gsdocs/paradocs/repository/gsapp support@gsdocs-prd.umbc.edu:/usr/local/data/repository/gsapp

Copy pd_search files [NEED TO ASK NICK ABOUT CURRENT CONTENT SEARCH CAPABILITIES]
Exit and exit
Login to gsdocs-prd.umbc.edu using proper credentials
```
chown root.root /var/www/html/pd_search
```
This returns the folder to web-safe permissions.
```
chown root.root /usr/local/data/repository
```
This returns the folder to web-safe permissions.
Is this needed???
```
chown root.root /usr/local/data/repository/gsapp
```
This returns the folder to web-safe permissions.
Perform additional testing via PD Explorer web interface