Hi All,
In my case the issue was IP address change in my cell manager where media agent is being installed. due to which the client machine was unable to reach the proper media agent because the host file had old IP address entered in it.
Just see the client machines host file and do the nessessary modification required.
set OB2PORTRANGE xMA-NET on the media agent and this will solve the problem
Hi. With some help from our local Wintel team we found a registry key which seems to have fixed the issue. The change we made was to the following key:
HKLM\software\policies\microsoft\systemcertifications\authroot Set 'DisableRootAutoUpdate' to 0
Running command omnirpt -report host -host server.domain.local -tab in cell server with a big list of clients, omnirpt takes minutes for finish. If you run the same command in the same server just leaving cell and client entries it takes seconds.
Command is reading cell_info file taking a lot of time when this is not necessary, host name is being determined with command syntax.
Open support case and request hotfix QCCR2A71548
Best Regards
Hello,
I have HPE Data Protector A.09.06 and every day use MS Volume Shadow Copy integration on MS Windows 2008 Server. When I try to restore objects, I can't choose date of the backup,like in "File System" specification (Interval,Last 3 Month, etc.). Does the Data Protector A 09.06 have any capabilities to restore "Shadow Copies" for different dates?
Thanks!
Hi,
I have the same error since this week. Have someone any idea what we have to do to fix this problem?
Thanks!
Regards Uli
Hello everyone,
After upgrading from Data protector 7.03 to 9.08 y get this error message un the Reporting context, event log (screenshot is attached)
[138:709] Health check message: "/opt/omni/bin/omnimm -list_pools" failed
and when running omnimm -list_pools I get the next output:
[root@server log]# /opt/omni/bin/omnimm -list_pools
Status Pool name Media Type MS # of media Free [MB]
========================================================================================
Good ARCH_lib01 LTO-Ultrium No 0 (null)
Good ARS0_SCSI01 LTO-Ultrium No 0 (null)
Good ARS0_SCSI02 LTO-Ultrium No 0 (null)
Good ARS0_SCSI03 LTO-Ultrium No 0 (null)
Good ARS0_SCSI04 LTO-Ultrium No 0 (null)
Good ARS0_SCSI05 LTO-Ultrium No 0 (null)
Good ARS0_SCSI06 LTO-Ultrium No 0 (null)
Good ARSCSI07 LTO-Ultrium No 0 (null)
Good ARS0_SCSI08 LTO-Ultrium No 0 (null)
Good ARS0_SCSI09 LTO-Ultrium No 0 (null)
Good ARS0_SCSI10 LTO-Ultrium No 0 (null)
Good ARS0_SCSI11 LTO-Ultrium No 0 (null)
Good ARS0_SCSI12 LTO-Ultrium No 0 (null)
Good ARS0_SCSI13 LTO-Ultrium No 0 (null)
Good ARS0_SCSI14 LTO-Ultrium No 0 (null)
Good ARS0_SCSI15 LTO-Ultrium No 0 (null)
Good ARS0_SCSI16 LTO-Ultrium No 0 (null)
Segmentation fault (core dumped)
Digging within the log files I found "exit code 1011".
backups are running normally but it is very annoying to hace this message everyday, please help
Hi, Sorry to jump in here but I'm also looking at performing the exact same type of backups.
We are using out Physical vCenter as our backup proxy, this is a 2012 R2 Server with FC HBA.
My question is around the presenting of the Datastore LUNs to the backup host .... Our 3PAR contains the Datastores, is there any function or requirement for the LUNs to be presented in 'READ ONLY' to ensure no issues are caused (Signatures aside).
Many thanks
I will answer for you....
1. do i need to buy a new license or the current one can be migrated (export/impot).
if you still have support then you can migrate your licenses to the new format in v9. Best to email HP licensing. See webware.hp.com
2. where do i get the software if i dont have an active support agreement.
you will need a SAID to login to the hp support site and download what you need. DP9 and 9.08 patches.
3. where can i find the steps & patches information to upgrade.
download patches from here:
if your cell manager is 64-bit you can upgrade straight to v9 from 6.2. Once on v9 you can then install the 9.08 bundle.
NOTE:
check your online backups and operating systems to make sure your environment is fully supported in v9...
click KUDOS if this is helpful to you!
Can my cell manager be the backup host for vmware?
The ESX host cannot be the backup proxy.
Hi Adam,
I've closed the case now because I've found an acceptable workaround (only 7 systems affected here):
I've manually deinstalled the old 9.07 client and reinstalled the 9.08 client from the installation share.
It works on both Windows 2008 64bit SP2 and old Windows 2003 32bit without a problem.
Perhaps you do have more luck with your case.
Kind regards
Guido
Hi ,
I'm trying to restore VM [SAN MODE] but i'm getting this error (Could not write in the disk scsi0:0 (Error: '-1') .
my environment [ data protector version 9.08 , storeonce 6500]
does anyone face this problem ? any suggestion would be highly appriciated.
After this error : restore failed
[Warning] From: VEPALIB_VMWARE@backup_host1.local "" Time: 12/14/2016 05:52:39 PM
Could not write in the disk scsi0:0 (Error: '-1')
Thanks,
DPx
Thanks, question: after you uninstalled 9.07 manually, did you have to also __manually__ reinstall by mounting the share or etc. or were you able to just use the DP GUI to install 9.08 like it was a new client? Basically, I am wondering if the reinstall of 9.08 was the same as if you were just adding a new client or if instead you had to do something manual with the installation share on the 2003 or 2008 system to run the install kit. I've only got about 15 or so and I could probably do them manually as a workaround as well. also 9.07 seems to be working, so I may just do nothing if the case goes no where.
I am running Data Protector 9.07 on a windows 2012 machine. I am seeing the below error in the event logs. This is a site that I have just started supporting and this error has been going on for a while. I tried running omnidbcheck -extended but everything comes back as failed. The site told me this happened before and they had to reinstall Data Protector. Does anyone know how this would happen and a possible fix other then reinstalling and losing everything.
[138:706] Corruption in the "[138:706] Corruption in the "[138:706] Corruption " part of the Data Protector Internal Database has been detected ("[138:706] Corruption in the "[138:706] Corruption in the "[138:706] Corruption " part of the Data Protector Internal Database has been detected ("[138:706] Corruption in the "[138:706] Corruption in the "[138:706] Corruption " part of the Data Protector Internal Database has been detected ("[138:7").
Description:
One of the modules detected possible corruption of the IDB (Data Protector Internal Database).
Note that the IDB consists of multiple parts and possible actions depend on which
part is corrupt.
Can my cell manager be the bakcup proxy for vmware?
There are a lot of reasons why this could happen, file system corruption and server getting a blue screen for example.
Analyzing and fixing this via the forum is not really the best way.
I recommend opening a support case.
Hello,
based on what I see, I assume that the content of the DP internal database is not 100% correct.
We can fix this by providing a repair script.
To create this script, the following data is needed:
1. omnimm -list_pools debugs
2. A dump of the internal database (omnidbutil -writedb)
Please open a support case, we cannot handle this via the forum.
Best regards,
Michael
It´s a bit hard to understand this question.
The best would be to contact a HPE sales representative or partner company.
I suggest to update to DP 9.08 and apply the current licenses then.
Hello
Could you please share list of DP patches installed? omnicheck -patches
Does it WIndows or Linux server?
How did you upgrade from 9.0 to 9.08? If this is a LInux cell after install bundle of patches you must upgrade cell manager itslef from GUI console.
I really suspect that you are running DP 9.0 instead 9.08
Best Regards