| 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 |
|---|
Currently, Advanced Backup from Rubrik is available in the DFW01 (Dallas) and ORD01 (Chicago ) environments. If you use the London (LHR01) or Amsterdam (AMS01) data centers, then you can use the Backup & Recovery add-on product from R1 Soft. To learn more, see Backup & Recovery. |
| Note |
|---|
If you plan to use the Advanced Backup service on the same VM where you also leverage the Continuous Server Replication service for Disaster Recovery, please review some important information regarding the interoperability of those two services here. |
...
| Anchor |
|---|
| Access-the-Advanced-Backup-screen |
|---|
| Access-the-Advanced-Backup-screen |
|---|
|
Access the Advanced Backup screen...
In the Armor Management Portal (AMP), in the left-side navigation, click Infrastructure.
Click Advanced Backup.
...
To enable backup on your virtual machine, you must:
...
| 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. |
|
...
| Expand |
|---|
| title | Step 3: Assign a policy |
|---|
|
In the Armor Management Portal (AMP), in the left-side navigation, click Infrastructure. Click Advanced Backup. In VM Protection, hover over the ( + ) icon. Click the Add VM Protection icon. For Select A Location, select the data center where the desired virtual machine lives. In Select Your VM(S), mark the desired virtual machine (or machines). This table will only list virtual machines that do not have an assigned policy. To assign a different policy to a virtual machine, see Replace an existing policy for a virtual machine. A newly created virtual machine may not appear immediately in this list. You may need to wait an hour before a newly created virtual machine appears.
In Select A Policy, select the newly created policy. Create Configure Backup.
|
...
| Note |
|---|
To restore a fileset from a virtual machine snapshot, you must have the Rubrik agent installed in the corresponding data center. |
...
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.
|
...
In the Armor Management Portal, in the left-side navigation, click Infrastructure.
Click Advanced Backup.
In Fileset Protection, locate and hover over the desired fileset.
Click the vertical ellipses.
Click Restore from Backup.
Locate and hover over the desired snapshot.
Click the vertical ellipses, and then click Browse.
Navigate to the specific file or folder to restore.
Hover over, and then click the vertical ellipses.
Click Restore.
There are two types of restorations.
Option 1: Mark Overwrite Original to replace your existing files with the restored files.
Option 2: Mark Restore to Separate Folder to place the restored files in a separate location. This option will not replace your existing files. You can use this option to verify specific files before you remove the original files.
(Optional) Slide Continue on restore errors to avoid a possible interruption or cancelation of the restoration.
If you activate this option, then in the event a file cannot be restored, the system will continue to try to restore all other selected files.
If you do not activate this option, then in the event a file cannot be restored, the system will not attempt to restore additional files. Files that were previously restored will remain.
Click Restore.
To review the status of the restoration, in the top menu, click Restore Logs.
| Anchor |
|---|
| Edit-an-existing-policy |
|---|
| Edit-an-existing-policy |
|---|
|
Edit an existing policy...
| Note |
|---|
Before you update an existing policy, consider that: You cannot update the location of an existing policy. If you update the Snapshot Window for an existing policy and there is a virtual machine already assigned to the policy, then the virtual machine will not experience another first full snapshot. Existing snapshots for the virtual machine will remain stored with Armor. If you decrease the Retention rate, then older snapshots will be removed in accordance with the updated policy. For example, if you lower the retention rate from 14 days to 10 days, then backups older than 10 days will be removed.
|
...