Ticket #265 (assigned problem)

Opened 7 weeks ago

Last modified 2 weeks ago

Set up vso02 as a backup to vso03 at NSO

Reported by: niles Owned by: niles
Priority: highest Milestone:
Component: NSO Servers Version:
Severity: blocker Keywords:


The machine vso02.nispdc.nso.edu needs to be set up as a backup to vso03.nispdc.nso.edu at NSO. Hopefully this will allow vso03 enough downtime that it can move from SuSE to CentOS.

vso02 (which is the old NetDRMS machine from Tucson) has been racked and the patitions have been mounted, although not permanently.

Change History

comment:1 Changed 6 weeks ago by alisdair

  • Component changed from (unfiled) to NSO Servers

comment:2 Changed 5 weeks ago by niles

Actively working on this as of March 16. I have the RAIDs re-done VERY conservatively as the disks in them are old. Oracle is installed and the perl DBD::Oracle module is installed on a per-user basis. The Oracle database is starting to get updates.

I have to copy mysql over (it's fighting me) for the vso_catalogs database. I'm realizing that the way I've backed up the mysql database is not good.

After this, I get the perl going and then this can be a backup VSO node. Still have to get CVS and some other stuff across, too.

comment:3 Changed 2 weeks ago by alisdair

  • Owner changed from Niles to niles
  • Status changed from new to assigned
Note: See TracTickets for help on using tickets.