Salta al contenuto principale

notification emails

Thread needs solution

I apologize in advance if this question has already been answered, but I just couldn't find anybody talking about this issue.

I can't find any way to temporarily disable email notifications on a failed backup job.

This is a huge problem because when a notebook computer is sometimes disconnected and its drive is being backed up by another machine I get emails telling me that the job failed every 10 minutes and I have no way to stop these emails until the notebook computer is reconnected to the network.

Can anyone help with this?

By the way am I the only user that would prefer seeing a simple icon in the notification area with either a red or green color that indicates successful backup failed backup as opposed to this fancy system of sending emails every 10 minutes?

 

0 Users found this helpful

Have you tried changing the settings available in the Additional Notification Settings panel?

This allows you to not send notifications on operation failure or when user intervention is required.

 

Allegato Dimensione
328249-125533.png 9.19 KB

Thanks for your attempt BUT you're not understanding my issue.

I want to know about a failure so I have the notification turned on.

What I don't want is to receive an email every 10 minutes that keeps reminding (nagging) me about the failure over and over again, once would be fine.

I have actaully even deleted the backup job from the system and I STILL get the failure messages on a job that wasn't completed 12 hours ago.

The only way I've found to end these silly emails is to reboot the computer (a bit extreme).

Bruce, have you considered approaching this issue from a different way, instead of trying to stop the notification emails when the backup fails because the target backup drive is disconnected, try adding a pre-command to test for the backup drive instead.

For example, you could create a simple batch command file to try to do a change directory to the target drive:

TEST.CMD
@echo off
cd H:\       (change to whatever the drive letter should be, assuming a local/mapped drive)

Save the TEST.CMD batch file to a place of your choosing, then select this in the Pre-Command (Edit) dialogue and leave the default settings that prevent the backup until the command has completed and aborts the backup if it fails (because the drive isn't found).

Allegato Dimensione
328257-125536.png 17.7 KB

Steve,

Thanks for the suggestion.

I'll try that but it does seem like a whole lot of effort to workaround what I think is a poorly designed notification system in the software.

 

Hi Bruce, I understand your frustration if you are seeing repeated 'nag' notifications for a failed operation, but assuming that you have not inadvertantly set the Advanced > Error handling options to do this, then removing the cause of the backup failure has to be a quicker fix than waiting for a software update for a possible bug in the code.

I have played a little more as I sometimes find one of my network drives is 'lost' which can cause one of my backups to fail, though I haven't hit the same 'nag' issue as you, but found that PowerShell has a cmdlet Test-Path that can be used to validate that the target backup path is found, this includes testing for network shares.

I was able to change my TEST.CMD to use this as follows:

powershell -command set-executionpolicy unrestricted
powershell -file "e:\test.ps1"
​powershell -command set-executionpolicy default

Where the file test.ps1 has a single line for the Test-Path cmdlet with the path to check:

test-path "\\MYBOOKLIVE\Backups\Dell Studio\"

The set-executionpolicy was needed on my system because otherwise the powershell failed as not permitted!