Knowledge Base

Older hardware does not need to be replaced solely because of its age, but it should not be kept in service after it becomes a security, compatibility, or reliability risk. Planning replacement before a failure also gives us time to coordinate FileMaker and operating-system upgrades with less disruption.

A computer may continue to run after its operating system stops receiving security updates, but that does not make it appropriate for business use. Unsupported operating systems can also prevent installation of current FileMaker versions, browsers, security tools, and backup software. 

Slow storage, insufficient memory, failing drives, overheating, and repeated unexpected restarts can affect FileMaker performance and increase the risk of downtime. A server should be replaced before hardware becomes unreliable rather than after a failure interrupts access to the system. 

Older hardware may not support the operating system required by a current version of FileMaker Server or FileMaker Pro. Continuing to delay replacement can create a larger upgrade gap and make future transitions more complicated.

An increase in users, file size, container data, integrations, remote access, or automated processes may require more capacity than the original computer was designed to provide. Even functioning hardware may need replacement when it no longer supports the current workload.

Workstations can often be replaced individually, but server replacement requires coordination of backups, security certificates, FileMaker Server configuration, schedules, and testing. 

Please involve Portage Bay Solutions before purchasing or configuring a replacement server so we can confirm that the proposed environment meets your FileMaker requirements.