[Major] Host for device "ESL01_D01" not found.

[Normal] From: BSM@cellsrv01.in.com "Backupspec_win1"  Time: 3/21/2014 6:04:27 PM

 Backup session 2014/03/21-104 started.

[Major] From: BSM@cellsrv01.in.com "Backupspec_win1"  Time: 3/21/2014 6:04:32 PM

 Host for device ESL01_D01 not found.

[Major] From: BSM@cellsrv01.in.com "Backupspec_win1"  Time: 3/21/2014 6:04:32 PM

 Host for device ESL01_D02 not found.

[Major] From: BSM@cellsrv01.in.com "Backupspec_win1"  Time: 3/21/2014 6:04:32 PM

 Host for device ESL01_D03 not found.

[Normal] From: BSM@cellsrv01.in.com "Backupspec_win1"  Time: 3/21/2014 6:04:32 PM

 Backup Statistics:

         

  Session Queuing Time (hours)         0.00      

  -------------------------------------------    

  Completed Disk Agents ........          0        

  Failed Disk Agents ...........          7        

  Aborted Disk Agents ..........          0        

  -------------------------------------------    

  Disk Agents Total  ...........          7        

  ===========================================    

  Completed Media Agents .......          0        

  Failed Media Agents ..........          0        

  Aborted Media Agents .........          0        

  -------------------------------------------    

  Media Agents Total  ..........          0        

  ===========================================    

  Mbytes Total .................       0 MB      

  Used Media Total .............          0        

  Disk Agent Errors Total ......          0  

This error occurs when the backup device wasn't removed from the devices context following the media server deletion/migration to other cell.

In other words, the media server could have moved to another cell server or might have been decommissioned and by mistake the devices were not removed from the devices list.

Check the media server's existence, if available;

Check the cell server name, it is pointing to;

Mostly, if the orphan device entry is removed, this error will disappear.

[90:1004] Device address not found.

[Normal] From: BSM@cellsrv01.in.com "Backup_Spec_Win1"  Time: 4/16/2014 12:08:46 PM

 Backup session 2014/04/16-256 started.

[Normal] From: BMA@winsrv01.in.com "AUT01_D01"  Time: 4/16/2014 12:08:55 PM

 STARTING Media Agent "AUT01_D01"

[Normal] From: BMA@winsrv01.in.com "AUT01_D01"  Time: 4/16/2014 12:09:01 PM

 By: UMA@winsrv01.in.com@Changer0:7:0:1

 Loading medium from slot 8 to device Tape1:7:0:0C

[Warning] From: BMA@winsrv01.in.com "AUT01_D01"  Time: 4/16/2014 12:09:57 PM

 The device "AUT01_D01" could not be opened("Device could not be accessed")

[Normal] From: BMA@winsrv01.in.com "AUT01_D01"  Time: 4/16/2014 12:09:57 PM

 Starting the device path discovery process.

[Critical] From: BMA@winsrv01.in.com "AUT01_D01"  Time: 4/16/2014 12:10:00 PM

[90:1004]  Device address not found.

[Normal] From: BMA@winsrv01.in.com "AUT01_D01"  Time: 4/16/2014 12:10:00 PM

 Device path discovery process finished.

[Normal] From: BMA@winsrv01.in.com "AUT01_D01"  Time: 4/16/2014 12:10:00 PM

 By: UMA@winsrv01.in.com@Changer0:7:0:1

 Unloading medium to slot 8 from device Tape1:7:0:0C

[Normal] From: BMA@winsrv01.in.com "AUT01_D01"  Time: 4/16/2014 12:10:39 PM

 ABORTED Media Agent "AUT01_D01"

[Normal] From: BSM@cellsrv01.in.com "Backup_Spec_Win1"  Time: 4/16/2014 12:10:39 PM

 Backup Statistics:

         

  Session Queuing Time (hours)         0.00      

  -------------------------------------------    

  Completed Disk Agents ........          0        

  Failed Disk Agents ...........          4        

  Aborted Disk Agents ..........          0        

  -------------------------------------------    

  Disk Agents Total  ...........          4        

  ===========================================    

  Completed Media Agents .......          0        

  Failed Media Agents ..........          1        

  Aborted Media Agents .........          0        

  -------------------------------------------    

  Media Agents Total  ..........          1        

  ===========================================    

  Mbytes Total .................       0 MB      

  Used Media Total .............          0        

  Disk Agent Errors Total ......          0  

Troubleshooting steps as follows:

>> Logged into the media server and checked for devices claimed in Device Manager. Found the devices.

>> Ran devbra -dev to determine the SCSI address.

>> Found N/A for drive

C:\>devbra -dev

Exch    HP:1x8 G2 AUTOLDR  Path: "Changer0:0:0:1"  SN: "AABBCCDD1E"

        Description: CLAIMED:HP StorageWorks 1x8 Cartridge Autoloader

        Revision: 4.20  Flags: 0x0016  Slots: 8  Drives: 1

        Drive(s) SN:

                "ABCDEFGHIJ"

Tape    HP:Ultrium 3-SCSI  Path: "Tape0:0:0:0"  SN: "N/A"

        Description: CLAIMED:HP LTO3 Drive

        Revision: Q51W  Device type: lto [13]  Flags: 0x0011

>> Checked if the drive is locked by DP

[root@cellsrv01:/root]

# omnimm -show_locked_devs | grep AUT01_D01

[root@ cellsrv01:/root]

>> Stopped DP Inet from Services.msc and Ran LTT.

>> Got error message that "mma.exe" process is accessing the device. Killed the mma.exe process from the Task Manager.

>> rescanned the devices in LTT. Able to detect both autoloader and it's drive this time.

>> Ran devbra -dev, which got the SCSI address.

C:\>devbra -dev

Exch    HP:1x8 G2 AUTOLDR  Path: "Changer0:7:0:1"  SN: "AABBCCDD1E "

        Description: CLAIMED:HP StorageWorks 1x8 Cartridge Autoloader

        Revision: 4.20  Flags: 0x0016  Slots: 8  Drives: 1

        Drive(s) SN:

                "ABCDEFGHIJ "

Tape    HP:Ultrium 3-SCSI  Path: "Tape1:7:0:0C"  SN: "ABCDEFGHIJ "

        Description: CLAIMED:HP LTO3 Drive

        Revision: Q51W  Device type: lto [13]  Flags: 0x0011

>> Ran the backup successfully.

Cause :

The DP media agent was accessing the drive and didn't let any other process to send commands. After the hung process is killed, the drive was accessible for normal operations.

[61:2015] Timeout waiting for the devices to get free.

[Critical] From: BSM@cellsrv01.in.com "cellsrv01_IDB"  Time: 02/27/14 02:00:31

[61:2015]  Timeout waiting for the devices to get free.

The session will terminate.

Ø  It is very common in every backup environment to share the same device for different backups. This is an error message due to device contention issue.

Ø  The backup device selected in the backup specification is unavailable for the backup to start. It is in use by another process or by another backup/restore/copy sessions.

Ø   Check the device status using the lock name. (Check Here for the commands used to find a locked device). Wait for the device to be free.

Ø  The backup will be queued for global timeout seconds and will fail if no device is freed / allocated to the backup session.

Ø  The queuing time can be found at the end of backup session from backup statistics. Shown below

  

Backup Statistics:

          

                   Session Queuing Time (hours)         0.00        

                   -------------------------------------------      

                   Completed Disk Agents ........          5          

                   Failed Disk Agents ...........          0          

                   Aborted Disk Agents ..........          0          

                   -------------------------------------------      

                   Disk Agents Total  ...........          5          

                   =====================================     

                   Completed Media Agents .......          1          

                   Failed Media Agents ..........          0          

                   Aborted Media Agents .........          0          

                   -------------------------------------------      

                   Media Agents Total  ..........          1          

                   ===========================================      

                   Mbytes Total .................   17985 MB        

                   Used Media Total .............          1          

                   Disk Agent Errors Total ......          0    

IDB on Exclusive mode

Cannot open Internal Database in exclusive mode

Problem: Cannot open Internal Database in exclusive mode
Cannot backup internal database because another database check in progress 

Solution 1: Bring down the omni services by typing the below commands

/etc/init.d/omni stop in unix
<omni dirc >/bin> omnisv -stop
Check if there is any hung process
do " ps -ef | grep omni "
if there is any hung process kill the hung sessions

use Kill -9 <process ID >

if there is no hung session , Bring up the omni services up 

/etc/init.d/omni start
check the services are up & running or not 
if all the services are up & running 

go to /opt/omni/sbin 

omnidbutil -clear ( this command will kill the ghost sessions )
you will get the message " Done ! "

to check the IDB database check is still running or not , go to " /opt/omni/sbin "
use " omnidbcheck " command

Now you will not get the message " Database check is in Process "

Now re initiate the IDB backup .... This will run the IDB backup successfully

Solution 2: If still the issue is not resolve by solution 1

log on to the cell manager and go the below path
/var/opt/omni/tmp

you can see a file name " tmp_dbcheck.lk" , Remove that file by using the command

rm tmp_dbcheck.lk

Restart the DP Services , your issue will resolve after performing any of the solutions

Batch script for " IDB Maintenance & Resolving the Velocis Error " for Windows Servers…

Solution : copy the below script and paste in notepad and save it as " IDB_velosis.bat" file and just click on the file ... 

Your Velocis error and IDB maintenance will be completed in Just-a-click!

Note:- Modify the script according to where [Which Drive/Path] we installed the DataProtector 

Copy the text which in blue color 

echo # IDB Maintenance & Resolving the Velosis Error #

echo # Resolving the Velosis Error #
cd \

D:

cd Program files\omniback\bin

omnisv -status

omnisv -stop

taskkill /IM vbda.exe /F /T
taskkill /IM bsm.exe /F /T
taskkill /IM dbsm.exe /F /T
taskkill /IM vrda.exe /F /T
taskkill /IM uma.exe /F /T
taskkill /IM crs.exe /F /T
taskkill /IM rds.exe /F /T
taskkill /IM mmd.exe /F /T

cd \

cd Program Files\OmniBack\tmp

del CRS.pid
del dbcheck.cdb
del dbcheck.mmdb
del lic.ctx
del mmd.ctx

cd \

cd Program Files\OmniBack\db40\logfiles\syslog

del *.chg
del *.chk

cd \

cd Program Files\OmniBack\db40\datafiles\catalog

rename rdm.bil rdm.bil.old
rename rdm.chi rdm.chi.old

cd \

cd Program Files\OmniBack\bin

echo # Now Bring up the databae

omnisv -start

omnidbutil -clear

omnidbutil -free_locked_devs

echo # IDB Maintanence

omnidbutil -purge -messages 30 -force
omnidbutil -purge -sessions 30 -force
omnidbutil -purge -dcbf -force
omnidbutil -purge -filenames -force

exit

End of the script

Try the same in Testing environment prior to Production, All the best :)

To check/free locked devices in HP DP

HP DP Command to check/free a device

>> omnimm -show_locked_devs | grep <lock_name>
this command would list all the devices that are being used by the DP cell server. Medium, cartridge, devices

Ex:

Type:               Medium
Name/Id:   c75f:0034:0000:XXXX            //Media ID
Pid:                 23362                                       //Process Id that utilizes the media
Host:               cellsrv01.in.com                    //name of the cell manager (useful in MOM)
Label:             BM1000L3                              //Medium label

Type:         Device        
Name/Id:   ESLE1_D02                          //Drive name
Pid:           25754                                     //Process Id that utilizes the drive
Host:              cellsrv01.in.com                    //name of the cell manager, (useful in MOM)

Type:         Cartridge                     
Name/Id:   ESLE1                                  //Name of the library
Pid:           25836                                   //Process Id that utilises the drive
Host:         cellsrv01.in.com                  //name of the cell manager, (useful in MOM)
Location: 102                           

>> omnidbutil -show_locked_devs
The command would list all the devices, media, cartridge and slots that are in use by Data Protector cell manager.

>> omnidbutil -free_locked_devs <device_name>

Ex:

>> omnidbutil -free_locked_devs ESLE1_D02
Confirm the command by hitting 'Y': Y

After execution of this command, the drive will get released and can be used for any other purpose.

P.S: Omnidbutil / Omnimm commands can be used interchangeably to identify locked devices, to free locked devs, use omnidbutil.

HP DP - IDB Maintenance

DataProtector IDB Maintenance

Step by Step procedure for IDB Maintenance

White Font à Steps
Green Font à Commands Used
Blue Font à Command O/P

       Check for any running sessions and abort if required

       Ensure no backup is running and take the IDB backup using DP.

       Disable the backup schedules (/sbin/init.d/cron stop, omnitrig -stop)

       Shutdown the DP with following command

/opt/omni/sbin/omnisv stop

       Check the omni service (omnisv status)

       Close the DP GUI & abort all DBSm Sessions

       Purge DB with below commands.

a.    omnidb -strip

b.    omnidbutil -purge_failed_copies

c.     omnidbutil -purge -filenames -force

d.    omnidbutil -purge –dcbf

       (If the purge has not finished, but you need to run backups simply stop the purge with omnidbutil -purge_stop and use DP as normal. )

       Check for a mount point with sufficient space. Usually /var/adm/crash

       Create two directories MMDB and CDB in /var/adm/crash

mkdir /var/adm/crash/MMDB /var/adm/crash/CDB

       Start the DP with following command

/opt/omni/sbin/omnisv start

       Create a copy of the existing sessions, medias, position information etc. with the following command

/omni/db40 # /opt/omni/sbin/omnidbutil -writedb -mmdb /var/adm/crash/MMDB -cdb /var/adm/crash/CDB -no_detail

       Once the above command is successful without any errors the output will be as below:

/omni/db40 # /opt/omni/sbin/omnidbutil -writedb -mmdb /var/adm/crash/MMDB -cdb /var/adm/crash/CDB -no_detail

10/07/05 12:44:18 Exporting libraries ...

10/07/05 12:44:18 Exporting pools ...

10/07/05 12:44:18 Exporting devices ...

10/07/05 12:44:18 Exporting cartridges ...

10/07/05 12:44:18 Exporting compounds ...

10/07/05 12:44:18 Exporting media ...

10/07/05 12:44:18 Exporting sessions ...

10/07/05 12:44:19 Exporting objects and object versions ...

10/07/05 12:44:23 Exporting positions ...

Please make a copy of following Internal Database directories and

then press ENTER to return Internal Database to normal state:

"/var/opt/omni/db40/msg"

DONE!

       After successful completion of writedb. Move folders /var/opt/omni/db40/dcbf* folders to /var/opt/omni/db40/dcbf*.old. Note that there can be more than one folder ex. dcbf, dcbf1, dcbf2 etc.

       Compress the content of the moved folder. This is done just to create space and these folders (dcbf*.old) will be removed later once the maintenance is successful.

       Restart the DP services using the below commands

/opt/omni/sbin/omnisv stop

/opt/omni/sbin/omnisv start

       Perform DB Read (Reads and writes to the database) using omnidbutil.

/omni/db40 # /opt/omni/sbin/omnidbutil -readdb -mmdb /var/adm/crash/MMDB -cdb /var/adm/crash/CDB -no_detail

       The above command will output messages similar to below:

       /omni/db40 # /opt/omni/sbin/omnidbutil -readdb -mmdb /var/adm/crash/MMDB -cdb /var/adm/crash/CDB -no_detail

Database import will overwrite old database. All data will be lost!

Are you sure (y/n)?y

10/07/05 12:17:53 Importing libraries ...

10/07/05 12:17:53 Importing pools ...

10/07/05 12:17:53 Importing devices ...

10/07/05 12:17:53 Importing compounds ...

10/07/05 12:17:53 Importing cartridges ...

10/07/05 12:17:53 Importing media ...

10/07/05 12:17:53 Importing sessions ...

10/07/05 12:17:53 Importing objects and object versions ...

10/07/05 12:25:27 Importing positions ...

DONE!

       Run following command omnidbutil -fixmpos

       Once the above command is successful. Connect to DP through GUI and check the last run sessions.

       enable the backup schedule (/sbin/init.d/cron start, omnitrig -start)

       If everything looks fine. You can remove the dcbf*.old directories from /var/opt/omni/db40.

       Note that once the DB maintenance is complete. All directory/file details will be removed from the database. Hence forth need to import the medias to browse files for any restore operation.

[Critical] Duplicate BARCODE information from Media Agent

[Normal] From: MSM@cellservero1.in.com "MSL2024_L01"  Time: 22.2.2014 10:33:56

      Media session 2014/02/22-179 started.

[Normal] From: UMA@mediaserver01.in.com "MSL2024_L01"  Time: 22.2.2014 10:34:07

      STARTING Media Agent "MSL2024_L01"

[Critical] From: MSM@cellservero1.in.com "MSL2024_L01"  Time: 22.2.2014 10:34:10

Duplicate BARCODE information from Media Agent, Not updating the Repository

[Normal] From: UMA@mediaserver01.in.com "MSL2024_L01"  Time: 22.2.2014 10:34:09

      COMPLETED Media Agent "MSL2024_L01"

======================================================

                      23 cartridges out of 23 successfully scanned.

======================================================

>> The Library model is MSL2024, but there were only 23 slots scanned and the barcode scan failed.

>> Check the Repository, It shows only 23 slots, add the 24th slot.

>> Now barcode info has valid argument to scan.



Guest Post done by: Anbu