VCF 9.0 Backup & Restore — SDDC Manager, vCenter, NSX and the Fleet Management Components
Objectives
- Articulate the VCF 9.0 backup set: the instance-level components (SDDC Manager, vCenter, NSX Manager, file-based) and the fleet-level components (VCF Operations, fleet management, VCF Operations for logs and for networks: image-based; VCF Automation and VCF Identity Broker: file-based), and the method each one uses
- Configure the external SFTP backup target for SDDC Manager from VCF Operations (Administration > SDDC Manager > Backup Settings) and schedule the SDDC Manager, vCenter and NSX Manager file-based backups so their restore points are consistent
- Configure the fleet-level SFTP backup and schedules for VCF Automation and the VCF Identity Broker appliance from Fleet Management > Lifecycle, and define the image-based (VADP) backup jobs for VCF Operations and the fleet management appliance
- Execute and validate a complete backup cycle and document the manifest of files on the SFTP server
- Perform the documented restore procedures: vCenter from a file-based backup (new appliance, management domain first), the first node of a failed NSX Manager cluster, and VCF Automation or the identity broker from the fleet SFTP location
- Compare VCF 9.0 backup and restore with the VCF 5.2 SDDC Manager model and place it in the VCF Instance Recovery timeline for a VCDX defence
Prerequisites
A VCF 9.0 instance with the management domain deployed and healthy: SDDC Manager, management vCenter, NSX Manager cluster, VCF Operations and the VCF Operations fleet management appliance; optionally VCF Automation and a VCF Identity Broker appliance cluster. An external SFTP server reachable from the management network with a service account (for example svc-vcf-bck) and a writable directory (for example /backups/). A VADP-compatible image backup product, or at least a plan for one, for the image-based components.
Prior labs: holodeck-02
Required skills:
- VCF 9.0 architecture: VCF Instance (SDDC Manager, vCenter, NSX, ESX) and fleet-level components (VCF Operations, fleet management, VCF Automation, Identity Broker)
- SFTP server administration (keys, fingerprints, directories, capacity)
- vCenter appliance management interface (VAMI) backup and the vCenter ISO installer Restore path
- NSX Manager backup and restore concepts
- VADP image-based backup concepts
Lab Environment
VCF 9.0 instance: management domain on 4 nested ESX hosts (vSAN) with SDDC Manager, vCenter 9.0, a 3-node NSX Manager cluster, VCF Operations, the fleet management appliance, and optionally VCF Automation and a 3-node VCF Identity Broker appliance. One external SFTP server (192.168.1.100 in the examples) holds the file-based backups; a VADP backup product targets the management cluster for image-based backups.
Mermaid source
graph LR SM[SDDC Manager] -->|file-based, daily 04:02, configured in VCF Operations| SFTP[External SFTP 192.168.1.100 /backups] VC[vCenter 9.0] -->|file-based, daily, same 5-min window| SFTP NSX[NSX Manager cluster] -->|file-based, hourly, configured by SDDC Manager at bring-up| SFTP AUTO[VCF Automation] -->|file-based, fleet SFTP via Fleet Management > Lifecycle| SFTP VIDB[VCF Identity Broker appliance] -->|file-based, fleet SFTP| SFTP OPS[VCF Operations + fleet management + logs + networks] -->|image-based VADP| VADP[Image backup product]
IP Addressing
| Network | Purpose | VLAN |
|---|---|---|
10.1.0.0/20 (Holodeck Site A master CIDR) | Management network on the Holodeck Site A plan from holodeck-02 (SDDC Manager, vCenter, NSX, VCF Operations, fleet management, Automation, Identity Broker); in the Holodeck DNS example esx-01a resolves to 10.1.1.10. Confirm the management subnet, gateway and VLAN in your lab with Get-HoloDeckSubnet -Site a and record them. | Site A management VLAN as reported by Get-HoloDeckSubnet -Site a (Site A uses VLANs 0 and 10-25 by default) |
192.168.1.0/24 | Backup network (SFTP server, VADP backup product) | VLAN 1700 |
Credentials
| System | Username | Password |
|---|---|---|
| VCF Operations | admin (local) | Set at VCF Installer deployment; needs Fleet Management permissions for backup settings |
| SDDC Manager | admin@local | Set at VCF Installer deployment; SSH root used only to test the SFTP connection |
| vCenter appliance management interface | root | Set at VCF Installer deployment (https://<vcenter_fqdn>:5480) |
| NSX Manager | admin | Set at VCF Installer deployment |
| SFTP server | svc-vcf-bck | Created on the SFTP server for this lab; SSH fingerprint recorded |
Tasks
Task 1 Map the VCF 9.0 backup set and the method for each component
RecoverabilityIn VCF 9.0 every VCF Instance still has SDDC Manager, vCenter and NSX Manager in its management domain, and all three are backed up with their native file-based backups; what changed is that SDDC Manager's backup settings are now configured from the VCF Operations console. The fleet-level components use image-based backups (VCF Operations, fleet management, logs, networks) or the fleet SFTP target (VCF Automation, VCF Identity Broker). Knowing which method protects which component, and in what order they are restored, is the VCDX-critical skill.
In VCF Operations, open Inventory and select your VCF Instance. Record the management domain components: SDDC Manager, the management vCenter, the NSX Manager cluster nodes, and the fleet management appliance. Then open Fleet Management > Lifecycle > VCF Management > Components and record the fleet-level components deployed (VCF Operations, fleet management appliance, VCF Automation, VCF Identity Broker, VCF Operations for logs, for networks).
Build the backup-method table from the documentation ('Backup Methods for VMware Cloud Foundation'): Core: vCenter = file-based or image-based (the docs use file-based); ESX = N/A; NSX Manager = file-based; NSX Edge = included in the NSX Manager backup. Management: VCF Operations, VCF Operations fleet management, VCF Operations for logs, VCF Operations for networks = image-based; VCF Identity Broker = file-based; SDDC Manager = file-based or image-based (the docs use file-based). Consumption: VCF Automation = file-based.
Record the scheduling rules from Table 948 'File-Based Backup Jobs': SDDC Manager daily with 7-day retention; vCenter daily with 7-day retention, and the SDDC Manager and all vCenter jobs must start within the same 5-minute window; vSphere Distributed Switch configuration on demand, retaining the last 3; NSX Manager hourly with 7-day retention, configured by SDDC Manager during bring-up. Note the two reasons the docs give for an external SFTP server: it is a prerequisite for restoring SDDC Manager file-based backups, and it decouples the NSX backups from SDDC Manager (by default both are stored on the SDDC Manager appliance).
Compare with VCF 5.2 from your 5.2 lab or documentation: in 5.2 the SDDC Manager UI owned the backup settings (Administration > Backup) and the NSX Manager backup was likewise configured by SDDC Manager; in 9.0 the settings for SDDC Manager move to VCF Operations (Administration > SDDC Manager > Backup Settings) and the fleet-level components gain their own SFTP settings under Fleet Management > Lifecycle. The SDDC Manager appliance, its file-based backup and the 'backup' local account all still exist in 9.0 (VCF Operations even manages the SDDC Manager backup account password).
Write the restore order you will need in Task 5, taken from the VCF Instance Recovery timeline: for the management domain, deploy vCenter and the first NSX Manager node from OVA, deploy SDDC Manager from OVA, restore vCenter, restore NSX Manager, restore SDDC Manager; then recover clusters, remediate NSX on the clusters, recover NSX Edge nodes; then restore VCF Operations and the fleet management appliance from image-based backups, redeploy and restore the VCF Identity Broker from its file-based backup, redeploy and restore VCF Automation from its file-based backup, then VCF Operations for logs and for networks from image-based backups. A workload-domain vCenter is restored only after the management-domain vCenter.
Validation Gate
Check: Inventory of instance-level and fleet-level components, backup-method table, Table 948 schedule rules, 5.2 comparison and the restore order are written down.
Expected: You can state for every management component how it is backed up and where it sits in the recovery order.
Common Errors
Task 2 Configure the SFTP target and schedule the instance-level file-based backups
RecoverabilityThe instance-level set is SDDC Manager, vCenter and NSX Manager. SDDC Manager's site settings and schedule are configured in VCF Operations; the vCenter schedule is configured in the appliance management interface; the NSX Manager backup was configured by SDDC Manager at bring-up and only needs to be verified and, if the SFTP target changed, pointed at the external server.
Prepare the SFTP server: create the service account svc-vcf-bck and the directory /backups/ with write permission, and record the server's SSH RSA key SHA256 fingerprint. The server must support a 2048-bit RSA and a 256-bit ECDSA SSH public key and at least one of rsa-sha2-512 / rsa-sha2-256 and one of ecdsa-sha2-nistp256/384/521 host-key algorithms (additional algorithm requirements apply when FIPS mode is enabled on SDDC Manager). SSH to the SDDC Manager appliance as root and test: sftp svc-vcf-bck@192.168.1.100.
In VCF Operations, navigate to Administration > SDDC Manager, select the VCF Instance, open the Backup Settings tab and click Site Settings. Enter Host FQDN or IP 192.168.1.100, Port 22, Transfer Protocol SFTP, Username svc-vcf-bck, Password, Backup Directory /backups/, verify the automatically retrieved SSH fingerprint and select Confirm Fingerprint, and enter an Encryption Passphrase. Save and Confirm.
On the same Backup Settings tab, click SDDC Manager Configurations, then Edit under Backup Schedule. Set Automatic Backup Enabled, Backup Frequency Weekly with all days selected, Schedule Time 04:02 AM, Take Backup on State Change Enabled, Retain Last Backups 7, Retain Hourly Backups for Days 1, Retain Daily Backups for Days 7. Save, then click Backup Now to verify.
Open the management vCenter's appliance management interface at https://<vcenter_fqdn>:5480 as root. Go to Backup > Configure: Backup location sftp://192.168.1.100/backups/vcenter-mgmt, credentials svc-vcf-bck, schedule Daily at 04:03 (within 5 minutes of the SDDC Manager job), retain the last 7 backups, and set an encryption password. Save, then run Backup Now.
Verify the NSX Manager backup configured by SDDC Manager: log in to NSX Manager, System > Backup & Restore. Confirm the SFTP destination is the external server, the schedule is hourly (interval-based) and that the passphrase is known. If the destination still shows the SDDC Manager appliance, follow 'Reconfigure SFTP Backups for SDDC Manager and NSX Manager' to move it to the external server. Click Start Backup once.
If the instance has a workload domain, repeat step 4 for the workload-domain vCenter (its own directory, start time within the same 5-minute window) and verify its NSX Manager backup as in step 5.
Validation Gate
Check: SDDC Manager site settings and schedule configured in VCF Operations; vCenter file-based backup scheduled within the same 5-minute window; NSX Manager hourly backup verified on the external SFTP server; one on-demand backup of each succeeded.
Expected: The instance-level file-based backup set is complete and consistent.
Common Errors
Task 3 Configure the fleet-level backups: VCF Automation, VCF Identity Broker and the image-based components
RecoverabilityThe fleet-level components have two patterns. VCF Automation and the VCF Identity Broker appliance back up to the fleet SFTP server configured in Fleet Management > Lifecycle. VCF Operations, the fleet management appliance, VCF Operations for logs and for networks are protected by full-VM image-based backups with a VADP-compatible product. Both patterns have consistency rules you must design for.
In VCF Operations, navigate to Fleet Management > Lifecycle, select VCF Management, open the Settings tab and under Backup & Restore select SFTP Settings. Configure the fleet-level SFTP server (the same external server, a separate directory such as /backups/fleet), then for each deployed component (VCF Automation, VCF Identity Broker) click Edit in the action column, choose the hour of day for the backup, enable the retention policy with a count, and Save. Monitor the task on the Tasks page.
Take an on-demand backup of VCF Automation: Fleet Management > Lifecycle > VCF Management > Components, click VCF Automation, click the horizontal ellipsis and choose Backup & Restore > Backup, confirm the SFTP page and click Backup. Repeat for VCF Identity Broker if the appliance cluster is deployed. The documentation recommends an on-demand backup of each before maintenance such as upgrades.
Define the image-based backup jobs for the VADP product from the table in 'Image-Based Backup for VCF Operations': the VCF Operations fleet management appliance (single appliance, quiescing enabled); VCF Operations simple deployment (primary node and collectors, quiescing disabled) or high availability deployment (primary, replica, data nodes and collectors, quiescing disabled). All VCF Operations cluster nodes must be backed up at the same time; it is recommended to take the cluster offline during the backup, and if that is not possible, do not quiesce the file system; do not back up while dynamic threshold calculations are running. Add VCF Operations for logs and for networks nodes as image-based jobs too.
If a VADP product is available in the lab, create and run the jobs; otherwise create the equivalent protection with a vSphere snapshot of each node at the same point in time as a stand-in, and document that a snapshot is not a backup.
Record the restore dependency for the fleet SFTP pattern: restoring the VCF Identity Broker requires the appliances to be running and vCenter, VCF Operations and the fleet management appliance to be available; restoring VCF Automation after two or three lost nodes requires deleting the component, deploying a new VCF Automation instance and restoring from SFTP to the new nodes, while a single lost node is redeployed automatically.
Validation Gate
Check: Fleet SFTP settings and per-component schedules configured; on-demand backups of VCF Automation (and Identity Broker) succeeded; image-based job definitions written for VCF Operations and the fleet management appliance with the consistency rules.
Expected: The fleet-level components are protected with the documented method each.
Common Errors
Task 4 Execute a complete backup cycle and document the manifest
RecoverabilityA backup set that has never been exercised is a hypothesis. Run every job once, in the order and windows you designed, then list what landed where so the recovery runbook can find it without guessing.
Trigger the SDDC Manager backup (VCF Operations > Administration > SDDC Manager > Backup Settings > SDDC Manager Configurations > Backup Now) and, within five minutes, the vCenter backup(s) from the appliance management interface (Backup > Backup Now). Record the start times.
Trigger an NSX Manager backup (System > Backup & Restore > Start Backup) for each NSX Manager cluster of the instance.
Trigger the fleet-level backups: VCF Automation and VCF Identity Broker via Fleet Management > Lifecycle > VCF Management > Components > (component) > Backup & Restore > Backup. Run the image-based jobs for VCF Operations and the fleet management appliance (or the stand-in snapshots).
On the SFTP server, list the result: ls -lah /backups/ /backups/vcenter-mgmt /backups/fleet/vcf/backups/*/*/* and df -h /backups. Record file names, sizes and timestamps.
Write the manifest /backups/MANIFEST-<date>.txt: one line per component with method, location, timestamp, size, retention, and where the encryption passphrase or password is held (by reference, not value). Add the image-based jobs with the backup product's job names.
Add the recommended on-demand triggers to your runbook from 'Backup and Restore of VMware Cloud Foundation': take a manual backup after a successful recovery, after resolving asynchronously reported errors, after resolving an incomplete SDDC Manager workflow, after a failed scheduled backup, and immediately before a system upgrade.
Check VCF Operations password management for the SDDC Manager backup account: Fleet Management > Passwords > VCF Instances > (instance) shows SDDC Manager with its backup account. Confirm its status is current and note that this is the only SDDC Manager local account managed there.
Validation Gate
Check: One successful backup of every component; SFTP listing and manifest written; on-demand trigger list in the runbook; SDDC Manager backup account verified.
Expected: The complete backup set exists on the external targets and is documented.
Common Errors
Task 5 Restore: vCenter from a file-based backup, the first NSX Manager node, and a fleet component
RecoverabilityThe restore procedures in VCF 9.0 are appliance-native and ordered. vCenter is restored by deploying a new appliance with the vCenter ISO installer and restoring from SFTP; a fully failed NSX Manager cluster is rebuilt from the first node deployed from OVA plus a file-based restore; VCF Automation and the Identity Broker are restored from the fleet SFTP location through VCF Operations. Practice each in the lab so the order and the prerequisites are in your hands, not only in a document.
Prepare: take a vSphere snapshot of the SDDC Manager, management vCenter and NSX Manager VMs from the outer (physical) vSphere layer so the lab can be reverted. Retrieve what the docs ask for before a vCenter restore: the vCenter deployment details and the administrator@vsphere.local credentials, and for a management-domain vCenter the root credentials of a healthy management ESX host (SDDC Manager API /v1/credentials?resourceType=ESXI).
Simulate the loss: power off the management vCenter appliance VM, rename it and remove it from inventory (do not delete its disks or snapshots, so the lab can be rolled back). Then restore it as documented in 'Restore a vCenter Instance from a File-Based Backup': download the vCenter ISO of the same build, mount it on a jump host with access to the management network, run the UI installer and click Restore. Stage 1: enter the backup location sftp://192.168.1.100/backups/vcenter-mgmt/<backup_folder>, review the backup details, and deploy the new appliance on a healthy ESX host in the management cluster with the original VM name, deployment size and network settings. Stage 2: provide the encryption password and complete the restore.
Simulate a fully failed NSX Manager cluster (power off all three nodes and remove them from inventory in the lab). Follow 'Restore the First Node of a Failed NSX Manager Cluster': retrieve the NSX version from SDDC Manager (Inventory > Workload Domains > domain > Update/Patches > NSX upgrade coordinator value) and the NSX root and admin credentials via the SDDC Manager API (/v1/credentials?resourceType=NSXT_MANAGER); in the management vCenter deploy a new NSX Manager from the OVA of that version with the first node's original name, size (Medium for the management domain), IP and hostname; then in the new node's UI, System > Backup & Restore, point to the SFTP server and restore the backup associated with that version; after the restore completes, redeploy the remaining two nodes to rejoin the cluster.
Restore a fleet component from the fleet SFTP location: in VCF Operations, Fleet Management > Lifecycle > VCF Management > Components, click VCF Automation (or VCF Identity Broker), horizontal ellipsis > Backup & Restore > Restore, choose Restore from the latest backup on the cluster (or give the backup path vcf/backups/<cluster-name>/<version>/<component-name>/<timestamp>), click Restore and monitor the task. For VCF Automation, afterwards rotate the service account (VCF Automation > VCF Instances > vertical ellipsis > Rotate service account). For the Identity Broker, afterwards trigger an inventory sync (component page > horizontal ellipsis > Trigger inventory Sync).
Document the SDDC Manager restore path without executing it (it needs an SDDC Manager OVA deployment): per the Instance Recovery timeline, SDDC Manager is deployed from OVA and restored from its file-based backup after vCenter and NSX Manager are restored; the external SFTP server is a prerequisite for the SDDC Manager file-based restore. Record the position of SDDC Manager in the order.
Validate after the restores: in VCF Operations check the VCF Instance inventory and the Fleet Management > Tasks page for errors; in vCenter confirm hosts are connected and vSAN is healthy; in NSX confirm transport nodes are up; run an SoS health check from SDDC Manager if available. Then take a new on-demand backup of each restored component, as the docs recommend after a successful recovery.
To roll back instead of keeping the restored state: power off and delete the restored appliances first (they reuse the original names and IP addresses), re-register the renamed originals and revert them to the pre-disaster snapshots. Either way, and record the time each restore took against your RTO targets.
Validation Gate
Check: vCenter restored via a new appliance from the SFTP backup; NSX Manager cluster rebuilt from the first node and a file-based restore; a fleet component restored from the fleet SFTP location with its post-restore step; SDDC Manager restore order documented; post-recovery validation and backups done.
Expected: Documented VCF 9.0 restore procedures executed and timed in the lab.
Common Errors
Final Validation
The VCF 9.0 backup set is mapped (SDDC Manager, vCenter and NSX Manager file-based; VCF Operations and fleet management image-based; VCF Automation and Identity Broker file-based to the fleet SFTP), configured with consistent schedules, exercised once, documented in a manifest, and the documented restore procedures for vCenter, NSX Manager and a fleet component have been executed and timed.
✓ Backup-method table and restore order recorded → 11 components with method; management-domain order vCenter > NSX Manager > SDDC Manager, then fleet components
✓ SDDC Manager backup configured from VCF Operations → External SFTP site settings, daily 04:02 schedule with state-change backups, Backup Now succeeded
✓ vCenter and NSX Manager backups → vCenter daily within the same 5-minute window as SDDC Manager; NSX hourly to the external SFTP server
✓ Fleet-level backups → VCF Automation and Identity Broker scheduled and backed up via Fleet Management > Lifecycle; image-based jobs defined for VCF Operations and fleet management with the consistency rules
✓ Manifest and runbook → SFTP listing, manifest without secret values, five on-demand backup triggers
✓ Restores executed → vCenter via new appliance + SFTP restore; NSX first-node rebuild + restore; fleet component restore with post-restore remediation; durations recorded
Cleanup / Restore
Snapshot: vcp-admin-09-complete
• Revert or consolidate the outer-layer snapshots taken before the restore exercises
• Keep the manifest and the restore durations with the recovery runbook
• Verify all scheduled backups are still enabled after the lab (SDDC Manager, vCenter, NSX, fleet components)
• Store the encryption passphrases in the password manager by reference from the runbook
Design Reflection (VCDX)
A panel examining VCF 9.0 backup design will probe the split between instance-level and fleet-level components and the restore order. Each VCF Instance still has SDDC Manager, vCenter and NSX Manager, protected with native file-based backups to an external SFTP server (SDDC Manager and vCenter daily, starting within the same 5-minute window; NSX hourly, configured by SDDC Manager at bring-up; SDDC Manager's settings configured from VCF Operations).
Fleet-level components are protected with image-based VADP backups (VCF Operations, fleet management, logs, networks) or with file-based backups to the fleet SFTP location (VCF Automation, VCF Identity Broker).
Be ready to defend: why an external SFTP server (prerequisite for the SDDC Manager restore; decouples NSX backups), the restore order (management vCenter before workload vCenters; vCenter and NSX before SDDC Manager in a full instance recovery; VCF Operations and fleet management before Identity Broker and Automation), the RPO and RTO per component, the consistency rules for image-based cluster backups, and the on-demand backup triggers around upgrades and recoveries.
Claiming that SDDC Manager was removed in 9.0, or that a single 'Restore Instance' button restores vCenter in place, would end the defence.
Requirements
- Every management component of each VCF Instance (SDDC Manager, vCenter, NSX Manager) is backed up with its native file-based backup to an external SFTP server
- SDDC Manager and all vCenter backup jobs start within the same 5-minute window; NSX Manager backs up hourly
- Fleet-level components are backed up with the documented method: image-based for VCF Operations, fleet management, logs and networks; file-based to the fleet SFTP location for VCF Automation and the Identity Broker
- Restore procedures are documented and tested in the order the VCF Instance Recovery timeline gives
- On-demand backups are taken before upgrades and after recoveries
- Encryption passphrases and backup account passwords are held outside the backup target and managed (SDDC Manager backup account in VCF Operations password management)
Constraints
- The SFTP server must support 2048-bit RSA and 256-bit ECDSA SSH keys and the documented host-key algorithms; SHA1 is not supported; FIPS mode adds algorithm requirements
- VCF Operations cluster nodes must be backed up at the same time, preferably offline, without quiescing, and not during dynamic threshold calculations
- Fleet SFTP schedules must be configured one component at a time
- A workload-domain vCenter can be restored only after the management-domain vCenter
- NSX Manager restore requires the OVA of the version that produced the backup
- Restoring the Identity Broker requires vCenter, VCF Operations and the fleet management appliance to be available
Assumptions
- The VCF Instance was deployed by the VCF Installer and is healthy (holodeck-02)
- An external SFTP server with enough capacity for the retention period is available
- A VADP-compatible backup product is available, or its absence is documented for the lab
- The lab has the vCenter ISO and NSX Manager OVA of the deployed builds
- Snapshots at the outer vSphere layer can be taken for the restore exercises
- Password manager holds the passphrases referenced from the runbook
Risks
- SFTP server loss removes every file-based restore point — Impact: no SDDC Manager, vCenter, NSX, Automation or Identity Broker restore — Mitigation: replicate or back up the SFTP server off-site; monitor capacity and job success
- Misaligned SDDC Manager and vCenter backups — Impact: inconsistent inventory after restore — Mitigation: same 5-minute window, monitored
- Image-based backups of VCF Operations taken node by node or quiesced — Impact: inconsistent cluster after restore — Mitigation: simultaneous jobs, quiescing disabled, cluster offline where possible
- Lost passphrase — Impact: backups unusable — Mitigation: passphrases in the password manager, referenced from the runbook, tested in the restore exercise
- Restore performed out of order — Impact: failed restores or re-work — Mitigation: runbook ordered per the Instance Recovery timeline, rehearsed
- Backups not refreshed after recovery or before upgrades — Impact: a second failure restores stale state — Mitigation: the five on-demand triggers in the runbook
Self-Assessment Discussion Prompts
- Why does the documentation require an external SFTP server for SDDC Manager and NSX Manager backups, and what breaks if they stay on the SDDC Manager appliance?
- Why must the SDDC Manager and vCenter backup jobs start within the same 5-minute window, and what is the consequence of ignoring it?
- Which fleet-level components use image-based backups and which use the fleet SFTP target, and how does that split change your backup product requirements?
- In a full VCF Instance recovery, why are vCenter and NSX Manager restored before SDDC Manager, and VCF Operations and fleet management before the Identity Broker and VCF Automation?
- What is your RPO and RTO per component, and which of the documented procedures sets the floor for each?
- How do you prevent a recovered environment from being protected by stale backups in the hours after a recovery?
Extensions
Full VCF Instance Recovery rehearsal
Follow 'VMware Cloud Foundation Instance Recovery' end to end in a disposable lab: redeploy ESX hosts, deploy the VCF Installer, perform the partial VCF deployment, deploy vCenter, the first NSX Manager node and SDDC Manager from OVA, restore all three, recover clusters and NSX Edge nodes, then restore the fleet components. Use the VMware.CloudFoundation.InstanceRecovery PowerShell module where it applies.
harderFIPS-mode SFTP compliance
Enable FIPS Security Mode on SDDC Manager in a lab and reconfigure the SFTP server with the required key exchange, MAC and cipher algorithms until the backup succeeds.
harderImage-based backup product integration
Integrate a VADP-compatible backup product with the management cluster and implement the VCF Operations cluster job with simultaneous node backup and quiescing disabled; restore a collector node from it.
sameBackup monitoring in VCF Operations
Build a VCF Operations alert definition and dashboard that flags a missed SDDC Manager, vCenter or NSX backup within 24 hours and an SFTP capacity threshold.
same⚠ Known Pitfalls
References
- VMware Cloud Foundation 9.0: Backup and Restore of VMware Cloud Foundation (backup methods, prerequisites, on-demand triggers)Tier 1 — Official
VCF 9.0.1 PDF pp.3003-3005. Task 1 and Task 4. - VMware Cloud Foundation 9.0: File-Based Backups for SDDC Manager, NSX Manager and vCenter; Back Up SDDC Manager (Table 948)Tier 1 — Official
VCF 9.0.1 PDF pp.3006-3007. Task 2. - VMware Cloud Foundation 9.0: Image-Based Backup for VCF Operations; On-Demand Backup of VCF Automation; On-Demand Backup and Restore of a VCF Identity Broker Appliance ClusterTier 1 — Official
VCF 9.0.1 PDF pp.3028-3035. Task 3 and Task 5. - VMware Cloud Foundation 9.0: Restore a vCenter Instance from a File-Based Backup; Restore the First Node of a Failed NSX Manager ClusterTier 1 — Official
VCF 9.0.1 PDF pp.3015, 3019-3020. Task 5. - VMware Cloud Foundation 9.0: VMware Cloud Foundation Instance Recovery (recovery timeline, documentation to keep, PowerShell module)Tier 1 — Official
VCF 9.0.1 PDF pp.3035-3039. Task 1 step 5, Task 5 step 5, Extension 1. - VMware Cloud Foundation 9.0: Managing Passwords for VMware Cloud Foundation ComponentsTier 1 — Official
SDDC Manager backup account managed in VCF Operations. VCF 9.0.1 PDF pp.2935-2937. Task 4 step 7.