We have Netbackup 5.1 backing up 8 Teradata nodes with 3 Windows servers. When the agent kicks off a backup job the fisrt job itiates the backup request and completes successully. The next Netbackup job is the one where the Teradata Agent is requesting the data and the backup actually begins. A third Netbackup job acknowledges the backup job success and updates the Windows Agent. My question is: Is there a way to keep the first Netbackup job in the "Open" state during the entire backup process? Other databases (SQL, Oracle, DB2) function like this in Netbackup. We'd like to have the 1st Netbackup job for the Teradata backup stay open during the entire cycle like the other DB's. This will allow us to run scripts based on the success or failure of this status.