.

A Flexible Edge for Your Immutable Setup to Ensure Optimized Security

N2WS, a leading provider of data protection solutions for enterprise-grade production environments in the public cloud, has officially announced the launch of several new features for its cloud-native backup and disaster recovery (BDR) platform. In case you weren’t aware, the stated platform is designed to help enterprises and managed service providers (MSPs) combat the escalating cybersecurity attacks on organizations. Not just that, the given platform is also capable of ensuring wider data sovereignty, enhancing data security, and optimizing costs. Talk about how the new features will upon this proposition, the answer begins from new cross-cloud BDR capabilities between Amazon Web Services (AWS) and Microsoft Azure. The stated capabilities have their utility rooted in enabling enterprises and MSPs to back up servers in AWS and recover volumes in Azure within seconds, offering cross-cloud protection and ensuring compliance with new data isolation regulations. Next up, we have Amazon S3 and EBS immutable snapshots available to designate a backup, considering immutable prevents anyone, including a hacker or disgruntled employee, from altering or deleting the data stored in it. Furthermore, such functionality can also come in handy when the agenda is to let the organization achieve compliance with regulatory requirements that mandate secure short- and long-term data storage to prevent unauthorized access.

Then, there are granular backup policy reports. You see, owing to the update in question, users can now seamlessly generate a consolidated report which will highlight all their backup policies, marking a game-changer for all the enterprises and MSPs that are managing extensive backup environments with hundreds of policies. Hence, while the earlier arrangement meant reports could only highlight regular backup generations and not disaster recovery backups, it now allows users to create and filter reports that detail whether each policy includes a disaster recovery backup, where the data is being archived, how long the data is retained in the archive, and more.

“N2WS offers great flexibility in creating backups,” said Sebastian Straub, principal solutions architect at N2WS. “We don’t see immutability as an all-or-nothing option. Users have the freedom to be as granular as they need. They can apply immutability to their disaster recovery region, regular backups, or both. With N2WS, creating immutable backups is as simple as checking a box.”

Moving on, the development in question even improves upon N2WS’ VPC capture & clone mechanism. Having previously allowed users to bootstrap other regions and accounts with an identical infrastructure setup, the functionality now lets you capture and clone all meaningful networking and configurations settings, including Elastic Load Balancers. This makes it possible for organizations to quickly restore services during a regional outage and ensure that security configurations are applied across all environments, both of which help with maintaining strong security postures.

Hold on, we still have a few bits left to unpack, as we still haven’t touched upon the solution’s newfound disaster recovery mechanism for DynamoDB. Under the stated facet, DynamoDB tables can be copied between AWS regions and accounts so to support instant restoration in the event of a full-scale regional outage or malicious activity that locks users out of their AWS accounts. To go with that, it also enables migration of DynamoDB table data between regions. Joining the same would be the presence of NIC/IP Support during Instance Restore. This translates to how Secondary IP and additional NIC can now be added during an instance restore to help users modify the network settings and achieve proper communication between a restored instance and its environment. Markedly enough, beneficiaries of N2WS’ latest update can even come expecting time-based retention. Here, you’ll be able to select time-based backup retention periods, alongside the generation-based retention periods already in place. Such a detail, like you can guess, makes for an optimally flexible operation.

Hot Topics

Related Articles