Network is fine.
Ping and telnet to vcenter from CM is ok and viceversa.
DNS resolution is fine.
Network is fine.
Ping and telnet to vcenter from CM is ok and viceversa.
DNS resolution is fine.
I have some tapes in my drive pools showing as poor quality and has a red mark to the left of it. How do I resuse them? These tapes are not expired yet.
Recommended option is to right click on the tape and run "verify" ... this wil read the the entire tape and match it with what's in the IDB, then reset poor status assuming operation is successful.
If you are in a hurry you can use command:
omnimm -reset_poor_medium Medium
However, this does NOT do any check of the media. But safe to use if you are sure it was a drive issue and not a tape issue that caused the poor media condition.
Hi,
Try to run this comands:
omnidbutil -remap_dcdir
omnidbutil -fixmpos
omnidbutil -remap_dcdir
After run :
omnidbcheck -extended
and post the results.
Regards
hi,
Run and post this command:
omnidbcheck -extended
Regards
Hi,
The setup of enviornemnt is
CM: Windows 2008 R2
DP : 9.01
Client: Exchange server
OS: Windows 2008 R2
DP: 9.01
I am trying to restore exchange backup using GRE for Microsoft Exchange but backup getting failed all the time with error as:
[Major]
From: OB2BAR_VSSBAR@skvmbx2.emaarec.com "MS Exchange 2010+ Server" Time: 7/16/2015 1:50:35 PM
No objects exist in Data Protector Internal Database for session '2015/07/11-16'.
Where as in the IDB I can see the session, media is also availaibel but still not able to restore.
The debug log from client GRE is attached with DP GUI Session report.
Appreciate any support in getting the issue fixed.
regards,
to logon to vsphere web client i use root
i don't know how to add a user to vsphere.local domain.
Because if i add a user it goes into nameofthevcenter domain and not to vsphere.local
i managed to use administrator@vsphere.local and i also did dpuser@vsphere.local.
Granted that user administrative privileges, but nothing changes.
Always get the same error:
Could not logon to vcenter
During the import of the Vcenter within Data Protector 9.02 / 9.03 (regardless of the vcenter being Linux appliance or Windows) ...if it is 5.5 update "1" (Vcenter) and above, we will only support Angular GRE plugin, not flex, so push install from DP install server is not possible. Which means that during the import of the vcenter, you specify a user name and password, that will allow a login, and then select the GRE registration. Now, during the GRE registration, we will use the informaiton provided in the username / password during the import ....if this informiiton is wrong, then a registration will not be made / will fail.
see screenshot(vcenter-import-GRE.png)
Now, administrator@vsphere.local with the corrcet password during import, should allow the login & registration of the plugin. So perhaps the password entered for the amdinistrator@vsphere.local user is wrong. Even if it is an appliance (Vcenter on linux and not windows), administrator@vsphere.local is "STILL" a valid user and it is confirmed here by vmware.
Notice how VMWare states: To reset the administrator@vsphere.local password on the vCenter Server Appliance.
This confirms that this is a valid user.
Perhaps the password you are specifying is invalid and needs to be reset.
Good Luck
We are trying to backup an Oracle 12c system and we keep getting the below error message.
BR0280I BRBACKUP time stamp: 2015-07-15 23:27:39
BR0301E SQL error -28012 at location BrDbConnect-3, SQL statement:
'CONNECT sysbackup/********'
ORA-28012: connection as SYSBACKUP should use AS SYSBACKUP
Has anyone else run into this issue with Oracle 12c and the new SYSBACKUP user?
We can get the backup to run using the SYSTEM user, however our DBA's want to take advantage of the 'SYSBACKUP AS SYSBACKUP' connection but I can't seem to figure out how to configure this.
Any help would be greatly appreciated.
Bryan
Hi,
I'd like to write some reports straight from the Data Protector 9 Postgres database.
Is there a published schema of this database out there? If so does anyone have a link to it or is it HPs secret?
Thanks,
John
Dear,
the password for administrator@vsphere.local is correct, as i can logon to vsphere web client.
I've also made a dpuser into the vsphere.local domain.
But if i import the client without the "Advanced Web Plugin" option thicked it imports the vcenter, but i can do nothing but to thick the GRE web plugin installation.
If i go further with the installation it always fails with the "Could not logon to vcenter".
And, more, if i would like to add it as a normal client installing a component (es.: Disk Agent) it fails with [110:24] error: vcenter not responding.
But:
the vcenter is reachable
telnet 443 open
all dns and related are working.
i'm really going mad!!!
The only time I can duplicate the error "Could not logon to vcenter". is if the credentials supplied are incorrect.
That being said, perhaps best a clal is logegd with HP support to confirm that it is not a code issue
This may be a possible issue, not saying that it is the only issue (it very well may in fact be something else), but something I have seen in the past, that may in fact be related to your environment.
If the integration during restore queries the database (DP database) ..looking for a long name ..for instance skvmbx2.emaarec.com ..but during the initial backup ... 2015/07/11-16..the objects in the internal DP database were tied to a shortname skvmbx2, then the query may fail, hence the error---No objects exist in Data Protector Internal Database for session '2015/07/11-16'
You can confirm by running omnidb -session 2015/07/11-16 -detail
There you wil lsee if the objects in IDB are shortname or longname
Then, what you can "try" is to set the OB2BARHOSTNAME variable in the omnirc on the restoring client skvmbx2.emaarec.com to that name recorded in teh database.
For instance / Example (NOTE, this is just an example)
ProgramData\omniback\omnirc (NO TXT EXTENSION) on my restoring exchange server
Within teh file:
OB2BARHOSTNAME=dag1.hp.com
Good Luck
Another fact is i cannot risk to modify adminstrator password.
so i created a dpuser@vsphere.local with admin privileges and a simple password, but nothing!
I don't think that:
es.: Disk Agent) it fails with [110:24] error: vcenter not responding.
Is related to the login / credential issue during GRE registration.
===========================>
Boh issues should be analyzed through different avenues.
The login / crendetial issue, will be using vmware API
The vcenter not responding will be a rsh(remote shell) push. And since I don't think that a DA is even supported on a Vcenter appliance (I understand it is only a flavor of unix, but still not certified to work...) ..we should really concentrate on issue "1"
My 2 cents
Thanks
Ok, but
so far, all logins and passwords are correct since i can login to vsphere web client with those credentials!
I just noticed that it is "NOT" a credential issue ...the error seems to be:
Logon to Virtual Center pippo could not be performed.
Details: Web service error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has faliled to respond.
==============================>
Is this the error every single time?
If so, this could very well have absol nothing to do with crendetials and can very well be a socket issue. I thought we were experiencing a login issue.
So can you confirm, what the specific error is, very single time..is it the above?
yes, i confirm the error i get is always the same stated above.
Well then, you aare absol correct, it is not a "credential" issue
Web service error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has faliled to respond.
This may in fact be a socket issue
Perhaps there is a delay of time between the DP login to the vcenter..or even a SOAP exception for whatever reason.
Debugs would need to be anlyzed to confirm this, if the virgo log on the vcenter itself is not reporting any relevant errors (when I say relevant....I mean...time stamps matching the DP login attempt)
Best you got a call logged so code can be analyzed