Version up from DX NetOps Ver. 2.0 to 2.2 / Retention period

[MARUBUN SUPPORT]

Hi Team.

Our customer has following question.
Please give me some advice

[Question]
The customer was using DX NetOps Ver. 20.2 with the setting to retain 180 days of data per hour (HourlyRollupDataRetentionPeriod=180).
They have upgraded to Ver. 22.2 with the default retention period of 90 days, resulting in an unexpected loss of 90 days (180-90=90) of data.
(For example, the data from January to June was retained in Ver. 20.2, but after upgrading to Ver. 22.2, only the data from April to June is retained.)

They have saved 5 minutes of data, so is it possible to generate 1 hour data from this data?
Or is there any way to recover from individual backup data?

<Target Data>
   Session Information
   Session information (aggregate data)
   Sent/received data information/number of sessions
   PPS information / number of sessions
   Packet Loss Ratio / Number of Sessions
   CPU utilization
   CPU utilization (aggregate data)
   Memory usage rate
   Memory usage rate (aggregate data)
   Pool address information

Best Regards,
Marubun Support

[Catalin Farcasanu]

Short answer is no. There no possibility other than restore of an old save and then re-running the upgrade. 
This is why testing is very important and why also reading the release notes prior to upgrades. Some of those might be mentioned in the release notes. 

[Jeffrey Pinard]

The retention settings at http://DA:8581/rest/globalretentiondefinition should be preserved during upgrade.  The values are stored on the globalretentiondefinition item in the database.

We only set the values to the default on initial install.

Was there any sort migration of the vertica DB during the upgrade?

There is no way to do the rollups.  The rollups are based on messages generated from data loading and the poll data has already been loaded.
Plus as-polled only goes back 45 days by default, so there is no data to roll up. 
What is the current PolledDataRetentionPeriod value?