Best way to offload most of site

[supernal]

In an ideal scenario I’m able to take a chunk of my site and place somewhere else as read-only so the content is preserved for future readers but for my production site in terms of backups and portability (when switching hosts), I’m only worried about migrating the most recent X years of content 

Has anyone encountered a scenario like that or have any ideas? 

[bfarber]

The forums application (only) has an archiving feature which will move the posts into another database table (or even another database server entirely) for this purpose. Archived topics are read-only and as mentioned, can be stored on a remote server. The system is configurable so you can specify what content to archive.

[supernal]

1 hour ago, bfarber said:

The forums application (only) has an archiving feature which will move the posts into another database table (or even another database server entirely) for this purpose. Archived topics are read-only and as mentioned, can be stored on a remote server. The system is configurable so you can specify what content to archive.

Unfortunately one limitation I ran into is that it archives topics by the last post and one option which is not configurable is making this go by start date instead. We were only able to get the archiving tool to recognize 17-20% of total topics to archive and we’d be ideally aiming to archive half or more 

Also when configuring a remote sql server IPS recommended a high speed link or else anticipate timeouts. With aiming to archive as much content as we’d like we wouldn’t want the user experience to degrade so heavily when looking at older posts. Although we won’t have a need to write to them they can get read fairly frequently