SUMMARY
The appliance may generate misleading alerts when application data is protected at the asset level.
ISSUE
When assets containing the application Oracle are registered to the Unitrends appliance, and the Oracle application is successfully detected and appears in the UI, but the Unitrends Application engine is not desired, customers will typically not add a credential for Oracle. Without adding an oracle credential however, Unitrends is unable to complete inventory sync of the databases under that instance normally, resulting in a UI inventory sync trap error.
In other cases, customer may add client agent assets with applications Exchange, SQL, Oracle, or Sharepoint, and do not intend to use those features, and further do not wish them to be displayed in the UI.
RESOLUTION
After upgrading to release 10.1, customers can use the unitrends-cli to mark database objects invisible. This will both remove the display of these objects from the UI and will also prevent attempts to sync inventory of objects that are not intended to be protected.
The steps to perform this process are located in How to Hide Application Instances from view in the Unitrends UI
CAUSE
With an instance visible and addressable, Unitrends expects to be able to scan that instance for valid database status. however in the case of Oracle, without a valid credential for the databases also being added, this process will fail. Customers who do not wish to protect Oracle directly with unitrends but who do wish to protect the OS it runs on can hide oracle to remove the requirement to add and manage the credetial. This is recommended for customers with multiple oracle servers,