Netbackup:: msi installer error 3

To resolve this issue, please try to do the following:

 1, Firstly, refer TECH59344, try to register the "scrrun.dll":

                      http://www.veritas.com/docs/000033272

      a. Open a Command Prompt by clicking on the Start button, and selecting Run, and typing "command" and pressing Enter.
      b. Change to the C:\Windows\System32 directory.
      c. Enter the following command: regsvr32 scrrun.dll and press Enter

      d.  Retry the installation of the NetBackup.

   2, If the step 1 cannot work, please try to install  "Windows Script 5.7 for Windows Server 2003" on this client, then retry NetBackup installation.

      You can download it from:

           http://www.microsoft.com/downloads/en/details.aspx?FamilyID=f00cb8c0-32e9-411d-a896-f2cd5ef21eb4&isplayLang=en&displaylang=en



      In one customer's case, the installation issue resolved with installing the "Windows Script 5.7 for Windows Server 2003".

What is the difference between FROZEN What is the difference between FROZEN and SUSPENDED volumes (tapes) in NetBackupand SUSPENDED volumes (tapes) in NetBackup

http://www.veritas.com/docs/000015799

A FROZEN volume is unavailable for future backups. A FROZEN volume never expires, even after the retention period ends for all backups on the media. The media ID is never deleted from the NetBackup media catalog, and it remains assigned to NetBackup.

Whereas SUSPENDED volumes cannot be used for backups until retention periods for all backups on the media have expired. At that time, NetBackup deletes the SUSPENDED volume from the NetBackup media catalog and unassigns it from NetBackup.
Note : Both SUSPENDED and FROZEN volumes (tapes) are available for restores.

HP Data Protector

Netbackup: perform a consistency check of the EMM and BMR databases.

http://www.veritas.com/docs/000006049

How to perform a consistency check of the NetBackup EMM and BMR databases using the command line or NetBackup NBDbAdmin(Windows) or dbadm(UNIX/Linux) utilities 

Description of Tape Alerts and code definitions

Article URL:http://www.veritas.com/docs/000005226


---------------------------------------------------------
A "tape alert" message is a critical, warning, or informational alert that occurs due to a tape drive or robotic library hardware event. These "tape alert" messages are stored on the tape drive or robotic library. Applications like NetBackup query the tape device or robotic library for these "tape alert" messages and display the "tape alerts" to the user. "Tape alert" messages are reported in the NetBackup bptm log. The tape alert technology detects and logs hardware and media errors.

It is important to remember that while NetBackup displays these "tape alerts," the alerts occur due to a tape drive or robotic library hardware event. Check the Event Viewer for any hardware related errors. Please contact the Original Equipment Manufacturer (OEM) for support.

The "errors" file may also contain specific Tape Alert information:

\Veritas\Netbackup\db\media\errors

TapeAlert is a standard for devices to report diagnostic messages to the controlling application. A "No TapeAlert Messages" response is a good thing. Here's the list of codes and definitions as it exists today.
(from the ANSI T10 Specifications):

tapealert_codes = {
0x01: 'Having problems reading (slowing down)',
0x02: 'Having problems writing (losing capacity)',
0x03: 'Uncorrectable read/write error',
0x04: 'Media Performance Degraded, Data Is At Risk',
0x05: 'Read Failure',
0x06: 'Write Failure',
0x07: 'Media has reached the end of its useful life',
0x08: 'Cartridge not data grade',
0x09: 'Cartridge write protected',
0x0A: 'Initiator is preventing media removal',
0x0B: 'Cleaning media found instead of data media',
0x0C: 'Cartridge contains data in an unsupported format',
0x0D: 'Recoverable mechanical cartridge failure (broken tape?)',
0x0E: 'Unrecoverable mechanical cartridge failure (broken tape?)',
0x0F: 'Failure of cartridge memory chip',

0x10: 'Forced eject of media',
0x11: 'Read only media loaded',
0x12: 'Tape directory corrupted on load',
0x13: 'Media nearing end of life',
0x14: 'Tape drive neads cleaning NOW',
0x15: 'Tape drive needs to be cleaned soon',
0x16: 'Cleaning cartridge used up',
0x17: 'Invalid cleaning cartidge used',
0x18: 'Retension requested',
0x19: 'Dual port interface failed',
0x1A: 'Cooling fan in drive has failed',
0x1B: 'Power supply failure in drive',
0x1C: 'Power consumption outside specified range',
0x1D: 'Preventative maintenance needed on drive',
0x1E: 'Hardware A: Tape drive has a problem not read/write related',
0x1F: 'Hardware B: Tape drive has a problem not read/write related',

0x20: 'Problem with SCSI interface between tape drive and initiator',
0x21: 'The current operation has failed. Eject and reload media',
0x22: 'Attempt to download new firmware failed',
0x23: 'Drive humidity outside operational range',
0x24: 'Drive temperature outside operational range',
0x25: 'Drive voltage outside operational range',
0x26: 'Failure of drive predicted soon',
0x27: 'Diagnostics required',

# 0x28 to 0x2E are obsolete, but some vendors still have them listed.

0x28: 'Loader Hardware A: Changer having problems communicating with tape drive',
0x29: 'Loader Stray Tape: Stray tape left in drive from prior error',
0x2A: 'Loader Hardware B: Autoloader mechanism has a fault',
0x2B: 'Loader Door: Loader door is open, please close it',

# 0x2F to 0x31 are reserved

0x32: 'Media statistics lost',
0x33: 'Tape directory invalid at unload (reread all to rebuild)',
0x34: 'Tape system area write failure',
0x35: 'Tape system area read failure',
0x36: 'Start of data not found',
0x37: 'Media could not be loaded/threaded',
0x38: 'Unrecoverable unload failed',
0x39: 'Automation interface failure',
0x3A: 'Firmware failure',

# 0x3B to 0x40 are reserved
} 
--------------------------------------------------------- 

netbackup :: восстановление протухших бэкапных образов

Step by step guide to importing a tape using the NetBackup: https://support.symantec.com/en_US/article.TECH72429.html

Veritas NetBackupTM 6.5: Designing and Implementing Backups Using Storage Lifecycle Policies

2.3
 Storage Lifecycle Policies vs. Disk Staging
...
2) Unlike tape devices, disks have no minimum streaming speed, so the write speed of a disk
device is not reduced if the incoming data fails to arrive at a high enough rate, so they are
better suited than tape to backups coming from ‘slow’ sources.

The main disadvantage of disk is that its relatively high cost compared to tape means that
disk space is always limited and backups written to disk can only have a short retention period.
This is fine for meeting the high RPO/RTO requirements for a critical application service level
but does not lend itself to the long retention periods often required for archival backups of such
mission critical applications (i.e., periodic backups that are retained as “point in time” records of the application long after they have ceased to have value as a recovery source in the event of data
loss).
 

netbackup timezone

проверка:

backup2:~ # strings /usr/openv/java/jre/lib/zi/ZoneInfoMappings | head -2
javazm
tzdata2013b

для обновления нужен Java SE TZUpdater Downloads

распаковать TZUpdater в /tmp

backup2:/tmp # cd /usr/openv/java/jre/bin

backup2:/usr/openv/java/jre/bin # ./java -jar /tmp/tzupdater-2.0.0-2015a/tzupdater.jar -u -v
java.home: /usr/openv/java/jre
java.vendor: Oracle Corporation
java.version: 1.7.0_25
JRE tzdata version: tzdata2013b
tzupdater tool would update with tzdata version: tzdata2015a
Extracting files... done.
Renaming /usr/openv/java/jre/lib/zi to /usr/openv/java/jre/lib/zi.tzdata2013b
Renaming /usr/openv/java/jre/lib/zi.tzdata2015a to /usr/openv/java/jre/lib/zi
Validating for : tzdata2015a
done.
JRE updated to version : tzdata2015a

проверка:
backup2:/usr/openv/java/jre/bin # ./java -jar /tmp/tzupdater-2.0.0-2015a/tzupdater.jar -V
tzupdater version 2.0.0-b03
JRE tzdata version: tzdata2015a
tzupdater tool would update with tzdata version: tzdata2015a


PS
Oracle как обычно желает всем добра:
Support customers can download a TZUpdater tool for older versions through My Oracle Support. See Note 1412103.2 

PPS
что б два раза не вставать:

Adjusting the time zone in the NetBackup-Java console

Use the following procedure in the NetBackup-Java console to adjust the time zone or to use daylight savings time.

To adjust the time zone in the NetBackup-Java console

1. In the NetBackup Administration Console, or in the Backup, Archive, and Restore client dialog box, select File > Adjust Application Time Zone.
2. Select the Standard tab.
3. Clear the Use custom time zone check box.
4. Select the time zone.
5. For daylight savings time, select Use daylight savings time.
6. To have administrative capabilities and to apply the settings to the current session and all future sessions, select Save as default time zone.
7. Click OK.

netbackup как найти jobid из cli

bpimagelist -media -client Client -policy  Policy -sl  Full_backup -st FULL -hoursago 1 -U

PS
DOCUMENTATION: What are the different fields in "bpimagelist -l" output?

Netbackup: Get Job ID by Backup ID и еще пара мелочей

найти job ID по backup ID
/usr/openv/netbackup/bin/admincmd/bpimagelist -l -backupid  dc2.domain.local_1388973304 | awk {'print $45'}
 145848

поиск backup ID и номера копии:
/usr/openv/netbackup/bin/admincmd/bpimmedia -client webdev.domain -d 1/20/2014 -e 1/25/2014 -U | less

сделать копию 2 "primary copy"
/usr/openv/netbackup/bin/admincmd/bpduplicate -npc 2 -backupid webdev.domain_1361650355

Netbackup: Status code 230

Job мрет сразу после запуска с кодом 230,  в поле client пишет *NULL*.

На win машинах с кириллицей в имени nbclient затягивает в "Client Name" имя русские буковки из имени хоста и ему дурнеет. Править на обоих сторонах.

Netbackup: Ways to change expiration date (retention levels) of media and backup IDs

Дока

/usr/openv/netbackup/bin/admincmd/bpexpdate -recalculate -backupid  YYYY_098843420 -d mm/dd/yy

NBU status: 2074, EMM status: Disk volume is down

Упал, отжался, поднялся. В задачах:  "NBU status: 2074, EMM status: Disk volume is down"

# ./nbdevquery -listdp -stype BasicDisk
...
V6.5.5 PromiseRAID0 1 3536.56 3536.56 1 95 40 -1 backup1

# ./nbdevconfig -changestate -stype BasicDisk -dp PromiseRAID0 -state UP
successfully changed the state of disk pool


тыц

Netbackup: How to setup cleaning tapes

http://www.symantec.com/business/support/index?page=content&id=TECH164472


Admin Console -> Device Management > Expand Devices > Robots > Inventory Robot > Update volume > Advanced Options > Barcode Rules Tab

220: database system error

При изменении политики ловим  "STATUS CODE 220: database system error"
т.к. настройки не меняли и с  интерфейсами не баловались, пропускаем рекомендованную проверку конфигурации и сразу пинаем emm сервер


/usr/openv/netbackup/bin/admincmd/nbemmcmd -listhosts


и получаем server down в ответе.


/usr/openv/db/bin/nbdb_admin -start


ЗЫ
Как бы лежащему EMM соответствует STATUS CODE 93, но в этом месте (Policies) не судьба.




пошагое руководство по лечению status code 220


STATUS CODE 93: "Database server is down"

veritas netbackup и отрыжка aix

Warning FREEZING media id 088AAI, it contains MTF1-format data and cannot be used for backups
Warning FREEZING media id 180AAI, it contains ANSI-format data and cannot be used for backups


These are usually tapes written outside of NetBackup that have found their way into the library. By default, NetBackup will only write to a blank media or other NetBackup media. Other media types (DBR, TAR, CPIO, ANSI, MTF1 and recycled Backup Exec BE-MTF1 media) will be frozen as a safety measure. This behavior can be changed with the following procedure:

UNIX
To allow NetBackup to overwrite foreign media, add the following to /usr/openv/netbackup/bp.conf for the media server in question:


ALLOW_MEDIA_OVERWRITE = DBR 
ALLOW_MEDIA_OVERWRITE = TAR
ALLOW_MEDIA_OVERWRITE = CPIO
ALLOW_MEDIA_OVERWRITE = ANSI ALLOW_MEDIA_OVERWRITE = MTF1
ALLOW_MEDIA_OVERWRITE = BE-MTF1


Stop and restart the NetBackup daemons for the changes to take effect
 


PS
и заодно уже: 


Warning FREEZING media id 160AAI, it contains NetBackup database backup data and cannot be used for backups
Warning FREEZING media id 190AAI, it contains NetBackup database backup data and cannot be used for backups
 
How to reuse or recycle unnecessary NetBackup database catalog tapes for normal backups with NetBackup 4.5 or later 

Step 2. Unassign the tapes you wish to re-use:

Example:
# /usr/openv/volmgr/bin/vmquery -deassignbyid 000101 1 0x1

Step 3. Overwrite the tape label:

NOTE: This will effectively erase any previous information on the tape.

Example for robotic volume:
# /usr/openv/netbackup/bin/admincmd/bplabel -m 000101 -d dlt -o -p NetBackup
 

установка(апгрейд) netbackup 6.5 на Debian 5.0

Сообщение:

A failure was detected running cp_to_client Linux RedHat2.6.
Rerun /usr/openv/netbackup/bin/install_bp when the problem has been resolved.

означает, что нужно прибить поззависший процесс: "/usr/openv/netbackup/bin/nbftclnt"

и перезапустить "/usr/openv/netbackup/bin/install_bp"

ЗЫ
ubuntu/debian оффициально не поддерживаются.

NetBackup Client 6.0. linux

Необходимая для клиента библиотечка  libstdc++ (хочет libstdc++-libc6.2-2.so.3) переместилась в пакет lsb-build-base3 и сменила путь на  /usr/lib/lsb3/libstdc++.so

при апгрейде старой системы автоматом не устанавливается.
Старый пакет libstdc++libc6 чудным образом превратился в lib64stdc++6 - это для i386 платформы.

Veritas vs Debian 5.0.1

Обновление софта - источник неиисякаемого геморроя опыта.

backup:/tmp# /etc/init.d/netbackup stop
stopping the NetBackup Service Monitor
tail: cannot open `+2' for reading: No such file or directory
tail: cannot open `+2' for reading: No such file or directory
.......много много строк.......
tail: cannot open `+2' for reading: No such file or directory
tail: cannot open `+2' for reading: No such file or directory
.......
stopping the NetBackup Media Manager
tail: cannot open `+2' for reading: No such file or directory
бла, бла, бла, но срет поменьше чем сервис монитор.

При запуске ругается аналогично, трудовую дейтельность симулирует.

причина: неуловимо изменились некоторые commandline тулзы

лекарство: export _POSIX2_VERSION=199209

хоть убейте, не понимаю, почему помогло


ЗЫ
Дополнение по клиентам веритаса на той же оси, создать линку в /usr/openv/lib
ln -s /usr/lib/libstdc++.so.6.0.8 libstdc++-libc6.2-2.so.3

для 32 битной оси или

ln -s /usr/lib32/libstdc++.so.6 libstdc++-libc6.2-2.so.3

для 64 битной

ln -sf /emul/ia32-linux/usr/lib/libstdc++.so.6 libstdc++-libc6.2-2.so.3

иначе будет притворяться мертвым

Установка Veritas NetBackup client на Debian r4.0 amd64

Вводная:
netbackup master и media server установлены на одном физическом сервере (32-bit, Debian)
Клиента ставим на Debian AMD64.

1. Установить ssh public ключ с сервера netbackup на клиента (ssh-copy-id).
2. На клиенте установить xinetd или inetd.
3. Клиентское ПО веритаса установил с administration console, в политиках ОС клиента указывать Redhat 2.4; Policy -> yourpolicy -> Clients -> Install UNIX Client Software в контекстном меню.
4. При запуске /usr/openv/netbackup/bin/bpcd будет сообщение "error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory"
Сама библиотека libstdc++ в системе есть, но 64-bit.
5. Устанавливаем пакет 32-битных библиотек ia32-libs, extra packages втягивает пакеты lib32asound2 lib32gcc1 lib32ncurses5 lib32stdc++6 libasound2. Теоретически должно хватить lib32stdc++6, не проверял.
6. Клиентская часть запускается без ошибок, со стороны сервера в Host Properties -> Clients видим "Connection requested by invalid server. Check to make sure that the configuration of 192.168.1.25 is set to allow access to server backup.domain (Status 46)"
7. На стороне клиента в /etc/hosts вносим строку "192.168.1.33 backup.domain backup"

Теперь все работает