Exporting historical RPO data for SAN Volume Controller Global Mirror with Change Volume sessions
You can use the GUI or the CLI to export historical RPO data for SAN Volume Controller Global Mirror with Change Volume sessions.
About this task
You can store and export historical records for recovery point objective (RPO) values on SAN Volume Controller Global Mirror with Change Volume sessions. Every time the actual RPO is calculated, the value is maintained in the internal data store. You can export the values to a CSV file, over a one-month time period.
You can use either the Copy Services Manager GUI or CLI to export RPO data.
Format of the CSV file for SAN Volume Controller Global Mirror
with Change Volumes history
The CSV file is generated with the following
values that are separated by a comma:
| CSV file value | Description |
|---|---|
| Query Time | Time that the actual RPO value was calculated. |
| Session Name | Name of the Copy Services Manager session. |
| Role Pair Name | Name of the role pair that is represented in the data. |
| Consistency Group Name | Name of the consistency group on the hardware. |
| Query Interval (in seconds) | Query interval setting to determine actual RPO. |
| Data Exposure (in hours:minutes:seconds format) | RPO data exposure is displayed in a readable format. |
| Data Exposure (in milliseconds) | RPO data exposure to provide for graphing and charting. |
Example CSV file output
#Generated at:,"Feb 23, 2016 4:14:55 PM"
#Session Name:,CSM-GMCV
#Role Pair:,H1-H2
#Start Date:,"Nov 1, 2015"
#End Date:,"Feb 23, 2016"
#Query Time,Session Name,Role Pair Name,Consistency Group Name,Query
Interval(secs),Data Exposure(hh:mm:ss),Data Exposure(milliseconds),
2015-11-23 11:56:05.0,CSM-GMCV,H1-H2,CSM-GMCV,30,0:03:19,199000
Interval(secs),Data Exposure(hh:mm:ss),Data Exposure(milliseconds),
2015-11-23 11:56:05.0,CSM-GMCV,H1-H2,CSM-GMCV,30,0:03:19,199000
Exporting RPO history by using the GUI
About this task
Follow these steps to export RPO history through the GUI:
Procedure
- Log in to the Copy Services Manager GUI as a user with administrator privileges.
- From the Overview panel, click Session Overview. Or, from the menu bar, click Sessions to get to the Sessions Details panel.
- From the Session Actions menu, select . A pop-up window is displayed.
- Select the role pair.
- Ensure that the RPO option is selected for the type of data.
- Enter a valid date range that spans no longer than a 31-day period for the start and end dates for the export.
- Click OK to confirm, or click Cancel to exit.
Results
Exporting RPO history by using the CLI
About this task
Follow these steps to export RPO history through the CLI:
Procedure
- Log in to the Copy Services Manager CLI as a user with administrator privileges.
- Use the exportgmdata command with the -rpohistory option to indicate that you want to export the RPO history. Then use the -rpo_start and -rpo_end parameters to specify the date range, which must span within a 31-day period.
Results
Customizing settings in the rmserver.properties file
About this task
You can customize some of the settings for the historical RPO reporting in the
rmserver.properties file, including the retention period, the query interval,
and the reserved disk space.
- Retention period: The default retention for RPO data is set to 91 days. After 90 days, RPO data is removed from the internal data store. The db.svcgmsessionrpo.retention.days property can be created and set in the rmserver.properties file to change the default retention value. Change this value to indicate how many days of data to keep in the internal data store.
- Query interval: During the 30-second default query interval, the actual RPO is calculated and an entry for the session is added to the internal data store. You can modify the query interval in the hw.svc.gmcv.dataExposureInterval property in the rmserver.properties file. The value is in seconds. Change the value of this property to the number of seconds that you want to determine the actual RPO.
- Reserved disk space: You can determine the amount of space that is needed for historical reporting. With the default query interval set to 30 seconds, a year of data for a single session is estimated at around 200 MB of disk space. If you increase values for retention or query interval, you must ensure that there is enough disk space to accommodate the changes.