Info2soft use cookies to help you have a superior and more admissible browsing experience on our website. Privacy Policy
Loading...
By:
A vCenter backup to an SMB share means configuring the vCenter Server Appliance (VCSA) to send its configuration and state data to a network share over the SMB protocol. This file-based backup runs natively from the appliance, with no need for third-party image-level backup agents.
The built-in backup utility packages the database, operating system settings, and historical records into a compressed set of files, then transmits them to your chosen SMB storage target.
This guide covers how vSphere administrators can set up VAMI backups for the first time, and how infrastructure engineers can troubleshoot a broken SMB backup job.
The vCenter Server Appliance Management Interface (VAMI), accessible on port :5480, is the primary place to manage file-based backups. The backup engine runs directly from the appliance operating system, not from vCenter inventory data or snapshot-based virtual machine backups.
VAMI supports several storage and transfer protocols, and teams typically pick the one that fits their existing infrastructure. The supported protocols include:
The file-based backup covers the appliance operating system configuration, vCenter database files, and inventory metadata. A common misconception is that this process also backs up the virtual machines managed by vCenter.
It only protects the management plane. Protecting the actual workload VMs still needs a dedicated image-level backup solution, which is typically agent-based or agentless depending on the platform.
Infrastructure teams often choose SMB for native Windows Server and Network Attached Storage (NAS) integration. This lets administrators reuse existing file server infrastructure and apply standard Active Directory permissions.
It also avoids deploying separate Linux-based storage servers just for backup targets.
Configuring an SMB backup target takes a few prerequisites in place first, then a short setup in VAMI.
Before configuring the backup schedule, make sure the following are in place:
user@domain format rather than domain\user, since VCSA’s backup client expects this format for SMB authentication.445, and sync both systems to the same NTP source, since Kerberos authentication fails if there’s clock skew between vCenter and the domain controller.Set up the SMB share and permissions.
Create the target directory on your Windows Server, Samba server, or NAS. Grant full share and NTFS read/write permissions to your dedicated backup service account.
Log in to VAMI.
Open a web browser and go to https://<vcenter-ip-or-fqdn>:5480. Log in with the appliance root credentials or an account with administrative privileges.
Navigate to the backup section.
Click Backup in the left navigation pane. In the Backup Schedule section, click Configure in the top-right corner.
Enter the backup location.
In the Backup Location field, enter the path in protocol:// format, such as smb://server.domain.com/share/path.
\\server\sharewon’t be accepted here.Enter service account credentials.
Enter the username in user@domain format along with the password.
domain\userformat. It has been linked to authentication failures during the SMB mount process on some VCSA versions.Choose backup pieces to include.
Select which data to include in each run, such as historical stats, events, and tasks. Leaving these unchecked keeps the backup smaller and the transfer faster, since only core configuration and database files are captured.
Set schedule and retention.
Choose how often the backup runs, the start time, and an optional encryption password. Set the retention policy, such as keeping a fixed number of backups, so the target storage doesn’t fill up over time.
Run an on-demand validation backup.
After saving the schedule, click Backup Now to trigger an immediate test run. This confirms that network routing, port 445 access, share permissions, and credentials all work before you rely on the scheduled job.
Restoring a vCenter Server Appliance from a backup is a two-stage process:
Before you start:
If the original deployment was part of a vCenter High Availability (HA) cluster:
Stage 1: Deploy the new appliance
Submit the backup location and credentials through the vCenter Server Appliance Management API. The API reads the backup metadata to determine the original vCenter version, size, and network settings, then deploys a matching VM on the target ESXi host.
Stage 2: Transfer the backup data
This stage configures the database, imports the inventory, and applies the appliance’s system configuration. Once complete, the new appliance takes over the original production IP address and FQDN.
When a backup fails, check the log files on the vCenter appliance first. Connect over SSH, enable the bash shell, and look in /var/log/vmware/applmgmt/. Check backup.log for execution details, backupScheduler.log for scheduling faults, and applmgmt.log for internal errors.
You can also test the SMB connection directly, separate from VAMI. Run smbclient //server/share -U user@domain from the vCenter command line. This isolates whether the issue is network, DNS, or credentials.
| Error Code | Likely Cause | Fix |
|---|---|---|
NT_STATUS_LOGON_FAILURE |
DFS referral path, not a direct path | Use the direct UNC path to the file server |
NT_STATUS_OBJECT_PATH_NOT_FOUND |
Same DFS root cause | Use the direct path, not a DFS namespace |
NT_STATUS_NOT_FOUND |
Short hostname won’t resolve | Use FQDN and fix the DNS search domain |
NT_STATUS_ACCESS_DENIED |
Service account lacks permissions | Grant full share and NTFS read/write access |
NT_STATUS_SHARING_VIOLATION |
Service account lacks write permission on the share | Confirm write access on the SMB server |
| SMB not supported / negotiation failure | SMBv1/SMBv2/SMBv3 mismatch | Enable SMBv2 or SMBv3 on both ends |
BackupManager encountered an exception |
Disk full, or stale mounts under /storage/remote/backup/cifs/ |
Free up space, or unmount stale folders via SSH |
If you’re specifically hitting the SMB not supported error, see this guide on how to fix vCenter backup SMB not supported for a deeper walkthrough.
Native VAMI backups protect vCenter’s configuration and database, but the virtual machines running in your vSphere environment still need their own dedicated protection.
i2Backup provides agentless VM backup at scale, using native virtualization platform APIs to protect and migrate VMs without installing agents or affecting production performance. It’s fully compatible with VMware, alongside other mainstream virtualization platforms such as Hyper-V.
Key features relevant to vSphere environments:
For teams running database workloads alongside vSphere, this means one solution can cover both the VMs and the databases running on them.
Q1: Can I use SMBv1 for vCenter backup?
Technically yes, but it’s not recommended. SMBv1 lacks encryption and modern security protections, and Microsoft has deprecated it. Use SMBv2 or SMBv3 whenever possible.
Q2: Does vCenter backup include VM data?
No. VAMI’s file-based backup only covers vCenter’s configuration, database, and inventory metadata. Your virtual machines need a separate, dedicated backup solution.
Q3: Can I use a DFS namespace as the backup target?
No. DFS namespaces can cause authentication failures like NT_STATUS_LOGON_FAILURE. Use a direct UNC path to the actual file server instead.
Q4: How much storage do I need for vCenter backups?
A basic configuration-only backup usually takes 3 GB to 10 GB. Adding historical data such as stats, events, and tasks can push this well past 20 GB, depending on your inventory size.
Backing up a vCenter Server Appliance to an SMB share protects your management plane through VAMI’s native file-based backup. Getting it right means setting up the share and service account correctly, using the right path and credential formats, and knowing how to troubleshoot common SMB errors when they come up.
Keep in mind that this backup only covers vCenter’s configuration and database, not the virtual machines it manages. For complete protection across your vSphere environment, a dedicated VM backup solution rounds out the picture, and Info2soft offers tools built for exactly that.
· Enterprise & Mid-market Customers Worldwide
· Support team available to assist you throughout your trial
· Start a 60-day free trial or view demo to see how Info2Soft protects enterprise data.
