server name not found in the NetBackup configuration

1. You were trying to expire a media from emm database:

bpexpdate -m media_id -d 0

Solution: Try to add -host media_server_hostname to end of the command

bpexpdate -m media_id -d 0 -host media_server

Please add your knowledge about this error…

Thanks.

Application connection failed for servername\. Please select a different SQL server host and instance, or press ‘cancel’ to exit the NetBackup for SQL Server Graphical User Interface.

According to this page, this error is caused by windows 2008′s “User Account Control”. You need to run”Netbackup Ms-Sql client” with “Run As Administrator” privilege.

Right click “Netbackup Ms-Sql client” and select “Run as Administrator” and “Apply”. Try to connect to ms-sql server again and you should be able to see databases now…

“All compatible drive paths are down, but media is available”

Try the following:

1. Go to the Device Monitor
2. Right click on any drive that is DOWN
3. Select Up Drive to up the drive
4. Wait 30 seconds and refresh this page if not already refreshed. You should be able to see the drive at UP state and you can start your backups again.

Since it won’t have any media id, you will not be able to see it on “netbackup administration console” and won’t be able to eject the tape out of library.

Instead of manually removing the tape from the library, you can use “robtest” to eject the tape. Follow these steps:You need to know which slot is tape inserted in the library. In this example tape is inserted on the slot 10

1. Start robtest, and choose you tape library, here TLD is selected.

/usr/openv/volmgr/bin/robtest
Configured robots with local control supporting test utilities:
TLD(0)    robotic-path = /dev/sg1

Robot Selection
———————
1) TLD 0
2) None/quit
Enter Choice: 1

Robot selected: TLD(0)   robotic-path = /dev/sg1
Opening /dev/sg1
MODE_SENSE complete

…..

Enter tld commands

2. Move your media from library slot 10 to media access port 1

m s10 i1

Initiating MOVE_MEDIUM from address 1009 to 10
MOVE_MEDIUM complete
Quit

3. Your tape is now on media access port slot 1, and can be removed easily.

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

[Tue Nov 25 23:32:36 2008] [error] [client 106.78.1.61] ModSecurity: Access denied with code 400 (phase 2). Match of “rx ^OPTIONS$” against “REQUEST_METHOD” required. [file "/optional_rules/modsecurity_protocol_anomalies.conf"] [line "41"] [id "960015"] [msg "Request Missing an Accept Header"] [severity "CRITICAL"] [tag "PROTOCOL_VIOLATION/MISSING_HEADER"] [hostname "www.netbackuphowto.com"] [uri "/ads.php"] [unique_id "oAIMD06rogtjw4jt"]
You need to add the following lines to your httpd.conf (or under your virtualhost directives)

<ifModule mod_security2.c>
SecRuleRemoveById 960015
</ifModule>

You can of course add more SecRuleRemoveById lines accourding to your needs.

Attention: This setting works site-wide…