When an archive becomes obsolete and is dropped via the ArchiveConfig.exe utility, there remain many references to the archive that require cleanup.
The most visible problem is that when Search templates have a list of servers / archives to access, the deleted archive remains in the template and produces errors when session search is performed. Even when the templates are cleaned, a report drill down produces the error... and in some case no CxVerify jobs can be added or removed... the error "doGetArchiveList: Data is null." is returned until the missing archive is disabled.
This request is to provide for a cleanup process when an archive is dropped:
Remove references to the archive across all search templates, if those references exist
Disable/delete scheduled archive or trim jobs start target the deleted archive
Remove the archive from the Archive Expiration list.
Disable/Remove the archive in the Portal Management server list
Similarly, CxVerify should better tolerate a deleted archive, when trim jobs are being edited.
How will this idea be used?
Deleting obsolete archives should not trigger search connection errors. |
|
What is your industry? | Healthcare |
What is the idea priority? | Low |
The archive jobs interface needs improvement, especially when there are may jobs defined. Some ideas/fixes:
Configured Tasks:
Add free-text filter by job name
Add free-text filter by server name (source/target)
Add filter by job type (Archive/Trim/Check jobs)
Allow direct right click to select (currently this resets the list)
Schedule Tasks:
Add free-text filter by job name
Add drop-down filter by job status