If you want to take advantage of all SCSI commands it's easier to set OB2FORCESCSI=ALL. In case of WFM(Write filemarks) it's only limited to that specific option.
↧
Re: RHEL6.5 supports MTWEOFI
↧
ERROR: The "checkinstall" script for "DATA-PROTECTOR" failed while upgrading from HPDP 7 to 9
Hello TEam,
I am getting below error message while upgrading from HPDP 7 to HPDP 9
Kindly help me in fixing the issue.
# swjob -a log odsapdb1-0234 @ odsapdb1:/
======= 08/22/16 18:41:39 SST BEGIN install AGENT SESSION (pid=23988)
(jobid=odsapdb1-0234)
* Agent session started for user "root@odsapdb1". (pid=23988)
* Beginning Analysis Phase.
* Source: odsapdb1:/var/adm/crash/dp9/hpux/DP_DEPOT
* Target: odsapdb1:/
* Target logfile: odsapdb1:/var/adm/sw/swagent.log
* Reading source for product information.
NOTE: The filesystems in the filesystem table will not be checked
against those currently mounted because the
"mount_all_filesystems" option is set to "false".
* Reading source for file information.
ERROR: Cannot execute
"/var/tmp/BAA023988/catalog/DATA-PROTECTOR.2/pfiles/checkinstall".
Command or script output (if any):
Permission denied (13).
ERROR: The "checkinstall" script for "DATA-PROTECTOR" failed (exit
code "1"). The script location was
"/var/tmp/BAA023988/catalog/DATA-PROTECTOR.2/pfiles/checkinstall".
* This script had errors and the execution of this product
cannot proceed until the problem is fixed. Check the above
output from the script for further details.
* Executing preDSA command.
NOTE: Could not install the bundle "B6960MA,r=A.09.00" because none
of its filesets could be installed.
NOTE: All filesets in the product "DATA-PROTECTOR,r=A.09.00" will be
excluded because there was an error in this product.
↧
↧
(DP) Support Tip: After updating to 9.07, Sybase fails with [70:5] Cannot execute 'C:\Program Files
After upgrading from 9.06_108 to DP9.07 the Sybase backups started to fail with the below error message :
[Critical] From: INET@cggwrapvipv1.grupo-oal.com.co "" Time: 08/16/16 10:48:50
[70:5] Cannot execute 'C:\Program Files\OmniBack\bin\ob2sybase.pl' ([22] The device does not recognize the command. ) => aborting
[Normal] From: BSM@cgdppdbrepv1 "NGP_LOGS_MIRR" Time: 08/16/16 10:59:51
OB2BAR application on "cggwrapvipv1" disconnected.
This QCCR2A68978 is soon to be fixed in the upcoming patch for Data Protector build 9.07_110. As workaround is the following since ob2sybase.pl exists :
C:\Windows\system32>mklink ob2sybase.pl ob2sybase.exe
symbolic link created for ob2sybase.pl <<===>> ob2sybase.exe
↧
Re: ERROR: The "checkinstall" script for "DATA-PROTECTOR" failed while upgrading from DP 7 to DP 9
also i cannot find any folder structure var/tmp/BAA023988/catalog/DATA-PROTECTOR.2/pfiles/
↧
Re: ZDB : [ 236:52] Failed to resolve a storage volume on the host
Hi Aleskol,
many thanks for suggestion. i've checked DNS resolution for ESX, 3par storage, backup hosts. all are OK - names are resolvable how they should be in small letters.
i've checked debug file and noticed that he is trying to resolve volume to device files at backup host [marked in red color].
but still i couldn't find any solution of this problem.
i see some warning at /var/log/message [backup host] but not sure if it is the reason of failure.
kernel: sd 3:0:6:56: Warning! Received an indication that the LUN assignments on this target have changed. The Linux SCSI layer does not automatically remap LUN assignments.
#### debug logs
[199] 2016-08-18 23:14:02.147 ("/integ/smis/Communication/Connections/IpcConnection.cpp $Rev: 9836 $ $Date:: 2010-06-15 07:30:58 ":317)
23468 [199] <<=== (5) } /* IpcConnection::send */
23469 [199]
23470 [100] *************** SKPrintf [START] ***************
23471 [100] Tokenize the string...
23472 [100] token [0] = ^G[%1$s] From: %3$s@%4$s "%6$s" Time: %2$s
23473 %5$s
23474
23475 [100] token [1] = Major
23476 [100] token [2] = 08/18/2016 11:14:02 PM
23477 [100] token [3] = SMISA
23478 [100] token [4] = backup_host.fqdn
23479 [100] token [5] = ^G[236:52] Failed to resolve a storage volume on the host.
23480 Storage volume: %s
23481
23482 [100] token [6] = DP-2016.08.18-44-057B616AE
23483 [100] token [7] = SMISA
23484 [100] *************** SKPrintf [END] ***************
23485
23486 [ 4] 2016-08-18 23:14:02.147 ("/integ/smis/Resolver/ResolverUxImpl.cpp $Rev: 52654 $ $Date:: 2016-03-23 06:11:33 ":1016)
23487 [ 4] [REPORT 2] in ResolverUxImpl::ResStorageVolumes2DeviceFiles
23488 Marked: ("":Line:0 in '')
23489 Code is:0
23490 [Major] From: SMISA@backup_host,fqdn"SMISA" Time: 08/18/2016 11:14:02 PM
23491 [236:52] Failed to resolve a storage volume on the host.
23492 Storage volume: DP-2016.08.18-44-057B616AE
23468 [199] <<=== (5) } /* IpcConnection::send */
23469 [199]
23470 [100] *************** SKPrintf [START] ***************
23471 [100] Tokenize the string...
23472 [100] token [0] = ^G[%1$s] From: %3$s@%4$s "%6$s" Time: %2$s
23473 %5$s
23474
23475 [100] token [1] = Major
23476 [100] token [2] = 08/18/2016 11:14:02 PM
23477 [100] token [3] = SMISA
23478 [100] token [4] = backup_host.fqdn
23479 [100] token [5] = ^G[236:52] Failed to resolve a storage volume on the host.
23480 Storage volume: %s
23481
23482 [100] token [6] = DP-2016.08.18-44-057B616AE
23483 [100] token [7] = SMISA
23484 [100] *************** SKPrintf [END] ***************
23485
23486 [ 4] 2016-08-18 23:14:02.147 ("/integ/smis/Resolver/ResolverUxImpl.cpp $Rev: 52654 $ $Date:: 2016-03-23 06:11:33 ":1016)
23487 [ 4] [REPORT 2] in ResolverUxImpl::ResStorageVolumes2DeviceFiles
23488 Marked: ("":Line:0 in '')
23489 Code is:0
23490 [Major] From: SMISA@backup_host,fqdn"SMISA" Time: 08/18/2016 11:14:02 PM
23491 [236:52] Failed to resolve a storage volume on the host.
23492 Storage volume: DP-2016.08.18-44-057B616AE
Thanks,
DPX
↧
↧
Data Protector - Database internal error
Good afternoon,
Some backup jobs are presenting the following error message:
From : BSM @ server " job" Time: 21/08/2016 15:36:01
[ 61: 4039 ] Following error occurred while storing detail catalog
information for device " TL4000_LTO3_D1 "
loaded with medium " d201010a : 47335eeb : 0a8c : 0001 " [ [ 000006L3 ] HSCMPA_106 ]
to Data Protector Internal Database :
Database internal error - see debug.log for details .
I would like to support to solve this problem.
Thank you very much.
↧
Hp Data protector Scratch tapes
Hi,
a question related to HP Data Protector Manager v A.09.00...
this week I replace a Backup guy. Have a quesion about moving scratch tapes to working Pool.
I had 3 min instructions so forgot one step that quickly put on paper (not my fault :) )
so, what I did:
1. found the tape with yesterday's back and removed it (was week 2)
2. inserted Tapes for a new week (Week 3 in my case)
The guy told me that he takes a photo of tapes before inserting them ... and then I should find them and move in DP Manager.
So what I could do ...
1. In HP DP Manager I moved the tape with yesterdays backup (that phisically removed) from working pool (Default LTO-Ultrium) to CS (it is Scratch pool).
2. Since I didn't take the photo of tapes that I inserted I decided to make it even simpler :)
(don't think that I have to have the tapes names before inserting them to the library (take a photo like instructed.)
In the scratch pool (SC) I see Expired with horisontal green tape icon. So for me it is a sign that those tapes could freely go to the working pool. This what I did: just moved them to working pool Default LTO Ultrium.
Could somebody confirm that I did right? (or what is my mistake if any...)
Thanks.
↧
Perform Restore of SAP Virtual Machine Other than using Volume Data Level Backup Restore Question
I'm interested in alternative options to restoring our SAP servers, vmware virtual machines. Our current environment is leveraged and are backed up using HP Data Protector, volume data level backups only, which doesn't support "bare metal" restores using VMware ESx/ESXI image .vmdk and .vmx backup file formats.
We need to do a proof of concept SAP restore scenario to recover a singel failed Windows Server VM instance in an ESX Cluster.
What are some options other than Volume Data Level Backup to accomplish restoring for this scenario?
Can we switch from Volume Data Level backups to something specific for that SAP Windows, OS, and database environment?
↧
Re: ERROR: The "checkinstall" script for "DATA-PROTECTOR" failed while upgradi
>I cannot find any folder structure var/tmp/BAA023988/catalog/DATA-PROTECTOR.2/pfiles/
Since in /var/tmp/, it is likely the directory was removed after swinstall ran.
I'm not sure how you could get permission denied if you are running as root.
You may have to look inside /var/adm/crash/dp9/hpux/DP_DEPOT to extract the checkinstall script.
↧
↧
Re: ERROR: The "checkinstall" script for "DATA-PROTECTOR" failed while upgradi
hi i have the below files in the path /var/adm/crash/dp9/hpux/DP_DEPOT/catalog/DATA-PROTECTOR/pfiles
I have extraced the iso file from windows system and copied to Hp ux machine.Let me know if i am missing something here
↧
Re: ZDB : [ 236:52] Failed to resolve a storage volume on the host
Hi,
If you have debug logs, can you share them? Only SMIS from backup host is needed.
Or if you can check for any of the following entries:
- Search for “[ -2]” and provide output +-10 lines
- Search for “error” and if in +- 10 lines (somewhere near) you can find also “exec3PARCliCommand” or “CDpArrayProviderObj” or “WebServiceAPI3ParMgmt” provide those lines also.
Regards
AlesKol
↧
Re: ZDB : [ 236:52] Failed to resolve a storage volume on the host
Many thanks ales for reply.
I've attached the logs. Please change the file extention to .7z
thanks,
DPX
↧
Re: Data Protector - Database internal error
Hi SantaCasa,
what is the Data Protector version (omnisv -version, omnicheck -patches)? Are you running out of disk space on the local disk where the Data Protector IDB is stored?
Please use the Accept Solution button next to my post and assign a KUDO (thumbs up icon) if this works for you.
Regards,
Sebastian Koehler
↧
↧
Re: ZDB : [ 236:52] Failed to resolve a storage volume on the host
Hi,
I am sorry, can’t help you here. Seems that communication with array is OK, but smis fail to find disk on backup host.
There could be multiple reasons for this. Maybe if you would share entire log, I might be able to help.
Otherwise I suggest that you open a call with HPE.
Regards Aleskol
↧
Re: Perform Restore of SAP Virtual Machine Other than using Volume Data Level Backup Restore Questio
Hi jharbor,
there are several options. For SAP on VMware vSphere I usually recommend doing both.
1. Image level backup using Data Protector Virtual Environment Protection Agent (VEPA) that allows restoring the whole VM including VMDKs and VMX files for disaster. This type of backup is usually executed once a week (full) and daily (incr/diff) depending on customer needs.
2. In addition you should do the Data Protector Online Integration backups (SAP R3 if running SAP on Oracle) inside the VM to ensure allow point in time restores of SAP can be done easily. This is usually a daily full with at least a single archive log backup per day (this will vary on how sensitive the customer is to data loss).
Please use the Accept Solution button next to my post and assign a KUDO (thumbs up icon) if this works for you.
Regards,
Sebastian Koehler
↧
Re: ERROR: The "checkinstall" script for "DATA-PROTECTOR" failed while upgradi
You should do a loopback mount on HP-UX or mount the Data Protector ISO using ILO/MP instead. I have seen similar cases and extracting on Windows is the worst thing to do.
Please use the Accept Solution button next to my post and assign a KUDO (thumbs up icon) if this works for you.
Regards,
Sebastian Koehler
↧
Re: Data Protector - Database internal error
Sebastian,
The server has 10 Gbps of free space on dirve E:\
Media Management database space usage:
Space used by Diskspace usage Records used Records total
============================================================================
Devices 96 6 40
Libraries 96 3 40
Cartridges 640 185 432
Compounds 32 0 96
Pools 64 21 40
Media 128 156 264
Catalog database space usage:
Space used by Diskspace usage Records used Records total
============================================================================
Sessions 8192 5774 7200
Objects 6720 9730 12864
Object versions 249664 28599 44560
Positions 99424 238464 364064
Filenames 14091104 127355232 127355414
Detail catalog binary files usage:
Diskspace usage Size limit DC Directory
============================================================================
2008 26384 e:/programdata/omniback/db40/dcbf
----------------------------------------------------------------------------
2008 26384
Session messages binary files usage:
Diskspace usage Num. of files SMBFs Directory
============================================================================
117 5704 E:/ProgramData/OmniBack/db40/msg
Serverless integrations binary files usage:
Diskspace usage Num. of files SIBFs Directory
============================================================================
0 0 E:/ProgramData/OmniBack/db40/meta
↧
↧
Re: Data Protector - Database internal error
What is in the Cell Manager debug.log (at the time when the error was written to session report)? You could try to add another DCBF directory, while the existing one still is within limits.
Regards,
Sebastian Koehler
↧
Re: Data Protector - Database internal error
Sebastian,
8/23/2016 8:30:45 AM BSM.4320.5028 ["/lib/snmpnt/snmp.c $Rev: 1981 $ $Date:: 2009-09-11 22:41:14":722] A.07.00 b106
Failed to send SNMP trap. Check SNMP service configuration.
8/23/2016 8:53:11 AM RSM.4960.3744 ["/lib/snmpnt/snmp.c $Rev: 1981 $ $Date:: 2009-09-11 22:41:14":722] A.07.00 b106
Failed to send SNMP trap. Check SNMP service configuration.
8/23/2016 9:08:00 AM BSM.1688.2628 ["/db/dbutil.c $Rev: 39452 $ $Date:: 2013-10-10 20:51:21":948] A.07.00 b106
VELOCIS DB ERROR [5] internal error [-14] member already owned (S_ISOWNED)
8/23/2016 9:08:36 AM BSM.4696.4192 ["/lib/snmpnt/snmp.c $Rev: 1981 $ $Date:: 2009-09-11 22:41:14":722] A.07.00 b106
Failed to send SNMP trap. Check SNMP service configuration.
8/23/2016 9:38:27 AM FSBRDA.4244.3104 ["/da/bda/win32.c $Rev: 39452 $ $Date:: 2013-10-10 20:51:21":2295] A.07.00 b106
GetVolumeName2ForVolumeMountPoint failed for Mountpoint [] with error [123]
8/23/2016 9:38:28 AM FSBRDA.3224.2072 ["/da/bda/win32.c $Rev: 39452 $ $Date:: 2013-10-10 20:51:21":2295] A.07.00 b106
GetVolumeName2ForVolumeMountPoint failed for Mountpoint [] with error [123]
8/23/2016 9:38:32 AM FSBRDA.2568.4736 ["/da/bda/win32.c $Rev: 39452 $ $Date:: 2013-10-10 20:51:21":2295] A.07.00 b106
GetVolumeName2ForVolumeMountPoint failed for Mountpoint [] with error [123]
8/23/2016 9:38:35 AM FSBRDA.4956.3212 ["/da/bda/win32.c $Rev: 39452 $ $Date:: 2013-10-10 20:51:21":2295] A.07.00 b106
GetVolumeName2ForVolumeMountPoint failed for Mountpoint [] with error [123]
8/23/2016 9:38:41 AM FSBRDA.3860.2600 ["/da/bda/win32.c $Rev: 39452 $ $Date:: 2013-10-10 20:51:21":2295] A.07.00 b106
GetVolumeName2ForVolumeMountPoint failed for Mountpoint [] with error [123]
8/23/2016 9:38:47 AM FSBRDA.3452.3320 ["/da/bda/win32.c $Rev: 39452 $ $Date:: 2013-10-10 20:51:21":2295] A.07.00 b106
GetVolumeName2ForVolumeMountPoint failed for Mountpoint [] with error [123]
8/23/2016 9:38:53 AM DBSM.1688.2628 ["/lib/cmn/win32io.c $Rev: 23060 $ $Date:: 2011-08-08 16:32:55":783] A.07.00 b106
[OB2_StatFile] FindFirstFile failed, errcode=123 [file=/E:/ProgramData/OmniBack/db40/dcbf]
8/23/2016 9:38:53 AM DBSM.1688.2628 ["/db/dc/dcbf/dcbf.c $Rev: 39452 $ $Date:: 2013-10-10 20:51:21":1698] A.07.00 b106
[dcbf_mediumFileDirectories_add] failed to stat mbf [123]: '/E:/ProgramData/OmniBack/db40/dcbf'
8/23/2016 9:38:53 AM DBSM.1688.2628 ["/lib/cmn/win32io.c $Rev: 23060 $ $Date:: 2011-08-08 16:32:55":670] A.07.00 b106
OB2_CreateDirectory: CreateDirectory() failed, errcode=123 [dir=/E:/ProgramData/OmniBack/db40/dcbf]
8/23/2016 9:38:53 AM DBSM.1688.2628 ["/db/dc/dcbf/dcbf.c $Rev: 39452 $ $Date:: 2013-10-10 20:51:21":1712] A.07.00 b106
[dcbf_mediumFileDirectories_add] failed to create mbf directory [123]: '/E:/ProgramData/OmniBack/db40/dcbf', _flags=448
8/23/2016 10:17:29 AM BSM.1688.796 ["/db/dbutil.c $Rev: 39452 $ $Date:: 2013-10-10 20:51:21":948] A.07.00 b106
VELOCIS DB ERROR [8] internal error [-14] member already owned (S_ISOWNED)
8/23/2016 10:18:06 AM BSM.152.4984 ["/lib/snmpnt/snmp.c $Rev: 1981 $ $Date:: 2009-09-11 22:41:14":722] A.07.00 b106
Failed to send SNMP trap. Check SNMP service configuration.
8/23/2016 10:23:48 AM BSM.1688.796 ["/db/dbutil.c $Rev: 39452 $ $Date:: 2013-10-10 20:51:21":948] A.07.00 b106
VELOCIS DB ERROR [7] internal error [-14] member already owned (S_ISOWNED)
8/23/2016 10:24:25 AM BSM.5064.2044 ["/lib/snmpnt/snmp.c $Rev: 1981 $ $Date:: 2009-09-11 22:41:14":722] A.07.00 b106
Failed to send SNMP trap. Check SNMP service configuration.
8/23/2016 10:47:36 AM RSM.4388.4300 ["/lib/snmpnt/snmp.c $Rev: 1981 $ $Date:: 2009-09-11 22:41:14":722] A.07.00 b106
Failed to send SNMP trap. Check SNMP service configuration.
How do I add a new DCBF ?
thank you
↧
Expired media not moving to free pool after upgrade from DP8.14 to DP9.07
We are experiencing and issue with our media not moving to the free pool once it expires. This started immediately after our upgrade to DP9.07. Wondering if anyone else has encountered this behaviour. We are using default setting for FreePoolDeallocFreq in the global options file. This worked fine on DP8.14 before the upgrade. Also all media pool settings are still in tact. We have 3 other cells that were upgraded from DP8.14 to DP9.05 with no issues as well. We are planning to upgrade the other three to DP9.07, but I would like to get this sorted first. Thought I would check here before I open a support case to see if this is a known issue.
# FreePoolDeallocFreq=TimesPerDay
# default: 4
# limit: 1 <= FreePoolDeallocFreq <= 96
# This period is used to run free pool deallocation process
# on Data Protector Cell Manager (Media Mgmt DB).
# If set to 1, deallocation is performed once per day (00:00),
# set to 2 two times per day (00:00,12:00), set to 3 three times
# per day (00:00, 08:00, 16:00), set to 4 four times per day
# (00:00, 06:00, 12:00, 18:00). If maximum (96) is specified,
# free pool deallocation will be started every 15 minutes.
Thanks in advance,
OmniBrian
↧