Install prerequisites
Hardware requirements
The minimum supported size for the Portworx Backup cluster is three worker nodes. Each node must meet the following hardware, software, and network requirements:
Hardware Requirements | |
---|---|
Upto 2,000 backups | |
CPU | 4 CPU cores minimum (8 recommended) |
RAM | 4 GB (8 GB recommended) |
Storage space required for PVC creation | 321 GB (In Total) |
For 10,000 to 15,000 backups | |
CPU | 8 CPU cores |
RAM | 16 GB |
Storage space required for PVC creation | 321 GB (In Total) |
Upto 75,000 backups | |
CPU | 32 CPU cores per node |
RAM | 32 GB |
Storage space required for PVC creation | 331 GB (In Total) |
You can change the Prometheus PVC size from 5 GB (default size) to 10 GB or more based on your needs.
Software requirements
- 2.7.2
- 2.7.1
- 2.7.0
Software requirements | |
---|---|
Operating System | x86-64 based Linux distros supported by your storage provider |
On-premises Kubernetes |
|
Managed Kubernetes |
|
Prometheus |
|
Prometheus Operator | 0.70.0 |
AlertManager |
|
Kubevirt | 1.0.0 |
Stork | 24.3.0 |
Portworx |
|
A block-based provisioner | At least 307 GB of free space to host the PVCs deployed by databases used by Portworx Backup |
External Auth Providers | External OIDC and LDAP based Auth providers |
FlashArray |
|
FlashBlade |
|
Software requirements | |
---|---|
Operating System | x86-64 based Linux distros supported by your storage provider |
On-premises Kubernetes |
|
Managed Kubernetes |
|
Prometheus |
|
Prometheus Operator | 0.70.0 |
AlertManager |
|
Kubevirt | 1.0.0 |
Stork | 24.2.1 |
Portworx |
|
A block-based provisioner | At least 307 GB of free space to host the PVCs deployed by databases used by Portworx Backup |
External Auth Providers | External OIDC and LDAP based Auth providers |
FlashArray |
|
FlashBlade | 3.3.1 |
Software requirements | |
---|---|
Operating System | x86-64 based Linux distros supported by your storage provider |
On-premises Kubernetes |
|
Managed Kubernetes |
|
Prometheus |
|
Prometheus Operator | 0.70.0 |
AlertManager |
|
Kubevirt | 1.0.0 |
Stork | 24.1.0 |
Portworx |
|
A block-based provisioner | At least 307 GB of free space to host the PVCs deployed by databases used by Portworx Backup |
External Auth Providers | External OIDC and LDAP based Auth providers |
FlashArray |
|
FlashBlade | 3.3.1 |
-
If you are using an external authorization provider, you must use certificates signed by a trusted certificate authority.
-
Make sure helm is installed on the client machine: Helm
KDMP backup prerequisites
If you need to initiate KDMP or cross-cloud backups, ensure that you allocate additional buffer storage that is double the size of the original Persistent Volume Claim (PVC) in your application cluster. This buffer ensures that there is sufficient storage allocation for data changes, snapshots, or temporary data generated during the backup process.
Prometheus prerequisites
If you have your own Prometheus installed cluster-wide, ensure that it does not reconcile with the Portworx Backup Prometheus in px-backup
namespace.
When Prometheus and Alertmanager are in CrashLoopBackOff state, ensure the that the global or cluster wide Prometheus Operator does not interfere with the Prometheus and Alertmanager instances in px-backup
namespace. If so, modify the cluster-wide Prometheus operator to exclude the namespace where the Portworx Backup Prometheus stack is installed.
Add the following entry under spec.template.spec.containers[0].args
in the cluster-wide Prometheus Operator spec to resolve conflicts if any:
--deny-namespaces=<px-backup-installed-namespaceName
Alternatively, you can also set the scope of the cluster-wide Prometheus to defined namespace using the below parameter:
-- namespaces = <namespace where cluster-wide prometheus is installed>
Portworx Backup 2.3.0 and above use MongoDB 5.x versions internally, which require Intel/AMD Chipsets that support Advance Vector Extensions (AVX). If you are deploying Portworx Backup 2.3.0 and above, please ensure that your Intel/AMD Chipset versions support AVX.
Related topics