[90:54] Cannot unload medium, target slot (255) appears to be occupied

[Warning] From: BMA@server01.na.com "ESLE01_D1"  Time: 2/9/2014 1:13:44 PM
[90:54]   /dev/nst1
Cannot open device (Unit not ready.)

[Major] From: BMA@server01.na.com "ESLE01_D1"  Time: 2/9/2014 1:13:55 PM
[90:114]   By: UMA@cellserver01.na.com@/dev/autoch3
Cannot unload medium, target slot (255) appears to be occupied

> The above error is due to DP couldn't unload the media from where it was actually loaded to the drive.

> Move the tape manually from the drive using UMA
/dev/autoch3> move D3 S13

> Then retry the backup, which should be successful/the error will not repeat.

[Critical] [12:1051] Client security violation. Access denied.

Error:

[Warning] From: BSM@cellserver1.eu.pg.com "backup_spec_01"  Time: 1/28/2014 12:30:57 PM

            Cannot get the list of filesystems on host "winclient02.na.pg.com".

            Backup of this host will be retried at end of session.

[Critical] From: INET@winclient02.na.pg.com ""  Time: 1/28/2014 12:31:08 PM

[12:1051] Client security violation. Access denied.

[Normal] From: BSM@cellserver1.eu.pg.com "backup_spec_01"  Time: 1/28/2014 12:31:20 PM

Solution:

> Manually, edit the hosts file located under the path:

C:\WINNT\system32\drivers\etc\                  - Windows 2003

C:\Windows\system32\drivers\etc\                 - Later versions

Hosts File would look like the below, Add an entry in the file and save it. The client hosts file should contain the cell server/media server name/IP. This would let the BSM to start/end the DAs on the client machine with ease.

127.0.0.1           localhost

#178.11.4.38     abchpdp.ap.pg.com          abchpdp

#188.10.4.43     winclient01.eu.pg.com      winclient01

#199.19.4.24     winclient02.na.pg.com      winclient02

You may have to check the below hosts file for DP
/etc/opt/omni/client/allow_hosts

Have a Great Week!

Tip of the Day!

Hi there,

Good Morning!

Tip of the day is related to Data Protector (Session abort)

Scenario: If you happen to abort a backup session that was already started and running, do not abort the session directly. (Assuming the backup is copied to tape library.)

Follow the steps below:

> Cancel all the devices that are running
> Then abort the session (either from CLI/GUI)

After the media agents are aborted, you will see the message like below:

[Normal] From: BSM@server01.fp.sa.com "backup_spec01"  Time: 1/31/2014 10:28:03 PM
Device canceled by user dpuser1@mgmt01.fp.sa.com

[Normal] From: BMA@server01.fp.sa.com "ESL01_D01"  Time: 1/31/2014 10:29:11 PM
ABORTED Media Agent "ESL01_D01"

Reason:

Aborting the session directly would not allow the media agents to a clean exit, which might end in damaging the media headers, chances are there for the media to get stuck in drive, media might be marked as poor.

It is always wise to abort the media agents and then your session.

Have a Great day!

Netbackup - media write error(84)

2014/01/17 3:56:42 - requesting resource Any
2014/01/17 3:56:42 - requesting resource ServerA01.NBU_CLIENT.MAXJOBS.ServerA01
2014/01/17 3:56:42 - requesting resource ServerA01.NBU_POLICY.MAXJOBS.ServerA01
2014/01/17 3:56:42 - awaiting resource ServerA01.NBU_CLIENT.MAXJOBS.ServerA01 - will retry logical later
2014/01/17 4:03:08 - granted resource ServerA01.NBU_CLIENT.MAXJOBS.ServerA01
2014/01/17 4:03:08 - granted resource ServerA01.NBU_POLICY.MAXJOBS.ServerA01
2014/01/17 4:03:08 - granted resource THU02A
2014/01/17 4:03:08 - granted resource HP.ULTRIUM3-SCSI.000
2014/01/17 4:03:08 - granted resource ServerA01-hcart3
2014/01/17 4:03:08 - started process bpbrm (8128)
2014/01/17 4:03:08 - connecting
2014/01/17 4:03:08 - connected; connect time: 00:00:00
2014/01/17 4:03:11 - mounted
2014/01/17 4:03:11 - positioning THU02A to file 2
2014/01/17 4:03:13 - positioned THU02A; position time: 00:00:02
2014/01/17 4:03:13 - begin writing
2014/01/17 4:08:50 - Warning bpbrm(pid=8128) from client ServerA01: WRN - can't open file: C:\COREUTIL\Altiris\eXpress\NS Client\Tasks\AeXTaskSchedulerLock\taskSchedulerLock.tmp (WIN32 32: Unknown error)
2014/01/17 4:22:40 - Error bpbrm(pid=8128) from client ServerA01: ERR - failure reading file: C:\osit\tmp\ps_mon.dbg (WIN32 13: Unknown error)
2014/01/17 4:26:07 - Error bpbrm(pid=8128) from client ServerA01: ERR - failure reading file: C:\Program Files\AccessData\Agent\s.bin (WIN32 32: Unknown error)
2014/01/17 4:43:54 - Warning bpbrm(pid=8128) from client ServerA01: WRN - Removable Storage Management: unable to export database (WIN32 -2147221164: Unknown error)
2014/01/17 8:15:11 - Error bptm(pid=11988) cannot write image to media id THU02A, drive index 0, The device is not ready.
2014/01/17 8:15:11 - Error bpbrm(pid=8128) from client ServerA01: ERR - bpbkar exiting because backup is aborting
2014/01/17 8:15:14 - end writing; write time: 04:12:01
media write error(84)



The media got ejected from the drive following the error message.


Solution:

> Cleaned the drive using cleaning tape.
> Inserted new tape and formatted.
> Rerun the backup, which was successful then.

Hope this helps!

Backup status in TSM

Full syntax:
query event <domain_name> <schedule_name> type=client begindate=mm/dd/yyyy begintime=00:00 enddate=mm/dd/yyyy endtime=hh:mm exceptionsonly=yes <format=detailed>

These commands needs to be run from the TSM server to check the pervious day's missed/failed backups of BA-client/admin schedules. Below is the short form of the same:

Short form:
q event * * begind=-1 endd=t ex=yes

Next we going to check the status of administrative schedules such as DB backup, reclamation.. etc

Full syntax:
query event <schedule_name> type=administrative begindate=mm/dd/yyyy begintime=00:00 enddate=mm/dd/yyyy endtime=hh:mm exceptionsonly=yes <format=detailed>

Short form:
q event * t=a begind=-1 endd=t ex=yes