| Note |
|---|
To fully use this screen, you must have the following permissions assigned to your account: Read Advanced Backup Plans Read Advanced Backup Read Advanced Backup VMs Write Advanced Backup Create an Advanced Backup Policy Read the Advanced Backup Policy Read Advanced Backup Snapshots Refresh Advanced Backup Snapshots Remove Advanced Backup Request Advanced Backup Restore Update Advanced Backup Policy Commit Advanced Backup Restore Refresh Advanced Backup Snapshots Restore from Backup Read Advanced Backup Overview
|
...
| Note |
|---|
A newly created virtual machine may not appear immediately in this screen. You may need to wait an hour before a newly created virtual machine appears. |
| Note |
|---|
To properly backup SQL databases, before you create a backup policy, Armor recommends that you separately create a backup of the database, and then place that backup in the server to be backed-up. |
| Expand |
|---|
| title | Step 1: Create a backup policy |
|---|
|
You must create a policy to configure how often to take a backup and how long to keep a backup. | Note |
|---|
By default, times are based on your web browser's configured time zone. The location of your virtual machine does not relate to the time zone used in this feature. |
In the Armor Management Portal (AMP), in the left-side navigation, click Infrastructure. Click Advanced Backup. Click Policies. Click plus ( + ) icon. In Policy Name, enter a descriptive name. In Location, select the data center where the virtual machine is located (and where the backup will take place). In Type, select VM Protection. Next to Backup Schedule, under Take Snapshots (Frequency), enter how often Armor should take a snapshot. And then directly across, under Keep Snapshots (Retention), enter how long Armor should keep this snapshot.
You must enter your time configurations in the same row. For example, to take a snapshot every week and to keep that snapshot for six months, under Take Snapshots (Frequency), in Every (Days), enter 7, and then directly across, under Keep Snapshots (Retention), in For (Days), enter 182.
You can create a maximum of four Frequency and Retention settings. The minimum retention period is 3 days. Additionally, you must create a policy that takes place once per day. You must enter a time in hours.
For example, to take a snapshot every two hours and to keep that snapshot for three days, under Take Snapshots (Frequency), in Every (Hours), enter 2, and then directly across, under Keep Snapshots (Retention), in For (Days), enter 3.
(Optional) In Snapshot Window, configure the time frame for when your scheduled snapshots should take place. By default, Rubrik will determine when the scheduled snapshots will take place; however, with this option, you have the ability to configure a specific time frame for when the scheduled snapshots will take place. This option can be useful if you want to perform snapshots during a period of low traffic. Next to First Full Window, configure the time frame for when the first full snapshot should take place.
Armor recommends that you configure a time when your environment experiences low traffic, low transaction volume, or low changes. By default, times are based on your web browser's configured time zone. After the first full snapshot is complete, the configuration you created under Take Snapshots (Frequency) and Take Snapshots Between will be implemented. For example, next to First Full Window, if you configure an initial time frame of Sunday 12 AM to Sunday 6 AM, then your first full snapshot will take place at any time during this time frame. After the first full snapshot is complete, then the time frame configured in Take Snapshots (Frequency) and Take Snapshots Between will begin. If the first snapshot completes at Sunday at 5 AM, and your policy includes a snapshot every 4 hours, then the next snapshot will take place at 9 AM, and then again at 1 PM.
Click Create Policy.
| Info |
|---|
There is a maximum number of 2000 retained backups per policy configuration per upcoming calendar year. This is calculated based on the values you supply for the Take/Keep field combinations. As you configure your policy, the system will perform calculations to determine if you have exceeded the maximum threshold. When this occurs, you will be blocked from saving your policy changes until you've changed your Take/Keep combinations to come back under the threshold. |
|
...
You can use these instructions to retain snapshots of specific files, and not of your entire virtual machine.
| Note |
|---|
To properly backup SQL databases, before you create a backup policy, Armor recommends that you separately create a backup of the database, and then place that backup in the server to be backed-up. |
| Expand |
|---|
| title | Step 1: Create a policy |
|---|
|
You must create a policy to configure often to take a backup and how long to keep a backup. | Note |
|---|
By default, times are based on your web browser's configured time zone. The location of your virtual machine does not relate to the time zone used in this feature. |
In the Armor Management Portal (AMP), in the left-side navigation, click Infrastructure. Click Advanced Backup. Click Policies. Click plus ( + ) icon. In Policy Name, enter a descriptive name. In Location, select the data center where the virtual machine is located (and where the backup will take place). In Type, select Fileset Protection. Next to Backup Schedule, under Take Snapshots (Frequency), enter how often Armor should take a snapshot. And then directly across, under Keep Snapshots (Retention), enter how long Armor should keep this snapshot.
You must enter your time configurations in the same row. For example, to take a snapshot every week and to keep that snapshot for six months, under Take Snapshots (Frequency), in Every (Days), enter 7, and then directly across, under Keep Snapshots (Retention), in For (Days), enter 182.
You can create a maximum of four Frequency and Retention settings. The minimum retention period is 3 days. Additionally, you must create a policy that takes place once per day. You must enter a time in hours. For example, to take a snapshot every two hours and to keep that snapshot for three days, under Take Snapshots (Frequency), in Every (Hours), enter 2, and then directly across, under Keep Snapshots (Retention), in For (Days), enter 3.
(Optional) To enable off-site replication, for Replication, mark On. Select a Location. Configure a time for retention. This time cannot be larger than the time configured for local retention. This feature stores copies of your snapshots in another physical location, which you can retrieve in case the copies in your local machine are not accessible or usable. There is a cost associated with this feature.
(Optional) In Snapshot Window, configure the time frame for when your scheduled snapshots should take place. By default, Rubrik will determine when the scheduled snapshots will take place; however, with this option, you have the ability to configure a specific time frame for when the scheduled snapshots will take place. This option can be useful if you want to perform snapshots during a period of low traffic. Under First Full Window, configure the time frame for when the first full snapshot should take place. Armor recommends that you configure a time when your environment experiences low traffic, low transaction volume, or less frequent changes. By default, times are based on your web browser's configured time zone. After the first full snapshot is complete, the configuration you created under Take Snapshots (Frequency) and Take Snapshots Between will be implemented. For example, under First full Window, if you configure an initial time frame of Sunday 12 AM to Sunday 6 AM, then your first full snapshot will take place at any time during this time frame. After the first full snapshot is complete, then the time frame configured in Take Snapshots (Frequency) and Take Snapshots Between will begin. If the first snapshot completes at Sunday at 5 AM, and your policy includes a snapshot every 4 hours, then the next snapshot will take place at 9 AM, and then again at 1 PM.
Click Create Policy.
|
...