Veritas NetBackup™ Cloud Administrator's Guide
- About NetBackup cloud storage
- About the cloud storage
- About the Amazon S3 cloud storage API type
- About EMC Atmos cloud storage API type
- About Microsoft Azure cloud storage API type
- About OpenStack Swift cloud storage API type
- Configuring cloud storage in NetBackup
- Scalable Storage properties
- Cloud Storage properties
- About the NetBackup CloudStore Service Container
- Configuring a storage server for cloud storage
- NetBackup cloud storage server properties
- Configuring a storage unit for cloud storage
- Changing cloud storage disk pool properties
- Monitoring and Reporting
- Operational notes
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting cloud storage configuration issues
- Troubleshooting cloud storage operational issues
Cloud storage disk pool properties
The properties of a disk pool may vary depending on the purpose the disk pool.
The following table describes the possible properties:
Table: Cloud storage disk pool properties
Property | Description |
---|---|
The disk pool name. | |
The storage server name. | |
The disk volume that comprises the disk pool. | |
The total raw, unformatted size of the storage in the disk pool. The storage host may or may not expose the raw size of the storage. | |
The total amount of space available in the disk pool. | |
A comment that is associated with the disk pool. | |
The , is a threshold at which the volume or the disk pool is considered full. | |
The is a threshold at which NetBackup stops image cleanup. | |
Select to limit the number of read and write streams (that is, jobs) for each volume in the disk pool. A job may read backup images or write backup images. By default, there is no limit. When the limit is reached, NetBackup chooses another volume for write operations, if available. If not available, NetBackup queues jobs until a volume is available. Too many streams may degrade performance because of disk thrashing. Disk thrashing is excessive swapping of data between RAM and a hard disk drive. Fewer streams can improve throughput, which may increase the number of jobs that complete in a specific time period. A starting point is to divide the of all of the storage units by the number of volumes in the disk pool. | |
Select or enter the number of read and write streams to allow per volume. Many factors affect the optimal number of streams. Factors include but are not limited to disk speed, CPU speed, and the amount of memory. For the disk pools that are configured for Snapshot and that have a property:
|