Yes this can be done.
ProSphere uses agentless performance data collection for discovered configuration items (CIs). Both Ionix ControlCenter 6.1 and ProSphere recognize a similar set of CIs, called "managed objects" in Ionix ControlCenter. This makes it possible to import historical performance data collected and stored in Ionix ControlCenter’s Workload Analyzer (WLA) Archiver to add to ProSphere’s performance data for trending.
The advantage of the WLA data import feature is that it enables you to view Ionix ControlCenter performance data in ProSphere without logging into Ionix ControlCenter. You can reimport the Ionix ControlCenter performance data any number of times to obtain the latest performance data for discovered CIs or import data for newly added Ionix ControlCenter CIs.
Only users with administrator privileges can view, set up, and run import jobs in ProSphere.
The import job imports 30 days of daily performance data (.btp files) for discovered CIs from the Ionix ControlCenter WLA Archiver data source. You can import 30 days of performance data, excluding the performance data for the day the import job starts running.
The imported performance data can be viewed in the Configuration Item dialog box.
If there are multiple instances of Ionix ControlCenter in your enterprise setup, you can import performance data from all the Ionix ControlCenter WLA Archivers to ProSphere.
You can access the Ionix ControlCenter performance data import feature by selecting Administration > System > Import Performance Data. The Import Performance Data from ControlCenter dialog box appears. The Import Performance Data from ControlCenter dialog box allows you to perform the following activities:
I have tried for weeks now to import WLA Archive data from ControlCenter into Prosphere 1.7. The process failed and keeps resubmitting itself and create a lot of concern for our VMware admins. The only thing I can do is to stop the pdc-server service and it is quite lame. Is there any other way for me to delete the CIs from the queue or stop the migration job or good?
Depending on the amount of Discovered objects and btp files been imported by ProSphere this can take a long time to complete.
The WLA import is a lower priority process so to not affect normal PDC-server activity. So when PDC-server is busy, WLA import will be paused. But some times the import process does not continue after the PDC-server becomes free from the normal activity. Where a restart of the PDC-server is required to kick off the import.
ProSphere Engineering are changing how the import WLA process is working in the next release of ProSphere.
Please open an SR with Support to look into your issue
Thanks. I will open a SR.
Dung N. Pham
Enterprise Storage Group
United States Senate Sergeant at Arms
Office: (202) 224-1085
Cell: (202) 525-9339