Managing Objects Collected from Centralized Systems
When collecting from a centralized system, such as Hitachi Device Manager or vCenter, Storage Viewer relies on the system to supply the information on the devices and resources that are available. For objects collected via a centralized system, there are two methods for removing collected objects:
• Preferred Method: Go to the Data Collector policy in the Portal and use the “Exclude” field to exclude objects from collection. For example, for Hitachi Data Systems, you would exclude arrays in the Data Collector policy. Similarly, for VMware, you would exclude ESX servers in the Data Collector policy. When you exclude objects through a Data Collector policy, Storage Viewer will automatically delete these objects from the reporting database.
• Alternatively, you can go to the centralized system and decommission the object. In this case, you must also delete the object from the Storage Viewer database. See
Remove Objects from the License Count.
Managing Directly Probed Enterprise Objects
Many enterprise objects are probed directly to collect metadata. For objects that are probed directly, follow these steps to remove them from license counts:
• Exclude from Collection: If the object was captured during data collection, you will need to exclude it from collection so that future collections do not recapture the object. See
Exclude Objects from Future Data Collections.
For Storage Viewer for Backup, you can go directly to the backup software and remove the client from the backup policy, according to the vendor’s instructions. In this case, you do
not have to delete the object from the database.
• Remove from License Count: In order to remove a directly probed object from licensing consideration, you must delete the object via the Object Maintenance tool in the Portal. See
Remove Objects from the License Count.