• Day-2 operations run through VCF Operations, which now owns fleet lifecycle, SDDC lifecycle, certificates, passwords and the software depot.
• Every VCF 9.1 upgrade starts by upgrading VCF Operations, then SDDC Manager, then the VCF management services.
• Routine tasks (upgrade, patch, cert rotation, password rotation, backup) apply to every fleet. Optional tasks (Live Recovery, external storage, NSX Federation) apply only when you need them.
• Back up SDDC Manager, vCenter and NSX Manager on a schedule, and test a restore before you rely on it.
• Prerequisites: admin access to VCF Operations and SDDC Manager, an SFTP backup target, an NTP source, and current depot access.
• Use the phase map below to pick the task you need, or read the parts in order.

You have a running VMware Cloud Foundation 9.1 fleet. This series covers what comes next: keeping it current, recoverable, secure, and correctly sized as demand grows. Each part is a plain task you can follow end to end, with the exact screens, fields and commands. This first part gives you the map, so you can see how the tasks fit together and decide which ones your environment needs.

In VCF 9.1, most operational work is centralized in VCF Operations. Fleet lifecycle and SDDC lifecycle, certificate management, password management, and the software depot all run from one place. That changes how you think about Day-2 work compared with older releases, so this part sets the model before the task parts go deep.

Confirm the following before you run any task in this series.

VCF Operations is the fleet manager. It holds the inventory of every vCenter, NSX Manager and cluster, and it drives the two lifecycle engines. Fleet lifecycle handles the VCF Operations family and the management services. SDDC lifecycle handles vCenter, NSX and ESXi. When you plan an upgrade, apply a patch, rotate a certificate or change a password, you start in VCF Operations and it coordinates the change across the managed components.

Because the lifecycle engines read from a software depot, depot health matters for every patching task. An online depot pulls bundles from Broadcom. An offline depot mirrors those bundles into an isolated environment. Part 4 covers the offline depot in detail, and the upgrade and patch parts assume the depot is already reachable.

Run this quick check in VCF Operations before you begin any task, so you start from a known good state.

You are ready to start the task parts when VCF Operations reports a healthy inventory, the lifecycle view shows a consistent version across the domain, no certificate or password is flagged, and at least one successful backup exists for SDDC Manager. If any of those is not true, resolve it first. The backup parts (8 through 10) and the certificate and password parts (5 and 6) are the ones to run before you attempt an upgrade.

Which tasks are mandatory for every fleet
Upgrades, patching, certificate rotation, password rotation, and backup apply to every environment. Treat them as routine. Live Recovery, external storage, hardening baselines and NSX Federation are optional and depend on your requirements.

Do I need to read the parts in order
No. Each task part stands on its own with its own prerequisites. The phase map above lets you jump straight to the task you need.

Where does VCF Operations fit against SDDC Manager
VCF Operations is the fleet manager and drives lifecycle, certificates and passwords. SDDC Manager still runs domain level operations such as adding hosts and clusters. Several tasks touch both, and each part names the exact console to use.

What should I run first after deployment
Configure backups, confirm certificate and password health, then set your patch cadence. That order gives you a recoverable, current fleet before you make larger changes.