——————————-
Installing VRTSpbx…

Can’t locate CPI/common/CPI.pm in @INC (@INC contains: ./authentication/scripts ./perl/lib/5.8.8/sun4-solaris-thread-multi-64int ./perl/lib/5.8.8/sun4-solaris-thread-multi-64int ./perl/lib/5.8.8 ./perl/lib/site_perl/5.8.8/sun4-solaris-thread-multi-64int ./perl/lib/site_perl/5.8.8/sun4-solaris-thread-multi-64int ./perl/lib/site_perl/5.8.8 ./perl/lib/site_perl/5.8.8/sun4-solaris-thread-multi-64int ./perl/lib/site_perl/5.8.8 ./perl/lib/site_perl /opt/VRTSperl/lib/5.8.8/sun4-solaris-thread-multi-64int /opt/VRTSperl/lib/5.8.8 /opt/VRTSperl/lib/site_perl/5.8.8/sun4-solaris-thread-multi-64int /opt/VRTSperl/lib/site_perl/5.8.8 /opt/VRTSperl/lib/site_perl .) at ./installics line 7.

BEGIN failed–compilation aborted at ./installics line 7.

The ICS install for VRTSpbx was unsuccessful.

Quitting the NetBackup install.

Rerun /usr/openv/netbackup/bin/install_bp when the problem has been resolved.

Extract your products into seperate folders like:

/NBU/6.5.3/base
/NBU/6.5.3/clt
/NBU/6.5.3/bmr
/NBU/6.5.3/bbs
… etc

Then copy all of the files containing product names to base folder:

cd /NBU/6.5.3/clt ; cp -p *CLT* …/base
cd /NBU/6.5.3/bmr ; cp -p *BMR* …/base
cd /NBU/6.5.3/bbs ; cp -p *BBS* …/base
… etc
cd /NBU/6.5.3/base ; ls -al

drwxr-xr-x   2 root     root        2048 Oca 14 14:13 .
drwxr-xr-x   5 root     root         512 Ara 17 11:02 ..
-rwxr-xr-x   1 root     bin       103077 Eki 31 19:25 NB_update.install
-rw-r–r–   1 root     bin         6428 Eki 24 06:10 VrtsNB_6.5.3.README
-rwxr-xr-x   1 root     bin        15141 Eki 31 19:29 VrtsNB_6.5.3.postinstall
-rwxr-xr-x   1 root     bin        15141 Eki 31 19:29 VrtsNB_6.5.3.postuninstall
-rwxr-xr-x   1 root     bin        15141 Eki 31 19:30 VrtsNB_6.5.3.preinstall
-rwxr-xr-x   1 root     bin        15141 Eki 31 19:30 VrtsNB_6.5.3.preuninstall
-rw-r–r–   1 root     bin      114653598 Eki 31 18:31 VrtsNB_6.5.3.solaris.tar.Z
-rw-r–r–   1 root     bin         3623 Eki 24 06:10 VrtsNB_BBS_6.5.3.README
-rw-r–r–   1 root     bin      5363531 Eki 31 17:43 VrtsNB_BBS_6.5.3.hp_ux.tar.Z
-rw-r–r–   1 root     bin      8651777 Eki 31 17:43 VrtsNB_BBS_6.5.3.linux.tar.Z
-rw-r–r–   1 root     bin      5033770 Eki 31 17:43 VrtsNB_BBS_6.5.3.linuxR_x86.tar.Z
-rw-r–r–   1 root     bin      3728518 Eki 31 17:44 VrtsNB_BBS_6.5.3.linuxS_x86.tar.Z
-rwxr-xr-x   1 root     bin         1412 Eki 31 19:30 VrtsNB_BBS_6.5.3.postinstall
-rwxr-xr-x   1 root     bin         1412 Eki 31 19:30 VrtsNB_BBS_6.5.3.postuninstall
-rw-r–r–   1 root     bin      9484145 Eki 31 17:44 VrtsNB_BBS_6.5.3.rs6000.tar.Z
-rw-r–r–   1 root     bin      5386510 Eki 31 17:44 VrtsNB_BBS_6.5.3.solaris.tar.Z
-rw-r–r–   1 root     bin         3302 Eki 24 06:10 VrtsNB_BMR_6.5.3.README
-rw-r–r–   1 root     bin      20946548 Eki 31 17:45 VrtsNB_BMR_6.5.3.hp_ux.tar.Z
-rw-r–r–   1 root     bin      26335410 Eki 31 17:45 VrtsNB_BMR_6.5.3.linux.tar.Z
-rw-r–r–   1 root     bin      15978564 Eki 31 17:45 VrtsNB_BMR_6.5.3.linuxR_x86.tar.Z
-rw-r–r–   1 root     bin      12074491 Eki 31 17:45 VrtsNB_BMR_6.5.3.linuxS_x86.tar.Z
-rwxr-xr-x   1 root     bin         6974 Eki 31 19:30 VrtsNB_BMR_6.5.3.postinstall
-rwxr-xr-x   1 root     bin         6974 Eki 31 19:30 VrtsNB_BMR_6.5.3.preuninstall
-rw-r–r–   1 root     bin      36923891 Eki 31 17:46 VrtsNB_BMR_6.5.3.rs6000.tar.Z
-rw-r–r–   1 root     bin      17074340 Eki 31 17:46 VrtsNB_BMR_6.5.3.solaris.tar.Z
-rw-r–r–   1 root     bin      40860183 Eki 31 17:49 VrtsNB_CLT_6.5.3.ALPHA.tar.Z
-rw-r–r–   1 root     bin      102559135 Eki 31 17:49 VrtsNB_CLT_6.5.3.HP-UX-IA64.tar.Z
-rw-r–r–   1 root     bin      138644022 Eki 31 17:51 VrtsNB_CLT_6.5.3.HP9000-800.tar.Z
-rw-r–r–   1 root     bin      4282656 Eki 31 17:52 VrtsNB_CLT_6.5.3.INTEL.tar.Z
-rw-r–r–   1 root     bin      113658066 Eki 31 17:54 VrtsNB_CLT_6.5.3.Linux-IA64.tar.Z
-rw-r–r–   1 root     bin      201341180 Eki 31 17:52 VrtsNB_CLT_6.5.3.Linux.tar.Z
-rw-r–r–   1 root     bin      13461446 Eki 31 17:55 VrtsNB_CLT_6.5.3.MACINTOSH.tar.Z
-rw-r–r–   1 root     bin        10229 Eki 24 06:10 VrtsNB_CLT_6.5.3.README
-rw-r–r–   1 root     bin      73555146 Eki 31 17:55 VrtsNB_CLT_6.5.3.RS6000.tar.Z
-rw-r–r–   1 root     bin      26870567 Eki 31 17:56 VrtsNB_CLT_6.5.3.SGI.tar.Z
-rw-r–r–   1 root     bin      217553396 Eki 31 17:57 VrtsNB_CLT_6.5.3.Solaris.tar.Z
-rwxr-xr-x   1 root     bin        13349 Eki 31 19:31 VrtsNB_CLT_6.5.3.postinstall
-rwxr-xr-x   1 root     bin        13349 Eki 31 19:31 VrtsNB_CLT_6.5.3.postuninstall
-rwxr-xr-x   1 root     bin        13349 Eki 31 19:31 VrtsNB_CLT_6.5.3.preinstall

Now you can upgrade your all products at once:

root@veritas # /NBU/6.5.3/base/NB_update.install

There are 4 packs available in /NBU/653/NB_6.5.3.solaris:
(* denotes installed pack)

NB_6.5.3
NB_BBS_6.5.3
NB_BMR_6.5.3
NB_CLT_6.5.3

Enter pack name (or q) [q]: NB_6.5.3

Pack NB_6.5.3 requires pack NB_CLT_6.5.3 or a later.

Pack NB_6.5.3 requires the following pack levels(s) :
NB_CLT_6.5.3.

Pack NB_6.5.3 co-requires the following pack level(s) :
NB_BMR_6.5.3.

Pack NB_6.5.3 will not be installed at this time.

Installing required pack, NB_CLT_6.5.3, now.

Pack NB_CLT_6.5.3 co-requires the following pack level(s) :
NB_6.5.3 NB_BMR_6.5.3 NB_BBS_6.5.3.

Install pack NB_CLT_6.5.3 Wed Jan 14 2009 14:13:48 Rev. 1.6.4.14.4.2

Can not install pack when NetBackup daemons are running.
Do you want to kill all NetBackup daemons? (y/n) [n] y

…

Looking for Media Manager processes that need to be terminated.
…

Looking for VxDBMS processes that need to be terminated.
…

Pack install will continue.
…

Running inetconv to convert and import NetBackup inetd.conf records.
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
————————————————
Installation of pack NB_CLT_6.5.3 completed Wed Jan 14 2009 14:13:48 Rev. 1.6.4.14.4.2.
————————————————
Installing required pack, NB_6.5.3, now.

Pack NB_6.5.3 co-requires the following pack level(s) :
NB_BMR_6.5.3.

Install pack NB_6.5.3 Wed Jan 14 2009 14:13:48 Rev. 1.6.4.14.4.2
…

Upgrading NBDB:

/usr/openv/db/bin/nbdb_upgrade -dbn NBDB

Execution of tpext command succeeded.
…

————————————————
Installation of pack NB_6.5.3 completed Wed Jan  14 2009 14:13:48 Rev. 1.6.4.14.4.2.
————————————————
…

Installing required pack, NB_BMR_6.5.3, now.

Pack NB_BMR_6.5.3 co-requires the following pack level(s) :
NB_BBS_6.5.3.

Install pack NB_BMR_6.5.3 Wed Jan 14 2009 14:13:48 Rev. 1.6.4.14.4.2
…

Upgrading BMRDB:

/usr/openv/netbackup/bin/bmrsetupmaster -patch
Verifying the running version of BMRDB …
BMRDB version 6.5.0.0 verified.
Upgrading BMRDB (6.5.0.0) to (6.5.1.0) …
Upgrading BMRDB (6.5.1.0) to (6.5.2.0) …
Upgrading BMRDB (6.5.2.0) to (6.5.3.0) …
Re-verification of BMRDB at new version, 6.5.3.0
Verification succeeded.
Successfully upgraded BMRDB to version 6.5.3.0
Database validation successful.
[Info] V-127-66 Setting up BMR master server completed successfully.
————————————————
Installation of pack NB_BMR_6.5.3 completed Wed Jan 14 2009 14:13:48 Rev. 1.6.4.14.4.2.
————————————————
…

Installing required pack, NB_BBS_6.5.3, now.

Install pack NB_BBS_6.5.3 Wed Jan 14 2009 14:13:48 Rev. 1.6.4.14.4.2
…

Running: /usr/openv/netbackup/bin/bmrsetupboot -patch
————————————————
Installation of pack NB_BBS_6.5.3 completed Wed Jan 14 2009 14:13:48 Rev. 1.6.4.14.4.2.
————————————————
There are 4 packs available in /NBU/653/NB_6.5.3.solaris:
(* denotes installed pack)

NB_6.5.3 *
NB_BBS_6.5.3 *
NB_BMR_6.5.3 *
NB_CLT_6.5.3 *

Enter pack name (or q) [q]: q

There are stopped daemons.

Do you want to restart all NetBackup daemons? (y/n) [n] y
Starting VxDBMS database server…
Starting nbevtmgr…
Starting nbemm…
Starting nbrb…
Starting ltid…
Starting bprd…
Starting bpcompatd…
Starting nbjm…
Starting nbpem…
Starting nbstserv…
Starting nbrmms…
Starting nbkms…
Starting nbsl…
Starting bmrd…
Starting nbsvcmon…
Starting nbftclnt…
Starting bmrbd…
Exiting NB_update.install

Finally you can go to your Administration Console and check master server’s version.

RMAN> run {
1> ALLOCATE CHANNEL chtape TYPE ‘SBT_TAPE’;
2> set until time ’2008-11-05:14:30:00′;
3> SEND ‘NB_ORA_CLIENT=realdb_host,NB_ORA_POLICY=rman_realdb,NB_ORA_SERV=veritas,NB_ORA_SCHED=Default-Application-Backup’;
4> RESTORE CONTROLFILE;
5> RELEASE CHANNEL chtape;
6> }

executing command: SET until clause
released channel: chtape
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of set command at 01/06/2009 15:07:58
ORA-01861: literal does not match format string

This can be caused by your date format. Set your NLS date format accordingly and retry your restore procedure.
/home/oracle> export NLS_DATE_FORMAT=”YYYY-MM-DD:HH24:MI:SS”

RMAN> run {
1> ALLOCATE CHANNEL chtape TYPE ‘SBT_TAPE’;
2> set until time ’2009-01-05:14:30:00′;
3> SEND ‘NB_ORA_CLIENT=realdb_host,NB_ORA_POLICY=rman_realdb,NB_ORA_SERV=veritas,NB_ORA_SCHED=Default-Application-Backup’;
3> RESTORE CONTROLFILE;
4> RELEASE CHANNEL chtape;
5> }

allocated channel: chtape
channel chtape: sid=1014 devtype=SBT_TAPE
channel chtape: Veritas NetBackup for Oracle – Release 6.5 (2008052301)

executing command: SET until clause

You have a unix based netbackup master server and have an windows server with oracle that you want to backup through rman catalog backup, but you are unable to use the templates created by the “Backup, Archive and Restore” application on windows.

On your windows server, you can convert your templates to rman scripts using the following line…

c:\Program Files\Veritas\Netbackup\bin\bpdbsbora -backup -g Full_backup.cmd -t Full_backup.tpl

Now you can enter this script on unix side as a backup selection script…

There may be more than one cause for this problem, here is a solution for me.
You might have two seperate ip definitons on /etc/hosts file with the same hostname for your netbackup master server. e.g
172.6.2.10 veritas
192.168.14.10 veritas
You are connecting through 192.168.14.10 interface but in /etc/hosts file 172.6.2.10 comes first, so netbackup client doesnt recognize netbackup master server correctly.
So, correct this problem and it should run through…

on Solaris:
1. extract NB_6.5.3.solaris_314587.tar and NB_CLT_6.5.3_314595.tar into the same directory in “/NBU” for example
2. run NB_update.install and enter NB_CLT_6.5.3 as the package to be installed. It will install NB_6.5.3 automatically. Confirm stop/start of the services when asked.
/NBU/NB_update.install

There are 2 packs available in /NBU:
(* denotes installed pack)

NB_6.5.3
NB_CLT_6.5.3

Enter pack name (or q) [q]: NB_CLT_6.5.3

3. Your Netbackup installation is now upgraded to 6.5.3.

?
for help

s d
show contents of the tape drives

m s10 i1
move a media on slot 10(library slot number) to media access port 1(CAP on some libararies)

s s
Show contents of the library

Checklist
1. Consider the above picture as our environment.
2. Download and install Vmware Consolidated Backup Proxy.
3. Keep in mind that VCB will be our interface to virtual machines, they’re not directly backed up.
4. Have your SAN configuration set up, and Both NBU master server and Vmware server are at the same LUNs
5. If you’re using newest VCB versions VCB management port is 443, not 902
6. Have your NBU master server installed and configured correctly (Storage devices, Tape drives, robots etc)

Howto

1. Add new Virtual Machine Server:

Media and Device Management -> Credentials -> Virtual Machine Server -> Right Click -> New

2. Fill Vmware server credentials

Add Virtal Machine Server

3. Open NetBackup Management -> Host Properties -> Master Servers window and add a new Virtual Machine Proxy server on Virtual Machines tab. Keep in mind that on this example, VCB proxy and NBU master server are the same server.

Virtual Machine Proxy Servers

4. Under NetBackup Management -> Host Properties -> Client window, Open NBU master server Properties window and expand windows client tab and select client settings. Make sure Incrementals is set to Based on timestamp setting, and Use change journal in incrementals is unchecked.

Client Settings

5. Reboot NBU master server and after restart, make sure the settings are saved and correct.

6. Create a New Policy (Do not use wizard) and select FlashBackup-Windows as Policy Type.

7. Select Perform off-host Backup and Use Virtual Machine Proxy, select the proxy you entered previously.

New Policy

8. Create new schedules according to your needs.

New Schedule

9. Under Clients tab, click New and select your virtual machines from the Virtual Machines List to be backed up.

Clients

10. Click OK and close the window.

11. To test, right click the policy and select Manual Backup and see if anything goes wrong.

vmquery -m <cleaning tape #>

C:\>vmquery -m CLN007
======================================
media ID: CLN007
media type: 1/2″ cleaning tape 3 (25)
barcode: CLN107L3
media description: —
volume pool: None (0)
robot type: TLD – Tape Library DLT (8)
robot number: 0
robot slot: 4
robot control host: Netbackup
volume group: 00_000_TLD
vault name: —
vault sent date: —
vault return date: —
vault slot: —
vault session id: —
vault container id: -
created: 7/11/2008 6:29:48 PM
assigned: —
last mounted: 8/11/2008 8:20:22 AM
first mount: 7/11/2008 7:17:04 PM
expiration date: —
cleanings left: 27
======================================

Frequency of cleaning with cleaning tapes
With modern drives, cleaning is done only when drives say they need…
This is done via “Tape Alert” feature. You configure NetBackup so that the cleaning frequency is set to 0, and it will clean drives only when they request to be cleaned.

Keep in mind that, cleaning a drive too often can cause more harm than good. You should find a good frequency that works for you.

If you face an error like “daemon failed accepting connection 59”

This error can be caused by different things. But first of all, check that there are enough “cleanings remaining” on the cleaning tape used.

Cleaning Tapes from command line

Show the drive name to be cleaned

tpclean -L

Manually clean the drive:

tpclean -C <drive_name>

Add

VERBOSE = x

line to bp.conf, where x is the number to set how verbose the logs will be.

Where are Netbackup logs?

Under /usr/openv/netbackup/logs on Unix or <INSTALL DIRECTORY>\VERITAS\netbackup\logs on windows systems.

Where are tape drive errors?

/usr/openv/netbackup/db/media/errors on Unix or <INSTALL DIRECTORY>\VERITAS\NetBackup\db\media\errors on windows systems.

2. The partiton where netbackup is installed must not be 100% full, or netbackup will basicaly stop functioning.

3.If dns does not work and there are no records on /etc/hosts netbackup will again stop functioning and netbackup will need to restart to be able to work again.

4. Some commands for troubleshooting:

a. /usr/openv/netbackup/bin/bpclntcmd -hn client_name

Returns client_name’s ip address if netbackup can do a successful lookup.

b. /usr/openv/netbackup/bin/bpclntcmd -hn client_ip_address

Returns client’s address, if netbackup can do a successfull reverse dns lookup

c. /usr/openv/netbackup/bin/bpexpdate -m 00m4l3 -d 0

Allows you to expire a media when needed.

d.bpstulist

Will show you all drives and hosts connected to master server

e. /usr/openv/volmgr/bin/tpautoconf -a

Will scan all local device on media manager.

f. /usr/openv/volmgr/bin/vmoprcmd

Shows information about your media servers.

g. /usr/openv/netbackup/bin/admincmd/bpmedialist -rl 1

Shows info about media that’s available, full, expired or other.

h. /usr/openv/netbackup/bin/admincmd/bpmedia -unfreeze -m 06m03l3

Unfreezes a media.

i. /usr/openv/volmgr/bin/vmupdate -rt tld -rn 1 -full [-interactive] -use_barcode_rules

Inventory a robot.

j. /usr/openv/netbackup/bin/bpmedialist -rl 1

List which disks are expired, full or available. (-rl used for retention level. 1 means retention of 2 weeks)

k. /usr/openv/netbackup/bin/bpps -x

All running netbackup processes are listed

l. /usr/openv/netbackup/bin/goodies/available_media

All media and its states are listed. The script runs other commands and formats the outputs to a usable format.

m. /usr/openv/netbackup/bin/admincmd/bpdbjobs

Activity monitor.

n. bplabel -ev media_id_number -d <tape density> -p Pool_Name

Label a media with “media_id_number” in pool “Pool_Name”.

o. bpimmedia -mediaid 0m0687 -L

List images on a tape with media id 0m0687

p. vmdelete -m 000687

Delete a media from netbackup emm database

Checklist

1. Check that netbackup client is installed on the sql server.

2. Check operating system (which windows version?)

3. Check that there is enough disk space where you will be installing netbackup client.

4. Check that netbackup server can reach client, and the client can reach to netbackup server, by resolving their names and IP addresses.

Howto

First of all, you need to create a backup script on the client server (ms-sql server). Enter required paramaters (eg: database username/password) and select the databases to backup. Then save this as a file (do not select backup option, select save option) in the directory c:\Program Files\Veritas\NetBackup\DbExt\MsSql

This directory is important as netbackup will try execute backup scripts inside this directory.

On the Netbackup administration console:

1.Create a new policy, choose “MS-SQL” as the policy type and select policy storage unit and volume pool according to your needs.

Create a new policy

2. After “MS-SQL” is selected as policy type, a schedule named “Default-Application-Backup” schedule is added automaticaly.

Default-Application-Backup Schedule

3. Create a new schedule with policy type “Automatic Backup” and configure according to your needs.

Create a new Application Backup schedule

4. Your schedules will look like below.

MS-SQL Schedules

5. Add your sql server as a new client and select operating system if necessary

Add your client (Sql Server)

6. Add backup script from the client (Backup script recorded on sql server) as a new backup selection.

Add Backup script

7. Click OK and start a new Manual Backup to test your policy. Keep in mind that, every database will be backed up  using Default-Application-Backup schedule, everytime called by Application Backup schedule.

MS-SQL Backup Activity