Skip to content

Commit dbc4574

Browse files
Update back-up-azure-stack-hyperconverged-infrastructure-virtual-machines.md
1 parent fb71ac0 commit dbc4574

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/backup/back-up-azure-stack-hyperconverged-infrastructure-virtual-machines.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ These are the prerequisites for backing up virtual machines with MABS:
7676

7777
2. Set up the MABS protection agent on the server or each cluster node.
7878

79-
3. To deploy the agent, choose one of the following method:
79+
3. To deploy the agent, choose one of the following methods:
8080

8181
- **Attach agents**: Select an agent that's already installed.
8282
- **Install agent**: If you don't have the agent installed:
@@ -132,7 +132,7 @@ These are the prerequisites for backing up virtual machines with MABS:
132132
133133
If MABS is running on Windows Server 2012 R2 or later, then you can back up replica virtual machines. This is useful for several reasons:
134134
135-
**Reduces the impact of backups on the running workload** - Taking a backup of a virtual machine incurs some overhead as a snapshot is created. By offloading the backup process to a secondary remote site, the running workload is no longer affected by the backup operation. This is applicable only to deployments where the backup copy is stored on a remote site. For example, you might take daily backups and store data locally to ensure quick restore times, but take monthly or quarterly backups from replica virtual machines stored remotely for long-term retention.
135+
**Reduces the impact of backups on the running workload** - Taking a backup of a virtual machine incurs some overhead as a snapshot is created. When you offload the backup process to a secondary remote site, the running workload is no longer affected by the backup operation. This is applicable only to deployments where the backup copy is stored on a remote site. For example, you might take daily backups and store data locally to ensure quick restore times, but take monthly or quarterly backups from replica virtual machines stored remotely for long-term retention.
136136
137137
**Saves bandwidth** - In a typical remote branch office/headquarters deployment you need an appropriate amount of provisioned bandwidth to transfer backup data between sites. If you create a replication and failover strategy, in addition to your data backup strategy, you can reduce the amount of redundant data sent over the network. By backing up the replica virtual machine data rather than the primary, you save the overhead of sending the backed-up data over the network.
138138

0 commit comments

Comments
 (0)