We had a major corruption on our central database, so our member dbs have been running stand-alone for a while. Since reinitialising the central DB, we're unable to successfully add the member db's back in.
Each time we get messages about the media in the device groups not being in the pools, as soon as they're unassigned they start working again.
I've tried restarts of the respective engines, to no avail.
Am I missing something or is it something really silly like - you have to re-create the pools, groups and jobs once you add them as member db's to the central?
The jobs were originally created when they were members to the central and when the dbs were unassigned, they carried on working without a problem.
The fact the jobs already exist is the only difference I can find between now and when they were set up the first time.
Any ideas would be gratefully received.
Each time we get messages about the media in the device groups not being in the pools, as soon as they're unassigned they start working again.
I've tried restarts of the respective engines, to no avail.
Am I missing something or is it something really silly like - you have to re-create the pools, groups and jobs once you add them as member db's to the central?
The jobs were originally created when they were members to the central and when the dbs were unassigned, they carried on working without a problem.
The fact the jobs already exist is the only difference I can find between now and when they were set up the first time.
Any ideas would be gratefully received.