diff --git a/README.md b/README.md
index 640e21b..47dba20 100644
--- a/README.md
+++ b/README.md
@@ -107,5 +107,17 @@ This will disrupt the whole cluster for a few seconds.
 ### Backup
 Install Velero backup from https://github.com/vmware-tanzu/velero/releases
 
-    velero install --provider aws --plugins velero/velero-plugin-for-aws:v1.2.1 --bucket velero --secret-file ./credentials-velero --use-volume-snapshots=false --backup-location-config region=sto3,s3ForcePathStyle="true",s3Url=https://s3.sto3.safedc.net
-    velero backup create rut-backup --selector 'backup notin (ignore)'
\ No newline at end of file
+    wget https://github.com/vmware-tanzu/velero/releases/download/v1.15.2/velero-v1.15.2-linux-amd64.tar.gz
+    tar xzf velero-v1.15.2-linux-amd64.tar.gz
+    cp velero-v1.15.2-linux-amd64/velero /usr/local/bin/
+
+Get s3 credential from sto3
+Save into a file called credentials-velero to be used during the install:
+
+    [default]
+        aws_access_key_id=123123123123123123123123123123
+        aws_secret_access_key=12312312312312312312312213123
+
+    velero install --features=EnableCSI --use-node-agent --provider aws --plugins velero/velero-plugin-for-aws:v1.2.1 --bucket velero --secret-file ./credentials-velero --use-volume-snapshots=true --backup-location-config region=sto3,s3ForcePathStyle="true",s3Url=https://s3.sto3.safedc.net --snapshot-location-config region=sto3 --wait
+    velero schedule create prod-schedule --schedule="0 3 * * *"
+    velero backup create rut-prod --default-volumes-to-fs-backup=false --from-schedule prod-schedule
\ No newline at end of file