Policy vaildation failed due to EMM status 213 storage units are not available

[chebrolu]

Hi

Problem:

======

Policy vaildation failed due to EMM status 213 storage units are not available.

Following the below steps while creating the netbackup policy
 
Steps:
-----
1.Added the ESXI host under master server and

2.Click on virtual machine access and provided ESXI credentials.

3.Restarted netbackup services using below link
 
https://www.veritas.com/support/en_US/article.TECH217024

4.Before trying to take VM backup's running on that host,need to create policy for VM backup
 
5.while Creating the policy,getting vaidation failed message on the screen.

Attached necessary screen shot to this forum.Please let me know your comments on the same.

Thanks

koti

[chebrolu]

Hi Marianne,

Yes, I tried to take VM backup and also Configure automatic selection of virtual machines for backup

But it t throws snapshot error encountered.Can you please suggest how to solve this issue?

Before going to take VM backup shall i create snapshot in vsphere webclient or not?

Thanks

koti

[Marianne]

No, you don't need to create a snapshot - NBU will instruct VMware to take a snapshot.
See Overview of the VMware backup process in the manual.)

Have you confirmed that vmtools is installed on all VMs? (and other requirements listed in the manual...)

Best to view notifications in vsphere webclient  after you have started the backup to see what the problem is.

Herewith a TN with the most common VMware snapshot problems: 

Snapshot error encountered (status code 156)
http://www.veritas.com/docs/000068085 

[chebrolu]

Yes,Marianne have gone through once again VMware backup process and followed same way.

Yes,i have already installed VMware tools in all VM's but out of date.Is it ok?

Attached vcenter snap to this thread.

Gone through above link,as per my knowledge doesn't match this issue.

Job status:

10/28/2015 6:56:41 AM - Info nbjm(pid=3344) starting backup job (jobid=8) for client MEDIA_SERVER, policy vmpolicy, schedule vmschedule  
10/28/2015 6:56:41 AM - Info nbjm(pid=3344) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=8, request id:{9FEB7D79-636D-4A4F-ACB3-5C76E9F99AF8})  
10/28/2015 6:56:41 AM - requesting resource disk_storageunit
10/28/2015 6:56:41 AM - requesting resource win-netbackup.ad.cptroot.com.NBU_POLICY.MAXJOBS.vmpolicy
10/28/2015 6:56:41 AM - granted resource win-netbackup.ad.cptroot.com.NBU_POLICY.MAXJOBS.vmpolicy
10/28/2015 6:56:41 AM - estimated 0 Kbytes needed
10/28/2015 6:56:41 AM - begin Parent Job
10/28/2015 6:56:41 AM - begin Application Resolver, Start Notify Script
10/28/2015 6:56:41 AM - Info RUNCMD(pid=4256) started            
10/28/2015 6:56:41 AM - Info RUNCMD(pid=4256) exiting with status: 0         
Status 0
10/28/2015 6:56:41 AM - end Application Resolver, Start Notify Script; elapsed time: 00:00:00
10/28/2015 6:56:41 AM - begin Application Resolver, Step By Condition
Status 0
10/28/2015 6:56:41 AM - end Application Resolver, Step By Condition; elapsed time: 00:00:00
10/28/2015 6:56:41 AM - begin Application Resolver, Resolver Discovery
Status 0
10/28/2015 6:57:57 AM - end Application Resolver, Resolver Discovery; elapsed time: 00:01:16
10/28/2015 6:57:57 AM - begin Application Resolver, Policy Execution Manager Preprocessed
Status 156
10/28/2015 7:03:01 AM - end Application Resolver, Policy Execution Manager Preprocessed; elapsed time: 00:05:04
10/28/2015 7:03:01 AM - begin Application Resolver, Stop On Error
Status 0
10/28/2015 7:03:01 AM - end Application Resolver, Stop On Error; elapsed time: 00:00:00
10/28/2015 7:03:01 AM - begin Application Resolver, End Notify Script
10/28/2015 7:03:01 AM - Info RUNCMD(pid=4760) started            
10/28/2015 7:03:01 AM - Info RUNCMD(pid=4760) exiting with status: 0         
Status 0
10/28/2015 7:03:01 AM - end Application Resolver, End Notify Script; elapsed time: 00:00:00
Status 156
10/28/2015 7:03:01 AM - end Parent Job; elapsed time: 00:06:20
snapshot error encountered(156)

Thanks

koti

[Marianne]

Hopefully one of our resident VMware experts can help here.
I cannot say if outdated vmtools will cause the snapshot failure - can you update vmtools?
Can you take a snapshot from vsphere client GUI?

I notice that the user-id for all tasks performed from the vsphere client is listed as AD\ram, but the user name for the NBU snapshot attempt is ram.
Is this how the credentials were added in NBU?
I am not sure if this is making a difference.

Have you worked through the list of possible reasons for snapshot failure in the TN above?

[chebrolu]

Hi Marianne,

According my knowledge vm backup is working properly.

Can you please confirm from your end as well..If yes, i will try on restore as well..

attached logs to this thread.

JoB status:

======

10/30/2015 2:39:33 AM - Info bpdbm(pid=4252) image catalog cleanup          
10/30/2015 2:39:33 AM - Info bpdbm(pid=4252) Cleaning up tables in the relational database      
10/30/2015 2:39:33 AM - Warning bpdbm(pid=4252) Hot catalog backup is not configured for 'win-netbackup.ad.cptroot.com', catalog cleanup will return partial success until hot catalog backup is configured.
10/30/2015 2:39:33 AM - Info bpdbm(pid=4252) deleting images which expire before Fri Oct 30 02:39:33 2015 (1446197973)  
10/30/2015 2:39:34 AM - Info bpdbm(pid=4252) deleted 0 expired records, compressed 0, tir removed 0, deleted 0 expired copies
the requested operation was partially successful(1)

The job was successfully completed, but some files may have been
busy or unaccessible. See the problems report or the client's logs for more details.

10/30/2015 2:33:55 AM - Info bpbrm(pid=2732) NBU-CLIENT is the host to backup data from     
10/30/2015 2:33:55 AM - Info nbjm(pid=3344) starting backup job (jobid=17) for client NBU-CLIENT, policy vmpolicy, schedule vmschedule  
10/30/2015 2:33:55 AM - estimated 0 Kbytes needed
10/30/2015 2:33:55 AM - Info nbjm(pid=3344) started backup (backupid=NBU-CLIENT_1446197635) job for client NBU-CLIENT, policy vmpolicy, schedule vmschedule on storage unit disk_storageunit
10/30/2015 2:33:55 AM - started process bpbrm (2732)
10/30/2015 2:33:56 AM - Info bpbrm(pid=2732) reading file list from client        
10/30/2015 2:33:56 AM - Info bpbrm(pid=2732) starting bpbkar32 on client         
10/30/2015 2:33:56 AM - connecting
10/30/2015 2:33:56 AM - connected; connect time: 00:00:00
10/30/2015 2:34:01 AM - Info bpbkar32(pid=4028) Backup started           
10/30/2015 2:34:01 AM - Info bptm(pid=2172) start            
10/30/2015 2:34:01 AM - Info bpbkar32(pid=4028) CONTINUE BACKUP received.          
10/30/2015 2:34:01 AM - Info bptm(pid=2172) using 262144 data buffer size        
10/30/2015 2:34:01 AM - Info bptm(pid=2172) setting receive network buffer to 1049600 bytes      
10/30/2015 2:34:01 AM - Info bptm(pid=2172) using 30 data buffers         
10/30/2015 2:34:02 AM - Info bptm(pid=2172) start backup           
10/30/2015 2:34:02 AM - begin writing
10/30/2015 2:40:58 AM - Info bptm(pid=2172) waited for full buffer 22216 times, delayed 26650 times    
10/30/2015 2:40:58 AM - Info bpbkar32(pid=4028) bpbkar waited 0 times for empty buffer, delayed 0 times.   
10/30/2015 2:41:43 AM - Info bptm(pid=2172) EXITING with status 0 <----------        
10/30/2015 2:41:43 AM - Info bpbrm(pid=2732) validating image for client NBU-CLIENT        
10/30/2015 2:41:44 AM - Info bpbkar32(pid=4028) done. status: 0: the requested operation was successfully completed    
10/30/2015 2:41:44 AM - end writing; write time: 00:07:42
the requested operation was successfully completed(0)

Thanks

koti

[Marianne]

The Vmware backup looks good - status 0.
(The image cleanup job is exiting with status 1 because you have not configured a CatalogBackup - not related to this discussion.)

We have now helped you to solve the 2 problems that you have started this discussion for:

1. Creation of a Storage Unit for backups

2. Configuring VMware backup policy.

Please close off this discussion:  select one or more posts that have helped you to solve these issues to mark Solution (use 'Request Split Solution' link to select more than one solution). 

If you need assistance with restore, please start a new discussion.

[chebrolu]

Thank you very much Marianne for your support and quick help.

[Marianne · Accepted solution]

Please remember to close off this discussion by marking solution or 'split solution'.