cancel
Showing results for 
Search instead for 
Did you mean: 

Can we prevent errors from reporting backup issues that don't exist?

newpotatoe
Level 3

We are currently configured to run snapshots on our partition archives, while we are set to remove the safecopies "remove immediately after archiving".  The combination of these two configurations, we don't require to configure the two options for checking whether items have been secured, "Use the archive attribute" or "Check for a trigger file".  It seems that both of these settings require to have setting "remove after backup (or journal)" for it to apply.  Since we have "remove immediately after archiving", neither would apply in our situation, we are receiving the errors below:

This is causing reports in the event viewer (eventid 41261) and in statuses in the admin console:

 

It is more than 2 days since backup or replication was detected for one or more open partitions.

Open partitions not scanned: 2

Total open partitions: 2

 

List of partitions:

MEMBER02 MAIL ARCHIVEB Ptn1

MEMBER05 MAIL ARCHIVEB Ptn1

 

You can use the System Status feature in the Administration Console to help you resolve this issue.

 

Is it possible to prevent these errors from reporting?

 

1 ACCEPTED SOLUTION

Accepted Solutions

JesusWept3
Level 6
Partner Accredited Certified
2 REPLIES 2

JesusWept3
Level 6
Partner Accredited Certified

GertjanA
Moderator
Moderator
Partner    VIP    Accredited Certified

Uncheck that specific monitoring part.

However, first check the document JW gave. That might explain also.

Regards. Gertjan