cancel
Showing results for 
Search instead for 
Did you mean: 

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

chebrolu
Level 4

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

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified

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

View solution in original post

27 REPLIES 27

Nicolai
Moderator
Moderator
Partner    VIP   

You got two different problems.

Can you show us:

bppllist NAME-OF-POLICY -L

and

bpstulist  -L

With the requested information available it will be easier to help you.

NB: The use of IP adresses is not support, you need to use name (screen shot 1).

Marianne
Level 6
Partner    VIP    Accredited Certified
Which machine are you trying to use as VMware backup host? Master? Media server? A NBU client? From the error message it seems that NBU is not installed on the IP address that you are trying to use. As Nicolai said - you should be using hostnames, not IP addresses. What type of Storage Unit did you configure to backup to? Disk? What type of disk? Tape?

chebrolu
Level 4

Hi Nicolai/Marianne,

Thanks for your quick response.

C:\Program Files\Veritas\NetBackup\bin\admincmd>bppllist.exe t1 -L

Policy Name:       t1
Options:           0x0
template:          FALSE
audit_reason:         ?
Names:             (none)
Policy Type:       VMware (40)
Active:            yes
Effective date:    10/20/2015 05:00:13
File Restore Raw:  yes
Mult. Data Stream: no
Perform Snapshot Backup:   yes
Snapshot Method:           VMware_v2
Snapshot Method Arguments: nameuse=0,Virtual_machine_backup=2,trantype=san:hotad
d:nbd:nbdssl,disable_quiesce=0,file_system_optimization=1,exclude_swap=1,drive_s
election=0,snapact=2,skipnodisk=0,post_events=1
Perform Offhost Backup:    yes
Backup Copy:               0
Use Data Mover:            no
Data Mover Type:           -1
Use Alternate Client:      no
Alternate Client Name:     50.6.0.37
Use Virtual Machine:      1
Hyper-V Server Name:     (none)
Enable Instant Recovery:   no
Policy Priority:   0
Max Jobs/Policy:   Unlimited
Disaster Recovery: 0
Collect BMR Info:  no
Keyword:           (none specified)
Data Classification:       -
Residence is Storage Lifecycle Policy:    no
Client Encrypt:    no
Checkpoint:        no
Residence:         -
Volume Pool:       NetBackup
Server Group:      *ANY*
Granular Restore Info:  no
Exchange Source attributes:              no
Exchange 2010 Preferred Server: (none defined)
Application Discovery:      yes
Discovery Lifetime:      28800 seconds
ASC Application and attributes: (none defined)
Generation:      1
Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
Use Accelerator:  no
Client/HW/OS/Pri/DMI:  50.6.0.37 VMware Virtual_Machine 0 0 0 0 ?
Include:           vmware:/?filter=Displayname Contains "win-2k12"
Schedule:              Full
  Type:                FULL (0)
  Frequency:           7 day(s) (604800 seconds)
  Maximum MPX:         1
  Synthetic:           0
  Checksum Change Detection: 0
  PFI Recovery:        0
  Retention Level:     1 (2 weeks)
  u-wind/o/d:          0 0
  Incr Type:           DELTA (0)
  Alt Read Host:       (none defined)
  Max Frag Size:       0 MB
  Number Copies:       1
  Fail on Error:       0
  Residence:           (specific storage unit not required)
  Volume Pool:         (same as policy volume pool)
  Server Group:        (same as specified for policy)
  Residence is Storage Lifecycle Policy:         0
  Schedule indexing:     0
  Daily Windows:
   Day         Open       Close       W-Open     W-Close
   Sunday      018:00:00  029:00:00   018:00:00  029:00:00
   Monday      018:00:00  029:00:00   042:00:00  053:00:00
   Tuesday     018:00:00  029:00:00   066:00:00  077:00:00
   Wednesday   018:00:00  029:00:00   090:00:00  101:00:00
   Thursday    018:00:00  029:00:00   114:00:00  125:00:00
   Friday      018:00:00  029:00:00   138:00:00  149:00:00
   Saturday    018:00:00  029:00:00   162:00:00  173:00:00 005:00:00

C:\Program Files\Veritas\NetBackup\bin\admincmd>
C:\Program Files\Veritas\NetBackup\bin\admincmd>
C:\Program Files\Veritas\NetBackup\bin\admincmd>
C:\Program Files\Veritas\NetBackup\bin\admincmd>bpstulist.exe -L
no entity was found

C:\Program Files\Veritas\NetBackup\bin\admincmd>bpstulist.exe -U
no entity was found

C:\Program Files\Veritas\NetBackup\bin\admincmd>bpstulist.exe -L
no entity was found

C:\Program Files\Veritas\NetBackup\bin\admincmd>

 

Using VMware backup host as a master server and also configured backup host with hostname instead of IP address.

 

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd.exe -pn
expecting response from server win-netbackup.ad.cptroot.com
win-netbackup.ad.cptroot.com *NULL* 10.114.12.205 56900

C:\Program Files\Veritas\NetBackup\bin>

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd.exe -hn win-netbackup.ad.cptroo
t.com
host win-netbackup.ad.cptroot.com: win-netbackup.ad.cptroot.com at fc00:10:114:1
3:3541:9339:6453:daf1
host win-netbackup.ad.cptroot.com: win-netbackup.ad.cptroot.com at 10.114.12.205

aliases:     win-netbackup.ad.cptroot.com     fc00:10:114:13:3541:9339:6453:daf1
     10.114.12.205

C:\Program Files\Veritas\NetBackup\bin>

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd.exe -ip 10.114.12.205
host 10.114.12.205: win-netbackup.ad.cptroot.com at fc00:10:114:13:3541:9339:645
3:daf1
host 10.114.12.205: win-netbackup.ad.cptroot.com at 10.114.12.205
aliases:     win-netbackup.ad.cptroot.com     fc00:10:114:13:3541:9339:6453:daf1
     10.114.12.205

C:\Program Files\Veritas\NetBackup\bin>

I'm trying to configure stoage unit as disk,but unable to configure storage unit.Please have a look into snapshot attached to this discussion.

 

Thanks

koti

Marianne
Level 6
Partner    VIP    Accredited Certified

So, 2 separate issues.

  1. VMware backup host.
    Your opening post shows that you have configured IP address 50.6.0.37 as VMware backup host.
    This is not your master server : win-netbackup.ad.cptroot.com at 10.114.12.205
    Please have another look at your config and ensure that you choose the backup server as VMware backup host.
    See NBU for VMware Admin Guide: 
    http://www.veritas.com/docs/000003337 
     
  2. No Storage Unit has been configured.
    To create a BasicDisk Storage Unit, use 'Storage Unit' in Administration section of the GUI.
    See chapter 10 & 11 in NBU Admin Guide I: http://www.veritas.com/docs/000003071 

Use 'Attachments' links to download the pdf's.

chebrolu
Level 4

Hi Marianne,

 

I would to share my config with you.please correct me if im wrong on configs.

1) I have installed Netbackup software on windows 2008 server and configured as master server and configure window IP/hostname address as master server i.e 10.114.12.205

2)Login into NBU and double click on master server under host properties

3)Add VMware acess host as ESXI host ip address i.e 50.6.0.37 and click ok.

4) Restarted netbackup services using below link
 
https://www.veritas.com/support/en_US/article.TECH...

5) click on virtual machine servers under credentails

6)Right click on empty page and select New 

7) add the virtual machine server as ESXI host IP address

8) select virtual machine server type as ESX and provided username/password and click OK.

9) trying to add policy hence the issue.

 

Can you please clarify me what is my vmware backup host and master server here i.e 50.6.0.37 or 10.114.12.205?

ESXI IP 50.6.0.37

window NIC IP 10.114.12.205

 

 

Thanks

koti

 

Marianne
Level 6
Partner    VIP    Accredited Certified

The VMware Access host or Backup host is the machine that will read the data from the datastore to back it up.
This is NOT the ESX/ESXi host.

The Backup host is where NBU is installed. it can be:
1) The master server
2) A media server or NBU Appliance
3) A NetBackup client

 

The ESX/ESXi host is added when you add credentials for the Backup Host in order to access/read data on the VMs on the ESX host.

Please see Overview of NetBackup tasks in the NBU for VMware Guide (link above).

Phase 1: 
Install the NetBackup master server and media server 
(Configure backup devices and test normal OS backups before proceeding.)

Phase 2: 
Install the NetBackup Enterprise Client license on the master server.

Phase 3: 
Add the VMware backup host to your NetBackup configuration.
See “Adding the VMware backup host to NetBackup” on page 39.

Phase 4:
Set NetBackup access credentials for the VMware vCenter or VirtualCenter
(if any), or for VMware ESX servers.
See “Adding NetBackup credentials for VMware” on page 40. 

Phase 5:
Create a NetBackup policy for VMware.

 

Please take time and read through the manual before attempting another backup.

chebrolu
Level 4

Thanks you very much Marianne.

I will go through above manual and let you know any queries from my side..

 

chebrolu
Level 4

Hi Marianne,

I have followed same steps which was there in vmware backup pdf.

Policy sucessfully created but unable to take virtual machine backup.Attached screenshot please check and let me know anything i missed out here.

Steps:

To back up a virtual machine manually from an existing policy
1 Click on Policies in the NetBackup Administration Console, select the policy, and click Actions > Manual Backup.

2  Select the type of schedule for the backup i.e FULL

3  Select the clients (virtual machines) to back up.

4  Click OK to start the backup.

5  To see the job progress, click Activity Monitor in the NetBackup Administration Console.

Thanks

koti

Marianne
Level 6
Partner    VIP    Accredited Certified

1. Have you gone through the steps in the Admin Guide to create a Storage Unit?

Can you create a test policy to backup a small folder on the backup server to this Storage Unit? 
Policy type: MS-Windows
Select the Storage Unit that you have created in previous step in the Policy Attributes -> Policy Storage (Do not leave as Any Available)
Add a Schedule in the relevant tab (no need for backup window)
Add the master server hostname in Clients tab
Add/Select a small folder in Backup Selection.
Run this policy.
Do not proceed unless backup to the Storage Unit is working.

2. It seems you have added the ESX host IP address in Clients tab.
You cannot backup the ESX host as no backup software is installed on it.
Please follow instructions in the NBU for VMware Guide to browse for VMs to be backed up or read up on VMware Intelligent Policies.

 

*** EDIT ***

There are lots of useful information in this post as well:

 VMware HOWTO 

It seems that you have missed basic conceps as far as NetBackup configuration and VMware backup is concerned.
Please get MS-Windows backup to work first of all.
Go through Chapter 1 and 2 of the VMware for NBU Guide again to understand concepts and configuration steps.

chebrolu
Level 4

Hi Marianne,

I have followed same steps which was mentioned in the earlier thread.

Storage unit is not working and also gone through steps mentioned in admin guide also.

trying take backup a small folder i.ec:/inetpub on the backup server to this Storage Unit.Not working

Please let me know something i missed out here.

 

Thanks

koti

Marianne
Level 6
Partner    VIP    Accredited Certified
Please show us Storage Unit config (bpstulist -L) and test policy config (bppllist ( policy-name ) -U) as before.

chebrolu
Level 4

C:\Program Files\Veritas\NetBackup\bin\admincmd>bpstulist -L

Label:                storage1
Storage Unit Type:    Disk
Media Subtype:        Basic (1)
Host Connection:      win-netbackup.ad.cptroot.com
Concurrent Jobs:      4
On Demand Only:       yes
Path:                 "C:\inetpub"
Robot Type:           (not robotic)
Max Fragment Size:    524288
Max MPX:              1
Stage data:           no
Block Sharing:        no
File System Export:   no
High Water Mark:      98
Low Water Mark:       80
Ok On Root:           no

C:\Program Files\Veritas\NetBackup\bin\admincmd>bppllist test -U
------------------------------------------------------------

Policy Name:       test

  Policy Type:         MS-Windows
  Active:              yes
  Effective date:      10/27/2015 07:27:18
  Backup network drvs: no
  Collect TIR info:    no
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           storage1
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      28800 seconds
ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  Windows-x64   Windows2008   win-netbackup.ad.cptroot.com

  Include:  C:\inetpub

  Schedule:              test
    Type:                Full Backup
    Frequency:           every 7 days
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (2 weeks)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
   Daily Windows:


C:\Program Files\Veritas\NetBackup\bin\admincmd>

Marianne
Level 6
Partner    VIP    Accredited Certified
Are you serious? Your Storage Unit where you want to backup to is C:\inetpub? And the data you want to backup to this STU is also C:\inetpub? Please specify an empty volume as STU as per NBU Admin Guide I.

chebrolu
Level 4

Hi Marianne,

As you said,i have created empty volume under disk storage services and also trying to take MS-Windows backup,Still it was failed.

FYI: while configuring disk storage services i have choosed F:  drive as empty volume.

And also while creating the test policy chooses D:/programfile/vmware directory as backup.

Attached logs to this thread.
 

Job Status details:

10/28/2015 2:59:53 AM - begin
10/28/2015 2:59:53 AM - Info nbdelete(pid=4432) deleting expired images. Media Server: win-netbackup.ad.cptroot.com Media: @aaaab     
10/28/2015 2:59:53 AM - Info bpdm(pid=5060) started            
10/28/2015 2:59:53 AM - started process bpdm (5060)
10/28/2015 2:59:53 AM - requesting resource @aaaab
10/28/2015 2:59:53 AM - granted resource MediaID=@aaaab;DiskVolume=F:\;DiskPool=diskpool;Path=F:\;StorageServer=win-netbackup.ad.cptroot.com;MediaServer=win-netbackup.ad.cptroot.com
10/28/2015 2:59:54 AM - Info bpdm(pid=5060) initial volume F:\: Kbytes total capacity: 62913532, used space: 93824, free space: 62819708
10/28/2015 2:59:54 AM - Info bpdm(pid=5060) ending volume F:\: Kbytes total capacity: 62913532, used space: 93824, free space: 62819708
10/28/2015 2:59:54 AM - end ; elapsed time: 00:00:01
the requested operation was successfully completed(0)

10/28/2015 3:04:05 AM - Info nbdelete(pid=4436) deleting expired images. Media Server: win-netbackup.ad.cptroot.com Media: @aaaab     
10/28/2015 3:04:05 AM - Info bpdm(pid=2268) started            
10/28/2015 3:04:05 AM - started process bpdm (2268)
10/28/2015 3:04:05 AM - Info bpdm(pid=2268) initial volume F:\: Kbytes total capacity: 62913532, used space: 93824, free space: 62819708
10/28/2015 3:04:05 AM - Info bpdm(pid=2268) ending volume F:\: Kbytes total capacity: 62913532, used space: 93824, free space: 62819708
10/28/2015 3:04:05 AM - end ; elapsed time: 00:00:00
the requested operation was successfully completed(0)
10/28/2015 3:04:05 AM - requesting resource @aaaab
10/28/2015 3:04:05 AM - granted resource MediaID=@aaaab;DiskVolume=F:\;DiskPool=diskpool;Path=F:\;StorageServer=win-netbackup.ad.cptroot.com;MediaServer=win-netbackup.ad.cptroot.com

===============================
C:\Program Files\Veritas\NetBackup\bin\admincmd>bpstulist -L

Label:                disk_storageunit
Storage Unit Type:    Disk
Media Subtype:        DiskPool (6)
Host Connection:      _STU_NO_DEV_HOST_
Concurrent Jobs:      2
On Demand Only:       yes
Robot Type:           (not robotic)
Max Fragment Size:    524288
Max MPX:              1
Block Sharing:        no
File System Export:   no
Ok On Root:           no
Disk Pool:            diskpool
Snapshots:            no
Replication Primary:  no
Replication Source:   no
Replication Target:   no
Mirror            :   no
Independent       :   no

C:\Program Files\Veritas\NetBackup\bin\admincmd>bppllist -U
Policy:            test

C:\Program Files\Veritas\NetBackup\bin\admincmd>bppllist test -U
------------------------------------------------------------

Policy Name:       test

  Policy Type:         MS-Windows
  Active:              yes
  Effective date:      10/28/2015 02:55:10
  Backup network drvs: no
  Collect TIR info:    no
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           disk_storageunit
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      28800 seconds
ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  Windows-x64   Windows2008   win-netbackup.ad.cptroot.com

  Include:  D:\Program Files\VMware

  Schedule:              schedule1
    Type:                Full Backup
    Frequency:           every 1 day
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (2 weeks)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:


C:\Program Files\Veritas\NetBackup\bin\admincmd>

Im suspecting that higher high water mark,shall i reduce it may reolve the issue or anything i missed out here

 

 

Thanks

koti

Marianne
Level 6
Partner    VIP    Accredited Certified
Status 71 means the path in Backup Selection does not exist. Is there such a folder (D:\Program Files\VMware) on the backup server?

chebrolu
Level 4

Yes,Marianne your right.file path doesn't exists.

I have changed the path and tried once again.It's working fine.Can you Please snap and confirm it whether it is working properly or not.

Here one more doubt ,in activity monitoring topology area,server i.e win-netbackup.ad.cptroot.com  always red color circle mark.may i know what it means?

Till now i have tried to take the MS-window backup.I think it is working fine.I will go ahead and take VM backup and also create a new policy for VM backup?

Attached snapshot to this thread.

Thanks

koti

sdo
Moderator
Moderator
Partner    VIP    Certified

Are you sure a 9 KB backup contains a valid backup?  Looks a tad on the small side to me.

Is this a production backup environment, with real business servers?

chebrolu
Level 4

Yes sdo,it is production backup environement.First of all i would like to check whether MS-windows backup is working fine or not.

Now i have tried to take VM backup,it 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
Level 6
Partner    VIP    Accredited Certified
Well, whatever was that small was backed up successfully. You have now solved your 1st problem - the STU issue. Go ahead and create VMware policy. Be sure you add VMs to be backed up and not the EXi server as previously.