Managed IT Services Seattle and Data Backup Done Right

How Seattle Businesses are developing contingencies that make sense

According to most businesses, they think that they have a backup. A significantly smaller number of enterprises have a backup which will actually save them in a disaster. Between “the backup runs every night” and “we can recover fully within hours” is where data disasters live and there is more in it than anyone will ever want to know until they find themselves in the middle of one. Managed IT services Seattle providers have made bridging that gap a core component of their offering, as those that succeeded and those that failed big data loss events were not just lucky. It was by preparation that they were separated.

managed IT services Seattle

Backup Strategy is a solved problem, right? Make a backup, save them somewhere, that’s it. The truth is much more complicated — and the risks of its being misinterpreted are so serious, the specifics are just that important.

What does most back up plans lack?

A one night-per-night backup that is successful is not a backup plan. It’s part of part one. The other components, where the backup is stored, how many copies exist, how recently the backup process was tested, how long the backup process takes when needed in reality, decide whether or not the backup will work when it is needed. In professional backup, the minimum requirement is three copies of data on two media types with one copy off-site: 3-2-1 rule Many businesses have one copy which is stored on their storage and there is no off-site redundancy. A fire, flood or ransomware attack that infects both the primary data and the backup occurs on the same network won’t work out, either.

 

Ransomware encryption goes beyond the critical systems and becomes the protection of backup systems, too: Off-site and offline backups — that is, copies which are physically or logically separated from the network — are the ransomware defense. It’s becoming more and more important as ransomware attackers have discovered how to specifically attack backup systems in preparation for the ransomware attack, because that is the reason why businesses are not paying.

 

Managed IT services Seattle providers recognize these threat vectors and create backup architectures that take them into consideration instead of simply running a scheduled backup. While the architecture may vary based on the size of the business’s data set, the recovery time goals, and budget, the underlying principles remain the same.

The number you’re interested in is recovery time

Businesses invest a lot of time in considering the frequency of the backups — how often they get backed up, how much data would be lost in the worst case scenario. These are significant questions. They’re not the most significant question. Perhaps the most significant query is, “How long does recovery really last? Hours? Days? Longer?

 

A business with a recovery capability of 4 hours is in a very different situation than a business with a recovery capability of 4 days. The four-day recovery business may have a technically functional backup that is compliant with all of the specifications that the IT team set. Four days of backups equals four days of downtime — lost revenue, missed obligations, relationships that may have been damaged, and organizational stress that doesn’t just vanish once systems are restored. Recovery time objectives should be established in advance, and not during a disaster. There are varying tolerance levels in different systems. Email doesn’t like to be lost. The relational database that supports the core business functions can be fatal. Those varying criticality levels should lead to implementing a variety of backup and recovery designs: aggressive replication, faster failover options, more systems investment for those systems whose downtime is more critical.

 

Managed providers closely work on this analysis with the clients while designing the backup architecture. This leads to a recovery strategy that focuses on ‘appropriate’ data first, and not all data at the same time.

The Testing Problem Nobody Talks About Enough

Untested backups are speculations. They might work. They could slip up when they’re needed most. If there’s no testing, no one can be certain which. Backup systems fail in particular ways which do not announce themselves. The backup job seems to be successful, and the data is corrupted, but only during a restore operation. The backup media is in poor condition. The version of the recovery software does not correspond to the one used for creation of the backup. The restoration process is fine for smaller data sets, but is more time consuming than time the business is willing to tolerate when it is running at full production data volume.

managed IT services Seattle

All these failures are actual and not theoretical. These are all actual businesses that have experienced them. None were found in the course of testing, but rather during actual recovery attempts (the worst time to find). Managed providers routinely test restores – they are restoring data from backups to ensure that the process is working and the recovery time is in the acceptable range. This is not something that could be considered an option for a professionally managed backup strategy. The difference between a backup system and a backup assumption is the verification part.

 

The frequency of tests should be based on the importance of the systems being tested. The frequency of testing varies based on the type of data, with core business systems requiring more frequent testing than archive data. Not only should the results of tests be noted, but documented and reviewed. If recovery from backup is becoming increasingly longer over time, due to larger data volumes, this trend should be detected and corrected before it becomes too difficult to adhere to an acceptable recovery time.

Disaster/Incident Response 24/7 IT Support and Response

Unfortunately, data loss events and ransomware attacks find their way into the news at the wrong times. Before most internal IT arrangements even know it is happening, the attack is allowed a few hours to run before it starts at 11pm on a Thursday. Having 24 hour IT support services from a managed service provider with continuous monitoring and an after hours response capability alters the time line dramatically. Monitoring systems alert to anomalous activity, such as encryption patterns to files, unusual access to the backup system, or unusual data movement, and on called staff review these at any hour. Containment begins during the attack and not the next morning.

 

The point of time is extremely critical in the case of backup integrity. Ransomware operators target backup systems because, like they know, it is the backups that can be used to recover without paying ransom. Ninety minutes have elapsed since an attack that has been detected and contained at 12:30am. The attack found at 8am the following morning has nine hours. This disparity in damage, including damage to backup systems, is not inconsequential. Off-site and air-gapped backups are just for such a situation in which the primary and secondary copies are accessed and corrupted before the attack is detected. However, the sooner a detection and containment, the more effective the backup situation will be and there will be more recovery options.

There are some version history and granular recovery options available

It can be helpful to have a backup that backs up a full system snapshot from last night. None of this helps when you need to recover a particular file that was accidentally deleted 3 days ago or when a corruption was added slowly, with the previous night’s backup already having the corrupted data. Version history — capable of keeping multiple versions of the data over a period of time, not just the latest — is relevant to these situations. While a most-recent back-up will protect against data corruption, restore from a specific point in time, days or weeks before, does. Because granular recovery allows you to restore a single file, folder or database record instead of a complete system restore, it can help save time on the most common data recovery requests. If an employee mistakenly removes an important document, the organization’s entire server doesn’t have to be restored. They need that one file back on track, and without any disruption to the business.

 

Managed backup systems with suitable version history and granular recovery can deal with these everyday recovery requests routinely as a service desk incident and not as an emergency. To the employee waiting and to the business paying for the time it takes, there is a difference between “we can get that file back in fifteen minutes” and “we’ll need to schedule a full restore and it’ll take most of the day.

Business Continuity Planning is Backup Strategy

Backup strategy is not a standalone plan — it’s part of a larger business continuity plan that includes all aspects of incident response, disaster recovery, and communication plans if systems are down. B2B with good backups, but no documented recovery procedures is partly prepared. With recovery procedures but no tested backups, a business is partially prepared. Neither is ready. The managed IT relationship that provides real business continuity coverage ties these together in to a plan — backups that are tested and up to date, documented and rehearsed recovery procedures, and rapid action that covers recovery in the event something goes wrong.

managed IT services Seattle

Seattle companies that have attempted to do so are consistent in their shift in paradigm from technology risk. It does not go away; the threats are real and even if there is a plan, they don’t stop. The anxiety is unique, though. The question becomes: we know what we would do if from what would we do. That’s the transition from uncertainty to preparation that good backup strategy and managed IT support is all about.

Scroll to Top