%402x.svg)
No results.
Teller Government Cashiering runs its disaster recovery on AWS, with primary hosting in Oregon and a separate disaster-recovery region in Virginia. The design targets a recovery point objective (RPO) of 5 minutes and a recovery time objective (RTO) of 1 business day, meaning at most about five minutes of transactions could be lost in a regional failure, and the platform is engineered to be restored and operational within one business day.
These two numbers are the core of any continuity plan, and they answer different questions.
For a treasury or finance team, the practical translation is straightforward: your continuity plan can be written around a small, bounded data-loss window and a defined restoration timeline, rather than an open-ended "we'll see how long it takes."
A 5-minute RPO means the maximum transaction exposure in a regional failure is roughly five minutes of activity. That is the number auditors and continuity planners care about most.
Geographic separation is the whole point of disaster recovery. The primary environment in Oregon handles day-to-day cashiering and revenue processing. The disaster-recovery environment in Virginia sits far enough away that a regional event affecting one location, such as a large-scale power, network, or facility disruption, does not take out both.
This is a standard and well-established pattern in cloud infrastructure: production in one region, a recovery target in another, with data replicated between them. The 5-minute RPO reflects how current the replicated data is kept. Because the replication window is small, the Virginia environment stays close to the live state of the Oregon environment at the moment of a failover.
Disaster recovery is not only about availability. It is also about keeping sensitive payment and citizen data secure through the entire lifecycle, including in backups and replicas.
Teller encrypts data both at rest and in transit, using AWS Key Management Service (KMS) for key management. In plain terms:
Because the data replicated to the Virginia region is encrypted the same way as the primary, the disaster-recovery copy does not become a weaker link in your security posture.
It helps to separate two related but distinct commitments. Disaster recovery addresses rare, large-scale events: what happens and how quickly service returns after a regional failure. Everyday availability addresses normal operations.
Teller targets a 99.9% availability SLA during business hours, with financial remedies for downtime. Disaster recovery, with its 5-minute RPO and 1-business-day RTO, is the backstop underneath that everyday commitment. One keeps counters running on a typical day, and the other defines the worst-case floor.
Government continuity plans and audit checklists tend to ask the same core questions of any hosted system. Teller's disaster recovery provides concrete answers to each.
These are the details that let a finance director, controller, or auditor slot Teller into an existing business continuity and disaster recovery plan without guesswork. The numbers are specific, the regions are named, and the encryption approach is defined, which is exactly what a review process is built to verify.
Teller's disaster recovery covers cross-region hosting on AWS (Oregon primary, Virginia DR), a 5-minute RPO, a 1-business-day RTO, and encryption at rest and in transit managed through AWS KMS. Together these give a finance team a bounded, documentable picture of both maximum data exposure and restoration time, which is what continuity planning and audit review actually require.
