VCSA VAMI backup retention might not be honored from VCSA 7.0U2 with few FTP or HTTP backup servers.
search cancel

VCSA VAMI backup retention might not be honored from VCSA 7.0U2 with few FTP or HTTP backup servers.

book

Article ID: 318147

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:

  • VCSA VAMI backup retention is not honored in VCSA 7.0U2
  • Recreating the policy has no affect on the issue
  • Log snippets are similar to below (date and time variables will change per environment)

 

/var/log/vmware/applmgmt/backupScheduelerCronJob.log

Error Code : 4312
2021-07-09 00:00:01,872 65336 Starting the scheduled retention jobs.
2021-07-09 23:00:01,671 12409 Issuing the scheduled backup request for schedule: default.
Error Code : 4312

 

  • Manually running a curl command to delete files fails with a 550 error
  • FTP log example for 7.0 delete command (date and time variables will change per environment)

2022-02-14 00:00:05 10.167.134.166 Domain\Administrator 10.126.3.15  21 dele /vCenter/sn_sc2-10-187-154-147.nimbus.eng.vmware.com/S_7.0.2.00200_20220213-235504_/backup-metadata.json 250 0 0 65acd21b-9dd0-40d9-bbdd-083d73da52c0 /vCenter/sn_sc2-10-187-154-147.nimbus.eng.vmware.com/S_7.0.2.00200_20220213-235504_/backup-metadata.json

 

  • FTP log for 6.7 delete command (date and time variables will change per environment)

2022-02-14 16:31:02 10.196.84.252 Domain\Administrator 10.126.3.15  21 dele vCenter/sn_sc2-10-186-84-242.eng.vmware.com/M_6.7.0.50000_20220214-162720_/backup-metadata.json 250 0 0 4e2d9118-ecbc-46af-882a-a190fb8fc5ef /vCenter/sn_sc2-10-186-84-242.eng.vmware.com/M_6.7.0.50000_20220214-162720_/backup-metadata.json

 

 

Environment

VMware vCenter Server 7.0.x

Cause

  • The path in the FTP logs doesn't include user name or the folder configured for ftp site. This is same for retention in both 6.7 and 7.0 setups.
  • 6.7 has an older curl version 7.59.0 which takes the path mentioned in the delete command (ftp) and keeps and keeps doing CWD (Change working directory) internally in curl and then deletes the mentioned file/folder.
  • In 7.0, if we provide the path starting with /<path>, it considers this as an absolute path and directly try to access/perform operations. So, in this case /vCenter doesn't seems to be in the root directory
  • This is due to a change in upstream curl from 7.67.0 onwards making this an issue present in 7.0

Resolution

The issue is resolved in vCenter Server 7.0 Update 3f

 

Powered by Wolken Software