You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage-mover/bandwidth-management.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ This schedule looks a lot like a calendar in outlook, but there are a few import
36
36
## Enabling or changing a bandwidth management schedule
37
37
38
38
Using the Azure portal, you can enable a bandwidth schedule on a registered agent resource.
39
-
1. With the portal showing your Storage Mover resource, select the "*Registered agents*" in the menu on the left.
39
+
1. With the portal showing your Storage Mover resource, select "*Registered agents*" in the menu on the left.
40
40
1. You now have two options to set or view a schedule. You can find the column "*Bandwidth management*" and click on the link for your selected agent. Or, you can select the checkbox in front of your agent. That enables and a command button above the list of agents, labeled "*Manage bandwidth limit*".
41
41
:::image type="content" source="media/bandwidth-management/bandwidth-registered-agents-command-small.png" alt-text="Azure portal, registered agents blade, showing to select and agent and then select the Bandwidth Management command." lightbox="media/bandwidth-management/bandwidth-registered-agents-command.png":::
42
42
1. The bandwidth management window opens and displays the schedule currently in effect for the agent. When an empty schedule is shown, there are no bandwidth limitations defined for this agent.
@@ -200,7 +200,7 @@ You can, however, manually form that JSON and directly supply it as an argument
200
200
> The schedule consists of one or more time spans during which a bandwidth limit applies that the agent is not to exceed. These time spans must not be overlapping. At any given time, only one limit may apply. A JSON specifying a schedule with overlapping times is considered malformed and cannot be applied to the agent.
201
201
202
202
The following two representations of a bandwidth limit schedule are equivalent:
203
-
:::image type="content" source="media/bandwidth-management/bandwidth-limit-json-small.png" alt-text="Azure portal dialog showing a calendar, similar to Outlook, with scheduled bandwidth limitation windows." lightbox="media/bandwidth-management/bandwidth-limit-json.png":::
@@ -235,7 +235,7 @@ The following two representations of a bandwidth limit schedule are equivalent:
235
235
}
236
236
```
237
237
> [!NOTE]
238
-
> Time spans not covered by an entry in the schedule allow the agent to utilize all available bandwidth. During these times, it is likely that and agent doesn't utilize all available bandwidth. You can find more details about that in the performance article, section: "[Why migration performance varies](performance-targets.md#why-migration-performance-varies)".
238
+
> Time spans not covered by an entry in the schedule allow the agent to utilize all available bandwidth. During these times, it is likely that an agent doesn't utilize all available bandwidth. You can find more details about that in the performance article, section: "[Why migration performance varies](performance-targets.md#why-migration-performance-varies)".
0 commit comments