Data Protector - Passion for Data Protection

data-protector.org

No available connections on gateway for StoreOnce Software Store

Posted on by

When using the StoreOnce Software Store in Data Protector for jobs an error might be displayed: There are no available connections on gateway. This can occur when there are locked devices in the media managemt database of Data Protector. Normally the devices are released automatically or when the Data Protector Services are restarted. This rarley warning can be solved using the command omnidbutil -free_locked_devs.

Changed syntax for omnib2dinfo

Posted on by

omnib2dinfo: With the lastest released patches for DP 7.01 from 2013/04/09 there was a change in the syntax for the command omib2dinfo. In previous versions it was required to provide parameters like device type and host name to retrieve information from the B2D device, no matter if a software store or StoreOnce system was queried. For the new version of omnib2dinfo a logical device name can be provided with the command. With the change in place the command now can be executed on cell server instead of on client with installed media agent (cell server or client with connected StoreOnce system or software store).

New syntax:

omnib2dinfo -help | -h
omnib2dinfo -version | -v
omnib2dinfo -store_info -b2ddevice libraryname
omnib2dinfo -list_stores -b2ddevice libraryname
omnib2dinfo -list_objects -b2ddevice libraryname
omnib2dinfo -get_server_properties -b2ddevice libraryname

Old syntax:

omnib2dinfo -help | -h
omnib2dinfo -version | -v
omnib2dinfo -list_stores -type=ObjectStore | StoreOnceSoftware (OS | SOS)
                         -host=hostname
                         [-port=portNumber]
                         [-name=storeName]
                         [-client=clientName]
omnib2dinfo -list_objects -type=ObjectStore | StoreOnceSoftware (OS | SOS)
                          -host=hostname
                          [-port=portNumber]
                          -name=storeName
                          [-client=clientName]
omnib2dinfo -get_server_properties -type=ObjectStore | StoreOnceSoftware (OS | SOS)
                                   -host=hostname
                                   [-port=portNumber]
                                   [-client=clientName]

VMware backup done over NBD instead of SAN

Posted on by 3 Comments

Problem: The backup of some virtual machines is done using transport mode NBD instead of SAN, even if it is configured for the virtual machine or a vApp container. There might be other virtual machines on the same SAN disk, which are able to do the backup over SAN. The cause of the problem is that in previous sessions the VMware SAN lock was not released, hence new backups were not able to use the transport mode SAN and switched to NBD. If NBD mode is available only and VMware does not unlock the lock, the complete backup of the virtual machine will fail.

The message you might see in Data Protector: Virtual Machine ‘Server_a.demo.local’: Backup disk scsi0:0 using transport method NBD

Solution: When no backup of virtual machines is running check the VE-Agent host and search e.g. in c:\windows\temp\vmware-SYSTEM for folders including the machine name. Listing the content of the folder will display a lock file. It is recommended to delete the content of the complete folder. After restarting the backup of a involved machine you can see that SAN transport mode is used again. In some cases you might Need to modify the permissions for the folders to allow the removal.