Video Screencast Help

Unable to select datastore - Netbackup, VMware restore

Created: 17 Oct 2011 • Updated: 19 Oct 2011 | 27 comments
This issue has been solved. See solution.

 

 

I'm setting up a DR environment, I've setup a Master Server running NBU 7.0.1 and I've installed a Standalone DR Vmware server running ESXi 4.1.  I've configured a new datastore on the DR VMware server.

 

But when trying to restore my images to an alternate location no Resoure Pool or Datastore information populates in the Restore Wizard.

 

I've tried the steps listed in this post:

https://www-secure.symantec.com/connect/forums/netbackup-vmware-restore-unable-select-datastore

,but they didn't work.  In addition I've added the VMWare server credentials using port 443 and have successfully veried them in the wizard. Any other ideas?

 

 

Notes:

Servers on the same subnet, using Cisco Router to communicate, Vmware box is pingable from NBU server using hostname & IP.  (Host file for DNS).

Comments 27 CommentsJump to latest comment

Mark_Solutions's picture

Hi

If you setup a new vSphere policy on your DR site can you browse the virtual machines in the client section?

Just to clarify is this a VCenter or ESX Server you have added?

If it is as ESX Server is it actually under the control of the vCenter?

Thanks

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

curtiplas's picture

It is an ESXi server running ESXi 4.1, it doesn't have a VCenter server right now.  In the restore wizard I'm selecting "None" under the VCenter option, but the ESX server field is autopopulating with my ESXi 4.1 server (I'm assuming this is because I've added it as a Virtual_Machine Host in the EMM database, via adding it's credentials).

I've not setup a new policy in the DR, as I'm not intending to back it up, but merely test restores.  Also since I've not been able to successfully restore any VMs to it, there are no Virtual Machines to browse in the client section.

 

Currently I've been controlling the ESXi server with the VSphere Client application, which is installed on the NetBackup server.

Mark_Solutions's picture

I was asking because if you are restoring to an alternate ESX server it must not be under the control of the original vCenter server - it must be a standalone ESX Server.

In the credentials section is should be added as an ESX Server not a vCenter Server.

Is that what you have?

So it all needs to match vCenter to vCenter or VCenter to ESX (not under vCenter control)

Just want to clarify this

Thanks

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

curtiplas's picture

Yes I have the server added in Netbackup as a VMWare ESX Server, I did double check this after your last post to ensure its setup correctly.  The server is a standalone ESX server (no Vcenter), and I've set it up that way in NBU, so I should be good on that, I think.

 

See screenshots below.

NBU VM Settings.png NBU Restore Settings.png
Mark_Solutions's picture

Just wondering about selecting the specific port - if it is the default you shouldnt need to select that - if it is not default then it doesnt work and there is an EEB to fix it.

http://www.symantec.com/docs/TECH128051

Having sadi that vCenter should use 443, ESX should use port 80 I believe so although the credential work it may just be the wrong port that you have specified?

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

curtiplas's picture

Okay,

I did try specifying port 80, but this doesn't work at all.

So, I then tried unchecking the specific port (which changes the port listing to 0), I'm still able to successfully validate the credentials this way, however the I get the same results when trying the restore (no datastore or resource pool info).

 

I'm going to try the EEB next, although I'm not sure if we're using the VStorage for restores or VCB. :/

Mark_Solutions's picture

If this is a test environment you could just patch it or upgarde it rather than wait for the EEB as it will probably have been included in any releases after 7.0.1

VCB is something else all together - need to know exactly how you have things setup on the live and test environment to go further with this

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

curtiplas's picture

So, the EEB didn't work

 

It seems to be for version 7.0 not 7.0.1.  I'm requesting to see if there is one for 7.0.1; however, any other suggestions?

 

Mark_Solutions's picture

Just double check that you have everything in place and setup correctly
Remove the ESX server and re-add it leaving it as the default port, add in your VMWare host (media server) and try again
Just follow the usual rules for a DR test - media and image ownership etc and ensure everything can be resolved
Also, if going to an ESX server use the root password and make sure that it not under vcenter control

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

curtiplas's picture

I did double check this all this morning, and I'm doing everything mentioned above with one exception:

 

Remove the ESX server and re-add it leaving it as the default port, add in your VMWare host (media server) and try again

 

I'm assuming you're referring to the Master Server (no Media Server in our DR environment), if that's the case then I've done that too.

 

But as you said I'm going to delete it all and re-create.

pikachu's picture

You need the EEB.

Create vmcloglevel with value 3 in the registry on the backup host. Setup logging for bpvmutil. Now open up BAR and start the restore. When you get to the point check bpvmutil.

Nothing has changed...

curtiplas's picture

 

I was looking into how to do that yesterday, but was having trouble locating instructions, can you refer me to any documentation?

pikachu's picture

 

Open up Backup, Archive& Restore on the backup host. Click on File and then Netbackup Client Properties. In the Troubleshooting tab set general to 2 and verbose to 5.
 
Next browse to c:\program files\veritas\netbackup\logs\bpvmutil\. If the folder does not exit please create the folder. Delete everything in the folder if the folder already existed.
 
Open up the registry and go to HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config\BACKUP\. If the key BACKUP does not exist just create it. Next under the BACKUP key create the dword vmcloglevel and set it to 3.

Nothing has changed...

curtiplas's picture

Okay I've done that and I've re-opened Backup Archive & Restore, re-attempted (which of course failed).  Now I'm looking at the log, but I'm not sure I understand it completely.  Any suggestions on what to look for?

pikachu's picture

Can you post the log? We will help you. :)

Nothing has changed...

pikachu's picture

vmcGetObjDetails for HostRoot failed with status 14

http://www.symantec.com/docs/TECH135461

 

Something doesn't seem to resolve back correctly. Follow the TN and let us know how that worked.

 

If that doesn't help. Open a ticket and PM me the case number. This should be fairly easy to fix.

Nothing has changed...

curtiplas's picture

Okay while I'm waiting I just took a peak at the new log that was created, and I'm not seeing the:

 

"vmcGetObjDetails for HostRoot failed with status 14"

Anyone want to take a peak?

AttachmentSize
101811_new.txt 33.18 KB
Mark_Solutions's picture

OK - looking much better now the FQDN is no longer being used - I guess you have changed something to resolve this.

It only seems to be failing now at the datastore section and has access to everything else

Are you using the root userr for Authentication?

Is everything OK with the datastores on the ESX Server?

Can the Media Server doing the restore see the LUNS via the SAN or are you doing this over the network - I see you have SAN then nbd in the restore selections list.

Also remeber the host name is case sensitive and must match that returned by the ESX Server if you run #hostname on it

Finally - try adding it as an ESX Restore Server rather than an ESX Server in the credentials section - just looking at your screen shots

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Mark_Solutions's picture

One more check .....

In an earlier post you say "Currently I've been controlling the ESXi server with the VSphere Client application, which is installed on the NetBackup server."

Does this mean that you ESX Server is under the control of vCenter somewhere?

If so you cannot use it as an ESX Server - you must add it as a vCenter Server (as i asked in my first post) - so add in the vCenter DR Server instead and then try it.

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

curtiplas's picture

Hello Mark,

 

I've done all the items mentioned in the first post.  The Screenshot with the SAN then nbd was in error, I hadn't changed it yet to just nbd.  So to answer the question in regards to seeing the Datastore via the SAN, no it can't as it's over the network to local disk on the ESXi Server.  Also I am using the root user for authentication.

 

The Server isn't under control of a vCenter server, but I'm using the vSphere client application to configure the Datastore and what not, so it's not technically under control of vCenter, like a normal ESX cluster.

 

-Thanks

curtiplas

Mark_Solutions's picture

Ok - so in my last but one post have you checked its #hostname and ensure that the same is entered when you added it to NetBAckup and have you tried adding it as an "ESX Restore Server" rather than an "ESX Server" in the Credentials section?

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

curtiplas's picture

Yeah I did try that when I was waiting to hear back from Symantec regarding my open case :/

 

I feel like I've been repeatedly running into the same brick wall :-(

Mark_Solutions's picture

OK

Well if you have added it with the same name as you get when you run a #hostname on the ESX Server itself and done all the other config of NBU and ESX correctly then i guess we need to see what Symantec say.

I do remeber that there was an issue if its hostname was short but that related to discovering the networks as it forces a FQDN but you haven't got as far as that so we need to establish where the issue lies with the datastores.

On your DR ESX Server are the datastore disks on the SAN or integrated - not sure if it makes a difference but it gives us even more of the full picture.

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

pikachu's picture

 

inserted string disableFQDN to hkey local machine software veritas netbackup current version config BACKUP
 
\veritas\netbackup\online_util\
=> was missing
\veritas\netbackup\online_util\fi_cntl\
=> was missing
 
rec-reated the folders and ran 'bpvmutil 0 0 _NONE'
=> cache files got created eventough the ESX is empty, because it is a blank ESX
 
(this is the cache folder)
 
installed vmware rollup bundle eebinstaller.2105102.14.AMD64
 
pre-check works, however restore fails with KMS issues
=> kms service is not up and running
 
 
installed KMS files:
\Program Files\Veritas\kms\db\KMS_DATA.dat
\Program Files\Veritas\kms\key\KMS_HMKF.dat
\Program Files\Veritas\kms\key\KMS_HKPKF.dat
 
optional:
inserted dword NoEagerlyScrub and set it to zero

Nothing has changed...

SOLUTION