University Calgary Library Test Server Reload Reminders

University of Calgary Library Test Server Reload Reminders

PRE-reloading tasks

Get date to do reload with IT.
Send a message out to IT staff involved eg, Glorious Tsui, and any ITS staff affected by this: Mary Jane, Nella, etc. with the following details:

Setup the date and time with IT and give instructions for what the overlay involves.


Kevin,

Could we schedule an overlay of sirsi2 (/sirsi and /oracle directories) with data from sirsi1's backup of the night before? 
Perhaps do this today, tomorrow or Monday?? Which of those dates work for you?

Directories to protect would be the same as last month:

Overlay the /sirsi and /oracle directories, with the following exceptions:

-/sirsi/s/sirsi/Unicorn/Bincustom
-/sirsi/s/sirsi/Unicorn/Rptcustom
-/sirsi/s/sirsi/Unicorn/Webcat -- NOT /WebCat
-/sirsi/s/sirsi/Unicorn/Work
-/sirsi/s/sirsi/.ssh
-/sirsi/Bowvalley (everything including the .ssh subdirectory)
-/sirsi/s/sirsi/Unicorn/Clients
-/sirsi/s/sirsi/Unicorn/Logs/Seterhist
-/sirsi/s/sirsi/Develop

.... and all files and subdirectories inside these.

NOTE (as always):
When you are done, please DO NOT restart services on sirsi2. We need to make sure we stop production jobs 
from running before we start things up. So just let me know when you are done via email or phone.

****Glorious and Osama: Let us know if there is any new directories to protect.  *****

Thank you for considering this request.
Nella

Something to think about:

    -/s/sirsi/Unicorn/Webcat -- NOT /WebCat!!!!--THINK hard about this directory whether you 
     want it in the list or not.  If you want a history of old customizations 
     just save a copy of the old test directory as Webcat.test but get 
     Webcat in sync with production ...

I wrote a program in /NDL/createstamp.ksh which puts a file called: stamp_preoverlay with a date (date the program was run) in it into each of the "protected" directories listed above except the /sirsi/Bowvalley directory since "sirsi" user can't write a file there.
All other filesystems on test should not be touched or overlayed.
Cronjobs on sirsi2 that run every few minutes should be stopped before IT begin the overlay so that constant emails do not get mailed out about the failed cronjobs during the overlay process. Eg. verify_cron_new and core_alert.ksh
It is CRITICAL that all file ownerships and permissions match those on production exactly. If they don't we could spend a whole day or two just cleaning them up. Although this has NOT been a problem for years now.
crontab of production will not be copied to test.
* N.B.: when IT is done, do NOT bring up the unicorn servers. (We don't want overdues etc to be emailed out from this server to clients! So need to get in there and stop all the reports from running daily etc. Suspend suspend suspend!)
Send date of reload to SMT and CWG and Serials and the consortia members via System sharing consortium in case they have test records to save etc.
Send date the reload will be done and date of the database being loaded onto test out to Glorious and N.Lall and Mary Jane and Osama Al-Eryani (sometimes the files being loaded onto test on date x are from the previous production backup from date x-so many days)

For INSURANCE purposes Nella use to tar'd and compressed backups of:
Save everything in /Bincustom.
Save everything in /Rptcustom
Save everything in /cgi-bin
Save everything in /s/sirsi/.ssh
Save anything which is unique to test from /Config, /Custom, /Webcat/Pages_custom or /Webcat/Images_custom etc. or just save the full /Webcat directory.
Save everything in Work/NDL and below
Save /Unicorn/Clients-stamp, custom.jar, and everything in /s/sirsi/Unicorn/Clients/Toolcust/Workflows and everything in /s/sirsi/Unicorn/Clients/Custom
Save all of these via tar and compression for ease during restore, save on horus or somewhere!
IT staff can save things in their home directory if they wish to.
- Step1...while in directory above one you want to tar issue the following command:
- tar cf newfilename.tar name_of_target_directory
- For example: tar cf rptcustom.tar Rptcustom
- Step2...compress this tar file to reduce space it consumes with:
- compress -v rptcustom.tar
- This creates a compressed file and output to screen tells you how much space it has been reduced to.
- Step3...ftp the tar.Z file to a "safe" place like acs4 or horus etc.

AFTER RELOAD is complete

Before starting the report server ensure that you:
- Suspend reports which you do not want running nightly on test
- Pay special attention to the reports for which EMAIL notices are automatically sent out, like moverdue, doverdue, holdnotice etc.!!! It may be easier to just suspend all running reports and then schedule the few nightly reports for test server purposes, like adutext.
If necessary...ftp the tar.Z file(s) back to test into the proper directory -- eg. for Rptcustom you would ftp the file back into Unicorn directory. The extraction from the .Z file will recreate the Rptcustom directory, files and all subdirectories files etc.
uncompress the file with:
$ uncompress rptcustom.tar.Z
If you want to VIEW the list of files in the archive with size etc. BEFORE extracting them from the .tar file you can use the command:
tar -vtf rptcustom.tar
Step6...extract the files from the tar file via:
tar -xf rptcustom.tar
Step7...remove the .tar file since it has been used and all the files/directories are back in place.

BRS and Reloading the test server

Years ago...and never recently: Sometimes after a full reload from production to test, the BRS needs to be reauthorized.
in /s/sirsi ensure that two files: sirsiauth and authorize are there and match production settings etc.
Also, ensure that in /usr/lib the files: brssearch and brsvalid exist with sirsi sirsi as owner/group.
Check in /Config that brskeys are setup and look correct--although even if these are for production last time in July 1999, this did not make any difference.

For more information see LP's Coil Bound server booklet under 1997 (Aug. 28)

Use sftp to bring over the various ALLckeys.sort file from production to test. This will be necessary since we now have a production ckey database for the various records and findmatch programs will need to use the production ckey file on it's next run. (If you want, you can first move the current test ALLckeys.sort file to something like ALLckeys.sort.prereload).
- /Work/NDL/Aaron/Twentyfour/ALLckeys.sort
- /Work/NDL/Aaron/Credoref/ALLckeys.sort
- /Work/NDL/Aaron/Worldbank/ALLckeys.sort
- /Work/NDL/Aaron/Springer/ALLckeys.sort
- /Work/NDL/Aaron/Morgan/ALLckeys.sort
- /Work/NDL/Aaron/Ebrary/Irwin/ALLckeys.sort
- /Work/NDL/Aaron/Ebrary/Health/ALLckeys.sort--old and unused now
- /Work/NDL/Aaron/Ebrary/Pubpolicy/ALLckeys.sort--old and unused now
- /Work/NDL/Aaron/Ebrary/Publishers/ALLckeys.sort
- /Work/NDL/Aaron/Ebrary/Group/ALLckeys.sort
- /Work/NDL/Aaron/Ebrary/Perpetual/ALLckeys.sort--seems static
- /Work/NDL/Aaron/Ebrary/CompleteNew/ALLckeys.sort
- /Work/NDL/Aaron/Ebrary/Complete/ALLckeys.sort--old and unused now
- /Work/NDL/Aaron/Ebrary/Elsevier/ALLckeys.sort
- /Work/NDL/Netlibrary/ALLckeys.sort
- /Work/NDL/Serialsolutions/ALLckeys.sort
- /Work/NDL/SSebooks/ALLckeys.sort
- /Work/NDL/DDA/ALLckeys.sort
- These are all the cases where updates are expected but remember if working with other static collections like /Work/NDL/Empire, the *ckeys* files should be refreshed from production before you try to do edits or deletions etc.
- Put the *keys* file from production into test for Work/NDL/Bowvalleyuser and any other files to re-sync them. Save these production keys on the day of the file that is used to reload to test system before another run of the bowvalleyuserload goes!
Change the homepage setting in the Opac Manager under GATEWAYS so that it points to test server address for HIN, ILINK, MAIN, UCILINK and WEBGATE.
Change /Webcat/Config/system.env variable HTTP_ADDRESS to test from production
Make changes in /Webcat/Pages_custom/Default of any files which refer to production to test eg. 54.pg, 57.pg, top.h, bclav.html etc.
Change /index.html to point to test instead of production
Change /cgi-bin/webcat to point to test instead of production
Edit the crontab if a full reload of test was done so that interface programs are commented out.
Remove all |shell| entries from /Custom/rptpasswords
Change the admin pin in the workstation client back to what the test server should have.

Change the pins of all STAFF so that they are alerted to the fact that they are working on test server via:

$ seluser -p"LIBSTAFF" -Q"~ADMIN" -oKBA > userstochange.ndl
one can ensure that only staff logins are in this final file by looking
through it.  Now do the change of ALL these pins to something obvious like: TEST
NOTE: the pin must be changed to something in ALL CAPS!! or CAPS and numerals

$ cat userstochange.ndl | edituser -R"TESTPIN" > usersnewpin.ndl

If Bincustom/newbooksv5.ksh (or other scripts that use scp) does not work for scp'ing files to library1 or library2, then the /s/sirsi/.ssh directory was overlaid and you will have to either regenerate new keys on test or simply copy the new id_dsa.pub to library1 and library2 .ssh directory and rename it as outlined here.
Add the TEST production empty toolbar to Java via--not necessary unless they forgot to protect the Unicorn/Clients directory:
- in /s/sirsi/Unicorn/Clients/Toolcust/Workflows touch test.tb
- edit toolbarlist to add the line:
```
You are in the TEST database|test|
```
- Then edit stamp to make it different from production -increment by one
Send out messages to folks to let them know the process is done-SMT,CWG,serials, Consortia etc etc.

No longer necessary since MULTIFLOWS put on staff PCs...Put the test Workflow toolbars back into effect by doing the following:

$ cd /s/sirsi/Unicorn/Workflows/Toolcust
$ cp /s/sirsi/Unicorn/Rptcustom/Wdls/Toolcust/*.tb .

Log onto test system via a workflows client and edit one toolbar,
say the liaison_ toolbar to simply add a space.  Log out and save
the edited toolbar under the same name on the SERVER so that the 
stamp file in the /s/sirsi/Unicorn/Workflows/Toolcust directory gets updated.

Reserve Fund Usage Report (which has not been requested in years)

Discuss specs for running the fundusage report with H. D'Amour
Run the fundusage report for all reserve funds target the past Fall/Winder term and give results to H. D'Amour in Collections.
This is run on test rather than production due to the huge amount of transactions this program is wading through to figure out the number of charge outs each item purchased with reserve funds had in the past term.

Back to: TOP of page

Back to: Some Unicorn Staff Help, Table of Contents

NDL
University of Calgary Library, ITS