NetBackup CloudCatalyst workflow processes
Figure: Workflow on a CloudCatalyst storage server shows the workflow on a CloudCatalyst storage server for uploading data to the cloud.
Note that a single CloudCatalyst storage server can only write to one cloud provider and to one bucket within that cloud provider.
The Filesystem in Userspace (FUSE) forwards data from MSDP to the File System Database (FSDB).
The File System Database (FSDB) tracks and stores metadata about all of the files written to the NetBackup Extendable Storage File System (ESFS).
NetBackup CloudCatalyst uses the NetBackup Extendable Storage File System Service (vxesfsd) and its subcomponents to move and manage files in the local cache directory and the cloud.
ESFS uses daemons to perform the following functions in its database:
Veritas NetBackup Extendable Storage File System Service daemon (vxesfsd): This is the primary file system daemon. It is responsible for writing data into the MSDP cache files.
Veritas NetBackup Extendable Storage Proxy (vxesp) daemons: These daemons are responsible for interacting with the cloud. Under normal operations, there are always two vxesp processes: one is the master and one is the worker.
The vxesp daemon produces the following log: /usr/openv/netbackup/logs/esfs_storage
vxesfsd includes three subcomponents that perform various tasks as part of ESFS:
Monitor component: The monitor component checks the file queue for files to be uploaded and checks the local cache directory for cache eviction purposes, among other activities.
Storage manager component: Notifies vxesp processes when there's work to be done, manages synchronous (downloads from the cloud) and asynchronous (uploads to and deletions in the cloud), and shared memory, among other activities.
The vxesfsd daemon produces the following logs in /usr/openv/netbackup/logs/:
esfs_filesystem | |
esfs_storagemanager | Logs the interactions of the ESFS storage manager with vxesp. |
esfs_monitor | Logs job status updates and periodic tasks such as cache eviction and FSDB backups. |
esfs_database | Logs FSDB actions that are specific to the ESFS database. |
As part of the Cloud Storage Server Configuration Wizard, the administrator configures a local cache directory (local_cache_dir). The directory must be on either a Linux file system or, in the case of an appliance, a VxFS file system.
The directory is then split into two:
A cache directory: local_cache_dir/cache/userdata
ESFS writes out the data and the metadata in this location. This directory is mapped directly to the storage directory (local_cache_dir/storage). There are not two copies of each file on this media server.
A storage directory: local_cache_dir/storage
This path is the mount point to the ESFS file system. This is what MSDP knows as its storage directory.
NetBackup periodically performs data eviction tasks in the cache directory to create space for new backups. If necessary, the administrator can change when or how often data eviction occurs. For example, by default, if a file is not accessed in 30 days, and it has been uploaded to the cloud successfully, it is removed from the cache directory. These options are configured in the esfs.json file.
See About the CloudCatalyst esfs.json configuration file.
