You should be able to refresh and update the information using the DP GUI, just open the "drop down buttom" where the SCSI path resides and DP will display the SCSI path that the serial has. Dont forget to apply the settings.
The other thing you can do is to use:
omnidownload -list_devices -detail >devs.txt
omnidownload -list_libraries -detail >libs.txt
Make necesary changes and then use "omniupload"
Regards,
But how do I change the SCSI ADDRESS ? There are several drives using the same path.
Exemple:
In MSL 2024, the client BHZ-XXX-APP1 use address Tape:0:0:0:0C
In MSL4048, the same client BHZ-XXX-APP1 use too address TAPE:0:0:0:0C and other client use the same address.
When a drive is using the path 0:0:0:0C and another backup starts (in another drive with same address), I have a conflict. I need to change this SCSI ADDRESS.
In this picture, how can I change this address Tape2:0:1:0C to another?
There is no way there, maybe try updating the library serial and SCSI path first, then it might let you if not you'll have to go with omnidownload and omniupload see the CLI guide.
SCSI address change every reboot maybe a reboot can fix this, if not paste the devbra output here.
devbra -dev
What is the reason for this use the same SCSI ADDRESS to multiple drives? I swear I do not understand.
I am not sure on what could cause this problem, if you run devbra do you also see duplicate SCSI paths?
Hi,
Need some help.
We have 2 nodes cluster, yesterday one of the node power off (node A) and the data protector job switch over to node B to run. Later we bring up the node A server and swtiched back user connection back.
The data proctector jobs in Node B is not running properly with error. At first I noticed the bma process hang. I manually killed the bma process but now having error "Cannot open exchanger control device (IPC Invalid Packet Size)" when backup the file system.
Not much research on this error. Any help really appreaciated.
I'm using data protector 6 and running backup on HP UX PA-RISC 11.23
------------------------------------------------------------------------
From: BMA@-i "NodeB-drv2" Time: 5/26/2015 2:52:40 PM
STARTING Media Agent "NodeB-drv2"
[Critical]
From: BMA@-i "NodeB-drv2" Time: 5/26/2015 2:53:09 PM
[90:59] san1.com.my:Changer0:1:2:0
Cannot open exchanger control device (IPC Invalid Packet Size)
From: BMA@-i "NodeB-drv2" Time: 5/26/2015 2:53:09 PM
ABORTED Media Agent "NodeB-drv2"
From: BSM@san1.com.my "FS-NodeB" Time: 5/26/2015 2:53:46 PM
None of the Disk Agents completed successfully.
Session has failed.
------------------------------------------------------------------------
Thanks,
Kelvin
I get this error whenever i try to backup idb:
[Normal] From: OB2BAR_POSTGRES_BAR@XXX "DPIDB" Time: 5/26/2015 10:36:35 AM
Check of the Internal Database consistency succeeded
[Critical] From: OB2BAR_POSTGRES_BAR@XXX "DPIDB" Time: 5/26/2015 10:36:35 AM
An error occurred during file search
I checked the database with "omnidbcheck -extended" and everything is fine. Also, i restarted dp services.
have you tried omnidownload and omniupload?
"omnidownload -device LogicalDevice -file FileName" writes out the DeviceSettings to Textfile.
That can then be edited to your desires. To update config in DP use
"omniupload -modify_device LogicalDevice -file FileName"
The Error usually indicates troubles with the VSS Writers.
Make sure they are all in stable state and show no errors (vssadmin list writers) and restry the job if that is the case.
If the Exchange Writer is in error state you have to check ApplicationLog for clues, in worst case Exchange or the whole Server has to be rebooted to fix VSS.
Could anyone help me?
I really appreciate!
Thanks a lot!
I have noticed this artical, but my DP version is 6.21 with some patches. And in the artical you provide the keepAlive option is only available in DP 7.03 and later version.
Hey there,
we have some trouble with an windows backup on our DP 9.02 environment.
Backup device is an VTL.
The Server we want to backup is an Winodws 2012 Server. The size of the files should be ~ 2 TB, so the backup need some time. For example:
Start: 03:00:07
Error: 13:33:03
Until the error everything looks fine. But then:
Major] From: BMA@backup_gateway.test.com "VTL_WIN_DEV01" Time: 22.05.2015 13:33:03
[90:51] /dev/nst28
Cannot write to device (Details unknown.)
[Critical] From: VBDA@windows_server "I: [Data1]" Time: 22.05.2015 13:33:05
Received ABORT request from SM => aborting.
[Critical] From: VBDA@windows_server "J: [Data2]" Time: 22.05.2015 13:33:05
Received ABORT request from SM => aborting.
[Critical] From: VBDA@windows_server "G: [Home1]" Time: 22.05.2015 13:33:05
Received ABORT request from SM => aborting.
[Critical] From: VBDA@windows_server"I: [Data1]" Time: 22.05.2015 13:33:05
Connection to Media Agent broken => aborting.
[Critical] From: VBDA@windows_server "J: [Data2]" Time: 22.05.2015 13:33:05
Connection to Media Agent broken => aborting.
[Critical] From: VBDA@windows_server "G: [Home1]" Time: 22.05.2015 13:33:05
Connection to Media Agent broken => aborting.
First i thought it could be an timeout or something, but the start and error time doesent indicate that.
Do you have an ideas?
Check your name resolution this is caused by MA trying to resolve its IP address and taking more than 10s.
Did you follow configuration standarts in design guide? Like for example creating a zone exclusivesly for server + VTL
http://www8.hp.com/h20195/V2/GetDocument.aspx?docname=4AA4-7983ENW&cc=us&lc=en
do you have access to C:/ProgramData/OmniBack/server/db80/keystore/catalog ? You can also try stoping services and killing all Postgress services running, then try again.
Found below tips on the help.chm, will try this:
Troubleshooting Networking and Communication
You can configure the TCP/IP protocol to use 8 instead of the default 5 retransmissions. It is better not to use higher values because each increment doubles the timeout. The setting applies to all network connections, not only to connections used by Data Protector.
If the Cell Manager is running on a Windows system, apply the change on the Cell Manager system first. If the problem persists or if the Cell Manager is running on a UNIX system, apply the change to the problematic Windows clients.
Add the DWORD parameter TcpMaxDataRetransmissions and set its value to 0x00000008(8) under the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Restart the system.
Hi good afternoon.
I'd like to know whether web services are supported in Data Protector to integrate with other tools such as Service Desk.
In advance, thank you very much for your attention.
Best regards.
