Veritas NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Planning your deployment
- About MSDP storage and connectivity requirements
- About NetBackup media server deduplication
- About NetBackup Client Direct deduplication
- About MSDP remote office client deduplication
- About MSDP performance
- MSDP deployment best practices
- Provisioning the storage
- Licensing deduplication
- Configuring deduplication
- Configuring the Deduplication Multi-Threaded Agent behavior
- Configuring the MSDP fingerprint cache behavior
- Configuring MSDP fingerprint cache seeding on the storage server
- About MSDP Encryption using KMS service
- Configuring a storage server for a Media Server Deduplication Pool
- Configuring a disk pool for deduplication
- Configuring a Media Server Deduplication Pool storage unit
- About MSDP optimized duplication within the same domain
- Configuring MSDP optimized duplication within the same NetBackup domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- Creating a storage lifecycle policy
- Resilient Network properties
- Editing the MSDP pd.conf file
- About protecting the MSDP catalog
- Configuring an MSDP catalog backup
- Configuring deduplication to the cloud with NetBackup Cloud Catalyst
- Using NetBackup Cloud Catalyst to upload deduplicated data to the cloud
- Configuring a Cloud Catalyst storage server for deduplication to the cloud
- Monitoring deduplication activity
- Viewing MSDP job details
- Managing deduplication
- Managing MSDP servers
- Managing NetBackup Deduplication Engine credentials
- Managing Media Server Deduplication Pools
- Changing a Media Server Deduplication Pool properties
- Configuring MSDP data integrity checking behavior
- About MSDP storage rebasing
- Managing MSDP servers
- Recovering MSDP
- Replacing MSDP hosts
- Uninstalling MSDP
- Deduplication architecture
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Troubleshooting Cloud Catalyst issues
- Cloud Catalyst logs
- Problems encountered while using the Cloud Storage Server Configuration Wizard
- Disk pool problems
- Problems during cloud storage server configuration
- Cloud Catalyst troubleshooting tools
- Appendix A. Migrating to MSDP storage
About the Cloud Catalyst esfs.json configuration file
NetBackup Cloud Catalyst uses the configuration options that are included in the esfs.json file for many operations. They include the options that determine when the files that have been uploaded to cloud storage are removed (evicted) from the local cache. Some of the options are configurable by the NetBackup administrator. The location of the esfs.json file depends on the location of the local cache directory.
As part of the Cloud Storage Server Configuration Wizard, the administrator configures a local cache directory. The local cache directory ( local_cache_dir in the following topic) determines the location of other directories which are installed automatically and are critical to Cloud Catalyst operations:
The NetBackup Cloud Catalyst configuration options are listed in Table: Configuration items in the esfs.json file .
To change the configuration items in the esfs.json configuration
- Change one or more of the configuration items in the esfs.json file. The file is found in the following location:
local_cache_dir/cache/etc/esfs.json
- Save and close the file.
- If vxesfsd is running, run the esfs_reconfig command (enter the mount path) as follows:
/usr/openv/esfs/bin/esfs_reconfig local_cache_dir/storage
If esfs.json is changed while vxesfsd is stopped, the changes take effect the next time vxesfsd starts.
- Some items require that you restart vxesfsd before the new configuration can take effect.
These items are indicated in Table: Configuration items in the esfs.json file .
Before vxesfsd is stopped, verify that no processes currently use vxesfsd, including the current working directory of any user.
The NetBackup Deduplication Manager (spad) and the NetBackup Deduplication Engine (spoold) use vxesfsd, so they need to be stopped if either is running.
Before vxesfsd is started, make sure that no data exists in the mount point. If data exists in the mount point, vxesfsd fails to start.
Table: Configuration items in the esfs.json file
Configuration item | Default setting | Description | vxesfsd restart required? |
---|---|---|---|
Log | |||
|
/usr/openv/ netbackup/logs |
This setting indicates the directory where logs for the vxesfsd process are created. The logs include the following:
|
Yes |
|
10485760 |
This value (in bytes) controls the maximum size that a single log file is allowed to grow. Once the file reaches that approximate size, the log file is closed and another log file is opened. |
No |
|
This value determines the logging level and what information is included in the logs:
|
No. Changes may not take effect until the next restart. | |
Monitor | |||
|
This value controls how full the Cloud Catalyst cache partition can become. The value represents the percentage of used space on the cache partition.
If the Cache eviction starts when the used space reaches the midpoint between If the Note: The file system on which the cache resides must not contain data from any other applications. |
No | |
|
This value determines at what point vxesfsd stops evicting container files after the HighWatermark triggers eviction. The value represents the percentage of used space on the cache partition. |
No | |
|
12 |
This value determines how frequently (in hours) the database is backed up. This value is unrelated to the drcontrol policy, if one exists. Veritas recommends that a drcontrol policy is created and used to protect your cloud storage server. Veritas recommends that this value is not changed. Note: This database is a special database for the cloud storage server, not the NetBackup or MSDP catalog. |
No |
StorageManager | |||
|
This value determines the maximum number of concurrent connections to the cloud provider for asynchronous (upload and delete) operations. |
Yes | |
|
This value determines the maximum number of concurrent connections to the cloud provider for synchronous (download) operations. |
Yes | |
|
14 |
This value determines the maximum number of saved copies of the database that are created for backup. Veritas recommends that this value is not changed. This value is unrelated to the drcontrol policy, if one exists. Veritas recommends that a drcontrol policy is created and used to protect your cloud storage server. Note: This database is a special database for the cloud storage server, not the NetBackup or MSDP catalog. |
No |
FileSystem | |||
|
192114 |
This value determines the maximum number of files that can be open at one time. Veritas recommends that this value is not changed. |
Yes |
|
This value indicates whether the files currently stored in the cloud can be modified:
This setting is used for disaster recovery and should not be changed under normal usage. |
Yes | |
|
1 |
This value is used for disaster recovery in the Cloud. This option is enabled by default. |
Yes |