File-Based Backup and Restore – VCHA

The backup/restore operation in embedded linked mode with VCHA enabled, will work exactly as it is today. The backup can be performed on the primary node. During recovery operation, VCHA configuration will be destroyed. User has to reconfigure VCHA after restore is complete.

However, the backup data does not preserve the VCHA Data. Hence, VCHA has to be recreated upon restore. The backup-metadata.json file would have the NIC information of the node from which the backup was initiated.

"MultiHoming": {
    "defaultNic": "nic0",
    "interfaces": [
        {
            "name": "nic0",
            "status": "up",
            "mac": "00:0c:29:de:7a:46"
        },
        {
            "name": "nic1",
            "status": "up",
            "mac": "00:50:56:b7:82:4c"
        }
    ],
    "totalNics": 2,
    "ipv4": [
        {
            "interface": "nic0",
            "mode": "static",
            "address": "10.109.38.25",
            "prefix": 20,
            "defaultGateway": "10.109.47.253",
            "updateable": true
        },
        {
            "interface": "nic1",
            "mode": "static",
            "address": "192.168.5.10",
            "prefix": 24,
            "defaultGateway": "",
            "updateable": true
        }
    ],

Note: All the 3 nodes has to be Shut down before the restore.

During the reconciliation process of the restore, VCHA would be destroyed.

/var/log/vmware/applmgmt/reconciliation.log

2021-08-25T11:02:36.623 [20210825-110159-18356314] [MainProcess:PID-12015] [ReconciliationManager::DoReconciliation:ReconciliationManager.py:180] INFO: Performing component specific post restore operations.
2021-08-25T11:02:36.623 [20210825-110159-18356314] [MainProcess:PID-12015] [Common::ComponentsPostRestore:Common.py:476] INFO: Component post-restore.
2021-08-25T11:02:36.630 [20210825-110159-18356314] [MainProcess:PID-12015] [Common::ComponentsPostRestore:Common.py:481] INFO: Post-restore comp name vcha comp script /etc/vmware/backup/component-scripts/vcha/vcha-post-restore.py.
2021-08-25T11:02:36.631 [20210825-110159-18356314] [MainProcess:PID-12015] [Proc::RunCmdForOutput:Proc.py:537] INFO: Executing command: /etc/vmware/backup/component-scripts/vcha/vcha-post-restore.py.

/var/log/vmware/vcha/vcha-post-restore.log

2021-08-25T11:02:37.318Z INFO vcha-post-restore **** START: vcha post restore actions ****
2021-08-25T11:02:42.575Z INFO vcha-post-restore destroyVcha finished. status: [0], stdout: [logs available at: /var/log/vmware/vcha
2021-08-25T11:02:40.558Z  Running command: ['/usr/lib/applmgmt/networking/bin/firewall-reload']
2021-08-25T11:02:41.482Z  Done running command
], stderr: [2021-08-25T11:02:38.651Z  Warning: service vMon is not running. State of service vcha is STOPPED.
]
2021-08-25T11:02:42.575Z INFO vcha-post-restore **** FINISH: vcha post restore actions ****

In the Series:

• File-Based Backup and Restore – vCenter
• FBBR – Troubleshooting – Using Self Backup
• FBBR – Troubleshooting – FTP Backup
• FBBR – Troubleshooting – FTP Retention
• FBBR – Troubleshooting – FTPS Backup
• FBBR – Troubleshooting – FTPS Retention
• FBBR – Troubleshooting – HTTP
• FBBR – Troubleshooting – HTTPS Backup
• FBBR – Troubleshooting – HTTPS Retention
• FBBR – Troubleshooting – SCP
• FBBR – Troubleshooting – SFTP
• FBBR – Troubleshooting – SFTP Backup
• FBBR – Troubleshooting – SFTP Retention
• FBBR – Troubleshooting – NFS Backup
• FBBR – Troubleshooting – SMB Backup
• FBBR – Troubleshooting – SMB – 6.x/Upto 7.0U3e
• FBBR – Troubleshooting – SMB – From 7.0U3f/8.x
• File-Based Backup and Restore – Strict Certificate Validation
• File-Based Backup and Restore – Steps to Restore
• File-Based Backup and Restore – VCHA