Skip to main content

Problem deleting ghost NSB task

Thread solved

Hi Everyone

I had been running an NSB task which inexplicably failed.

I then set up a new NSB task (same source same destination) which has been running fine since.

The two NSB tasks show in the list of backups with different names. The one which failed (last backup 24 July 21) shows as not scheduled.

If I delete the failed NSB task it deletes all the current NSB backup data too. Very annoying.

However the failed NSB task still shows. Can I remove this manually by editing a script?

I looked through the scripts but couldnt see one that referred to either non stop backup task.  Perhaps these are handled differently?

I hope this is clear.

Thanks for any info.

BR

 

0 Users found this helpful

BR, as you can only ever have a single NSB task, the only way that you are likely to be able to clear up this issue with the ghost task would be to delete the existing task so that both NSB tasks are removed, then make a fresh start.

The above is my best guess as I have never needed to use NSB for my own systems!

Thank you Steve.

That makes perfect sense.

Of course I forgot that only one NSB is allowed so it's logical they are both inextricably linked.

I am loathed to delete a perfectly working task.

I'll put up with the ghost task in the list for the time being.

Should the NSB fail anytime in the future I'll then delete them both a create a new task.

Thanks for your help.

BR 8^)