If you plan to migrate to the latest version of Exchange, tackling the size of the Exchange information store (IS) to be moved or upgraded is paramount:
- The smaller your IS, the quicker the migration process will be, and migrating outside of core office hours becomes a possibility.
- The smaller your IS, the faster you will be able to recover your old Exchange service if your upgrade goes wrong for whatever reason. Again, this makes achieving an upgrade (as well as having a contingency plan) a possibility outside of working hours.
- The smaller your IS, the more stable your old Exchange server will be to migrate or upgrade from, and you will be able to eliminate IS corruption issues.
By using EAS to reduce the size of your existing Exchange stores in advance of migrating, the time taken to convert the message store is considerably less, and the whole process is made faster, simpler and less fraught with risk.
By archiving everything older than 30 days, one site was able to reduce its migration time from a predicted 76 hours to an actual 22 hours.
You can also reduce the size and the number of Exchange servers you will need once you’ve migrated. This is because EAS can be used to archive ‘colder’ messages onto less expensive systems rather than ‘clog up’ the disks of expensive, high-end Exchange servers.
Prior to the installation of EAS, a leading pharmaceutical was adding new Exchange servers were bi-monthly to accommodate growth.
Uniquely, EAS is really simple to migrate between versions of Exchange, with no need to 're-poiint' shortcuts when you move to the new Exchange environment.
|