cancel
Showing results for 
Search instead for 
Did you mean: 

Restore is failing with error code 2820

Mack_Disouza
Level 4

Hello Guys, 

I am trying to restore VM backup .This VM backup was taken when VM was powered-off.

Now i am trying to restore this backup to its original location and getting the error code 2820.

Restore job logs are attached too. if anybody can help or guide ?

1 ACCEPTED SOLUTION

Accepted Solutions

Hello Guys,

Thanks for your inputs and suggestions.

Below is the resolution to this case:-

  1. Veritas support suggested that there is an emergency engineering binary (EEB) to be applied on Netbackup version 8.3.0.1 to get the desired vTPM enabled VM backup and restore.
  2. The advised EEB is to be applied only on version 8.3.0.1 to support vTPM enabled VM on vcenter 7.0.U1.This required EEB can be obtained from veritas technical support .
  3. Upgraded master server from 8.3 to 8.3.0.1 successfully.
  4. EEB (ebinstaller_4014637_1_linuxR_x86_2_6_32-210122160951) was applied successfully to backup/restore/vmware access host after master server version upgrade.
  5. Triggered the full vm recovery of the deleted vm and restore was successful.

 

View solution in original post

17 REPLIES 17

pats_729
Level 6

@Mack_Disouza 

Are you trying to restore full vm or some files to same vm ?

Also mention... whats the NetBackup version you have

NetBackup Master and OS

NetBackup Media and OS

NB version on Backup Host  and OS

Thanks

Hello Pats,

I am trying to restore a full vm to the original location as the individual files required the NB agent to be installed and as i said earlier,I've taken the backup when it was in powered-off state.

The netbackup master is media server and vmware access host too.

Netbackup master : OS --> Red Hat Enterprise Linux Server release 7.4 (Maipo).

Netbackup master version :--> 8.3.0.1 build:0042

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@Mack_Disouza 

Can you show us screenshots of the entire restore process? From the very 1st screen where you select the restore type, please.

The restore log looks like NBU is trying to connect to the client. This should not happen with a full VM restore.

@Marianne 

Screen attached.

Below are the logs:-

---------------------

22 janv. 2021 05:21:47 - begin Restore
22 janv. 2021 05:21:47 - Info bprd (pid=22668) Found (94,882) files in (1) images for Restore Job ID 12959.xxx
22 janv. 2021 05:21:55 - restoring from image Win2k19_1611220926
22 janv. 2021 05:22:12 - Info bprd (pid=22668) Searched (124,506) files of (94,882) files for Restore Job ID 12959.xxx
22 janv. 2021 05:22:12 - Info bprd (pid=22668) Restoring from copy 1 of image created Thu Jan 21 10:22:06 2021 from policy Policy_vc7u1_encrypted
22 janv. 2021 05:22:12 - Info bprd.sfr (pid=22668) Checking OS on destination.  Operation may take CLIENT_CONNECT_TIMEOUT=3600 seconds
22 janv. 2021 05:22:12 - Warning bprd.sfr (pid=22668) cannot set destination platform, dest_clnt_hostname=Win2k19, status=48
22 janv. 2021 05:22:12 - Warning bprd.sfr (pid=22668) Unable to determine destination operating system type. Restore operation may fail if the source and destination operating systems do not match
22 janv. 2021 05:22:14 - Info bpdm (pid=22932) started
22 janv. 2021 05:22:14 - started process bpdm (pid=22932)
22 janv. 2021 05:22:14 - Info bpdm (pid=22932) reading backup image
22 janv. 2021 05:22:14 - Info bpdm (pid=22932) using 30 data buffers
22 janv. 2021 05:22:14 - Info bpdm (pid=22932) spawning a child process
22 janv. 2021 05:22:14 - Info bpbrm (pid=22932) child pid: 22934
22 janv. 2021 05:22:16 - begin reading
22 janv. 2021 05:22:33 - end reading; read time: 0:00:17
22 janv. 2021 05:22:33 - Info bpdm (pid=22932) completed reading backup image
22 janv. 2021 05:22:33 - Info bpdm (pid=22932) EXITING with status 0
22 janv. 2021 05:22:33 - Error bpbrm (pid=23016) bpcd on Win2k19 exited with status 48: client hostname could not be found
22 janv. 2021 05:22:33 - Info tar (pid=0) done. status: 48: client hostname could not be found
22 janv. 2021 05:22:33 - Error bpbrm (pid=23016) client restore EXIT STATUS 48: client hostname could not be found
22 janv. 2021 07:24:34 - restored from image Win2k19_1611220926; restore time: 2:02:39
22 janv. 2021 07:24:34 - end Restore; elapsed time 2:02:47
NetBackup VMware policy restore error  (2820)

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@Mack_Disouza 

You are trying to do a 'Normal Restore' - look at the top of the screen under 'Restore Type'.

This is doing a file-level restore to the client, not a full VM restore via vCenter to the ESXi server.

You need to select Virtual Machine Backup under 'Restore Type'.

The entire process is explained in NBU for VMware manual in chapter 10 under this topic: Restoring the full VMware virtual machine.

@Marianne 

Yes Marianne....You are right. Such a dumb..i am !!

I triggeredrd the VM restore again. Hope it'll work now.

Triggered the restore again after successful restore validation check.

But it failed again.NetBackup VMware policy restore error  (2820).

Restore job logs attached.

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Did you watch the vSphere console after you started the resore? And checked VMware logs?

All of those errors are from VMware, not NBU.

VM is gone from the vsphere console now. I can't see the VM anymore.

One more thing..The VM was vTPM enabled VM.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@Mack_Disouza 

I found this article that matches part of the error you are seeing:

https://www.veritas.com/support/en_US/article.100005440

If this does not solve your problem, you will need bpVMutil log on the Recovery Host that you have selected (should be same as Backup Host. 

Please see Troubleshooting section of NBU for VMware for detailed logging info.

@Marianne :- The VC is added with account as administrator. 

administrator is the top most account in VC. no account above this. It possess all the required permissions.

[root@test ~]# /usr/openv/volmgr/bin/tpconfig -dvirtualmachines

==============================================================================

Virtual Machine Host Name:           vc7u1.vc7nsxt3.local

Virtual Machine Type:                VMware Virtual Center Server

SubType:                             (1)

User Id:                             administrator@vsphere.local

Required Port:                       443

======================================================

Progress log filename : /usr/openv/netbackup/logs/user_ops/root/logs/jbp-26641611302183278353000000038-dbCN5j.log Restore Job Id=12964
08:56:52 (12964.001) Restoring from copy 1 of image created Thu 21 Jan 2021 10:22:06 AM CET from policy Policy_vc7u1_encrypted
08:56:53 (12964.xxx) Restoring to vCenter server vc7u1.vc7nsxt3.local, ESX host 10.1.212.73, Datacenter /Datacenter, Folder /Datacenter/vm/, Display Name Win2k19, Resource Pool/vApp /Datacenter/host/Compute-CLU/Resources, Datastore/Datastore Cluster NFS-DS05
08:56:56 INF - Beginning read-blockmap on server nbu-01 of client Win2k19, reading file /images//Win2k19_1611220926_C1_F1.
08:56:56 (12964.xxx) Executing Virtual machine creation on nbu-01 to server vc7u1.vc7nsxt3.local.
08:56:58 (12964.001) Status of restore from copy 1 of image created Thu 21 Jan 2021 10:22:06 AM CET = Restore failed due to failure to create the virtual machine

08:56:58 (12964.001) The following files/folders were not restored:
08:56:58 (12964.001) UTF - /NFS-DS05/Win2k19/Win2k19-000002.vmdk

08:56:58 (12964.xxx) INF - Status = VMware policy restore error.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
@Mack_Disouza wrote:

VM is gone from the vsphere console now. I can't see the VM anymore.


Have you checked the event logs in vSphere?


One more thing..The VM was vTPM enabled VM.


Always good to mention all relevant info....

Have you checked the 8.3 NBU for VMware manual for anything about vTPM ?
This is obviously putting things in a totally different light.
I have no experience with this.

Yes NetBackup 8.3 supports backup and recovery of vTPM devices.

  • NetBackup supports backup and recovery of VMware NVRAM files and the vTPM devices that are associated with virtual machines.

    • A NetBackup 8.3 or later backup or recovery host is required for NVRAM and vTPM protection. Supported recovery methods include Full VM recovery and VMware Instant Recovery.

    • NetBackup does not support the backup or restore of NVRAM and vTPM for the virtual machines whose display names begin with a period ('.'). An existing VMware limitation prevents downloading or uploading data store files beginning with a period ('.') to a virtual machine's working directory as these appear as hidden files.

  • If the virtual machine was backed up by its display name or UUID, and the display name differs from the host name, note: You must specify the correct destination client for the restore. Use the Specify NetBackup Machines and Policy Type dialog in the NetBackup Backup, Archive, and Restore interface.

  • More can be read in :--> https://www.veritas.com/content/support/en_US/doc/21902280-139625479-0/v19545942-139625479

Required bpVMutil logs are attached.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I can unfortunately not find anything useful in the log.

Maybe additional steps are needed for vTPM backup and restore that is not documented in NBU manual.

I found a doc about vTPM backup and restore that is not NBU related, so, no idea how NBU is doing all of that:
https://vdc-repo.vmware.com/vmwb-repository/dcr-public/8f96698a-0e7b-4d67-bb6c-d18a1d101540/ef536a47...

Probably best to log a call with Veritas Support.
Please mention upfront that your are trying to restore a vTPM VM.

Do you have vxms logs enabled at verbose 8 for this restore. There we might see something interesting why restore... (actually VM creation )failing.

Hello Guys,

Thanks for your inputs and suggestions.

Below is the resolution to this case:-

  1. Veritas support suggested that there is an emergency engineering binary (EEB) to be applied on Netbackup version 8.3.0.1 to get the desired vTPM enabled VM backup and restore.
  2. The advised EEB is to be applied only on version 8.3.0.1 to support vTPM enabled VM on vcenter 7.0.U1.This required EEB can be obtained from veritas technical support .
  3. Upgraded master server from 8.3 to 8.3.0.1 successfully.
  4. EEB (ebinstaller_4014637_1_linuxR_x86_2_6_32-210122160951) was applied successfully to backup/restore/vmware access host after master server version upgrade.
  5. Triggered the full vm recovery of the deleted vm and restore was successful.

 

View solution in original post

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Thanks for the feedback!