Scribd
Upload
293 views11 pages

VCSA 6.7 Backup Solve

The VCSA 6.7 backup failed due to insufficient permissions on the destination backup folder. The user account used for backups did not have read/write permissions to access the remote folder. After granting full control permissions to the folder for the user account, the backup succeeded.

Uploaded by

Clément Minougou
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
293 views11 pages

VCSA 6.7 Backup Solve

The VCSA 6.7 backup failed due to insufficient permissions on the destination backup folder. The user account used for backups did not have read/write permissions to access the remote folder. After granting full control permissions to the folder for the user account, the backup succeeded.

Uploaded by

Clément Minougou
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

VCSA 6.

7 Backup Failed :
Structure
com.vmware.appliance.recov
ery.backup.job.details.info
has a union with a field not
required for this case =
end_time
149272

Share on FacebookShare on Twitter


This error was occurred while I was configuring the VMware vCenter Server Appliance 6.7
and my first VCSA 6.7 Backup Failed with an error. This automated backup scheduler was
introduced in vCenter Server 6.7 and I was very exited to configure this in my environment.

VCSA backup and restoration was there in vCenter Server 6.5 but there was no a way to
automated the VCSA backup in the appliance. Read my previous blog post with related to the
backup and restoration for more information. With vCenter Server 6.5 we had to use the
traditional cron script backups to make it automate and save it in a remote location.
I have setup a FTP server in my network and I have created a folder to store the vCenter
backup files. Once I configured and started the backup this error message appeared on my
web client and backup failed.

Structure com.vmware.appliance.recovery.backup.job.details.info has a union with a field


not required for this case = end_time

VCSA 6.7 Backup Failed : Check Share and


Security Permissions for the Destination
Backup Folder
The user account that I used to create this backup job didn’t have the read/write share
permissions and the relevant security permissions to access the folder.

So I changed the folder share permissions and shared the folder with the user.
I have changed the security permissions as well. In my case I was able to grant the “Full
Control” to the folder to the user account without an Issue.
I re-run the manual backup and it was successful after changing the folder permission

If You Found This Post As Useful Please Rate The Post And Share It!

Click to rate this post!


[Total: 9 Average: 5]
Backup and Restore VCSA 6.7 VMware

Aruna Lakmal
Associate Technical Specialist at Pearson, Sri Lanka. Technology junky, enthusiast, a
VMware vExpert and a blogger with more than 7 years of Experience in Information
Technology more focusing on VMware Virtualization, Microsoft and Datacenter
Technologies.

Get Updates Directly To Your Inbox!


Sign up
Email address :
Show 2 comments

Leave a Comment

Post comment

S P O N S O RS
VMWARE May 31, 2018

vCenter 6.0 Upgrade Error:


Source vCenter Server
Schema Validation Found An
Issue.
92620
Share on FacebookShare on Twitter
This was a different type of incident and I experienced this issue while I’m upgrading the
vCenter server 5.5 to 6.0 and “Source vCenter Server Schema validation found an issue” error
appeared at the start of the upgrade. First of all I would like to tell you this this vCenter was
an old vCenter server with Oracle database which was coming from earlier vCenter server
editions and it was finally upgraded to vCenter server 5.5.

I had to upgrade this vCenter server to vCenter server 6.0 and this error message appeared in
the very beginning of the vCenter upgrade.

Resolution: Please Ensure Extensions Are Compatible With The New VCenter Server And Re-
Register Extensions With The New VCenter Server After Upgrade.

Please Refer To The VSphere Documentation On Extensions, And The Upgrade And
Interoperability Guides. Error: Source VCenter Server Schema Validation Found An Issue.

Resolution: Read The Vcdb_req.Err Log File And Address The Issue Found.
Actually, we can think about the extensions issue later or we can ignore that as we can re-
register them. Actual issue was not with the extensions and “Source vCenter Server Schema
validation found an issue”, that’s was the main concern about this issue.

I opened the “vcdb_req.err” file which was under


“C:\Users\Administrator\AppData\Local\Temp\vcsUpgrade” location
I was able to identify the below errors in the “vcdb_req.err” log as below

1 [HY000](20000) [Oracle][ODBC][Ora]ORA-20000: ERROR ! Missing constraints:


VPX_DATASTORE.FK_VPX_DS_DC_REF_VPX_ENT,VPX_DEVICE.VPX_DEVICE_P
1;
ORA-06512: at line 260

ERROR: Cannot execute statement(rc=-1).


DECLARE
l_text_full VARCHAR2(32767) := NULL;
l_text VARCHAR2(2000) := NULL;
l_verid int;
BEGIN

I was searching a solution for this “ERROR” I was able to find couple of VMware
Knowledge base articles and some database level queries had to directly run on the database
console.

Manual modification to the Database has a Risk! Take a backup of the database and proceed
with the modification
I found the similar errors in VMware KB 2147549 and I wanted to check this in the database.

Those entries were like this


The given queries in the VMware KB article has some query errors and had to modify those
queries in order to do the modification correctly on the DB.

These are the corrected queries to fix the issue

alter table VPX_DEVICE add constraint VPX_DEVICE_P1 primary key


(DEVICE_ID) using index VPX_DEVICE_P1;

alter table VPX_DATASTORE rename constraint FK_VPX_DS_REF_VPX_ENTITY


to FK_VPX_DS_DC_REF_VPX_ENT

alter table VPX_DATASTORE rename constraint FK_VPX_DS_REF_VPX_ENTI


to FK_VPX_DS_REF_VPX_ENTITY

After that I was able to proceed with the upgrade successfully.

A Word Of Advise
Make sure to check and verify the required Database permissions with your database as
mention in this VMware Document.
That’s it, hope this article will help you to fix similar issues in your environment. Normally,
this happens in very old vCenters which are upgraded to different versions.

References:
• VMware Knowledge Base Article (2147549)
• Database Permission Requirements for vCenter Server

If You Found This Post As Useful Please Rate The Post And Share It!

Click to rate this post!

You might also like