starkpr backups

UserPreferences

STARKEEPER BACKUP PROCEDURE

System Description

Starkeeper is an Lucent product developed to monitor communications networks that use AT&T Datakits.

STARKPR

Starkpr Starkeeper machine. it performs the following functions:

• monitors the Datakit Console ports for alarms,
• maintains console logs which are log files for all commands entered via Starkeeper and all alarms reported by Datakits, and;
• runs the graphics software to display network maps and alarms
• displays performance data generated by star4b
• tracks the database configuration. There are two related databases as follows:

Informix

stores the Datakit configurations, only for use by Starkeeper

Backup

copy of Datakit configurations used for emergency retrieval and downloading to a Datakit.

Starkeeper Backup Procedures

Before beginning procedure, the TSC (314-298-9390) needs to be called, and informed that starkeeper backups will begin. They need to put tapes in for the backups, and they also need to stop the workstation software.

Weekly backups are run to backup the datakit configuration files that reside on starkpr.

Monthly backups are run to backup the entire disk on starkpr.

Weekly Backup Starkpr

STOP THE WORKSTATION SOFTWARE: (TSC does this)

(log on to starkpr as cnmsadm, for eg: )

telnet starkeeper

su - <root>

su - cnmsadm

INITIALIZE DATABASES

SKsh (this will load a menu based system)

go to sysadm and select shutsk

Go to dbutils and select initdb (say yes to "re-initialize database...[y/n])

Initialize alarms, billing, perf (DO NOT SELECT CONFIG)

(Initdb takes about 3 minutes)

Select rspace from dbutils menu

(Regain space from alarms, billing and perf) (NOT CONFIG)

BACKUP CONFIG DATA TO TAPE:

get out of SKsh (keep hitting enter)

Put a blank cartridge tape in Starkpr labled Starkpr SKbackup <date>

skbackup -c HR

When prompted for Label:

SKbackup <date>

followed by a period on a line by itself

(This will backup config data to cartridge tape and to a file)

If this is a Weekly restart the software go to "Restart Software" HERE(link)?

If this is a Monthly, continue on with next step.

NOTE: Restoral of this tape is part of the starkeeper recovery procedure outlined in the Starkeeper users guide (255-114-707 Section 6 Maintenance)

Monthly - Backup

STARKPR File System

/root, usr, usr2

you should already be logged in

Login as cnmsadm

Use SKsh shutsk to stop

Put new tape

Backup Root file system Put in tape

login as root

cd (must be at root)

find / /usr /usr2 -xdev -print | cpio -ocmvdB> /dev/rmt/0m

NOTE:

FOLLOW STANDARD TAPE ROTATION PROCEDURES;

USE 120m TAPE CARTRIDGES

DISCARD TAPES AFTER 12 USES

WEEKLY TAPES, KEEP 2 WEEKS

MONTHLY TAPES, KEEP 6 MONTHS

Restart Software

EITHER AFTER WEELY

OR MONTLY PROCEDURE

START CORE SOFTWARE command: xcnms_start

Execute conn_sync

to make sure alarms are coming in and displayed in gui interface

the command: conn | grep CONS will show if consoles are connected, run restetcon to fix is all don't come up in 5 minutes or so

RESTART WORKSTATION (TSC does this as well) Call TSC to inform them that the backups are complete, and that the workstation software can be reloaded.

Start your task manager and network monitor screens

Verify alarms are being displayed

In case of trouble, call the Starkeeper administrator for assistance. (TSC)