Documentation  >  Operations  > 

Maintenance

We are committed to keeping the TicketRx servers running well for our customers. An integral part of this is regular, routine maintenance on the TicketRx servers. This maintenance includes items like:

  • installing TicketRx software updates
  • applying operating system security and bug fixes
  • adding additional hardware to handle customer growth
  • replacing failed equipment

Unless an emergency arises, the TicketRx team schedules maintenance windows with our customers in advance. There is always a chance of something going wrong when we are working on the system, so it is important for customers to know when we are working on the system. That is what the maintenance window is for, it lets customers know in advance that we are working on the system. This allows customers to be prepared for the maintenance work.

Sometimes, the maintenance work requires taking all or part of the system offline for a time. Typically, this downtime is much shorter than the maintenance window. We do as much work as possible in our test systems to prepare for the maintenance. This allows us to keep the downtime low.

We also schedule maintenance windows for longer than we expect to need in order to accommodate our contingency plans if something does not go as expected.

A typical maintenance window involves accessing the production servers, making some changes, and then incurring a short downtime. For example, we may schedule a 30-minute maintenance window to perform 10 minutes of work that includes a downtime of 5 minutes.

When we schedule a maintenance window, we tell our customers how long the maintenance window needs to be and how much downtime to expect.

When we do maintenance, we send a notification to our customers when we start and finish the maintenance work.