cancel
Showing results for 
Search instead for 
Did you mean: 

Opscenter showing different policies than master server

Tdizzle
Level 2

Hello,

 

I am having an issue where Opscenter is showing different policies than what is on our master server. The policies it shows no longer exist and have been removed from the master server.  This is causing opscenter to send 24 hour failure reports. The current version being run is 7.6.0.2

Has anyone come across an issue like this before? Is there a way to re-sync the policy or remove the clients from the policy in opscenter?

1 ACCEPTED SOLUTION

Accepted Solutions

INT_RND
Level 6
Employee Accredited

That is not how OpsCenter works. You should look at how that report is configured. The failed jobs report can only contain failed jobs. The failures come from the Netbackup database. The OpsCenter database is a copy of information from the Netbackup database. It does not run it's own policies. You can send commands from OpsCenter to Netbackup but everything is still happening on the master server. OpsCenter is a sort of web console.

There is a report feature that will show clients not backed up. Clients not backed up will include the ones you removed because they are not backed up. This is not a failure and shouldn't be in the failure report.

View solution in original post

4 REPLIES 4

RonCaplinger
Level 6

Are you referring to policies showing up in reports?  Or are you looking at some other output in OpsCenter? Are these failure reports actually OpsCenter Alerts that are specifcially looking for those old policy names?

Tdizzle
Level 2

I have Ops Center scheduled to email a report of failed backups at 12 and 24 hour intervals. Only on the 24 hour failed report do these two clients show up. When I look at the policy they are part of on the master server, they are not listed in that master servers policy.  What it looks like is happening is Ops Center has it's own copy of the policies not current to the Master Server. When it runs that policy and cannot see the client on the server anymore it thinks it failed and then shows up.  In fact the VM's no longer exist, they were decommissioned and removed from the policy sometime ago. 

RonCaplinger
Level 6

OpsCenter is, at its heart, a historical database of the NetBackup jobs data.  If you ever had a backup for a client in a specific policy, then that info is now stored in the OpsCenter database with that policy name and that client.  If a report definition includes dates where that client was backed up with that policy, or failed, they will continue to be reported in that report so long as the report parameters include those dates.

Is this one of the canned reports, or is it something you customized and maybe have a parameter that needs to be tweaked?

INT_RND
Level 6
Employee Accredited

That is not how OpsCenter works. You should look at how that report is configured. The failed jobs report can only contain failed jobs. The failures come from the Netbackup database. The OpsCenter database is a copy of information from the Netbackup database. It does not run it's own policies. You can send commands from OpsCenter to Netbackup but everything is still happening on the master server. OpsCenter is a sort of web console.

There is a report feature that will show clients not backed up. Clients not backed up will include the ones you removed because they are not backed up. This is not a failure and shouldn't be in the failure report.