run "post backup process" only backup ended successfully

@Mike Struening OK I'll try some more tests. Thanks

Hey @ITStorageEWL

 @Sunil beat me to it!  You can set the pre/post process to run pretty much any script you can come up with.  You (or commonly, a vendor) have to create the script itself, and we can execute it (as the listed user in the config).

Assuming you’d set this to run AFTER the backup phase, then you likely won’t encounter any issues with premature deletion; however, if the backup is killed BEFORE the script portion runs, then you’ll likely the files sitting in place where you expected them to have been deleted.

Is your intent to stage files in a folder, have them get backed up, then delete them after (to clear the staging area)?

Thanks!

While we wait for @Sunil I am going to send this page to our documentation team to see if we can get examples added for clarity!

@ITStorageEWL you don’t HAVE to add in that parameter; it’s there if you want to force the script to make a more informed decision to only run IF a prior event succeeded/failed, etc.

You should be able to test it out with a VERY small subclient with some random text files thrown in.  Set the subclient to that folder only, set the script syntax to delete that folder’s content and run a full and see what happens.

@ITStorageEWL the status argument will only prevent the script running if the prior phase has failed.  Is the prior phase failing?  If the backup phase works (assuming this is a post backup script), then the script will run.

I’ll tag in @Sunil for any additional context.

You can always just do it within the script as you said, though it might be tougher to monitor the phase of the backup/scan, etc.