While N2WS Backup & Recovery for AWS works very well, there are a few areas for improvement. As an enterprise managing a large number of accounts, the main challenge we face is the rollout of new JSON scripts during upgrades. This process can be tedious and time-consuming. If you have a strong AWS team, automating these rollouts internally helps, but I would recommend that N2WS provide built-in automation for JSON script deployment as part of the upgrade process. This enhancement would make upgrades smoother and reduce operational overhead.
Director of Information Technology & Customer Success at Maplewave
Real User
Top 10
Nov 18, 2025
N2W currently offers a rich feature set, but we believe a few enhancements could make it even more powerful, especially for enterprises. One area where we would appreciate improvement is support for additional AWS native services, such as Lambda function backups and S3 beyond archive. This would help secure a broader range of workloads without custom scripting.
Cloud Engineer at a tech vendor with 51-200 employees
Real User
Top 20
Oct 14, 2025
I am quite satisfied with N2WS Backup & Recovery for AWS backup and disaster recovery. However, it could be improved to include disaster recovery in cross accounts for Azure in upcoming releases.
Enterprise Systems Engineer at a writing and editing position with 51-200 employees
Real User
Top 10
Sep 29, 2025
They could expand their offering to include Lambda function backups and other native AWS services, as these can be recreated through CloudFormation or Terraform. This would help those who are not familiar with Infrastructure as Code to back up and restore these services without the overhead of understanding IaC configuration.
Cloud Engineer at a financial services firm with 1,001-5,000 employees
Real User
Top 20
Sep 15, 2025
While the product is excellent, there are a couple of areas for potential improvement. The process for version upgrades, which sometimes requires deploying a new instance, could be streamlined to allow for a more seamless in-place update. It would be extremely useful to have the ability to set a retention period on manual backups. Occasionally, we take a manual snapshot before a major deployment, and currently, these can be forgotten, leading to unnecessary storage costs. Adding an 'auto-delete after X days' option to manual backups, similar to scheduled policies, would be a fantastic addition for cost management and general housekeeping. The EKS backup module should be a great feature, and it would have been a useful functionality to have for cluster backup management.
Improved disaster recovery options and expanded multicloud support are two areas where N2WS has already made significant advancements in the latest version. I am eager to upgrade and take full advantage of these enhancements.
Data Backup & Recovery Administrator at LTIMINDTREE
Real User
Sep 18, 2023
N2WS Backup & Recovery efficiently takes cloud backups on EC2 instances. The solution has the option to take backup on-prem servers, but it's not very efficient.
Technical Adviser, Data Center at a wholesaler/distributor with 10,001+ employees
Real User
Feb 16, 2020
In terms of what can be improved, the problem is not on the feature. The problem we have found is the network because it's not so easy to access a second link for backup or data recovery or connecting to the cloud with very strict protection security. They are more oriented towards security than how to work with the backup and we have to explain how to use encryption and to manage it. In a second time customer address deduplication and compression to reduce storage size and cost. At this time, we just use the regular feature, using the AWS repository as storage for them all. Lastly, it's a global feature that the customer thinks they don't have enough tools to manage, to copy, to delete, to move, and to classify the object file in the backup directory a the storage feature level. So they need more tools to manage files in the object directory.( REST API is not enough for customers).
Pre-Sales Engineer at a comms service provider with 11-50 employees
Real User
Jan 16, 2019
Deployment is one area that could use improvement. Additional features I would like to see are the ability to restore to different vendors, AWS and Azure, and/or the ability to take the information out of the AWS cloud.
Cloud Architect, Oracle ACE, Oracle DBA at Pythian
MSP
Top 20
Jan 14, 2019
More documentation would be helpful, especially some step-by-step documents for recovery scenarios. In addition, a seamless integration with on-premise third party backup solutions would be great.
I would like them to make the controls a bit more user-friendly. The UI is a little dated and hard to use. Some of the buttons are a bit small. You have to go into the menu to get the settings you want. It would probably be good if there were some analysis dashboard or an easily accessible web dashboard for a lot of users where individual clients could see their backups, and even get recommendations or estimates of costs.
N2W offers a cloud-native backup and recovery platform tailored for AWS and Azure environments, delivering secure and rapid data protection.
N2W enables IT teams to effortlessly manage backup and restore processes within AWS and Azure environments. By leveraging policy-based management, users gain full control over rapid, secure recovery across regions and accounts. Designed to scale with workloads of any size, N2W ensures business continuity through features like immutable...
While N2WS Backup & Recovery for AWS works very well, there are a few areas for improvement. As an enterprise managing a large number of accounts, the main challenge we face is the rollout of new JSON scripts during upgrades. This process can be tedious and time-consuming. If you have a strong AWS team, automating these rollouts internally helps, but I would recommend that N2WS provide built-in automation for JSON script deployment as part of the upgrade process. This enhancement would make upgrades smoother and reduce operational overhead.
N2W currently offers a rich feature set, but we believe a few enhancements could make it even more powerful, especially for enterprises. One area where we would appreciate improvement is support for additional AWS native services, such as Lambda function backups and S3 beyond archive. This would help secure a broader range of workloads without custom scripting.
I am quite satisfied with N2WS Backup & Recovery for AWS backup and disaster recovery. However, it could be improved to include disaster recovery in cross accounts for Azure in upcoming releases.
They could expand their offering to include Lambda function backups and other native AWS services, as these can be recreated through CloudFormation or Terraform. This would help those who are not familiar with Infrastructure as Code to back up and restore these services without the overhead of understanding IaC configuration.
While the product is excellent, there are a couple of areas for potential improvement. The process for version upgrades, which sometimes requires deploying a new instance, could be streamlined to allow for a more seamless in-place update. It would be extremely useful to have the ability to set a retention period on manual backups. Occasionally, we take a manual snapshot before a major deployment, and currently, these can be forgotten, leading to unnecessary storage costs. Adding an 'auto-delete after X days' option to manual backups, similar to scheduled policies, would be a fantastic addition for cost management and general housekeeping. The EKS backup module should be a great feature, and it would have been a useful functionality to have for cluster backup management.
Improved disaster recovery options and expanded multicloud support are two areas where N2WS has already made significant advancements in the latest version. I am eager to upgrade and take full advantage of these enhancements.
N2WS Backup & Recovery efficiently takes cloud backups on EC2 instances. The solution has the option to take backup on-prem servers, but it's not very efficient.
There is room for improvement in stability.
The GUI has room for improvement.
In terms of what can be improved, the problem is not on the feature. The problem we have found is the network because it's not so easy to access a second link for backup or data recovery or connecting to the cloud with very strict protection security. They are more oriented towards security than how to work with the backup and we have to explain how to use encryption and to manage it. In a second time customer address deduplication and compression to reduce storage size and cost. At this time, we just use the regular feature, using the AWS repository as storage for them all. Lastly, it's a global feature that the customer thinks they don't have enough tools to manage, to copy, to delete, to move, and to classify the object file in the backup directory a the storage feature level. So they need more tools to manage files in the object directory.( REST API is not enough for customers).
The GUI could be slightly improved.
Deployment is one area that could use improvement. Additional features I would like to see are the ability to restore to different vendors, AWS and Azure, and/or the ability to take the information out of the AWS cloud.
More documentation would be helpful, especially some step-by-step documents for recovery scenarios. In addition, a seamless integration with on-premise third party backup solutions would be great.
I would like them to make the controls a bit more user-friendly. The UI is a little dated and hard to use. Some of the buttons are a bit small. You have to go into the menu to get the settings you want. It would probably be good if there were some analysis dashboard or an easily accessible web dashboard for a lot of users where individual clients could see their backups, and even get recommendations or estimates of costs.