CloudSnaps can be setup in two ways. First, by configuring the schedule as part of Storage Class (this applies to all volumes created using that Storage Class) and second, by creating a per volume schedule using Portworx CLI:
pxctl cloudsnap schedule create —help
The former schedule is triggered from Stork (hence only for Kubernetes) and the later is instrumented in PX storage system. The schedule will take parameters for frequency interval (custom) or specific intervals (for daily, weekly, monthly) runs.
The solution today is efficient in the way it addresses bandwidth utilization by throttling, queuing. Only one backup can be active per volume. More backup requests to the same volume with active backup are queued( snap is taken, but the process of pushing snap to cloud is queued). If the queue grows beyond 5 ( per volume), backup requests are failed. So number of backups being triggered at any schedule and frequency of the schedule must be considered during system design ( so that no more than 5 backups per volume are accumulated in the queue).
Monitoring for cloudsnaps includes following metrics (PX version 2.0.3 and later) - px_backup_stats_status, px_backup_stats_size and px_backup_stats_duration_seconds