Backup and Restore Resource Allocation
Vertica allows administrators to allocate bandwidth and TCP rsync connection resources to backup and restore operations. By default, Vertica allows a single connection and unlimited bandwidth for any backup or restore operation. By changing the default allocations in your vbr
configuration file, you can:
- Increase the number of available connections. If you have many Vertica files, more connections can provide a significant performance boost as each connection increases the number of concurrent file transfers.
- Assign a limit to the total amount of bandwidth that a particular operation uses. If your files are fewer and larger, additional bandwidth can provide a performance boost.
For more information, refer to the total_bwlimit_backup
, total_bwlimit_restore
, concurrency_backup
, and concurrency_restore
settings in Configuring Advanced VBR Options.
Increasing Queue Transport
Each connection creates an additional process that can transport an additional queue of files. When you start a backup or restore operation, Vertica creates a list of all the files requiring transport. As a connection completes a transfer, it takes the next file on the list until the list has been completed. If any file fails to transfer, Vertica assigns that file to another process.
The retryCount
setting in the vbr
configuration file determines the number of times vbr
attempts to transfer a file. If the number of failures for a particular file exceeds the limit specified in the retryCount
setting, the entire operation fails. Vbr
then terminates processing.
Bandwidth Limits
Vertica can limit its network bandwidth use through the total_bwlimit_backup
and total_bwlimit_restore
data transmission parameters. For more information, refer to [Transmission] Data Transmission .