Welcome to the Frontpage

Netbackup & VCS - Failing cluster

Tuesday, 23 February 2010 22:07 administrator

If your're Netbackup cluster switches or restarts unexpected, you can find the process causing the switch in :

/usr/openv/netbackup/bin/cluster/AGENT_DEBUG.log

A example:

# grep "Detected process offline" AGENT_DEBUG.log

02/23/10 14:55:091 Detected process offline:nbemm monitor::main
02/23/10 15:00:331 Detected process offline:vmd monitor::main
02/23/10 15:02:331 Detected process offline:nbemm monitor::main
02/23/10 15:42:031 Detected process offline:vmd monitor::main
02/23/10 15:44:031 Detected process offline:nbstserv monitor::main

Last Updated on Tuesday, 23 February 2010 22:47

Netbackup Fibre Transport Layer status code 40

Friday, 11 December 2009 10:48 administrator

If you encounter status code 40 - "network connection broken" using Netbackup Fibre Transport Layer (FTL) on Windows 2003 SP2 and you see event id 129 - Source ql2300 in the event log

and vxlogview report some or all of the errors below for Fibre Transport service :

CHECK CONDITION
    Valid                     = false
    Error Code                = 0x70
    Segment Number (0)        = 0x0
    Mark                      = false
    EOM                       = false
    ILI                       = false
    Sense Key                  = 0x9
    Information Bytes MSB1            = 0x0
    Information Bytes MSB0            = 0x0
    Information Bytes LSB1            = 0x0
    Information Bytes LSB0            = 0x0
    Additional Sense Length (0xE)        = 0x8
    Command Specific Information Bytes MSB1    = 0x0
    Command Specific Information Bytes MSB0    = 0x0
    Command Specific Information Bytes LSB1    = 0x0
    Command Specific Information Bytes LSB0    = 0x0
    Additional Sense Code            = 0x80
    Additional Sense Code Qualifier        = 0x2
    Field Replaceable Unit Code        = 0x0
    SKSV                    = 0x0
    C/D                    = 0x0
    BPV                    = 0x0
    Bit Pointer                = 0x0
    Field Pointer/Drive Error Code MSB    = 0x0
    Field Pointer/Drive Error Code LSB    = 0x0
    Command Descriptor Block (Hex Values, Cdb[0]...Cdb[15])   3b 2 1 0 0 c1 4 0 0 0 0 0 0 0 0 0

10/20/2009 14:19:50.734 [BackupThread] 1272: Pipe ID = 1 ftseq  243 length 262144
10/20/2009 14:20:26.954 [BackupThread] 1272: Pipe ID 1 Exceeded MAX_SEM_TIMEOUT_COUNT at ftseq 244
10/20/2009 14:20:26.954 [BackupThread] 1272: Pipe ID 1 wait count source 0 dest 0 write ahead wait count 0 ioctl error count 5 Thread bytes 63963136 Total bytes 63963136
10/20/2009 14:20:26.954 [BackupThread] 1272: Pipe ID 1 stopped at ftseq 244 with 16 full buffers offlining device, Device name \\.\Scsi4:0.0.0
10/20/2009 14:20:26.954 [OpenPTDeviceHandle] \\.\Scsi4:0.0.0 m_HandleOpenCount 2
10/20/2009 14:20:26.954 [ValidateOpenDevice]  DeviceInquiry succeeded; \\.\Scsi4:0.0.0
10/20/2009 14:20:26.954 [ClosePTDeviceHandle] \\.\Scsi4:0.0.0 m_HandleOpenCount 1
10/20/2009 14:20:26.969 [PipeCleanupTaskThread]  (4712) PTT_PipeShutdown

Set the data rate to a fixed speed and the connect option to "Point to Point only".

Last Updated on Friday, 11 December 2009 13:45

How to use a LUN larger than 2TB with Veritas Volume Manager (VXVM)

Monday, 09 November 2009 13:44 administrator

If you want to use LUN's larger than 2TB with VXVM on a LINUX host you need to use parted instead of fdiske to create partitions. fdisk is limited to 2TB partitions. The CDS feature is a no-go as well

We assume disk is sdu. Before VxVM can use the disk is must have a GPT label

# parted /dev/sdu mklabel gpt (the change is instant !!!!)

The default format for vxdisksetup is CDS format, we can't use so we revert to the old format:

# /etc/vx/bin/vxdisksetup -i sdu format=simple

From here it's business as usual :-D

Some links to Symantec support pages (will open a new browser window):

How to use a LUN greater than 2TB on Red Hat Enterprise Linux 4.0 Update 3 with Volume Manager 5.0

Initializing a LUN that is greater than 2TB creates usable space equal to, or less than 2TB with Volume Manager 5.0 on Red Hat Enterprise Linux 4 Update 3 or higher.

Last Updated on Monday, 09 November 2009 15:21

More Articles...