Skip to content

Commit fe9c114

Browse files
authored
Merge pull request #164107 from SwathiDhanwada-MSFT/patch-37
(Azure CXP) fixes MicrosoftDocs/azuredocs#77380
2 parents e844b93 + 9fee0d4 commit fe9c114

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/backup/faq-backup-sql-server.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ sections:
113113
- question: |
114114
Why can’t I see an added database for an autoprotected instance?
115115
answer: |
116-
A database that you [add to an autoprotected instance](backup-sql-server-database-azure-vms.md#enable-auto-protection) might not immediately appear under protected items. This is because the discovery typically runs every 8 hours. However, you can discover and protect new databases immediately if you manually run a discovery by selecting **Rediscover DBs**, as shown in the following image:
116+
A database that you [add to an autoprotected instance](backup-sql-server-database-azure-vms.md#enable-auto-protection) might not immediately appear under protected items. This is because the discovery typically runs every 8 hours, and the actual protection of the system can take additional time as it depends on the size of the VM. However, you can discover new databases immediately if you manually run a discovery by selecting **Rediscover DBs**, as shown in the following image:
117117
118118
![Manually discover a newly added database](./media/backup-azure-sql-database/view-newly-added-database.png)
119119
@@ -136,4 +136,4 @@ sections:
136136
additionalContent: |
137137
138138
## Next steps
139-
Learn how to [back up a SQL Server database](backup-azure-sql-database.md) that's running on an Azure VM.
139+
Learn how to [back up a SQL Server database](backup-azure-sql-database.md) that's running on an Azure VM.

0 commit comments

Comments
 (0)