I'm looking for suggestions or documentation on the best way to do it.
The database is huge. 10 years of data (still trying to find out if we can purge some older data first).
The biggest issue is the attachments. because of how HPSM stores them, it seems we must keep the application (and the web client) active as long as the data is needed. Right now we have 3 web servers (linux), application server (unix) with 11 servletts, and the database server (also unix). I'm assuming we can at least pare down to 1 webserver (no lb). If it werent for the attachments, we could just keep the ticket tables (and activity), and offer reporting, but we have a lot of attachments.
Any suggestions?
Comment