maksh84
Contributor
Contributor

VCSA 7.0 restore issue

I am restoring VCSA 7.0 from Backup which is on FTP. while Step 1 is completed successfully step 2 is getting the error with below statement

Metadata and system validation failed.

Error: Unknown system resource type vtsdblog

Error: Unknown system resource type vtsdb

and so on attached.

I have installed the VCSA 7.0 with default settings and backup taken on FTP. Now when restoring it from backup it throws these errors any clue please ?

Thanks

Manish

0 Kudos
7 Replies
ryanrpatel
Enthusiast
Enthusiast

Try this...

  1. Shut down the VCSA created during stage 1 of restore.
  2. Edit settings of virtual machine.

    Ensure the following settings match the vCenter Server Appliance which was backed up:
    - CPU Hot Add
    - Memory Hot Add
    - Memory assigned
  3. Once settings have been changed and saved, power on virtual machine.
  4. Connect to restored vCenter Server Appliance on port 5480 and continue with restore.
0 Kudos
maksh84
Contributor
Contributor

Thanks for reply.

I have tried all these setting and tried again but no luck.

It has same problem popping up everytime.

Thanks

Manish Sharma

0 Kudos
Raudi
Expert
Expert

Did you created the backup with the same version and same build of the VCSA?

0 Kudos
maksh84
Contributor
Contributor

Yes, all versions are same. However as I am testing the backup and restore, I am now reconfiguring the VCSA (as it's in my test lab) and again take the backup and will try to restore.

I will update here my result once I repeat the same.

Thanks

0 Kudos
jefftse
Contributor
Contributor

what happened to this?  I'm getting the same thing.  These Vcenter updates are terrible.  It screwed me up every time. 

0 Kudos
Raudi
Expert
Expert

A few days ago i restored a VCSA 7.0.0a from my backup, firtst i got the metadata validation error too, and a additional info that i should increase the memory from 12 to 16 gb, after i had done that and tryed the restore again all works fine.

So it is important that the new VCSA VM is identical to the source VM...

0 Kudos
MillardJK
Enthusiast
Enthusiast

That error is a horrible one, mostly because it doesn't really tell you what's going on...

The 'backup-metadata.json' in the backup has a section that indicates the size (in GB) that each volume requires to restore. If that size doesn't match up with (or is exceeded by) volumes in your new vCenter, it throws that error.

Other posters are correct: if you stop the new vCenter, and balloon the size of the volumes to the size expected by the JSON data, it will pass muster.

Alternatively, if you know that the existing volumes will store the restored data (ie, you know from before that >25% free space was available in the volume), you can instead edit the JSON for the volume to be the size-as-deployed instead of the original size. This is one nice way to reduce space consumed by the VCSA: in my case, I was able to shrink the "seat" and "vtsdb" volumes from 550G each to 25G, and still have *tons* of capacity still in the volumes.

——
Jim Millard
Kansas City, MO USA