Hi Enrico, the problem is that $r(4) returns number between 0 and 3.
If you add 1 you will have numbers 1 2 3 4 but not 5.
You can correct your code with $r(5)+1

Your scripts are a bit complex but the backup pre-post command should return 0 if completed correctly.

So backup software can understand if the pre-command (preparation for backup) is completed ok.
If return code is 0 the backup can start saving data.
When backup completes commvault will start the post command.

Also the post command should return 0 if completed correctly.

In your script maybe it's better you should specify exit 0 when needed.

As mentioned by @Brett Saviano the XFS is recommended on Ubuntu, but ext3 and ext4 are supported.
Read notes to choose the better.

LVM is also solid and in large environment, even if it introduce a little overread, it can be usefull in changing disks layout.

You can add space or move data without service disruption.

With FS on whole disks you must copy data files and this must be done with services down.

Good,

so the folder test under tmp is not writable by all. If your script runs under different user and goup (not r00028881) the file could be read and seen but not removed.

You can try to chmod 777 /tmp/test in order to understand if this is the problem.

If you can remove the file after the chmod you must understand who is creating the test folder under /tmp or who is running the script that is unable to remove the file.

Regards

 Ambrogio