SYSMGR

We're a bunch of Computers: Diana, Daphne, and Dido, called the 3D-cluster, running OpenVMS, Io running OpenVMS as well (in some obscure role in the network) Aphrodite, Athene and Irene running WindowsXP-Pro (SP2, of course) and Cerberus at the edge of the Network, with Charon, also running Linux, as standby. SYSMGR takes care of us.

Wednesday, November 2

02-Nov-2005

Updates
of Time...
Change because of Daylight Saving Time setting. No issues on any system. Just Windows asks, as if it's not sure it did it right...
Perhaps, set all systems to GMT - without DST, but that would confuse everyone but me. So no, to keep everybody happy...
of Windows...
The Windows boxes have their VirusScan updates automatically so whenever they start up, it will download and install McAfee updates autoomatically. Matter of minutes (a few, at least). But on Hera the kids (they usually login adn do NOT logout) have no Administrator rights so I still have to login, at least once a week, to get the updates installed.
No windows updates, this time. Not signalled, not downloaded, but I think there must be...
of VMS...
As suggested on the ITRC forum, I chnaged the format of the compressed file:
$ set file/attr=(fm:fix, lrl:512) -
_$ DEC-AXPVMS-TCPIP-V0505-11ECO1-1.PCSI$COMPRESSED;1
and now it could be installed. Since IO is not so fast, it took some time.
In the mean time, downloaded the new verion of SBW (aka Mozilla) that previously failed to install - now it suceeded without problems.
After that was done, IO was rebooted, and, again, CommunigatePro was not started. Found the reason in the logfile (since that part is done in batch, like on Diana): IO_DATA is not known. Obviously, since DKA100 (the disk labeled IO_DATA) is mounted later in the procedure. So moved start of Communigate to after mounting the disk.
The changes still have to be applied to the 8.2 mother disk; the files have been copied on that before using them on IO so the file attributes are still wrong.
Hardware preparations
Added the KZPSB-CY cards (differential SCSI) in both Alphastation 200's and hooked up the HSZ50, in preparation of starting up the machines. But I still have to configure the BA356 IO units, collect the remaining 36GB disks, and get power cords and netwerk connections. Also, the DSSI cards need to be inserted, but one of the Alphastations carries a graphics card, so I'm out of PCI slots there....
Monthly maintenance
As usual at month change, zipped the operator logfiles and cleaned up Diana's system disk.
The backup from the disks hosted by HSD04 (DSSI disk unit) was incorrect so I re-inited USER2 - a 36Gb disk, and created two directies on it: one for DIAo and one for DIA100. Next, I started a backup session for each of the disks to copy all files from these RAID volumes to their own directory on USER2, so that BA356 is now free to be used in combination with the HSZ50. This backup is now correct.

0 Comments:

Post a Comment

<< Home