Showing posts with label Server side. Show all posts
Showing posts with label Server side. Show all posts

Sunday, March 16, 2014

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 :)

Friday, March 7, 2014

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.

Sunday, February 23, 2014

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.


Saturday, February 22, 2014

HP DP Mount Requests 'Mount request for medium'

[Warning] From: BSM@cellserver01.in.com "Backup_spec_15"  Time: 2/13/2014 9:00:27 PM
 Medium "c02cbeed:aaaa:0001" in device "HP:Ultrium 2-SCSI_ Dev001"
 in the pool " Dev001_media" cannot be appended.
 Medium label is: "THU02a"

[Normal] From: BMA@Server01.in.com " HP:Ultrium 2-SCSI_ Dev001"  Time: 2/13/2014 9:00:40 PM
 Tape0:0:0:0
 Medium header verification completed, 0 errors found.

This is a Warning message that DP produces and it can continue with any other good tape if found in the media pool. If not, then the backup would pause with Mount request for medium with the message like below.

[Warning] From: BSM@cellserver01.in.com "HP:Ultrium 2-SCSI_Dev001"  Time: 2/13/2014 9:00:40 PM
    ___________________________________________________________________
    Mount request for medium:
        MediumId        : c02cbeed:aaaa:0001
        Label               : MON02a
        Location          :
        Device             : HP:Ultrium 2-SCSI_Dev001
        Host                : Server01.in.com
        Physical device : Tape0:0:0:0
    ___________________________________________________________________

[Normal] From: BSM@cellserver01.in.com "backup_spec_15"  Time: 2/13/2014 9:00:42 PM
 Starting the mount request notification script "/opt/omni/lbi/Mount.sh".

Firstly, check if the respective media pool is set to ‘Appendable’.

Secondly, copy the Medium label and go to the respective media pool. Find the media and it's status to be good.

 v  If the medium condition is good and DP gives out the error. Check the next step
 v  If the medium contains protected objects and has some space left over. Even though the medium has free space, it may either insufficient or otherwise the protected objects may be scattered within the media.

[OR]

  v  The media is expired but the status in ‘Fair’ or ‘Poor’ which DP may not use for backup. Check if you can reuse it by reformatting. If the media still shows ‘Poor’ condition, kindly do not use the medium. Either the backup would fail or data might not be recoverable.

To confirm the MR from DP cell server CLI

# omnistat –mount

SessionID          Type            Status             User
==============================================
2014/01/07-9     Backup   Mount Request   localadmin

# omnimnt -device ' HP:Ultrium 2-SCSI_Dev001' -session 2014/01/07-9
Mount request confirmation sent to the Session Manager.

Thursday, February 20, 2014

TSM Admin Tasks

This post would give an idea of the commands and tasks that a backup administrator would carry-on everyday from TSM server end.

Ø  q event * t=a begind=-1 endd=t
Ø  BACKUP DB type=full dev=<device_class_name> wait=yes
Ø  BACKUP DEVCONFIG
Ø  BACKUP VOLHISTORY
Ø  PREPARE source=dbbackup devclass=<device_class_name> wait=yes
Ø  DELETE VOLHISTORY todate=today-7 type=all
Ø  EXPIRE INVENTORY wait=yes duration=240
Ø  RECLAIM STGPOOL <stgpool_name> th=75 du=120
(Repeat this command for all the storage pools)
Ø  QUERY STGPOOL
Ø  QUERY MOUNT
Ø  QUERY SESSION
Ø  select count(*) as Scratch, library_name from libvolumes where status='Scratch' group by library_name
(To check for scratch volumes count in each library)
Ø  select source_name as source, destination_name as target,library_name as library, device from paths where online = 'NO'
(To check any offline paths)
Ø  QUERY DRIVE
Ø  QUERY ACTLOG s=error
Ø  QUERY ACTLOG s=failure
Ø  QUERY ACTLOG s="Server out of data storage space