INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

Restoring a Tru64 Box with Sybase

Restoring a Tru64 Box with Sybase

(OP)

What exactly do I need to do to prepare our Tru64 box for a disaster?  Do I run btcreate?  Or do I run vdump/vrestore?  Do I use both?  What would the restore steps be?  I am not a Tru64 person but am being held responsible.  Any help would be GREATLY appreciated.  

RE: Restoring a Tru64 Box with Sybase

ALPHA Disaster Recovery

This document provides details of a generic procedure to perform a disaster recovery of a Tru64 V5.X AlphaServer  called alpha.

Please note, it is assumed that although an exact duplicate of the existing system is not required, the system should be of as similar a type as possible and include sufficient disk space to restore the complete Operating System as well as all data filesystems.
 
Contents

ABSTRACT    1
1.    ALPHA DISASTER RECOVERY    3
1.1    OPERATING SYSTEM RECOVERY    3
1.2    DATA FILESYSTEM RECOVERY    13


 
·    ALPHA Disaster recovery
·    Operating System Recovery

The following is a procedure to rebuild a generic Tru64 V5.X AlphaServer system on a replacement system, using a TRU64 Unix Operating System CD to boot to system management mode.

The disk storage used in this example was provided via an HSZ80 dual redundant controller. The procedure is the same regardless of whether the disk storage is provided via SAN, local RAID controllers (KZPCC) or local SCSI disks.

Please Note : It is highly recommended that for Disaster Recovery purposes, regular sys_checks be run and the output saved to one or more remote systems for easy recovery & reference when required.

·    Power up the system to firmware level ( >>> prompt )

·    Verify the firmware is at an appropriate level, if not the run a firmware upgrade.

P00>>>show version
version                 v6.1-3 Oct 15 2001 14:00:54

·    At the >>> prompt verify the disks available and the CD drive, enter show dev which will display all devices detectable by the firmware. In the case of the example disaster recovery, this displayed the six hard disks at dkc0 upto dkc300, the cd device at dqa0, and a TZ90 40/80 DLT tape device at mkb400, as shown below:

P00>>>show dev
dkc0.0.0.2.0               DKC0                          HSZ80  V83Z
dkc1.0.0.2.0               DKC1                          HSZ80  V83Z
dkc2.0.0.2.0               DKC2                          HSZ80  V83Z
dkc200.2.0.2.0             DKC200                        HSZ80  V83Z
dkc3.0.0.2.0               DKC3                          HSZ80  V83Z
dkc300.3.0.2.0             DKC300                        HSZ80  V83Z
dqa0.0.0.15.0              DQA0             Compaq   CRD-8402B  1.03    
dva0.0.0.1000.0            DVA0                               
mkb400.4.0.1.0             MKB400             COMPAQ SDT-10000  1.12
eia0.0.0.6.1               EIA0              00-02-A5-42-B6-EF
pka0.7.0.1.1               PKA0                  SCSI Bus ID 7
pkb0.7.0.1.0               PKB0                  SCSI Bus ID 7  5.57
pkc0.7.0.2.0               PKC0                  SCSI Bus ID 7  5.57
P00>>>

·    Ensure the AlphaServer firmware settings are correct enter the following commands

P00>>> set os_type unix
P00>>> set auto_action halt
P00>>> set bootdef_dev “”
P00>>> set boot_osflags 0
P00>>> set eia0_mode fastfd
P00>>> init

·    Insert the TRU64 Unix V5.1A cd and boot up, enter boot dqa0. If a graphical console is connected, then the TRU64 Unix installation GUI will be displayed. Select the Unix Shell radio button at the bottom of the screen. This will return you to the # prompt in Unix system maintenance mode. Otherwise, if a dumb terminal is connected as the console you will be presented with the following menu:







The following options are available:

o  The "U.S. English Installation" installs the base operating system
   software.

o  The "Installation with Worldwide Language Support" (WLS) lets you
   internationalize your system.  This option installs the base operating
   system software as well as WLS software.  The additional software subsets
   provide support for various countries and their native languages.

o  The "Exit Installation" option stops the installation and puts your
   system in single-user mode with superuser privileges.  This option
   is intended for experienced UNIX system administrators who want to
   perform file system or disk maintenance tasks before the installation.
   This option may also be used for disaster recovery on a previously
   installed system.

Remember, you can always get extra information by typing help.

1) U.S. English Installation
2) Installation with Worldwide Language Support
3) Exit Installation

Enter your choice: 3

Select option 3 to enter Unix system maintenance mode.

·    At the # prompt, verify that you can locate all disk devices & their location.

# hwmgr -view devices
 HWID: Device Name          Mfg      Model            Location
 ------------------------------------------------------------------------------
    6: (unknown)                                      
    7: (unknown)                     (unknown)        (unknown)
    8: (unknown)                                      
   47: /dev/disk/floppy0c            3.5in floppy     fdi0-unit-0
   52: /dev/disk/dsk0c      DEC      HSZ80            bus-2-targ-0-lun-0
   53: /dev/disk/dsk1c      DEC      HSZ80            bus-2-targ-0-lun-1
   54: /dev/disk/dsk2c      DEC      HSZ80            bus-2-targ-0-lun-2
   55: /dev/disk/dsk3c      DEC      HSZ80            bus-2-targ-0-lun-3
   56: /dev/disk/dsk4c      DEC      HSZ80            bus-2-targ-2-lun-0
   57: /dev/disk/dsk5c      DEC      HSZ80            bus-2-targ-3-lun-0
   58: /dev/disk/cdrom0c    COMPAQ   CRD-8402B        bus-3-targ-0-lun-0
   59: /dev/ntape/tape0     COMPAQ   SDT-10000        bus-1-targ-4-lun-0


·    Ensure the system disk is labelled with the correct partition sizes.

# disklabel -z dsk0
# disklabel -wr -t advfs dsk0 hsz80
#
# TERM=vt100
# EDITOR=vi
# export TERM EDITOR
#
# disklabel -e dsk0        edit & write label similar to that below














# /dev/rdisk/dsk0c:
type: SCSI
disk: HSZ80
label:
flags:
bytes/sector: 512
sectors/track: 169
tracks/cylinder: 20
sectors/cylinder: 3380
cylinders: 5257
sectors/unit: 17769177
rpm: 3600
interleave: 1
trackskew: 7
cylinderskew: 26
headswitch: 0        # milliseconds
track-to-track seek: 0    # milliseconds
drivedata: 0

8 partitions:
#            size       offset    fstype  fsize  bsize   cpg  # ~Cyl values
  a:      1228800            0    unused      0      0        #      0 - 363*
  b:      9216000      1228800      swap                      #    363*- 3090*
  c:     17769177            0    unused      0      0        #      0 - 5257*
  d:            0            0    unused      0      0        #      0 - 0
  e:            0            0    unused      0      0        #      0 - 0
  f:      2048000     10444800    unused      0      0        #   3090*- 3696*
  g:      2048000     12492800    unused      0      0        #   3696*- 4302*
  h:      3228377     14540800    unused      0      0        #   4302*- 5257*

·    Now create the AdvFS filesystems ready to restore

# mkfdmn -r /dev/disk/dsk0a root_domain
# mkfset root_domain root

# mkfdmn /dev/disk/dsk0g usr_domain
# mkfset usr_domain usr

# mkfdmn /dev/disk/dsk0h var_domain
# mkfset var_domain var

·    Mount the root fileset & restore ALPHA root filesystem

# mount -t advfs  root_domain#root  /mnt
# mt -f /dev/ntape/tape0 rew

# vrestore -xf /dev/ntape/tape0 -D /mnt

vrestore: Date of the vdump save-set: Mon Sep 30 10:27:02 2002
vrestore: Save-set source directory : /
vrestore: informational: [13] posting event: sys.unix.fs.advfs.fset.backup.lock
    If running in single user mode, EVM is not running.
    Please ignore this posting.
vrestore: informational: [13] posting event: sys.unix.fs.advfs.fset.backup.unlock
    If running in single user mode, EVM is not running.
    Please ignore this posting.

·    Mount usr fileset & restore usr filesystem

# mount -t advfs usr_domain#usr /mnt/usr
# vrestore -xf /dev/ntape/tape0 -D /mnt/usr
vrestore: Date of the vdump save-set: Mon Sep 30 10:29:47 2002
vrestore: Save-set source directory : /usr
vrestore: informational: [13] posting event: sys.unix.fs.advfs.fset.backup.lock
    If running in single user mode, EVM is not running.
    Please ignore this posting.
vrestore: informational: [13] posting event: sys.unix.fs.advfs.fset.backup.unlock
    If running in single user mode, EVM is not running.
    Please ignore this posting.



·    Mount usr fileset & restore usr filesystem

# mount -t advfs var_domain#var /mnt/var
# vrestore -xf /dev/ntape/tape0 -D /mnt/var
vrestore: Date of the vdump save-set: Mon Sep 30 10:43:47 2002
vrestore: Save-set source directory : /var
vrestore: informational: [13] posting event: sys.unix.fs.advfs.fset.backup.lock
    If running in single user mode, EVM is not running.
    Please ignore this posting.
vrestore: informational: [13] posting event: sys.unix.fs.advfs.fset.backup.unlock
    If running in single user mode, EVM is not running.
    Please ignore this posting.

·    Verify OS filesystems fully restored

# df -k
Filesystem    1024-blocks     Used   Available Capacity  Mounted on
root_device      612892     612892           0   100%    /
mfs:49           301422        202      301220     1%    /var
mfs:60           64543          40       64503     1%    /cluster/members/{memb}/dev
mfs:418          64543           6       64537     1%    /devices
mfs:421          31              2          29     7% /cluster/members/member0/devices
root_domain#root 614400     122721      484584    21%    /mnt
usr_domain#usr   1024000    639625      368736    64%    /mnt/usr
var_domain#var   1614184     66462     1540728     5%    /mnt/var

·    Modify AdvFS filedomain definitions under /mnt/etc/fdmns

# cd /mnt/etc/fdmns
# cd root_domain
# rm *
# ln -s /dev/dsk/dsk0a
#
# cd ../usr_domain
# rm *
# ln -s /dev/dsk/dsk0g
#
# cd ../var_domain
# rm *
# ln -s /dev/dsk/dsk0h
#
# cd ..        Remove details of data filesystems
# rm -rf u01_domain u02_domain u03_domain u04_domain u05_domain

·    Define new swap device entries in /mnt/etc/sysconfigtab file as detailed in the extract below

# tail -20 /mnt/etc/sysconfigtab

    message-buffer-size = 16384
    msgbuf_size = 16384

vm:
    swapdevice = /dev/disk/dsk0b        Set swap device
    vm_swap_eager = 0            Set swap mode
    new_wire_method = 0
#    vm-maxvas = 5368709120

vfs:
    name-cache-hash-size = 512

proc:
    max-per-proc-address-space = 5368709120
    max-proc-per-user = 512
    max-threads-per-user = 512
    maxusers=1024

hwc:
    hwc_boot_old = 0



·    Modify /mnt/etc/fstab file to comment out apps & data filesystem entries.

# cd /mnt/etc
# vi fstab            edit & write file as shown below

root_domain#root / advfs rw,userquota,groupquota 0 1
/proc /proc procfs rw 0 0
usr_domain#usr /usr advfs rw,userquota,groupquota 0 2
var_domain#var /var advfs rw,userquota,groupquota 0 2
#u01_domain#u01 /u01 advfs rw,userquota,groupquota 1 2
#u02_domain#u02 /u02 advfs rw,userquota,groupquota 1 2
#u03_domain#u03 /u03 advfs rw,userquota,groupquota 1 2
#u04_domain#u04 /u04 advfs rw,userquota,groupquota 1 2
#u05_domain#u05 /u05 advfs rw,userquota,groupquota 1 2
    
·    Edit /mnt/etc/rc.config file to ensure HOSTNAME, Network Card, & IP address are set correctly, as shown in the extract below

#  
. /etc/rc.config.common
#  
DISPLAYTYPE=
HOSTNAME="ALPHA"
NUM_NETCONFIG="1"
MAX_NETDEVS="24"
NETDEV_0="ee0"
NETDEV_1=
NETDEV_2=
NETDEV_3=
NETDEV_4=
NETDEV_5=
NETDEV_6=
NETDEV_7=
IFCONFIG_0="192.100.200.6 netmask 255.255.255.0"
IFCONFIG_1=
IFCONFIG_2=
IFCONFIG_3=
IFCONFIG_4=

·    If necessary ensure /mnt/etc/inetd.local file has appropriate lan card definitions.

# cat /mnt/etc/inet.local
#!/bin/sh
#
# *****************************************************************
# *                                                               *
# *    Copyright (c) Digital Equipment Corporation, 1991, 1999    *
# *                                                               *
# *   All Rights Reserved.  Unpublished rights  reserved  under   *
# *   the copyright laws of the United States.                    *
# *                                                               *
# *   The software contained on this media  is  proprietary  to   *
# *   and  embodies  the  confidential  technology  of  Digital   *
# *   Equipment Corporation.  Possession, use,  duplication  or   *
# *   dissemination of the software and media is authorized only  *
# *   pursuant to a valid written license from Digital Equipment  *
# *   Corporation.                                                *
# *                                                               *
# *   RESTRICTED RIGHTS LEGEND   Use, duplication, or disclosure  *
# *   by the U.S. Government is subject to restrictions  as  set  *
# *   forth in Subparagraph (c)(1)(ii)  of  DFARS  252.227-7013,  *
# *   or  in  FAR 52.227-19, as applicable.                       *
# *                                                               *
# *****************************************************************
#
# HISTORY
#
# @(#)$RCSfile: inet.local,v $ $Revision: 1.1.2.2 $ (DEC) $Date: 1995/12/04 22:36:21 $
#
# Repository for local network daemons and startup commands
#
# This script is called by /sbin/init.d/inet after all the
# network interfaces are up and running, but before any
# other network services have been started.
#
# Examples of things to put in here would be pfconfig,
# adding aliases for existing IP addresses, etc.
#
#    echo "Starting local Internet services."
lan_config -i ee0 -a 0 -s 100 -x 1


·    Remove details of all hardware & SCSI device databases

# rm /mnt/etc/dec*
# rm /mnt/etc/dccd.*
# rm /mnt/etc/dcdd.*
# rm /mnt/etc/dfsc.*
# rm /mnt/etc/dfsl.*
# rm /mnt/cluster/members/member0/etc/cfginfo
# rm /mnt/etc/cfginfo
# rm /mnt/cluster/members/member0/etc/dfsl.dat
# rm /mnt/dev/tty0*
# rm /mnt/dev/lp*
# rm /mnt/dev/kevm*
# rm /mnt/dev/scp*
# rm /mnt/devices/disk/*
# rm /mnt/devices/rdisk/*
# rm /mnt/devices/tape/*
# rm /mnt/devices/ntape/*
# rm /mnt/devices/changer/*
# rm /mnt/devices/dmapi/*
# rmdir /mnt/devices/disk
# rmdir /mnt/devices/rdisk
# rmdir /mnt/devices/tape
# rmdir /mnt/devices/ntape
# rmdir /mnt/devices/changer
# rmdir /mnt/devices/dmapi
# rm /mnt/dev/disk
# rm /mnt/dev/rdisk
# rm /mnt/dev/tape
# rm /mnt/dev/ntape
# rm /mnt/dev/changer
# rm /mnt/dev/dmapi
# rm /mnt/cluster/members/member0/.Booted
# rm /mnt/devices/cport/*
# rmdir /mnt/devices/cport
# rm /mnt/cluster/members/member0/dev/cport

·    Umount filesets & remove new filedomain entries

# umount  /mnt/var /mnt/usr  /mnt
# df -k
Filesystem    1024-blocks     Used   Available Capacity  Mounted on
root_device      612892     612892           0   100%    /
mfs:49           301422        202      301220     1%    /var
mfs:60           64543          40       64503     1%    /cluster/members/{memb}/dev
mfs:418          64543           6       64537     1%    /devices
mfs:421          31              2          29     7% /cluster/members/member0/devices

·    Umount any remaining filesystems and halt system

# cd /
# umount -a
# halt
syncing disks... done


CPU 0: Halting... (transferring to monitor)


 halted CPU 0

halt code = 5
HALT instruction executed
PC = ffffffff002c5f30
resetting all I/O buses
P00>>>

·    This will return you to the firmware level (with the >>> prompt). You can now boot up from your newly recovered alpha system. However, please remember to boot to single-user mode only from the generic kernel, as there will be minor hardware differences between the new and old AlphaServer models. For example, the network card may be installed in a different PCI slot. This means that the kernel configuration file will need to be recreated to take any possible differences into account. Once the kernel configuration file has been recreated, a kernel rebuild will be required, along with a system reboot.

P00>>>boot -fi genvmunix -fl s dkc0

(boot dkc0.0.0.2.0 -file genvmunix -flags s)
block 0 of dkc0.0.0.2.0 is a valid boot block
reading 19 blocks from dkc0.0.0.2.0
bootstrap code read in
base = 200000, image_start = 0, image_bytes = 2600
initializing HWRPB at 2000
initializing page table at 3ff54000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

UNIX boot - Thursday August 24, 2000

Loading genvmunix ...
Loading at 0xffffffff00000000

Sizes:
text =  7671552
data =  1953968
bss  =  2460480
Starting at 0xffffffff0000fbf0

set_pmap_memdsc_state: start 0x0 end 0x47c4 cl 0xffffffffffd2cd90
Alpha boot: available memory from 0x8f88000 to 0x1bffe8000
Compaq Tru64 UNIX P5.1 (Rev. 725); Wed Apr 10 15:41:45 EDT 2002
physical memory = 7168.00 megabytes.
available memory = 7023.69 megabytes.
using 27464 buffers containing 214.56 megabytes of memory
Master cpu at slot 0

Starting secondary cpu 1

Starting secondary cpu 2

Starting secondary cpu 3

Firmware revision: 6.1-3

PALcode: UNIX version 1.88-101

Compaq AlphaServer ES40

pci1 (primary bus:1) at nexus

itpsa0 at pci1 slot 1

IntraServer ROM Version V2.0 (c)1998

scsi0 at itpsa0 slot 0 rad 0

comet0:  Card type 'Elsa GLoria' with 8MB framebuffer memory.

comet0 at pci1 slot 5

ee0 at pci1 slot 6

ee0: COMPAQ Intel 82559 (10/100 Mbps) Ethernet Interface

ee0: Driver Rev = V1.0.15, Chip Rev = 8, hardware address: 00-02-A5-42-B6-EF

pci0 (primary bus:0) at nexus

isp0 at pci0 slot 1

isp0: QLOGIC ISP1040B/V2

isp0: Firmware revision 5.57 (loaded by console)

isp0: Fast RAM timing enabled.

scsi1 at isp0 slot 0 rad 0

isp1 at pci0 slot 2

isp1: QLOGIC ISP1040B/V2 - Differential Mode

isp1: Firmware revision 5.57 (loaded by console)

isp1: Fast RAM timing enabled.

scsi2 at isp1 slot 0 rad 0

isa0 at pci0

gpc0 at isa0

gpc1 not probed

ace0 at isa0

ace1 at isa0

lp0 at isa0

fdi0 at isa0

fd0 at fdi0 unit 0

ata0 at pci0 slot 15

ata0: ACER M1543C

scsi3 at ata0 slot 0 rad 0

scsi4 at ata0 slot 1 rad 0

usb0 at pci0 slot 19

Created FRU table binary error log packet

kernel console: ace0

NetRAIN configured.

vm_swap_init: warning /dev/disk/dsk0b swap device not found




















 INIT: SINGLE-USER MODE
#

·    At the # prompt make sure the root device is writeable. This will begin the recreation of the Hardware & SCSI devices databases.

# /sbin/mountroot
Mounting / (root)
msfs_mount: error getting disk list for domain "root_domain"
msfs_mount: Setting root device name to "root_device" RW
user_cfg_pt: reconfigured
root_mounted_rw: reconfigured
user_cfg_pt: reconfigured
root_mounted_rw: reconfigured
Device Naming: first boot initialization . . .
  etc/cfginfo -> ../cluster/members/member/etc/cfginfo
  cluster/members/member0/etc/cfginfo
  etc/dccd.dat
  etc/dcdd.dat
  etc/dfsc.dat
  etc/dfsl.dat -> ../cluster/members/member/etc/dfsl.dat
  cluster/members/member0/etc/dfsl.dat
ptm
 cport disk rdisk tape ntape changer dmapi
user_cfg_pt: reconfigured
dsfmgr: NOTE: creating device special files for system at /
    +scp_scsi +kevm +kevm.pterm +kevm.debug -kevm.debug +tty00 +tty01 +lp0 +floppy0a +floppy0a +floppy0b -floppy0b +floppy0b -floppy0b +floppy0c +floppy0c +floppy0d -floppy0d +floppy0d -floppy0d +floppy0e -floppy0e +floppy0e -floppy0e +floppy0f -floppy0f +floppy0f -floppy0f +floppy0g -floppy0g +floppy0g -floppy0g +floppy0h -floppy0h +floppy0h -floppy0hAssigning a cluster device number to root
 +dsk0a +dsk0a +dsk0b +dsk0b +dsk0c +dsk0c +dsk0d +dsk0d +dsk0e +dsk0e +dsk0f +dsk0f +dsk0g +dsk0g +dsk0h +dsk0h +dsk1a +dsk1a +dsk1b +dsk1b +dsk1c +dsk1c +dsk1d +dsk1d +dsk1e +dsk1e +dsk1f +dsk1f +dsk1g +dsk1g +dsk1h +dsk1h +dsk2a +dsk2a +dsk2b +dsk2b +dsk2c +dsk2c +dsk2d +dsk2d +dsk2e +dsk2e +dsk2f +dsk2f +dsk2g +dsk2g +dsk2h +dsk2h +dsk3a +dsk3a +dsk3b +dsk3b +dsk3c +dsk3c +dsk3d +dsk3d +dsk3e +dsk3e +dsk3f +dsk3f +dsk3g +dsk3g +dsk3h +dsk3h +dsk4a +dsk4a +dsk4b +dsk4b +dsk4c +dsk4c +dsk4d +dsk4d +dsk4e +dsk4e +dsk4f +dsk4f +dsk4g +dsk4g +dsk4h +dsk4h +dsk5a +dsk5a +dsk5b +dsk5b +dsk5c +dsk5c +dsk5d +dsk5d +dsk5e +dsk5e +dsk5f +dsk5f +dsk5g +dsk5g +dsk5h +dsk5h +cdrom0a +cdrom0a +cdrom0b -cdrom0b +cdrom0b -cdrom0b +cdrom0c +cdrom0c +cdrom0d -cdrom0d +cdrom0d -cdrom0d +cdrom0e -cdrom0e +cdrom0e -cdrom0e +cdrom0f -cdrom0f +cdrom0f -cdrom0f +cdrom0g -cdrom0g +cdrom0g -cdrom0g +cdrom0h -cdrom0h +cdrom0h -cdrom0h +tape0 +tape0 +tape0c +tape0c +tape0_d0 +tape0_d0 +tape0_d1 +tape0_d1 +tape0_d2 +tape0_d2 +tape0_d3 +tape0_d3 +tape0_d4 +tape0_d4 +tape0_d5 +tape0_d5 +tape0_d6 +tape0_d6 +tape0_d7 +tape0_d7


·    Mount remaining OS filesystems

# bcheckrc
Checking device naming:
    Passed.
Checking local filesystems
Mounting local filesystems
exec: /sbin/mount_advfs -F 0x14000 root_domain#root /
root_domain#root on / type advfs (rw)
/proc on /proc type procfs (rw)
exec: /sbin/mount_advfs -F 0x4000 usr_domain#usr /usr
usr_domain#usr on /usr type advfs (rw)
exec: /sbin/mount_advfs -F 0x4000 var_domain#var /var
var_domain#var on /var type advfs (rw)













·    Create new kernel configuration file and rebuild kernel. If required, edit kernel configuration file to insert specific customizations.

# TERM=vt100
# export TERM
# cd /sys/conf
#
# doconfig

*** KERNEL CONFIGURATION AND BUILD PROCEDURE ***

Enter a name for the kernel configuration file. [ALPHA]:

A configuration file with the name 'ALPHA' already exists.
Do you want to replace it? (y/n) [n]: y

Saving /sys/conf/ALPHA as /sys/conf/ALPHA.bck


*** KERNEL OPTION SELECTION ***

    Selection   Kernel Option
--------------------------------------------------------------
    1    System V Devices
    2    NTP V3 Kernel Phase Lock Loop (NTP_TIME)
    3    Kernel Breakpoint Debugger (KDEBUG)
    4    Packetfilter driver (PACKETFILTER)
    5    IP-in-IP Tunneling (IPTUNNEL)
    6    IP Version 6 (IPV6)
    7    Point-to-Point Protocol (PPP)
    8    STREAMS pckt module (PCKT)
    9    X/Open Transport Interface (XTISO, TIMOD, TIRDWR)
    10    Digital Versatile Disk File System (DVDFS)
    11    ISO 9660 Compact Disc File System (CDFS)
    12    Audit Subsystem
    13    Logical Storage Manager (LSM)
    14    ATM UNI 3.0/3.1 ILMI (ATMILMI3X)
    15    IP Switching over ATM (ATMIFMP)
    16    LAN Emulation over ATM (LANE)
    17    Classical IP over ATM (ATMIP)
--- MORE TO FOLLOW ---
Enter your choices or press <Return>
to display the next screen.

Choices (for example, 1 2 4-6):
    18    ATM UNI 3.0/3.1 Signalling for SVCs (UNI3X)
    19    Asynchronous Transfer Mode (ATM)
    20    All of the above
    21    None of the above
    22    Help
    23    Display all options again
--------------------------------------------------------------

Enter your choices.

Choices (for example, 1 2 4-6) [21]: 20

You selected the following kernel options:
    System V Devices
    NTP V3 Kernel Phase Lock Loop (NTP_TIME)
    Kernel Breakpoint Debugger (KDEBUG)
    Packetfilter driver (PACKETFILTER)
    IP-in-IP Tunneling (IPTUNNEL)
    IP Version 6 (IPV6)
    Point-to-Point Protocol (PPP)
    STREAMS pckt module (PCKT)
    X/Open Transport Interface (XTISO, TIMOD, TIRDWR)
    Digital Versatile Disk File System (DVDFS)
    ISO 9660 Compact Disc File System (CDFS)
    Audit Subsystem
    Logical Storage Manager (LSM)
    ATM UNI 3.0/3.1 ILMI (ATMILMI3X)
    IP Switching over ATM (ATMIFMP)
    LAN Emulation over ATM (LANE)
    Classical IP over ATM (ATMIP)
    ATM UNI 3.0/3.1 Signalling for SVCs (UNI3X)
    Asynchronous Transfer Mode (ATM)

Is that correct? (y/n) [y]: y

Do you want to edit the configuration file? (y/n) [n]: n


*** PERFORMING KERNEL BUILD ***

A log file listing special device files is located in /dev/MAKEDEV.log
    Working....Wed Oct  2 13:51:55 BST 2002

The new kernel is /sys/ALPHA/vmunix

# mv /sys/ALPHA/vmunix /vmunix

·    Reboot system

# cd /
# umount -a
# sync
# sync
# sync
# halt
:
P00>>>
P00>>> set auto_action boot
P00>>> set bootos_flags a
P00>>> set bootdef_dev dkc0
P00>>> boot

The ALPHA system should boot to multi-user mode, with all OS services running. This can be verified by logging on to the system and running the  df -k command to check /, /usr & /var filesystems are mounted.


·    Data Filesystem Recovery

·    Make application & data AdvFS filesystems

# disklabel -z dsk1
# disklabel -z dsk2
# disklabel -z dsk3
# disklabel -z dsk4
# disklabel -z dsk5
#
#
# disklabel -t advfs -wr dsk1 HSZ80
# disklabel -t advfs -wr dsk2 HSZ80
# disklabel -t advfs -wr dsk3 HSZ80
# disklabel -t advfs -wr dsk4 HSZ80
# disklabel -t advfs -wr dsk5 HSZ80
#
# mkfdmn /dev/disk/dsk1c u01_domain
# mkfset u01_domain u01
#
# mkfdmn /dev/disk/dsk2c u02_domain
# mkfset u02_domain u02
#
# mkfdmn /dev/disk/dsk3c u03_domain
# mkfset u03_domain u03
#
# mkfdmn /dev/disk/dsk4c u04_domain
# mkfset u04_domain u04
#
# mkfdmn /dev/disk/dsk5c u05_domain
# mkfset u05_domain u05



·    Add datafilesystem entries in /etc/fstab

# TERM=vt100
# EDITOR=vi
# export TERM EDITOR
# vi /etc/fstab

root_domain#root / advfs rw,userquota,groupquota 0 1
/proc /proc procfs rw 0 0
usr_domain#usr /usr advfs rw,userquota,groupquota 0 2
var_domain#var /var advfs rw,userquota,groupquota 0 2
users_domain#users /usr/users advfs rw,userquota,groupquota 0 2
u01_domain#u01 /u01 advfs rw,userquota,groupquota 1 2
u02_domain#u02 /u02 advfs rw,userquota,groupquota 1 2
u03_domain#u03 /u03 advfs rw,userquota,groupquota 1 2
u04_domain#u04 /u04 advfs rw,userquota,groupquota 1 2
u05_domain#u05 /u05 advfs rw,userquota,groupquota 1 2

·    Mount empty filesystems

# mount -a

·    Restore data to apps & data filesystems from backup tapes.

·    Reboot system to Multi-user mode

# shutdown -r now

The ALPHA system should now reboot to multi-user mode, with all OS and database services operational. This can be verified by logging on to the system and running whatever database applications are necessary.

RE: Restoring a Tru64 Box with Sybase

The above advice is excellent for getting the O/S up and running, but I notice that your question also involves Sybase.
Sybase, like most database servers, has "hot" files (i.e. always open for writing) that generally don't backup & restore correctly using conventional O/S backups.
In fact, it is common for Sybase to use raw devices such as "/dev/rvol/group2/<volumename>" to store data rather than files on a mounted file system.  
So yes, you do want to follow a procedure such as that listed above, but also be prepared to dump all of your databases to tape on a regular basis using a script that calls the sybase "dump database" command, and load the databases back in afterwards.
To make it easier to manage, you might consider using a third-party software tool such as Veritas or Legato to perform daily tape backups and restores of your O/S, and make sure it includes an add-on "agent" that directly queries your Sybase servers and dumps the databases to tape.  
If you are unsure of how to back up and recover Sybase databases, I would definitely recommend involving your DBA's (if you have any) or bring in outside help to ensure that you are backing up everything required.
 

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close