Running GoodSync on both ends moves records out of locked-down county networks to a central store, with minimal firewall changes and 600 million files managed.
Roughly 140 servers and a handful of workstations across town and county clients in multiple states, managed from two central sync servers
Tens of thousands of new record images are pulled in every day from client sites
Same-day for clients on data replication services, so clerks and residents can find new records quickly
The company is a software vendor serving town and county clerks' offices, providing digital land record management. Its clients' digitized records (property, vital, judicial, and other municipal records) are pulled from each office's local servers into a central image store and published on a public, searchable website. The company also pulls database backups from clients so its team can troubleshoot, run upgrades, and verify data. Competition is limited to a handful of regional providers, and word of mouth between clerks matters, so service standards are a competitive advantage.
Clerks expect new records to appear on the public site quickly. Meanwhile, client IT departments keep tightening security, and every new client adds more data.
Many counties sit behind firewalls. Reaching a client's server to check on a failing job means requesting access first, and some small offices have a single IT contact located hours away.
Digitized records (TIFF images of maps, deeds, and judicial documents) add up to roughly 600 million files in the central repository. Tens of thousands of new images arrive each day.
The company's service standard is records live on the web the next day, and same day for some clients. If images are late, clerks field calls from residents, and the company hears about it fast.
The company adds roughly two new clients a month. Each one brings its own set of jobs, so the approach has to scale without adding administrative work.
We have a number of counties now that are behind firewalls. We need to request access before we can log in.
The company standardized on GoodSync as its data pipeline between client sites and its central servers, using a repeatable job template for every new client.
GoodSync is installed on each client machine and connects back to the company's servers with GoodSync Connect. No elaborate firewall rules are needed, as long as the company's network is whitelisted.
Each client gets a consistent set of roughly three to four jobs built from templates. One syncs record images, one pulls a database backup, and others push reports and configuration files back out. Some clients also get custom file-verification jobs.
Images flow from client sites into a central repository and are published on a searchable public website, so residents and professionals can find and download records themselves.
The company runs GoodSync in two parallel roles: pulling images and backups to its own central servers, and pushing reports and configuration back to clients.
Two central sync servers run the jobs, rather than the client machines. That way the team doesn't have to request access to each county's server whenever it needs to check or change a job.
GoodSync moves new record images to the central image store and pulls database backups, which the team uses for troubleshooting, upgrades, and data verification.
The same connection is used in reverse to deliver reports and configuration files to each client site.
GoodSync has become the backbone of the company's data pipeline: predictable to deploy and workable in environments where other approaches would need extensive IT approvals.
With GoodSync on both ends, jobs run without extensive firewall changes. The only requirement is that the company's network is allowed through. This matters in government environments where every rule change takes time.
Tens of thousands of images a day flow into a repository of more than 600 million files, supporting the company's next-day publishing standard.
Changes the team has made to its GoodSync setup have reduced the number of 'where are our images?' calls from client offices.
If GoodSync is running on both sides, it pretty much just works. As long as our network is whitelisted, it works.
Runs on both sides of the connection, so data moves without extensive firewall changes
About two new clients a month, each with the same proven set of jobs, feeding 600M+ files
See how GoodSync can move records and files reliably from client sites, even behind strict firewalls.
