Skip to content

Commit bf1f44a

Browse files
minor changes
1 parent 6c6b8eb commit bf1f44a

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/backup/backup-azure-files-faq.yml

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -198,7 +198,7 @@ sections:
198198
answer: |
199199
The **duration** attribute helps to determine the timestamp for last backup of the day.
200200
201-
For example, if the **start time** is “x AM” and **duration** is “y hours”, the backups will be scheduled between “x AM” and based on the **schedule** attribute (x AM + y hours) defined in the policy. This attribute enables you to ensure backups are only triggered during your working hours when there're frequent update operations on file share contents; therefore, taking multiple snapshots will safeguard data from any accidental changes.
201+
For example, if the **start time** is “x AM” and **duration** is “y hours”, the backups will be scheduled between “x AM” and **schedule** attribute (x AM + y hours) as defined in the policy. This attribute enables you to ensure backups are only triggered during your working hours when there're frequent update operations on file share contents; therefore, taking multiple snapshots will safeguard data from any accidental changes.
202202
203203
- question: |
204204
How are the backups scheduled based on the attributes - start time, schedule, and duration?
@@ -211,29 +211,29 @@ sections:
211211
212212
Based on these values, the backup window is calculated as 9 AM – 9 AM + 12 hours, that is, 9 AM – 9 PM. Therefore, all backups will be scheduled within this window.
213213
214-
The first backup of the day is triggered at the start time mentioned in the policy, that is, 9 AM, and the schedule determines the time difference between consecutive backups, that is, 6 hours. With this calculation, your backup schedule would be: 9 AM, 1 PM (9 AM + 6 hours), 5 PM (1 PM + 6 hours), and 9 PM (5 PM + 6 hours).
214+
The first backup of the day is triggered at the start time mentioned in the policy, that is, 9 AM, and the **schedule** determines the time difference between consecutive backups, that is, 6 hours. With this calculation, your backup schedule would be: 9 AM, 1 PM (9 AM + 6 hours), 5 PM (1 PM + 6 hours), and 9 PM (5 PM + 6 hours).
215215
216-
Since, the end time of backup window we calculated was 9 PM, no backup would be triggered after this time.
216+
Since the end time of the backup window we calculated was 9 PM, no backup would be triggered after this time.
217217
218218
- question: |
219219
Why am I getting the error “The selected configuration will trigger only 1 backup per day”?
220220
answer: |
221-
This error would occur if you specified a **schedule** that's greater than the **duration**. For example, you've configured **start time** as 9 AM, **schedule** as 6 hours, and **duration** as 4 hours. In this scenario, the only time when backup job can trigger is 9 AM, since the next backup time of 3 PM (9 AM + 6 hours) is outside the backup window: 9 AM – 1 PM (9 AM + 4 hours).
221+
This error occurs if you specified a **schedule** that's greater than the **duration**. For example, you've configured **start time** as 9 AM, **schedule** as 6 hours, and **duration** as 4 hours. In this scenario, the only time when backup job can trigger is 9 AM, since the next backup time of 3 PM (9 AM + 6 hours) is outside the backup window: 9 AM – 1 PM (9 AM + 4 hours).
222222
223223
To fix this, we recommend you adjust your schedule or duration, or select **Daily** frequency instead of **Hourly**.
224224
225225
- question: |
226226
Why am I getting the error “The selected configuration extends backup window to next day”?
227227
answer: |
228-
This error occurs if the backup window's **start time** and **end time**, determined based on the backup schedule and duration configuration, falls on two different days.
228+
This error occurs if the backup window's **start time** and **end time**, determined based on the backup **schedule** and **duration** configuration, falls on two different days.
229229
230230
For example, you configured a policy with the following parameters:
231231
232232
- **Schedule**: Every 4 hours
233233
- **Start time**: 12 PM
234234
- **Duration**: 15 hours
235235
236-
Based on this configuration, the backup window will be: 12 PM – 3 AM (12 PM + 15 hours). Since, the start and end time are falling on two different days, we recommend you adjust the **start time** or **duration** to ensure they are on the same day.
236+
Based on this configuration, the backup window will be: 12 PM – 3 AM (12 PM + 15 hours). Since the start and end times are falling on two different days, we recommend you adjust the **start time** or **duration** to ensure they are on the same day.
237237
238238
- question: |
239239
What’s the impact on the existing recovery points when I switch from “Daily” to “Hourly” frequency?

0 commit comments

Comments
 (0)