Allowing BE jobs to skip client system backups when they're switched off

[J_Page-_Helical]

How can I get BE to carry on a job when it detects a client system isn't available? If a system is simply offline, BE returns a 'failed' job at the moment, which stops an otherwise working backup job.

[Rohit_Sonawale]

Hi,

Thank you for posting your query,

Currently there is no option available which will update the selection list automatically.


So that you need to manually edit the selection list before performing backup.

We hope this information helps, if you have any other questions please respond to the post and we will be more than happy to assist you further.

[Abhinav_Bindroo]

In reference to our previous reply to your post, we would request you to update us on the progress. However, if we do not receive your intimation within two business days, this post would be assumed answered and archived.

[Ken_Putnam]

This would be pain to set up, but once set, should do what you want.

Create a separate backup job for each DLO Client. rather than schedule them through BackupExec, create a script that will ping each client, and if it responds, use BEMCMD to release the appropriate job.

make each job "Append - Else Overwrite" so it doesn't matter which is the first machine to respond

[Amruta_Purandar]

Hello,

Please let update us on the status of the issue.

NOTE: If we do not receive your intimation within two business days, this post would be assumed answered and archived.

[Sheetal_Risbood]

As per our previous reply, marking the case as assumed answered and moving it to answered questions pool.