# Page


# 1  Get Started with N2W

Quickly install N2W, set up your server, and configure your first automated backup.

N2W Backup & Recovery is a powerful tool that's essentially "plug-and-play". It takes about 20 minutes to set up and works in your existing AWS environment. N2W plays well with other platforms for making backup and recovery worry-free. This Quick Start guide will walk you through the core steps to get N2W up and running.

A quick word about passwords before we get going. N2W strongly recommends that you create a strong password for the server. Make sure no one can access it or guess it. Change it regularly. N2W enforces the following password rules:

·         Minimum length of 8 characters.

·         Not a common word or phrase.

·         Not numeric characters only.

{% hint style="info" %}
Prefer a video tutorial? Follow along right here 👇 and you'll be set in \~12 minutes.
{% endhint %}

[https://n2ws.com/support/install-guide ](<https://n2ws.com/support/install-guide >)


# 2  Launching N2W  Backup & Recovery

You have 2 options to launch: via the 8 steps below or using CloudFormation.

#### To launch N2W as part of a 30-day free trial or as a BYOL edition:

1. Go to <https://aws.amazon.com/marketplace/>
2. Search for ‘n2w’.
3. Select your edition of **N2W Backup & Recovery (CPM)**.
4. Select **Continue to Subscribe**.
5. In the AWS login page, enter your AWS account information, and select **Continue to Configuration**.
6. Under **Configure this software**,:
   1. Change the fulfillment option to **Amazon Machine Image (AMI)**.
   2. Select the latest version in the **Software Version** list.
   3. Select the **Region** you want to deploy to.
7. Select **Continue to Launch**.
8. In the **Choose Action** list, select **Launch through EC2**.

## 2.1  Launching with CloudFormation

CloudFormation is an AWS service that allows you to treat a collection of AWS resources as one logical unit. CloudFormation provides a common language for you to describe and provision all the infrastructure resources in your cloud environment, across all regions and accounts in an automated and secure manner.

{% hint style="info" %}
The IAM role will automatically contain the required permissions for N2W operations.
{% endhint %}

To configure N2W using CloudFormation, see section [6](/quick-start/6.-configure-n2ws-with-cloudformation).


# 3  N2W Server Instance Configuration

## 3.1  N2W Server Instance Connectivity

For the configuration process to work, as well as N2W’s normal operations, N2W needs to be able to “talk” with AWS APIs. Thus, it needs to have outbound connectivity to the Internet.&#x20;

Verify that the N2W instance has Internet connectivity; this can be achieved by placing the instance in a public subnet with a public IP address, by assigning an Elastic IP to the instance, using a NAT instance, or by using the Internet Gateway. You also need to make sure DNS is configured properly and that HTTPS protocol is open for outbound traffic in the VPC security group settings. It is by default.

## 3.2  Creating an Instance When Launching through EC2

1. Under the **Name and tags** section, enter a name for your instance in the **Name** box.

   If required, select **Add additional tags.**

<figure><img src="https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/20667JAjsalg9aoC20Is/name-and-tags.png" alt=""><figcaption></figcaption></figure>

&#x20; 2\.  Under **Application and OS images (Amazon Machine Image)**, leave all default values, as this section shows what AMI we are using for the EC2 instance image.

<figure><img src="https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/moH5d8oojsHd6CnGvzPT/AMI.png" alt=""><figcaption></figcaption></figure>

&#x20; 3\.  Under **Instance type**, the recommended minimum size is **t3.medium**. However, for bigger environments, the type may need to be larger.

{% hint style="info" %}
For information on choosing the appropriate size, see [https://n2ws.zendesk.com/hc/en-us/articles/28811725028125-Recommended-instance-sizes-and-volume-types-for-N2W-Servers ](<https://n2ws.zendesk.com/hc/en-us/articles/28811725028125-Recommended-instance-sizes-and-volume-types-for-N2W-Servers >)
{% endhint %}

<figure><img src="https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/RWIBynNGDEh77H6vbTEv/Instance-type.png" alt=""><figcaption></figcaption></figure>

4\.  Under **Key pair**, you can create a new key pair or use an existing one. The key pair is used when connecting to the instance’s CLI.

<figure><img src="https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/HCIgDX5dE0cFtPVS9tWP/key-pair.png" alt=""><figcaption></figcaption></figure>

&#x20; 5\.  Under **Network settings**, select a relevant **VPC**, **Subnet**, and **Security group** for the instance. For the configuration process to work, as well as for normal N2W operations, N2W needs outbound connectivity to the Internet for the HTTPS protocol. Needed are:

* A public IP, or
* An Elastic IP attached to the instance, or
* Connectivity via a NAT setup, Internet Gateway, or HTTP proxy,

<figure><img src="https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/4f7iwXonxCISOegU7zcM/Network-settings.png" alt=""><figcaption></figcaption></figure>

&#x20; &#x36;**.**   Under **Configure storage**, keep the Root volume as 30GB, but change the volume type to General Purpose SSD **(GP3).** You can also encrypt the volume with a default or custom managed KMS key.

<figure><img src="https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/hie1UkK8YgXWMMeRzVvl/Configure-storage.png" alt=""><figcaption></figcaption></figure>

&#x20; 7\.  Under **Advanced details**, the only mandatory field to change is the IAM instance profile. Create a new role to give the EC2 instance the minimum permissions needed to perform its functions. See <https://n2ws.zendesk.com/hc/en-us/articles/28832964188573-Required-Minimum-AWS-IAM-permissions-for-N2W-operations>

&#x20; 8\.  Select **Launch instance.**

## 3.4 N2W Server Instance Configuration

{% hint style="info" %}
For N2W to work, JavaScript needs to be enabled on your browser.
{% endhint %}

N2W has a browser-based management console. N2W supports Mozilla Firefox, Google Chrome, and Safari.

After launching the N2W AWS instance, use the AWS Management Console or any other management tool to obtain the address of the new instance:

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/tNL2KR2XScard73ZLfdA/3-2%20config%20new%20instance.png)

{% hint style="info" %}
Use the address provided to you by N2WS to connect to the N2WS Server using the HTTPS protocol in your browser (`https://<server address>`).
{% endhint %}

When a new N2W Server boots for the first time, it will automatically create a self-signed SSL certificate. After the initial configuration, it is possible to upload a different certificate. Since the certificate is unique to this server, it is perfectly safe to use. However, since the certificate is self-signed, you will need to approve it as an exception for the browser. To add an exception for the default certificate in Chrome and Firefox, see [Appendix B – Adding Exception for Default Browser.](/quick-start/appendix-b-adding-exception-for-default-browser)

After adding the exception, you get the first screen of the N2W configuration application.

## 3.3  N2W Server Configuration Wizard

The N2W Server Configuration wizard takes you through the process step by step. There are a few differences between configuring N2W for the Free Trial and other paid editions.&#x20;

#### For the N2W Free Trial Edition:

* A new volume must be defined for the N2W server.
* You will need to enter a user name, a valid email address, and enter a password and verify it.

#### For other N2W Editions:

#### **Step 1: Verify ownership of the new instance**

On the first screen, you will be asked to type or paste the instance ID of this new N2W instance. This step is required in order to verify that you are indeed the owner of this instance.

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FIlHkeBiP9GkiTAUx88up%2F2.1.1%20screenshot.jpg?alt=media\&token=af199345-eba1-43a9-97dd-c58dbf84fe0a)

Select **Next**. In the next step, the N2W configuration procedure begins.

#### **Step 2: Approve the N2W license agreement**

Review the end-user license terms, select the acceptance checkbox, and select **Next**.

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FDzTY29AOa3u7OuoW0tHj%2F2.1.2%20screenshot.jpg?alt=media\&token=9d3f266b-8b95-4cee-831c-668839eaffac)

#### **Step 3: Configure the license type, N2W “root” account password, and user information**

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FkRTGwJHt0GrpQicfBBum%2F2.1.3%20%20screenshot.jpg?alt=media\&token=5fe4342e-1e3f-4407-8ffa-feafc72fd7b7)

For the Free Trial, leave the **License** list with the defaul&#x74;**.** If you purchased a license directly from N2W Software, choose one of the **License** options, according to the instructions you received.

{% hint style="info" %}
If anyone in your organization already installed an N2W Free Trial in the past on the same AWS account, you may receive an error message when trying to configure or connect to N2W. Contact <support@n2ws.com> to resolve.

If you are using one of the N2W paid products on AWS Marketplace, you will not see the License field.
{% endhint %}

If this is an upgrade, the username must remain as it was prior to the upgrade, but the password can be modified.

{% hint style="info" %}
Passwords: N2W does not enforce password rules. However, it is recommended that you use passwords that are difficult to guess and to change them regularly.
{% endhint %}

When you have completed entering the details for Step 3, select **Next**.

#### **Step 4: Time zone, new volume, force recovery mode, and web proxy settings**

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FcUjgxbYWwOPM508Wuvcw%2F2.1.4%20screenshot.jpg?alt=media\&token=42f16a6a-ca97-4e13-a9f2-cb7b1c8951e8)

1. Choose your time zone.
2. If configuring a paid edition, choose whether to create a new data volume or use an existing one. To configure an additional N2W server, in recovery mode only, choose an existing data volume and select **Force Recovery Mode**. In Step 5, you will be presented with a list of existing N2W data volumes.

{% hint style="info" %}
**The N2W server configured for recovery mode will&#x20;*****NOT*****:**

* Perform backups.
* Copy to S3.
* Have Resource Control management.
* Perform any scheduled operations.
  {% endhint %}

&#x20;   3\. If you select **Enabled** for **Connect via Web proxy**, additional boxes appear for defining the proxy:

&#x20;   4\. Select **Next**.

#### **Step 5: Data volume type and encryption, security settings, and anonymous usage reports**

1. If you are configuring a new data volume, you have an option to encrypt N2W user data. Select **Encrypted** in the **Encrypt Volume** drop-down list and choose a key in the **Encryption Key** list. You have the option to use a custom ARN.

{% hint style="info" %}

* Volume capacity should be at least 10 GB, which is large enough to manage roughly 50 instances and about 3 times as many EBS volumes.
* If your environment is larger than 50 instances, increase the volume at about the ratio of 1 GB per 10 backed up instances.
* Volume type should be at least GP3.
  {% endhint %}

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2Fy1zlMy36FM6pdauyxOwG%2F2.1.5%20screenshot.jpg?alt=media\&token=8abd0e7d-afce-40eb-8400-247e07ec52d6)

&#x20;   2\. If you chose to use an existing volume or selected **Force Recovery Mode** in Step 4, you will see a drop-down volume selection box.

&#x20;   3\. Complete the Web Server settings. The default port 443 is used by the N2W manager.

&#x20;   4\. Allowing anonymous usage reports will enable N2W to improve the product. The usage reports are sent to N2W with no identifying details in order to maintain customer anonymity. You can disallow the anonymous reports at a later time in the N2W **General Settings** menu.

&#x20;   5\. Select **Next** when finished.

#### **Step 6: Register the account with N2W**

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FdU0lhPJSbjZcK79MaJwe%2F2.1.6%20screenshot.jpg?alt=media\&token=a4467e66-043f-427e-9e4f-73e1b56833ba)

**Registration is mandatory for free trials** and optional for paid product&#x73;**.** N2W recommends that all customers register, as it will enable us to provide faster support. N2W guarantees not to share your contact information with anyone.

If you have a Reference Code, enter it in the **Ref Code** box.

{% hint style="info" %}
**WARNING**: Use English characters only in registration. Non-English characters (e.g. German, French) will cause the operation to fail.
{% endhint %}

Select **Configure System** when finished. The Configuring Server message appears.

<img src="https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/FW9EkHE7py9W6L3FoRrB/3-3%20config%20step%206a.png" alt="" width="188">

The registration and configuration process may take a while, after which a ‘Configuration Successful – Starting Server …’ message appears. It will take a few seconds for the application to start.

{% hint style="info" %}
If, for any reason, you are not directed automatically to the application login screen, reboot the instance from the management console.
{% endhint %}

<img src="https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/xwsmyi7VmlS0tr1w1rBP/3-3%20config%20step%206b.png" alt="" width="188">

You are now ready to log on with the credentials you created in the first screen and begin using N2W. Selecting **Sign in with** **Identity Provider** will redirect you to the organization’s IdP system using SAML.

{% hint style="info" %}
Logging on for the first time with a trial edition can take up to 5 minutes as N2W must connect and get approved by our licensing service.
{% endhint %}

The “Please wait …” message should go away in a few minutes. Allow 4-5 minutes and then refresh the screen.


# 4  Creating a Simple AWS Backup Policy with N2W

{% hint style="info" %}
For instructions on how to quick start using Azure with N2W, see section ‎[7](/quick-start/7-backing-up-and-recovering-azure-vms-and-disks).&#x20;
{% endhint %}

N2W automatically creates your first AWS account and policy. The required `cpmdata` policy is used to back up the N2W data volume.

You can create additional accounts by following the instructions in section [4.1](#id-4.1-adding-an-aws-account), or see <https://n2ws.zendesk.com/hc/en-us/articles/28829961679901-How-to-add-an-additional-AWS-account-to-N2W-for-Backup-or-DR>

For creating a simple AWS backup policy, see section [4.3](#id-4.3-creating-a-simple-backup-policy). While a backup schedule is geared toward a production environment, it is optional, as you can run a policy independently of a schedule. To set a backup schedule, see section [4.2](#id-4.2-creating-a-simple-backup-schedule).

## 4.1 Adding an AWS Account

‌After logging on to the system for the first time, you will see the main screen, the Dashboard:​‌

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/n8FDTSHiaeZzLgST0xjT/3%2017-1%2025%20Dashboard%20\(2\)%20cropped.png)

It is currently empty. The first thing you need to do is to associate an AWS account so you can start backing up EC2 instances. Depending on your edition of N2W, you can associate one or more AWS accounts.&#x20;

**To associate the AWS account with an N2W account:**

In the left panel, select the **Accounts** tab, and in the + **New** menu, select **AWS** account.‌

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/q1fNqAYtYGVrAID9CMYY/3-1%20New%20Acct-cropped.png)

1. In the **Name** box, type the name you would like to associate with your primary AWS account.
2. In the **Account Type** list, select **Backup**. A **DR** account is for cross-account backup and recovery and is out of the scope of this guide. See "[Account Type](https://n2ws.gitbook.io/documentation/start-using-n2ws#3-1-1-account-type)" in the [*N2W Backup & Recovery User Guide*](https://docs.n2ws.com/user-guide).
3. In the **Authentication** list, select your desired type of authentication. You can either choose to use your AWS access key and secret key or **CPM Instance IAM Role**, which is recommended. These credentials are saved in the N2W database. However, the secret key is kept in an encrypted form. There is no way these credentials will ever appear in a clear text format anywhere. See “[Security Concerns and Best Practices](https://n2ws.gitbook.io/documentation/16-security-concerns-and-best-practices)” in the [*N2W Backup & Recovery User Guide*](https://docs.n2ws.com/user-guide).
4. Select **Scan Resources** to turn on the capability for this account to scan resources.
5. Select the **Scan Regions** and **Resource Types** in their respective lists.
6. **Capture VPCs** is enabled by default. Clear **Capture VPCs** to turn off automatic capturing of VPCs for this account.
7. Select **Save**.

## ‌4.2 Creating a Simple Backup Schedule

‌In the left panel, select the **Schedules** tab. Currently, the list of schedules is empty. You will now create the first schedule. Select + **New**.​‌

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/naDqxwVIiOOiNWI4tEvq/4-1-1%20New%20Sched-cropped.png)

1. Type a name for the schedule and an optional description.
2. In the **First Run** box, if the First Run is other than immediately, select **Calendar** ​![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2F1Yp0KXsChlyA1K2FGkzi%2Fcalendar%20icon.png?alt=media\&token=1a517534-0b82-4153-b5a0-f968796fa670) to choose the date and time to first run this schedule. The time set in **First Run** becomes the regular start time for the defined schedule. The default schedule expiration is never.
3. Set the schedule frequency in the **Repeat Every** list. Available units are minutes, hours, days, weeks, and months. Set the days of the week on which the schedule runs in the **Enabled On** checkboxes.
4. Select **Save**.

## ‌4.3 Creating a Simple Backup Policy

‌In the left panel, select the **Policies** tab. Currently, the list of policies is empty. You will now create the first policy. Select + **New**.​‌

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/a1UTZRB5RhH0opTb0b4a/4-2-1%20New%20Policy-cropped.png)

1. In the **Create** **Policy** page, enter a policy name and description. Other fields in this screen include:

* ‌**Account** – Each policy can be associated with one AWS account.
* **Auto Target Removal** – Whether to auto-remove resources that no longer exist.
* **Enabled** – By default, a policy is enabled.
* **Schedules** – Select the schedule just created.
* **Auto Target Removal** – Select from the list whether to automatically remove resources that no longer exist. If you enable this removal, if an instance is terminated, or an EBS volume deleted, the next backup will detect that and remove it from the policy. Choose **yes and alert** if you want the backup log to include a warning about such removal.

&#x20;2\. When finished, select **Save** and select the **Backup Targets** tab. Backup targets define what a policy is going to back up.**​**‌

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/FUGv8lNEnfBDcnv6Y55q/4-2-2%20Add%20Backup%20Targ-cropped.png)

Following are the types of objects you can back up:‌

* **Instances** - Back up EC2 instances, including their metadata, and optionally some or all of their data volumes. This is the most common backup target.
* **Volumes** - Back up EBS volumes independently, whether or not they are attached to an instance, and regardless of which instance they are attached to. This can be useful to back up volumes that are not always attached to an instance, or volumes that move between instances, like cluster volumes.
* **RDS Databases** - Back up RDS DB instances. This will use RDS snapshots and can be useful for backing up RDS databases together with other types of objects, or for anyone who wishes to backup RDS databases using N2W, in addition to or instead of using AWS automatic backup.
* **Aurora Clusters** - Aurora is similar to RDS but handles Aurora clusters.
* **Redshift Clusters** - Manage Redshift Cluster snapshots.
* **DynamoDB Tables** - Back up DynamoDB Tables.
* **Elastic File Systems** – Back up EFSs.
* **FSx File Systems** - Back up FSx File Systems.
* **S3 Bucket Sync** - Copy objects between S3 buckets.

**To add an instance, for example, to the policy:**

In the **Add Backup Targets** menu, select **Instances.** The list of instances you have in the region for the policy’s account appears. The **Region** list allows you to switch between different regions. You can use the free text search, column-based sorting, or pagination if there are a lot of instances and you are seeking a specific one.

{% hint style="info" %}
Although you can add backup objects from different regions in the same policy, in many cases it is not a good practice to do so.‌
{% endhint %}

Select the instance that you want to back up and select **Add Selected**. This will add the requested instance to the screen in the background and remove it from the popup window, although it does not close the popup.​

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/m9ur0uU0r2CUf9yai80J/4-2-2%20Add%20Instance-cropped.png)

You can add as many instances as you want up to the limit of your license.‌

Select **Close** when finished.‌

Back in the **Backup Targets** screen, you can see the instance in the list of instances. You have an option to remove it from the policy and a **Configure** button. Select the instance and then select **Configure** to review which volumes to back up and other options.‌

By default, all EBS volumes which are attached to this instance will be backed up. If a volume gets detached from or attached to the instance, it will not interfere with the normal operations of the policy. In every backup, N2W will check which volumes are attached to the instance and take snapshots of them.‌

To view the planned backups for this policy, select **Backup Times** in the Policies list.‌

The backups will start automatically at the time configured previously in the schedule.‌

If you want to initiate an immediate backup, select a policy and then select **Run ASAP.**&#x200B;‌

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/sVMUaLGAhc65xaDI11Cf/QSG%204-4%20policies-cropped.png)

N2W will report that the backup policy will now run. The process can be monitored by following the **Status** in the **Backup Monitor** tab.​‌

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/3rEliHlPusVaqIyICegz/QSG%204-4%20Bckup%20Mntr-cropped.png)

Check out the [*N2W Backup & Recovery User Guide*](https://n2ws.gitbook.io/documentation) to see how to create application consistency for Linux and Windows servers.


# 5  Performing a Basic AWS Recovery with N2W

N2W backs up the requested objects at the requested times.

You can view the backups in the **Backup Monitor** tab. You can search for snapshots based on the Backup Target type, Policy, Account, and backup status.

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/cP4xe55xNbAo6sct41Gq/QSG%205%20Basic%20Recovery-Basic%20Recovery%20cropped.png)

For each backup, you can see the exact start and finish times, and status. Select **View** **Snapshots** to see the individual EBS snapshots of all the volumes. Select **Log** to view the log of this backup with all the details. To recover from a particular backup (typically the most recent successful backup), select the backup and then select **Recover**:

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/7YtwlYMuhPJRtDtp9Y4T/bckup-monitor.png)

In the **Recover** screen, you can see all the instances that this backup contains. Should this policy include also EBS volumes, RDS databases, Redshift Clusters, or DynamoDB Tables, you will have a tab to recover them as well. In order to recover an instance, select the **Instances** tab.

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/2AuOa3ipHk3KNYQTtbjR/QSG%205%20Basic%20Recovery%202%20cropped.png)

{% hint style="info" %}
**Recover Volumes Only** is for recovering only the EBS volumes of the instance without actually creating a new instance.
{% endhint %}

Select the instance to recover and select **Recover** again. The **Basic Options** tab of the **Instance Recovery** page opens. You can enlarge the page by selecting the expand icon ![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/kDbi8sZMPDUalDFSMWaj/Expand%20icon.png) in the upper right corner.

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/5F4VFeXw7DLLuzsuPeb0/QSG%205%20Basic%20Recovery%203-cropped.png)

Most of the options when launching EC2 instances are available here and may be modified. The currently selected defaults are exactly the options the original backed-up instance had at the time of the backup, including the tags associated with it.

A further option worth mentioning here is **Launch from**. This sets the option for the image the new instance will be launched from.&#x20;

In the case of an instance-store-based instance, the only option would be to launch from an image. The default will be the original image, although it can be changed. In case it is a Linux EBS-based instance, as in this example, and the backup includes the snapshot of the boot device, you can choose between launching from an image (the original image or another), and launching from the snapshot, which is the default.&#x20;

If you choose to launch from a snapshot, a new image (AMI) will be created, and you can choose whether you want to keep the image after the recovery is complete or deregister it. You can even choose not to perform the recovery now, and only create the image, to recover from it later.&#x20;

Select **Recover Instance** to recover an instance exactly like the original one.

For paid editions, if **Capture VPCs** was enabled in the **Account** settings, the **Basic Options** tab will also contain a **Clone VPC** button next to the **VPC** box.

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/hFBZVLQjpuQ9vO16g3Dl/5%20Recovery%204.png)

The **Clone VPC** option allows you to recover the instance to a clone of a selected VPC environment. See <https://docs.n2ws.com/user-guide/10-performing-recovery>

{% hint style="danger" %}
If you intend to test the recovery of an instance in the same region as the originally backed up instance, you will need to change the IP to avoid an IP conflict. This can be mitigated by leaving the **VPC Assign IP** box blank
{% endhint %}

Select the **Volumes** tab to choose which volumes to recover and how.

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/N1OwjQy9JOpFhN6etHhC/QSG%205%20Basic%20Recovery%204-cropped.png)

Select the **Advanced Options** tab for additional recovery parameters.

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/bNL0InD4Kz0iUxTBO8Ke/QSG%205%20Basic%20Recovery%205-cropped.png)

After you select **Recover Instance** and confirm, you will be directed to the Recovery Monitor page where you can follow the progress in the **Status** column. You can view recovery details by selecting **Log**.

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/WlrXeycgSDlRmuAZA5HL/QSG%205%20Basic%20Recovery%206%20cropped.png)

The log message will include the instance ID of the new instance, and now you can go and verify the successful recovery in the AWS Management Console. The recovered instance is exactly the same as the original one, with all its EBS volumes.


# 6  How to Configure N2W with CloudFormation

The process to configure N2W to work with CloudFormation is a single stream that starts with subscribing to N2W on the Amazon Marketplace and ends with configuring the N2W server.

{% hint style="info" %}
Configure CPM with CloudFormation will fail where the requested Instance type is not supported in the requested Availability Zone. Retry your request, but do not specify an Availability Zone or choose `us-east-1a`, `us-east-1b`, `us-east-1c`, `us-east-1d`, or `us-east-1f`.
{% endhint %}

* N2W provides several editions, all of which support CloudFormation.
* An IAM role will automatically be created with minimal permissions and assigned to the N2W instance.

### Get Started with CloudFormation

1. Go to <https://aws.amazon.com/marketplace>
2. Search for N2W Software.
3. Select the **AWS Free Trial & BYOL** edition, and then select **View purchase options**:

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FA7REL9cqspkZjY2nXb9r%2FSubscription%201.png?alt=media\&token=94a9808f-f21c-4617-a375-a5065c70f9fe)

&#x20;   4\. After reviewing the overview, select **View purchase options** again.

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2F8t5TzSRPhc2JnJDFO8vY%2FSubscription%202.png?alt=media\&token=7895899d-d07a-4d72-a890-b88bf92e0f40)

&#x20;   5\. After purchasing N2W Backup & Recovery for AWS Free Trial/BYOL, select **Launch your software**.

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2Fi3d5S2pimQ2owwo3Ynfo%2FSubscripiion%203.png?alt=media\&token=f1075e88-1ab5-49fa-a0d4-948e97569852)

&#x20;   6\. In the Setup section, select **AWS CloudFormation** for the **Service**. Select the relevant **Version** and **Region**, and then select **Launch with CloudFormation**.

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FrVjnkqprEsaNdtJMtHIw%2FSubscription%204.png?alt=media\&token=db96ad0b-8a4b-4ed5-a77f-2d158602fa4a)

&#x20;   7\. In the Create Stack page:

* In the Prerequisite – Prepare template section, select **Choose an existing template**.
* In the Specify template section, select **Amazon S3 URL**. In the Amazon S3 URL window, the address of the template will appear.
* Select **View in Infrastructure Composer**.

&#x20;  8\.  Select **Next**. The **Configure stack options** page opens.   &#x20;

* If needed, select **Add new tag**.
* In the **Capabilities** section, select **I acknowledge that AWS CloudFormation might create IAM resources**.

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FfCRQWeRyQudeeCr25v4x%2FSubscription%205.png?alt=media\&token=455ac461-95e1-4675-a8f2-aeba6abc1fa8)

&#x20;   9\. Select **Next**. The **Specify stack details** page opens. Provide a stack name and parameters.

{% hint style="info" %}
For Inbound Access CIDR, security groups act as a firewall for associated instances, controlling both inbound and outbound traffic at the instance level. Configuring Inbound Access CIDR allows you to add rules to a security group that enable you to connect to your Linux instance from your IP address using SSH:

* If your IPv4 address is `203.0.113.25`, specify `203.0.113.25/32` to list this single IPv4 address in CIDR notation.
* If your company allocates addresses within a range, specify the entire range, such as `203.0.113.0/24`.
* If you specify `0.0.0.0/0`, it will enable all IPv4 addresses to access your instance using SSH.
* For further details, refer to “Adding a Rule for Inbound SSH Traffic to a Linux Instance” at <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/authorizing-access-to-an-instance.html>
  {% endhint %}

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2F27CYsyFk3CX3rZiEi8Gv%2FSubscription%206.png?alt=media\&token=b584002f-7bf9-47c9-89a3-88f90717406d)

&#x20;   10\. Select **Nex**t. The **Review and create** page opens. Review and edit as necessary.

* Step 1, Specify template, and Step 2, Specify stack details:

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FkpsVq4uOQKakrIQQu0Eh%2FSubscription%207.png?alt=media\&token=3cb8c671-2d5f-4b6a-a3e6-6db73777a43d)

* Step 2, Parameters, and Step 3 Configure stack options, such as Tags and Permissions:&#x20;

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2F7hHbWcDCVekkfJa8IqRi%2FSubscription%208.png?alt=media\&token=0226f710-08d5-44bf-ac85-e3cbde912b5d)

* Step 3, Stack failure options, Stack policy, and Rollback configuration:

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FK4ZBZEbaFItoo8l83TyX%2FSubscription%209.png?alt=media\&token=90b2cdd6-b8b9-406e-b6e8-af552e6214a5)

* Step 3, Notification options, Stack create options, and Quick-create link:

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2Fj8N6dWjpHMuLjJXhFakI%2FSubscription%2010.png?alt=media\&token=e560cfe5-2817-4de9-84b8-b7305b0d161c)

&#x20;   11\.  After all sections are reviewed, select **Submit**. The last configuration page opens, where you can observe the progress of the stack creation.

<figure><img src="https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2Fg9boV2Si34JH8QwVSh6o%2FSubscription%2011.png?alt=media&amp;token=426263d8-4fe2-4d51-b55c-3f711fed8f23" alt=""><figcaption></figcaption></figure>

&#x20;   12\. Continue configuring N2W from section [3](/quick-start/3.-n2ws-server-instance-configuration).


# 7 Using N2W with Azure

Following are the steps for setup, backup, and recovery of Azure VMs and Disks:

1. Before starting, configure N2W Backup and Recovery according to [Configuring N2W.](/quick-start/3.-n2ws-server-instance-configuration)
2. After the final configuration screen, prepare your Azure Subscription by adding the required permissions and custom IAM role in AWS. See section [7.1](/quick-start/7-backing-up-and-recovering-azure-vms-and-disks#7-1-setting-up-your-azure-subscription).
3. In N2W, add an Azure account with the custom N2W role. See section [7.2](/quick-start/7-backing-up-and-recovering-azure-vms-and-disks#7-2-adding-an-azure-account-to-n-2-ws).
4. Create an Azure policy in N2W with Azure backup targets. See section [7.3](/quick-start/7-backing-up-and-recovering-azure-vms-and-disks#7-3-creating-an-azure-policy).
5. Back up the policy. See section [7.4](/quick-start/7-backing-up-and-recovering-azure-vms-and-disks#7-4-backing-up-an-azure-policy).
6. Recover from a backup. See section [7.5](/quick-start/7-backing-up-and-recovering-azure-vms-and-disks#7-5-recovering-from-an-azure-backup).

## 7.1  Setting Up Your Azure Subscription

N2W Backup and Recovery needs the following permissions to perform backup and recovery actions. In addition, see&#x20;

1. For the minimal permissions for Azure, see <https://n2ws.zendesk.com/hc/en-us/articles/28833036917021-Required-Minimum-Azure-permissions-for-N2W-operations>
2. Add your subscription ID value to the `subscriptions` attribute in the minimal permissions JSON.

```
{
    "properties": {
        "roleName": "CPM",
        "description": "",
        "assignableScopes": [
            "/subscriptions/<subscriptionID>"
        ],
        "permissions": [
            {
                "actions": [
                    "Microsoft.Compute/virtualMachines/read",
                    "Microsoft.Compute/disks/read",
                    "Microsoft.Compute/snapshots/write",
                    "Microsoft.Network/networkInterfaces/read",
                    "Microsoft.Compute/snapshots/read",
                    "Microsoft.Resources/subscriptions/resourceGroups/read",
                    "Microsoft.Compute/disks/write",
                    "Microsoft.Compute/snapshots/delete",
                    "Microsoft.Resources/subscriptions/resourceGroups/delete",
                    "Microsoft.Network/virtualNetworks/read",
                    "Microsoft.Network/virtualNetworks/subnets/read",
                    "Microsoft.Network/networkInterfaces/write",
                    "Microsoft.Network/virtualNetworks/subnets/join/action",
                    "Microsoft.Network/networkInterfaces/join/action",
                    "Microsoft.Compute/virtualMachines/write",
                    "Microsoft.Compute/diskEncryptionSets/read",
                    "Microsoft.Compute/virtualMachines/powerOff/action",
                    "Microsoft.Compute/virtualMachines/start/action",
                    "Microsoft.Compute/availabilitySets/read",
                    "Microsoft.Compute/availabilitySets/vmSizes/read"
                ],
                "notActions": [],
                "dataActions": [],
                "notDataActions": []
            }
        ]
    }
}

```

&#x20;   2\. In the Azure Portal, go to your subscription. Select a subscription that you want to use with N2W Backup & Recovery. <img src="https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/WCA5YLaO4M0SOnhD17II/Azure%20subscription%20icon.png" alt="" data-size="line"> \
&#x20;   3\. Select **Access control (IAM)**, select **+Add**, and then select **Add custom role**.

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/XP9ND4MkKrAHFijfqTFT/image.png)

\
&#x20;   4\. Complete the form by providing a **Custom role name**, such as **N2WBackupRecoveryRole**, and then select the JSON file saved in step 1.

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/qBVi0T8CYsLCCICl6kfM/image.png)

&#x20;   5\. Create the role with the new JSON file.

## 7.2  Adding an Azure Account to N2W

1. Log on to N2W using the root username and password used during the N2W configuration.
2. Select the **Accounts** tab.
3. If you have a license for Azure cloud, select **Azure account** in the **+ New** menu.  <img src="https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/2Yf68T6nF96niD2OozqC/26-2%20Acct%20menu.png" alt="" data-size="original">&#x20;
4. Complete the New Azure Account screen using the App Registration view information in the Azure portal as needed. &#x20;

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/Eq9CISPcWTQhdy7pQC4Z/26-4%20new%20azure%20acct-cropped.png)

* **Name** - Copy from your App Registration name.
* In the **Use**r list, select your username. Or, select **+ New** to add a new user. See section 18 in the [*N2W Backup & Recovery User Guide*.](https://docs.n2ws.com/user-guide/)
* **Directory (tenant) ID** – Copy from your App Registration.
* **Application (client) ID** – Copy from your App Registration.
* **Client Secret** – Copy from your App registration Certificates & Secrets in the App Registration view, or set a new secret.

&#x20;   5\. Select **Save**. The new account appears in the Accounts list as an Azure Cloud account. &#x20;

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/LhkWGQveyudxVNHQGh0c/26-4%20add%20azure%20acct%20to%20n2ws-cropped.png)

## 7.3  Creating an Azure Policy

To backup resources in Azure, create an N2W policy.

1. In N2W, select the **Policies** tab.
2. In the **+ New** list, select **Azure policy**.
3. In the New Azure Policy screen, complete the fields:

* **Name** – Enter a name for the policy.
* **User** – Select from the list.&#x20;
* **Account** – Select from the list. Or, select **+ New** to add an account. See section [7.2](/quick-start/7-backing-up-and-recovering-azure-vms-and-disks#7-2-adding-an-azure-account-to-n-2-ws).
* **Enabled** – Clear to disable the policy.
* **Subscription** – Select from the list.
* **Schedules** – Optionally, select one or more schedules from the list, or select **+ New** to add a schedule. See section [4.3](/quick-start/4.-creating-a-simple-backup-policy#4-3-creating-a-simple-backup-policy).
* **Auto Target Removal** – Select **Yes** to automatically remove a non-existing target from the policy.

&#x20;   4\. Select the **Backup Targets** tab.\
&#x20;   5\. In the **Add Backup Targets** menu, select the targets to backup, Disks and/or Virtual Machines. The Add Virtual Machines / Disks screen opens.\
&#x20;   6\. When selecting Virtual Machines, it is *required* to filter by the **Location** of the target resources using the list in the upper left corner *before* selecting the individual targets. Filtering by Resource Group is optional.

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/ySZsbyYNkQ1kGPuvu6yJ/26-6%20Azure%20policy-cropped.png)

&#x20;   7\. When finished selecting targets, select **Add selected**. The Backup Targets tab lists the selected targets.

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/l0sjcYAuDJvnUhs5JhPP/26-6-1%20Azure%20bckup%20targets-cropped.png)

&#x20;   8\. To determine which disks for each Virtual Machines target to backup, select<img src="https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/OEYwO9RVtUrlvZdkZVga/Configure%20icon.png" alt="" data-size="line">**Configure**. In the **Which Disks** list of the Policy Virtual Machine and Disk Configuration screen, select the disks to include or exclude in the backup.\
&#x20;   9\. When finished, in the **Backup Targets** tab, select **Save**.

## 7.4  Backing Up an Azure Policy

If the policy has a schedule, the policy will backup automatically according to the schedule. To run a policy as soon as possible, in the **Policies** view, select the policy and select<img src="https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/n5LJqxFfy4Z4lhdp7HG4/Run%20icon%20(2).png" alt="" data-size="line">**Run ASAP**.

To view the policy progress and backups, select **Backup Monitor**.

* The backup progress is shown in the **Status** column.&#x20;
* Use the Cloud buttons to display the Azure policies.

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/xkFwixDBwQdO0WzelUFn/26-8%20Bckup%20Azure%20policy-cropped.png)

## 7.5  Recovering from an Azure Backup

{% hint style="info" %}
Only one VM is recoverable during a recovery operation.
{% endhint %}

After creating a backup, you can recover it from the **Backup Monitor**.

In the VM recovery Basic Options, there are Azure options for replicating data to additional locations in order to protect against potential data loss and data unavailability:

* **Availability Zone** – A redundant data center (different building, different servers, different power, etc.), within a geographical area that is **managed by** **Azure.**
* **Availability Set** – A redundant data center (different building, different servers, different power, etc.) that can be launched and fully configured by the customer and **managed by the customer.**
* **No Redundancy Infrastructure Required** – By selecting this option, the customer can choose not to replicate its data to an additional (redundant) location in another zone or set. By choosing this option, the customer would save some money, but in rare cases (usually 11 9s of durability and 99.9% of availability), the customer can experience some degree of data loss and availability.

In the Disk Recovery screen, you may be presented with an option to change the encryption when recovering certain disks.

{% hint style="info" %}

* To add an additional layer of encryption during the recovery process, see <https://docs.microsoft.com/en-us/azure/virtual-machines/disks-enable-customer-managed-keys-portal>.&#x20;
* Disk encryption settings can be changed only when the disk is unattached or the owner VM is deallocated.
  {% endhint %}

### 7.5.1  Recovering a VM and Disks

**To recover a VM with or without attached disks:**

<figure><img src="https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FMOO4aIZvX6Xl3fEni6kZ%2Fazure%206-1.png?alt=media&amp;token=a64ab14e-b61e-4fab-9165-a75c9926dbbe" alt=""><figcaption></figcaption></figure>

1. &#x20;In the **Backup Monitor**, select the backup, and then select ![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FTy9LlwLpi1kn3qeLg4dA%2Fimage.png?alt=media\&token=3a70d507-e1fe-4de5-99a3-db7775048b18) **Recover**.

<figure><img src="https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2F9jrxWKYbOKBpH9xlWFDB%2Fazure%206-2.png?alt=media&amp;token=2992a7f7-da3d-4ccb-bbfe-35ef73e2dc8b" alt=""><figcaption></figcaption></figure>

&#x20; 2\.  Select the VM snapshot that you want to recover from, and then select ![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FCBzZVIoGD5eYKfuI4fB9%2Fimage.png?alt=media\&token=93903754-b5f7-4887-a5b9-a6462a5ba880) **Recover**.

&#x20; 3\.  In the **Virtual Machines** tab of the Recover screen, select 1 VM, and then select ![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2F8OCLLgTudFDoCtfTchL4%2Fimage.png?alt=media\&token=60bd1dc5-d736-40e5-8a07-e856ef066b4d) **Recover**. The **Basic Options** tab opens.

<figure><img src="https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FrAxgGG0pxMsarPB4eDty%2Fazure%206-3.png?alt=media&amp;token=c864adb7-6457-4c7d-b9b2-055b81d953b0" alt=""><figcaption></figcaption></figure>

&#x20; 4\.  In the **Availability Type** list, select one of the following:

* **No Infrastructure Redundancy Required** – Select to not replicate data at a redundant location in another zone or set.
* **Availability Zone** – Select a zone in the Availability Zone list.
* **Availability Set** – Select a set in the Availability Set list.

&#x20; 5\.  In the **Private IP Address** box, assign an available IP address, or switch the **Custom** toggle key to **Auto assigned**.

&#x20; 6\.  In the **Disks** tab, enter a new Name for each disk. <mark style="color:$danger;">Similar names will cause the recovery to fail.</mark>

&#x20; 7\.  Select **Recover Virtual Machine**.

&#x20; 8\.  To view the recovery progress, select **Recovery Monitor**. Use the Cloud buttons to display the Azure  (<img src="https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FjCAXmR06QOCD2DabDbdQ%2Fimage.png?alt=media&amp;token=c995a4d5-3d08-4cc3-8e9b-b929dd67c7b6" alt="" data-size="line">) recoveries.

### 7.5.2 Recovering Only Disks of a VM

**To recover only disks attached to the VM:**

1. Select **Recover Disks Only**.&#x20;

<figure><img src="https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FwmzTbqWhSZH8440DH449%2Fazure%206-5.png?alt=media&amp;token=8b25501b-3a83-4e98-a5f7-da4048df91d6" alt=""><figcaption></figcaption></figure>

&#x20; 2\.  In the **Disks** tab, enter a new **Name** for each disk. <mark style="color:$danger;">Similar names will cause the recovery to fail.</mark>

&#x20; 3\. See Note above about changing the Encryption Set for certain disks.&#x20;

&#x20; 4\.  Change other settings as needed, and select **Recover Disk**.

&#x20; 5\.  To view the recovery progress, select **Recovery Monitor**. Use the Cloud buttons to display the Azure  (<img src="https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FjCAXmR06QOCD2DabDbdQ%2Fimage.png?alt=media&amp;token=c995a4d5-3d08-4cc3-8e9b-b929dd67c7b6" alt="" data-size="line">) recoveries.

### 7.5.3 Recovering Independent Disks

**To recover from backups with independent disks:**

1. Select the backup, and then select  <img src="https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FH66KhzbMDdtwlnLhh157%2Fimage.png?alt=media&amp;token=9d750d8c-42a1-49ca-9a11-169753005793" alt="" data-size="original"> **Recover** as in step 1 of the VM recovery.

<figure><img src="https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FWXqpfkjniqThfzzgstlA%2Fazure%206-4.png?alt=media&amp;token=e4bef725-daea-40d6-8e91-3ff1d5ea258b" alt=""><figcaption></figcaption></figure>

&#x20; 2\.  In the **Independent Disks** tab, enter a new **Name** for each disk to recover. <mark style="color:$danger;">Similar names will cause failure</mark>.&#x20;

&#x20; 3\.  See Note above about changing the Encryption Set for certain disks.

&#x20; 4\.  Change other settings as needed, and select **Recover Disk**.

&#x20; 5\.  To view the recovery progress, select **Recovery Monitor**. Use the Cloud buttons to display the Azure  (<img src="https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2F5g4We6H5hQD2Fk7Dyrne%2Fimage.png?alt=media&amp;token=1d9dbed9-1305-44be-8afc-738f95876e60" alt="" data-size="line">) recoveries.


# Appendix A - AWS Authentication with N2W

For N2W to perform its backup and restore management functions, it needs to have the correct permissions assigned.

N2W supports two different types of AWS authentication during setup:

* AccessKey / SecretKey &#x20;
* Role-based authentication (recommended)

The permissions necessary have been combined into a JSON file for convenience and can be downloaded from the N2W Knowledge Base:

<https://n2ws.zendesk.com/hc/en-us/articles/28832964188573-Required-Minimum-AWS-IAM-permissions-for-N2W-operations>

1. At the top of your AWS console, select the **Services** tab. In the **Security Identity & Compliance** section, select **IAM**.
2. In the left menu, select **Policies**.

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FnFMEeanoEYSCP4QLJPGm%2FAzure%20AppA%201.png?alt=media\&token=6dc64d70-1472-4b83-9c6f-9bed379302c3)

&#x20;   3\. Select the **Create policy** button.

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2Fx9ScZMeatWg45SSn00pN%2FAzure%20AppA%202.png?alt=media\&token=182d09a6-295a-4c23-a500-54ddfd73adb9)

&#x20;   4\. Select the **JSON** tab.

&#x20;   5\. Delete the default contents and copy and paste the contents of the JSON file downloaded from our Knowledge Base (see above).

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FcDzl1wB9fvWe9DErtKpk%2FAzure%20AppA%203.png?alt=media\&token=c27cd3d0-24ca-4f2c-b29e-fa1a8abd3032)

&#x20;   6\. At the bottom of the screen, select **Next.**

&#x20;   7\. Type a **Name** for the policy, and select **Create policy**.

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2Fm2sgGFALTv4uQTfAQaXC%2FAzure%20AppA%203-1.png?alt=media\&token=54d95f30-2deb-48f1-a690-d7808d0e7e3f)

&#x20;   8\. Create a role, and then assign the policy you just created to that role. In the left menu, select **Roles** and then select **Create role**.

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2F9gXQfPlCZxc5jNM7yqek%2FAzure%20AppA%204-1.png?alt=media\&token=9405197c-b13b-41c6-a789-daa098dd4065)

&#x20;   9\. In the list of **type of trusted entity**, select **AWS service** and then select **EC2**. \
&#x20;   10\. Select **Next: Permissions**.

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FJzDxuutJXVNiwKpaIBB4%2FAzure%20AppA%204.png?alt=media\&token=a063aa86-5557-4f64-b961-d38889c31c48)

&#x20;   11\. On the **Add Permissions** page, search for the 3 previously created polices, and then select **Next.**

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FnCWD4h1BuDN520RWxTpk%2FAzure%20AppA%205.png?alt=media\&token=9e406535-6450-44c9-b62a-973810d4b6e0)

&#x20;   12\. Name the **Role**, and select **Create Role**.

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2F8DZusdvGyRn8J3YVJJJ5%2FAzure%20AppA%206.png?alt=media\&token=4c716bc2-6e06-4af8-9f57-ef575bffdc34)

&#x20;   13\.  Assign the resulting role to the N2W trial instance:

* Select the N2W instance name.
* In the **Actions** menu, select **Instance Settings** and then **Attach/Replace IAM Role**.

![](https://2579379328-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFJ1e0ApAPsExzRxsFpe8%2Fuploads%2FoUM5OggoTfYJg0A7XiAy%2FAzure%20AppA%207.png?alt=media\&token=22413227-e9e0-4ea7-8312-324effd5e41a)

&#x20;&#x20;


# Appendix B  - Adding Exception for Default Browser for N2W

### For Chrome

When you first navigate to your N2W instance, you'll see a screen like this. It's nothing to worry about. We are SSL secured but because it is a self-signed certificate, you may want to add an exception to your browser following these steps.

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/00bNeLE04KIeMXgkk7Ph/App%20B%20Browser%20Exception%201.png)

1. Open the Chrome browser. In the top right, select **More** ![](broken://files/-M9KiWCcqRFJQAiWRsnk).
2. Select **Settings**, **Advanced**, and then in the **System** section, select **Open** **proxy settings.**

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/xpD3WyCd9320BiBPCmba/App%20B%20Browser%20Exception%202.png)

&#x20;   3\. Choose the **Security** tab and then select **Trusted Sites**.

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/gxlGvY4jwbIMTiLn7cid/App%20B%20Browser%20Exception%203.jpeg)

&#x20;   4\. Select the **Sites** button.

&#x20;   5\. Type the N2W server’s IP address in the **Add this website to the zone** box, and then select **Add**, **Close**. and **OK**.

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/IRSF0RAdEasJp7GDOpcb/App%20B%20Browser%20Exception%204.jpeg)

You should not get the warning on the certificate again.

### For Firefox

The example is from Firefox Quantum.&#x20;

1. Select **Advanced,** the "1" label in the screenshot below.&#x20;
2. Select **Add Exception** for this server, the "2" label in the screenshot below.

![](https://content.gitbook.com/content/FJ1e0ApAPsExzRxsFpe8/blobs/9Ff0BMsiMrjEiQjaeCwl/App%20B%20Browser%20Exception%206.png)