j5d

ORA-01034: ORACLE not available / ORA-27101: shared memory realm does not exist

2008-02-26T16:11:00.006+07:00

Database is "UP" but Veritas Netbackup detect that the oracle db is down and cannot create template from Netbackup Java Console.

Because of this error, than I try to configure the Hot Backup Oracle using RMAN script provided by Netbackup on "/usr/openv/netbackup/ext/db_ext/oracle/samples/rman". Using this script, I also found the same error.

RMAN-00571:=============================================
RMAN-00569:======== ERROR MESSAGE STACK FOLLOWS =========
RMAN-00571:=============================================
RMAN-03002: failure of allocate command at 02/25/2008 15:12:29
RMAN-06403: could not obtain a fully authorized session
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory

We can connect locally to RMAN, and test the link to Veritas Netbackup with successfully.

bash-2.05$ pwd
/rdbms/oracle9

bash-2.05$ rman target veritas/veritas
Recovery Manager: Release 9.2.0.6.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: ODONG2 (DBID=1263713746)
RMAN> RUN {
2> ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
3> RELEASE CHANNEL ch00;
4> }
using target database controlfile instead of recovery catalog
allocated channel: ch00
channel ch00: sid=38 devtype=SBT_TAPE
channel ch00: VERITAS NetBackup for Oracle - Release 5.0GA (2003103006)
released channel: ch00
RMAN> quit
Recovery Manager complete.
bash-2.05$

But using the netbackup Java Console & Netbackup Script still the same error. After discuss with the DBA, refer to documentation support from Veritas Netbackup, and some tries, we found that, the problem is on environtment variables :

Here is our environtment variables on this server :

bash-2.05$ env
PWD=/rdbms/oracle9
ORACLE_SID=test
HOSTNAME=odong2
LD_LIBRARY_PATH=/rdbms/oracle9/OraHome1/lib
MACHTYPE=sparc-sun-solaris2.9
MAIL=/var/mail/oracle9
EDITOR=vi
ORACLE_BASE=/rdbms/oracle9/
ORACLE_HOME=/rdbms/oracle9//OraHome1/
LOGNAME=oracle9
SHELL=/bin/bash
HOSTTYPE=sparc
OSTYPE=solaris2.9
HOME=/rdbms/oracle9

And the problem is we cannot go directly to ORACLE_HOME using the script, but must be used "ORACLE_HOME=$ORACLE_BASE/OraHome1/" .

To SOLVE the problem, we "add" the ORACLE_BASE parameter to the Script :

# ----------------------------------------------------------
# Replace /db/oracle81, below, with the Oracle home path.
# ----------------------------------------------------------

ORACLE_BASE=/rdbms/oracle9/
export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/OraHome1/
export ORACLE_HOME

After adding the ORACLE_BASE parameter, Hot Backup Online Oracle running normal.

Hot Backup Oracle using Veritas Netbackup

2008-01-31T14:54:00.000+07:00

Requirements :
Oracle DB Archivelog status = ON & Start …….. here
Controlfile Autobackup = ON…….. here
Default Autobackup device type = SBT_TAPE

Preparations :
Install Netbackup for Oracle Agent
Shutdown all of the Oracle instances (SIDs).
Login or su – from root to oracle user

# sqlplus /nolog

SQL> connect / as sysdba
SQL> shutdown immediate
SQL> exit

Link Netbackup to Oracle :
Automatically link :

/install_path /netbackup/bin/oracle_link

Manually Link :

ln -s /install_path /netbackup/bin/libobk.so.1 libobk.so (solaris)
ln -s /install_path /netbackup/bin/libobk.so64.1 libobk.so (solaris with 64-bit Oracle Software)
ln -s /install_path /netbackup/bin/libobk.a64 libobk.a (AIX)
ln -s /install_path /netbackup/bin/libobk.sl64 libobk.sl (HP-UX)
ln -s /install_path /netbackup/bin/libobk.so libobk.so (linux)

Test Connectivity from Oracle RMAN to Veritas Netbackup :

RMAN> run{allocate channel ch00 type 'SBT_TAPE';
2> release channel ch00;
3> }

Output :

using target database controlfile instead of recovery catalog
allocated channel: ch00
channel ch00: sid=14 devtype=SBT_TAPE
channel ch00: VERITAS NetBackup for Oracle - Release 5.0GA (2006030216)
released channel: ch00
RMAN> quit
Recovery Manager complete.

Hot Backup Oracle :

Create Online Backup Shell Script for Full DB & archivelogs refer to sample RMAN script on "/install_path/netbackup/ext/db_ext/oracle/samples/rman" or using template from Veritas Netbackup GUI Wizard.

Hot Backup Oracle SCRIPT…….. here
Hot Backup Oracle TEMPLATE…….. here

Create Policy for Full Online Backup & Archivelogs Backup.
Test Hot Backup Oracle using Veritas Netbackup.

Hot Database Backup Sample Script

2008-01-31T14:37:00.000+07:00

Online Backup Shell Script for Full DB & archivelogs refer to sample RMAN script (/install_path/netbackup/ext/db_ext/oracle/samples/rman)

#!/bin/sh
# $Header: hot_database_backup.sh,v 1.2 2002/08/06 23:51:42 $
#bcpyrght
#***************************************************************************
#$VRTScprght:Copyright 1993-2003 VERITAS Software Corporation,All Rights Reserved $
#***************************************************************************
#ecpyrght
#hot_database_backup.sh
# Determine the user which is executing this script.
CUSER=`id |cut -d"(" -f2 | cut -d ")" -f1`
# Put output in .out. Change as desired.
# Note: output directory requires write permission.
RMAN_LOG_FILE=${0}.out
# You delete the output file so that backup information does not accumulate.
# If not, delete the following lines.

if [ -f "$RMAN_LOG_FILE" ]
then
rm -f "$RMAN_LOG_FILE"
fi
# Initialize the log file.
echo >> $RMAN_LOG_FILE
chmod 666 $RMAN_LOG_FILE
# Log the start of this script.
echo Script $0 >> $RMAN_LOG_FILE
echo ==== started on `date` ==== >> $RMAN_LOG_FILE
echo >> $RMAN_LOG_FILE

# Replace /db/oracle/product/ora81, below, with the Oracle home path.
ORACLE_HOME=/db/oracle/product/ora81
export ORACLE_HOME
# Replace ora81, below, with the Oracle SID of the target database.
ORACLE_SID=ora81
export ORACLE_SID
# Replace ora81, below, with the Oracle DBA user id (account).
ORACLE_USER=ora81
# Set the target connect string. Replace "sys/manager", below, with the target connect string.
TARGET_CONNECT_STR=sys/manager
# Set the Oracle Recovery Manager name.
RMAN=$ORACLE_HOME/bin/rman
# Print out the value of the variables set by this script.
echo >> $RMAN_LOG_FILE
echo "RMAN: $RMAN" >> $RMAN_LOG_FILE
echo "ORACLE_SID: $ORACLE_SID" >> $RMAN_LOG_FILE
echo "ORACLE_USER: $ORACLE_USER" >> $RMAN_LOG_FILE
echo "ORACLE_HOME: $ORACLE_HOME" >> $RMAN_LOG_FILE
# Print out the value of the variables set by bphdb.
echo >> $RMAN_LOG_FILE
echo "NB_ORA_FULL: $NB_ORA_FULL" >> $RMAN_LOG_FILE
echo "NB_ORA_INCR: $NB_ORA_INCR" >> $RMAN_LOG_FILE
echo "NB_ORA_CINC: $NB_ORA_CINC" >> $RMAN_LOG_FILE
echo "NB_ORA_SERV: $NB_ORA_SERV" >> $RMAN_LOG_FILE
echo "NB_ORA_POLICY: $NB_ORA_POLICY" >> $RMAN_LOG_FILE
# NOTE: This script assumes that the database is properly opened.
# If desired, this would be the place to verify that.
echo >> $RMAN_LOG_FILE
if [ "$NB_ORA_FULL" = "1" ]
then
echo "Full backup requested" >> $RMAN_LOG_FILE
BACKUP_TYPE="INCREMENTAL LEVEL=0"
elif [ "$NB_ORA_INCR" = "1" ]
then
echo "Differential incremental backup requested" >> $RMAN_LOG_FILE
BACKUP_TYPE="INCREMENTAL LEVEL=1"
elif [ "$NB_ORA_CINC" = "1" ]
then
echo "Cumulative incremental backup requested" >> $RMAN_LOG_FILE
BACKUP_TYPE="INCREMENTAL LEVEL=1 CUMULATIVE"
elif [ "$BACKUP_TYPE" = "" ]
then
echo "Default - Full backup requested" >> $RMAN_LOG_FILE
BACKUP_TYPE="INCREMENTAL LEVEL=0"
fi
# Call Recovery Manager to initiate the backup. This example does not use a Recovery Catalog.
# If you choose to use one, replace the option 'nocatalog' from the rman command line below
# with the 'rcvcat /@' statement.
# Backs up the whole database. This backup is part of the incremental strategy
# (this means it can have incremental backups of levels > 0 applied to it).
CMD_STR="
ORACLE_HOME=$ORACLE_HOME
export ORACLE_HOME
ORACLE_SID=$ORACLE_SID
export ORACLE_SID
$RMAN target $TARGET_CONNECT_STR nocatalog msglog $RMAN_LOG_FILE append <<>> $RMAN_LOG_FILE
RSTAT=$?
else
/usr/bin/sh -c "$CMD_STR" >> $RMAN_LOG_FILE
RSTAT=$?
fi
# Log the completion of this script.
if [ "$RSTAT" = "0" ]
then
LOGMSG="ended successfully"
else
LOGMSG="ended in error"
fi
echo >> $RMAN_LOG_FILE
echo Script $0 >> $RMAN_LOG_FILE
echo ==== $LOGMSG on `date` ==== >> $RMAN_LOG_FILE
echo >> $RMAN_LOG_FILE
exit $RSTAT

Enabling Oracle ARCHIVELOG Mode

2008-01-31T14:18:00.000+07:00

Procedure 1

Login as "ora" or su - from "root" at operating system

# sqlplus /nolog

SQL > connect / as sysdba
SQL > shutdown immediate;
SQL > startup mount;

Checking the current archive mode status.

SQL> SELECT LOG_MODE FROM SYS.V$DATABASE;
LOG_MODE
------------
NOARCHIVELOG

Set archivelog destination and format :

SQL> alter system set log_archive_format=’ SIDarch%t_%s.dbf;
SQL> alter system set log_archive_dest=’/oracle/SID/archivelogs;

Check archivelog destination and format

SQL> select name,value from v$parameter where name=’log_archive_format’;
SQL> select name,value from v$parameter where name=’log_archive_dest’;

Backup or Copy original "initSID.ora" :

# cp /oracle/SID/920_64/dbs/initSID.ora /oracle/SID/920_64/dbs/initSID.ora.orig

SQL> create pfile=’ /oracle/SID/920_64/dbs/initSID.ora’ from spfile;
SQL> alter database archivelog;
SQL> select log_mode from v$database;
LOG_MODE
------------
ARCHIVELOG
SQL> alter database open;
SQL> exit

PROCEDURE 2 [only do this procedure if procedure 1 above failed]

This procedure update the pfile directly. The pfile should be in either $ORACLE_BASE/admin/SID/pfile or $ORACLE_HOME/admin/SID/pfile.

Login as "ora" or su - from "root" at operating system.

# sqlplus /nolog

SQL > connect / as sysdba

Checking the current archive mode status, if status "NOARCHIVELOG" than shutdown database to run enable archivelog mode procedure.

SQL> SELECT LOG_MODE FROM SYS.V$DATABASE;
LOG_MODE
------------
NOARCHIVELOG
SQL > shutdown immediate;
SQL > exit

# vi $ORACLE_BASE/admin/SID/pfile

Add the following lines to the end of the pfile :

# Archive Log Destinations #
log_archive_dest_1='location=/oracle/SID/archivelogs'
log_archive_start=TRUE

Startup the database in mount mode and put it in archivelog mode.

# sqlplus /nolog

SQL > connect / as sysdba
SQL > startup mount;
SQL> alter database archivelog;
SQL> alter database open;

Check archivelog destination and status

SQL> SELECT LOG_MODE FROM SYS.V$DATABASE;
LOG_MODE
------------
ARCHIVELOG
SQL> show parameter log_archive_dest_1
SQL> show parameter spfile;
SQL> show parameter log_archive_start;

Test create archivelog

SQL> alter system switch logfile;
SQL> create pfile from spfile;
SQL> shutdown immediate;
SQL> startup
SQL> exit

Problem solving Error Status Code 6 [NBU - Oracle]

2008-01-31T14:06:00.000+07:00

Problem :
STATUS CODE 6: "The backup failed to back up the requested files"
The archive log file may have been deleted from the operating system and it does not exist at the specified location.

Reference :
http://seer.entsupport.symantec.com/docs/275089.htm

Resolution :

RMAN> Change Archivelog All Validate;
RMAN> Change Archivelog All Crosscheck;

HP-UX as SAN Media Server in Netbackup 5.X

2008-01-21T13:43:00.000+07:00

Step by step documentation configuring HP-UX as SAN Media server on Veritas Netbackup 5.X environtments.
Before configure the drives in netbackup, at first we must configure the drives at OS level and zoning the tape drives from HP-UX to Tape Library.

List all HBA (Host Bus Adapter) in the HP-UX server to get the hardware path :

root@j5d # ioscan -funC fc

Class I H/W Path Driver S/W State H/W Type Description
=================================================================
fc 2 4/1/0 td CLAIMED INTERFACE HP Tachyon TL/TS Fibre Channel Mass Storage Adapter
/dev/td2
fc 0 1/1/0 td CLAIMED INTERFACE HP Tachyon TL/TS Fibre Channel Mass Storage Adapter
/dev/td0
fc 1 1/2/0 td CLAIMED INTERFACE HP Tachyon TL/TS Fibre Channel Mass Storage Adapter
/dev/td1

Check FC cable connectivity (driver state) and WWN for Zoning purpose on SAN Switch Level :

root@j5d # fcmsutil /dev/td2

Vendor ID is = 0x00103c
Device ID is = 0x001028
TL Chip Revision No is = 2.3
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x000006
Topology = PTTOPT_FABRIC
Local N_Port_id is = 0x043900
N_Port Node World Wide Name = 0x50060b000006714f
N_Port Port World Wide Name = 0x50060b000006714e
Driver state = ONLINE
Hardware Path is = 4/1/0
Number of Assisted IOs = -1906797105
Number of Active Login Sessions = 1

After get the wwn do zoning on SAN Switch, next step, check the tape drives on the hp-ux :

root@j5d # ioscan -funC tape

Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
tape 20 0/1/1/1.6.0 stape CLAIMED DEVICE HP Ultrium 2-SCSI
/dev/rmt/20m /dev/rmt/20mn /dev/rmt/c3t6d0BEST /dev/rmt/c3t6d0BESTn
/dev/rmt/20mb /dev/rmt/20mnb /dev/rmt/c3t6d0BESTb /dev/rmt/c3t6d0BESTnb
tape 1 0/4/1/0.234.18.255.5.5.0 stape CLAIMED DEVICE IBM ULTRIUM-TD1

Install the driver for this tape drives, when the OS has detected :

root@j5d # insf -e

insf: Installing special files for stape instance 1 address 0/4/1/0.234.18.255.5.5.0

Check again to make sure all the tape drives and drivers for the tape drives has been detect and installed :

root@j5d # ioscan -funC tape

Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
tape 1 0/4/1/0.234.18.255.5.5.0 stape CLAIMED DEVICE IBM ULTRIUM-TD1
/dev/rmt/1m /dev/rmt/1mn /dev/rmt/c16t5d0BEST /dev/rmt/c16t5d0BESTn
/dev/rmt/1mb /dev/rmt/1mnb /dev/rmt/c16t5d0BESTb /dev/rmt/c16t5d0BESTnb

After above step successfully done, than we can continue to configure on netbackup level :
- Install Netbackup Master/Media agent.
- Do "scan" from netbackup to check the drives has been detect by netbackup :

root@j5d # /usr/openv/volmgr/bin/scan

make sure all tape drives has been successfully detect.
If netbackup still cannot detect the tape drives, re-start the server ....

- Set parameter Global Device :

root@j5d # /usr/openv/volmgr/bin/vmglob -set_gdbhost "master" -h "master" --> master = master backup hostname

- Configure tape drives :

root@j5d # /usr/openv/volmgr/bin/tpautoconf -a --> automatic configure tape drives

- Stop all Netbackup process :

root@j5d # /usr/openv/netbackup/bin/goodies/netbackup stop "or" /usr/openv/netbackup/bin/goodies/netbackup/bp.kill_all

- Start all Netbackup process :

root@j5d # /usr/openv/netbackup/bin/goodies/netbackup start

- Check All Netbackup Process running well.

root@j5d # /usr/openv/netbackup/bin/bpps -a

After completed the devices configuration, create the storage unit, volume pool, and backup policy. Afterward test Backup and Restore. Thanks.

Turning on "AUTOBACKUP" Oracle RMAN

2008-01-16T14:15:00.000+07:00

Steps:

# rman target /
RMAN>
RMAN> show all;

CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default

RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON;
RMAN> SET CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
RMAN> SET CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
RMAN> show all;

CONFIGURE DEFAULT DEVICE TYPE TO SBT_TAPE; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default

Test the control file backup to tape :

RMAN> backup current controlfile;

Controlling services on RHEL 4 :

2008-01-11T01:44:00.000+07:00

List all services :

# chkconfig --list

Active/Deactive services

# chkconfig "servicesname" on/off

Set service active on specific run level

# chkconfig --level 35 "servicesname" on/off

Remove service

# chkconfig --del "servicesname"

Add Service

# chkconfig --add "servicesname"

Restart service

# service "servicesname" restart

or using GUI/System Utility :

# system-config-services

# ntsysv

Fixing a corrupt GRUB MBR on RHEL 4

2008-01-11T01:38:00.000+07:00

Use grub-install to fix:

# chroot /mnt/sysimage
# /sbin/grub-install /dev/hda
# quit

# /sbin/grub-install --directory="mountpoint" /dev/hda

where "mountpoint" is boot partition

If above steps fails try the following :
Launch a grub shell:

# /sbin/grub

grub>root (hd0,0)
grub>setup (hd0)
grub>quit

Create grub password :

# grub-md5-crypt
password : password
retype : password

Copy encryption password to /boot/grub/grub.conf under hiddenmenu

# vi /boot/grub/grub.conf

----------
hiddenmenu
password --md5 ialknda$SDLKANDADikaldnald9addasdad
----------

Additional step (troubleshooting) to Configure Solaris Tape drives for Netbackup .....

2008-01-07T16:23:00.000+07:00

This procedure must be successfully "done" to troubleshoot Un-Detect tape drives after netbackup sg.install installation.

root@j5d # ls -l /dev/rmt/*cbn

root@j5d # /usr/openv/volmgr/bin/scan

Display PCI slot configuration information for tape drives

root@j5d # cfgadm –al

c0::dsk/c0t6d0 CD-ROM connected configured unknown
c1 fc-private connected configured unknown
c1::21xxxxxxxxxxxxx2 disk connected configured unknown
c5 fc-fabric connected configured unknown
c5::50xxxxxxxxxxxxx2 tape connected configured unknown
c5::50xxxxxxxxxxxxxe tape connected configured unknown
....
c6 fc connected unconfigured unknown

Unconfigure tape devices

root@j5d # cfgadm -c unconfigure c5

Clean-up device file

root@j5d # devfsadm –C

Reconfigure tape device

root@j5d # cfgadm -c configure c5

if configure failed, try force update with command :

root@j5d # cfgadm –c configure –o force_update c5

List PCI slot configuration information for tape drives

root@j5d # cfgadm –al

root@j5d # ls -l /dev/rmt/*cbn

lrwxrwxrwx 1 root root 71 Jan 7 15:39 /dev/rmt/0cbn ->
../../devices//fp@0,0/st@xxxxxxxxxxxxxxxbe,0:cbn
.......
lrwxrwxrwx 1 root root 71 Jan 7 15:41 /dev/rmt/9cbn ->
../../devices/fp@0,0/st@xxxxxxxxxxxxxxx82,0:cbn

root@j5d # /usr/sbin/rem_drv sg
root@j5d # /usr/bin/rm -f /kernel/drv/sg.conf
root@j5d # /usr/openv/volmgr/bin/driver/sg.install

Copied files to /kernel/drv and to /kernel/drv/sparcv9.
Doing add_drv of the sg driver
Removing old /dev/sg entries.
Editing /etc/devlink.tab...
Copying original /etc/devlink.tab to /etc/devlink.tab.01-07-08-15:44:06.
Added entry in /etc/devlink.tab file.
Made links in /dev/sg

root@j5d # /usr/openv/volmgr/bin/scan

************************************************************
*********************** SDT_TAPE ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
------------------------------------------------------------
Device Name : "/dev/rmt/0cbn"
Passthru Name: "/dev/sg/c0txxxxxxxxxxxxxxxbel0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "IBM ULTRIUM-TD3 5BG2"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD3 "
Product Rev: "5BG2"
Serial Number: "XXXXXXXXXX"
WWN : "IBM ULTRIUM-TD3 XXXXXXXXXX"
WWN Id Type : 1
Device Identifier: "IBM ULTRIUM-TD3 XXXXXXXXXX"
Device Type : SDT_TAPE
NetBackup Drive Type: 16
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------

Logical Volume Manager [LVM] on RHEL 4

2007-12-28T10:14:00.001+07:00

Logical Volume Manager (LVM) = Disk management to manage physical disks as logical volumes.

Volume = A device used for a filesystem, swap, or raw data. Without Logical Volume Manager, a volume would be either a disk partition or an entire disk drive.

Physical Volume (PV) = The standard partition that you add to the LVM.

Volume Group = a collection of logical volumes that are managed by Logical Volume Manager.

Logical Volume = Space that is defined within a volume group. A volume group is divided up into logical volumes.

Creating logical volumes on RHEL 4 :

Add new hard drive or create X partitions if using single hard drive, and change partition type to linux lvm (8e) using "fdisk"

Create physical volume

# pvcreate /dev/hda1
# pvcreate /dev/hdb1

Create volume group (vg)

# vgcreate vg0 /dev/hda1 /dev/hdb1

Check available volume group space

# vgdisplay -v

Create logical volume (lv) on new VG (for example 200 MBytes)

# lvcreate -L 200M -n test vg0

Create file system for the new logical volume

# mkfs.ext3 /dev/vg0/test

Create new directory to mount the logical volume

# mkdir /test

Add new logical volume to "/etc/fstab" to make automaticly mount at system start and reboot the system or manually mount with :

# mount /dev/vg0/test /test

Resizing Logical Volume on RHEL 4 :

Add new hard drive / partitionChange partition type to linux lvm (8e) using "fdisk"

# vgextend vg0 /dev/hdc1

Check available volume group space

# vgdisplay -v

Add new free space to logical volume

# lvextend -L +50M /dev/vg0/test

Resize filesystem (never used mkfs/mke2fs because it will be format all the logical volume)

# ext2online /dev/vg0/test

Reducing logical volume on RHEL 4 :

Unmount any directories associated with the logical volume.

# umount /test

Reduce the volume group

# resize2fs /dev/vg0/test 120M

Reduce the logical volume

# lvreduce -L 120M /dev/vg0/test

Mount again with the new size

# mount /dev/vg0/test /test

Check status disk free.

# df -h

Removing Logical volumes on RHEL 4 :

Unmount any directories associated with the logical volume

# umount /dev/vg0/test

Remove the logical volume with a command :

# lvremove /dev/vg0/test

IBM AIX as Netbackup 5.X SAN Media Server

2007-12-11T10:50:00.000+07:00

Installing NetBackup Media Server Agent for AIX.
Login as root. Mount the CD-ROM auto using the following methods:

# smitty cdrfs "or" # smitty mountfs

Mount the CD-ROM manually :

# mkdir /cdrom
# mount -v cdrfs -r /dev/cd0 /cdrom
# cd /cdrom
# ./install

Before start the configuration of Netbackup storage devices, make sure all the device tapes have been already recognized on the operating system level.

# cfgmgr -v
# lsdev -Cc tape

If the devices could not be found on the OS level do the following method :

Check your installed version of Atape.driver

# lslpp -l Atape.driver
Fileset Level State Description
----------------------------------------------------------------------------
Atape.driver 9.1.6.0 COMMITTED IBM AIX Enhanced Tape and Medium Changer Device Driver

Un-install existing tape drive driver

# installp -u Atape.driver

Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
Atape.driver 9.1.6.0 USR DEINSTALL SUCCESS

Install new driver "atape" for AIX that compatible with your tape drives

# installp -acXd /tmp/atape/Atape.10.3.5.0.bin Atape.driver
Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
Atape.driver 10.3.5.0 USR APPLY SUCCESS# cfgmgr -v
# lsdev -Cc tape

If netbackup still cannot detect the tape drives, re-start the server ....

After all the device tapes have been already recognized on the operating system level :
Do "scan" from netbackup and make sure all tape drives has been successfully detect.

# /usr/openv/volmgr/bin/scanSet media parameter Global Device :
# /usr/openv/volmgr/bin/vmglob -set_gdbhost "master" -h "master" --> master = master backup hostname

Configure tape drives :

# /usr/openv/volmgr/bin/tpautoconf -a --> automatic configure tape drives

Stop all Netbackup process :

# /usr/openv/netbackup/bin/goodies/netbackup stop "or" /usr/openv/netbackup/bin/goodies/netbackup/bp.kill_all

Start all Netbackup process :

# /usr/openv/netbackup/bin/goodies/netbackup start

Check All Netbackup Process running well :

# /usr/openv/netbackup/bin/bpps -a

After completed the devices configuration, create the storage unit, volume pool, and backup policy.
Afterward test Backup and Restore.

Troubleshooting Netbackup Error Status 57 on Solaris 10

2007-12-11T09:32:00.000+07:00

Here is sample error from system log.

# dmesg
May 24 11:24:57 hostname inetd[467]: [ID 702911 daemon.warning] Configuration file /etc/inet/inetd.conf has been modified since inetconv was last run. "inetconv -i /etc/inet/inetd.conf" must be run to apply any changes to the SMF
May 24 13:29:30 hostname last message repeated 1 time

Lists all Netbackup services currently installed, including their state and check services for netbackup.

# svcs -a |grep bp

Update /etc/inet/inetd.conf for Veritas Netbackup Services if do not exist.

# inetconv -i /etc/inet/inetd.conf
inetconv: Notice: Service manifest for 100235/1 already generated as /var/svc/manifest/network/rpc/100235_1-rpc_ticotsord.xml, skipped
bpcd -> /var/svc/manifest/network/bpcd-tcp.xml
Importing bpcd-tcp.xml ...Done
vnetd -> /var/svc/manifest/network/vnetd-tcp.xml
Importing vnetd-tcp.xml ...Done
vopied -> /var/svc/manifest/network/vopied-tcp.xml
Importing vopied-tcp.xml ...Done
bpjava-msvc -> /var/svc/manifest/network/bpjava-msvc-tcp.xml
Importing bpjava-msvc-tcp.xml ...Done

List again to make sure all Netbackup services currently installed, including their state.

# svcs -a |grep bp
online 13:36:01 svc:/network/bpcd/tcp:default
online 13:36:11 svc:/network/bpjava-msvc/tcp:default

Restart inetd daemon to re-read the configuration :

# /usr/bin/pkill -HUP inetd

Solaris as Netbackup 5.X SAN Media Server

2007-12-10T14:41:00.000+07:00

Install Netbackup Media Server Agent for Solaris
Before configure solaris as Netbackup SAN Media Server, make sure all the device tapes have been already recognized on the operating system level.
Check existing SCSI passthru drivers (sg driver) :

# /usr/sbin/modinfo | grep sg
92 78152ea7 16ea 97 1 sysmsg (System message redirection (fan)
124 78000000 1eb8 49 1 msgsys (System V message facility)
124 78000000 1eb8 49 1 msgsys (32-bit System V message facilit)
147 102d7780 31cd 252 1 sg (SCSA Generic Revision: 3.5a)

Remove existing SCSI passthru drivers (sg driver) if available :

# /usr/sbin/rem_drv sg
# /usr/sbin/modinfo | grep sg --> make sure the driver has been unload
92 78152ea7 16ea 97 1 sysmsg (System message redirection (fan)
124 78000000 1eb8 49 1 msgsys (System V message facility)
124 78000000 1eb8 49 1 msgsys (32-bit System V message facilit)

Backup drive configuration before replace to the new one :

# cp /kernel/drv/sg.conf /kernel/drv/sg.conf_old
# /usr/bin/rm -f /kernel/drv/sg.conf

Install sg driver :

# /usr/openv/volmgr/bin/driver/sg.install

Reconfigure target and lun server to cover all backup hardware (tape drives).
Note : This command must be run on directory "/usr/openv/volmgr/bin/driver"

# cd /usr/openv/volmgr/bin/driver
# /usr/openv/volmgr/bin/sg.build all -mt 10 -ml 1 --> for 10 target(drive) and 1 lun
The file ./st.conf should be appended to /kernel/drv/st.conf.
A reboot may be necessary to create any new device files.
Created file ./sg.conf.
Created file ./sg.links.

Remove existing content of "/kernel/drv/st.conf", and replace with content "/usr/openv/volmgr/bin/driver/st.conf"
Make sure all directory and link for new tape drives has been automaticly created after the driver instalation (sg install).

# ls -l /dev/rmt/*cbn

Do "scan" from netbackup to check the drives has been detect by netbackup.

# /usr/openv/volmgr/bin/scan

If the tape drives has not detect by netbackup, remove sg driver and install again to re-read (refresh) the configuration.

# /usr/sbin/rem_drv sg
# /usr/bin/rm -f /kernel/drv/sg.conf
# /usr/openv/volmgr/bin/driver/sg.install

"scan" again and make sure all tape drives has been successfully detect.
If netbackup still cannot detect the tape drives, re-start the server ....
Set parameter Global Device :

# /usr/openv/volmgr/bin/vmglob -set_gdbhost "master" -h "master" --> master = master backup hostname

Configure tape drives :

# /usr/openv/volmgr/bin/tpautoconf -a --> automatic configure tape drives

Stop all Netbackup process :

# /usr/openv/netbackup/bin/goodies/netbackup stop "or" #/usr/openv/netbackup/bin/goodies/netbackup/bp.kill_all

Start all Netbackup process

# /usr/openv/netbackup/bin/goodies/netbackup start

Check All Netbackup Process running well.

# /usr/openv/netbackup/bin/bpps -a

After completed the devices configuration, create the storage unit, volume pool, and backup policy. Afterward test Backup and Restore.