Veeam Backup & Replication 10
User Guide for VMware vSphere
Related documents

Clearing Global Cache

You can clear the global cache on the target WAN accelerator. It is recommended that you clear the global cache in the following situations:

  • Global cache is corrupted.
  • Global cache contains data that is no longer needed. This situation may occur, for example, if you have processed VMs running one OS and do not plan to process VMs with such OS in future. The global cache will contain data blocks that may be of no use for VMs running other OS.

In such cases, it is recommended that you clear the global cache and populate it anew before you start remote jobs processing new types of VMs.

To clear the global cache:

  1. Open the Backup Infrastructure view.
  2. In the inventory pane, click WAN Accelerators.
  3. In the working area, right-click the target WAN accelerator and select Clear cache.

Clearing Global CacheImportant!

Before you clear the global cache, make sure that you do not have any running jobs that use this target WAN accelerator. When the global cache is cleared, Veeam Backup & Replication will restart the Veeam WAN Accelerator Service, and running jobs will complete with the Failed status.

Click to enlarge

This Document Help Center
User Guide for VMware vSphereUser Guide for Microsoft Hyper-VVeeam Backup Enterprise Manager GuideVeeam Agent Management GuideVeeam Cloud Connect GuideVeeam Explorers User GuideVeeam Plug-ins for Enterprise Applications GuideVeeam PowerShell ReferenceVeeam Explorers PowerShell ReferenceVeeam RESTful API ReferenceRequired Permissions for VMware vSphereQuick Start Guide for VMware vSphereQuick Start Guide for Microsoft Hyper-VVeeam Backup for AWS DocumentationVeeam Availability for Nutanix AHV DocumentationVeeam Backup for Microsoft Office 365 DocumentationVeeam ONE DocumentationVeeam Agent for Windows DocumentationVeeam Agent for Linux DocumentationVeeam Management Pack Documentation
I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.