Iterative history export

This is an advanced procedure to try if it is absolutely not possible to accept loss of history data from a station to which you are adding NCHSD, you can potentially use this iterative process to get all the history records to the cloud.
Prerequisites:
  • Before using this, please delete or clear records from any history that are not essential. Also, clear records before the earliest time you actually need the data. Any reduction in size you can achieve will make this process easier.
 NOTE: For a very large database, the following may need to be done in many steps. Start with very small steps, perhaps even one history, and conservatively increase the number of histories you add. This is particularly important when the time range is long, as that means each history will have many records. 
Perform the following steps:
  1. Set the CloudHistoryDeviceExt Batch Trigger Time property to Manual.
    This will prevent any archival attempts when you are not expecting it.
  2. Open the Cloud History Export Manager view, and click All Descendants so that all histories will be shown.
  3. Click History Learn.
    This will add CloudHistoryExports for ALL the histories in the database.
  4. Select a single Cloud History Export and click Archive.
    This will archive the single Cloud History Export's records to Sentience.
  5. If the previous step is successful, continue with each additional export, one at a time.
     NOTE: If you know that the amount of data is not large, you may conservatively increase the number of history exports you select to expedite the process. 
  6. Once completed for all cloud history exports, set the Batch Trigger Time property back to its original value. (The default is Interval - 15 minutes.).
 WARNING: If you push too much data at one time, by selecting too many histories, Sentience will block the station from sending further data. In addition, you can cause blockages for other completely unrelated systems if too much of the Sentience IoTHub processing bandwidth is consumed by sending too many histories. Use great care when grouping history exports for archival.