Post Command after Duplication

[irix]

Hi,

is there a way to execute a command after a duplication job finished?

The Pre/Post Comannds option is not available in the dupliction step, only in the backupjob.

Kind regards

[pkh]

Unfortunately, no

[Colin_Weaver]

Typically pre-and post commands are used to affect the environment you are backing up  with the pre-command being used to put the environment in a state suitable for backup and the post command used to put the environment back into usual operational status. Hence for most customers it only makes sense to have them only operate against the actual backup job itself as a duplicate job does not touch the environment that was backed up. As such (and confirming PKH answer) no there is no option for pre/post commands against duplication.

If you have a good business requirement that you can expain for needed such an option you could fill in an Idea request (by going ot the Ideas section of the Connect Website.)

[irix]

We backup our Data to a DeDup Disk daily. Also we backup the data to tape weekly.

To increase the speed writing to tape we backup all servers to Disk an then duplicate the data in one stream on Tape.

Now I need to clear the disk after the duplication on tape is finish. Otherwise there is not enough space for the next weekend.

My suggestion was to start a tiny batch script after the deuplication finished. But I can't trigger it automatically, when the job is finish.

Any other idears?

[pkh · Accepted solution]

You should not be clearing the disk. If you do, you will leave orphaned backup sets in the BE console. Set a reasonable retention period so that DLM will clear the disk storage before your next weekly job. Doing it this way will also allow you do rerun the tape duplicate job if there is a failure. Rerun is not possible if you clear the disk immediately after the duplicate job. You will need to set the DLM option to delete anyj expired backup sets. Otherwise at least one backup set will be kept for each server

[teiva-boy]

Your retention needs to be shortened to about 6 days on disk.  This will allow backupexec to free up the diskspace and mark media as overwritable all on its own, before the next full backup. Retention levels are essesntial in a properly running environment.  Learn and understand them well.