Original description from https://bugzilla.redhat.com/show_bug.cgi?id=2155830

 
Describe the issue:
Even though we state in the documentation that `The size of the requested PVC must be the same as that of the source volume of the snapshot` it raises the question how to deal with a situation where a restore to a bigger sized PVC is desired.
When this is tried a error message is shown and the restore fails.

Describe the task you were trying to accomplish:
Restoring a volume snapshot to a new Persistent Volume Claim (PVC) with a bigger size to accommodate anticipated growth

Suggestions for improvement:
Add to section `Restoring volume snapshots in single node openshift` a hint that first a snapshot needs to be restored to a PVC of the same size which can then be resized, after snapshot has completed, e.g.
`If it is desired to have a bigger sized PVC as restore target, first restore to a PVC of the same size as the source volume of the snapshot and increase the PVC size after a successful restore`

Document URL:
https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.11/html/deploying_and_managing_openshift_data_foundation_on_single_node_openshift_clusters/volume_snapshots_for_single_node_openshift#restoring-volume-snapshots-in-single-node-openshift_sno
Chapter/Section Number and Title:
5.2. Restoring volume snapshots in single node openshift

Product Version:
LVMO 4.11.2

Environment Details:
OCP version: 4.11.13
ODF LVM Operator 4.11.2

Any other versions of this document that also needs this update: n/a

Additional information:
see also discussion in
https://bugzilla.redhat.com/show_bug.cgi?id=2155672