That’s a good suggestion, thanks for commenting on it. I’d probably follow-up with by still saying that VSS directives shouldn’t be applied to backups of anything other than Windows systems. It’s always better to avoid engineering unpredictability into a solution.

Cheers,

Preston.

The semi-colon is a special character and causes getopt() fail to parse the command line arguments properly. That is why the following error message shows up
/usr/sbin/nsrnmo[..]: -l: not found

BTW, nsrnmo script (template) was changed in NMO 5.0 to enclose -o option’s value in double quotes to avoid interpreting any special character in the save operations value, which is typically should not be set for Oracle backups in the first place. So, the other option for a customer to change their nsrnmo script to add the following line to the loop that generates nsrnmostart command line:

-o ) # Save operations options
opts=”$opts $1 ‘$2′”
shift 2
;;

thanks.