Thanks for the details. Let me give you some overview on how you should do this upgrade.
You are currently running version 3.7.1 which is close to 5 years old.
After that we have made the following version,
The current release is 5.2RC1 which is soon going to become GA. I am writing this in the assumption that you will upgrade to the latest version 5.2RC1.
The current upgrade plan would be to go like this
3.7.1 > 4.0.2D12 > 5.2RC1
Upgrade from 3.7.1 to 5.2RC1 is directly supported and seamless. But you should know and consider the following.
Version 3.7.1 was running with sybase version 18.104.22.16896
In version 4.0 there are 2 major changes
Sybase version 10.0.1.3831. Also in 4.0 there is
Major change in the way Performance Adviser data was written/stored
So since you are upgrading, all these PA flat files needs to be rewritten in the new format which would take considerable amount of time depending upon the amount of PA data you have.( We have seen PA flats files upgrade taking up to 26 hours when the data was close to 250GB). The rule of thumb is that its takes approximately 1 hour for each GB of PA data. Also it needs atleast 40% free space of the perf dir current size, inorder to do this upgrade with out any issue.
In 5.0 there is introduction of edition of dfm called express and standard.
In 5.1 there is a split of mode in the dfm called cluster-mode and 7-mode.
In 5.2 there is purge of dfm database for the following type of data which may again take considerable amount of time
Deletion of mark-deleted objects and its history
Purge of data protection job progress events older than the value specified in dfbm options list jobpurgeolderthan value. By default the value is 90days.
Purge of events older than the value specified in dfm options list eventpurgeinterval. By default the value is 180days
Also before upgrading pls find a 64bit server with supported OS by referring the IMT.
The current memory footprint is not sufficient, you would atleast need 8GB of memory and my recommendation would be 16GB.
Some of your existing monitoring intervals are too frequent than the default ones.
Pls reset them back to default. List below are the same.
ccTimestamp 8 hours 4 hours 13 Jun 08:03
cfTimestamp 1 minute 5 minutes 13 Jun 16:03 Normal 13 Jun 16:02
diskTimestamp 1.25 hours 4 hours 13 Jun 15:36 Normal 13 Jun 14:48
ifTimestamp 1 minute 15 minutes 13 Jun 16:03 Normal 13 Jun 16:02
licenseTimestamp 8 hours 4 hours 13 Jun 13:31 Normal 13 Jun 08:03
qtreeTimestamp 30 minutes 8 hours 13 Jun 15:33
userQuotaTimestamp 15 minutes 1 day 13 Jun 16:03 Normal 13 Jun 15:48
statusTimestamp 1 minute 10 minutes 13 Jun 16:03 Normal 13 Jun 16:02
sysInfoTimestamp 30 minutes 1 hour 13 Jun 15:57 Normal 13 Jun 15:33
svTimestamp 30 minutes 30 minutes 13 Jun 15:33
svMonTimestamp 8 hours 8 hours 13 Jun 08:03
xmlQtreeTimestamp 30 minutes 8 hours 13 Jun 16:03 Normal 13 Jun 15:33
vFilerTimestamp 1 minute 1 hour 13 Jun 16:03 Normal 13 Jun 16:02
Pls take a backup using the cli dfm backup create before you upgrade and keep it safe.
I would also recommend you to do a dry to know exactly how much time the entire upgrade would take before you go for the live one.
Stand up a new 64bit server, install 4.0.2D12
Stop all service and start only sql service
Restore the backup taken from 3.7.1 using dfm backup restore cli. Time the entire upgrade process.
This is where the PA flat files will be rewritten in the new format
Create another backup in 4.0.2D12 after completion of step 3
Now Download 5.1 and upgrade on the same server, here you will make the following choices,
Edition as Standard
Mode as 7-Mode
After completion of step 5 install the dfmpurge https://communities.netapp.com/videos/3134 tool and run it in report mode to estimate how much time the upgrade to 5.2 will take as in 5.2 upgrade the following is involved ( its recommended to reduce the value of jobspurge and events purge before upgrade to 5.2 as maximum stale data is cleaned and db is de-fragmented)
Database validation, if its an upgrade,(not in case of restore as database backups are by default verified and validated. ) it takes close to 10mins for every GB of the database size.
Purge of Mark-Delete objects
Purge of DataProtection Job history
Purge of all events older than eventpurge interval.
Based on the dry run estimated plan a downtime and upgrade as per the plan of 3.7.1 to 4.0.2D12 to 5.2RC1.