Introduction

Description

You can use the capabilities of storage tiers to implement data redundancy.

You can provide your own NSP storage solution instead of using the default local storage. You must provide access to the storage using Kubernetes storage classes that are accessible to each NSP cluster.

You can use your own storage solution in the following deployments:

• New installation using your own storage—see To install an NSP cluster

• Data migration from local storage to your own storage in a standalone NSP deployment—see To migrate to your own storage in a standalone NSP deployment

• Data migration from local storage to your own storage in a DR deployment—see To migrate to your own storage in a DR NSP deployment

• Upgrade from Release 23.11 or Release 24.4 to Release 24.8 in a standalone deployment—see To upgrade a Release 22.9 or later NSP cluster

See the NSP Planning Guide for information about the requirements for your deployment.

Note: See Appendix C, NFS storage configuration and Appendix D, Ceph storage configuration for sample storage classes.

Using NFS

You can host NFS servers instead of using the default local storage. You must provide access to the storage using Kubernetes storage classes that are accessible to each NSP cluster.

You can use NFS subdir external provisioner on NSP cluster nodes for dynamic provisioning in Kubernetes.

See Appendix C, NFS storage configuration for information about provisioning NFS servers.

See the NSP Planning Guide for information about the requirements for your deployment.

Providing Rook Ceph storage

You can provide Rook Ceph storage solution instead of using the default local storage. You must provide access to the storage using ReadWriteOnce and ReadWriteMany storage classes that are accessible to each NSP cluster.

See Appendix D, Ceph storage configuration for information about configuring Ceph, creating storage classes, and connecting to NSP.

See the NSP Planning Guide for information about the requirements for your deployment.