Skip to content

Commit 0f52f81

Browse files
Merge pull request #28713 from MicrosoftDocs/WilliamDAssafMSFT-patch-2
20231009 broken link fix in Update sql-server-backup-and-restore-with…
2 parents e45f724 + 501c46c commit 0f52f81

1 file changed

Lines changed: 7 additions & 7 deletions

File tree

docs/relational-databases/backup-restore/sql-server-backup-and-restore-with-s3-compatible-object-storage.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: "Backup & restore with S3-compatible object storage"
33
description: "SQL Server backup and restore with S3-compatible object storage"
44
author: WilliamDAssafMSFT
55
ms.author: wiassaf
6-
ms.date: 05/18/2023
6+
ms.date: 10/09/2023
77
ms.service: sql
88
ms.subservice: backup-restore
99
ms.topic: conceptual
@@ -14,7 +14,7 @@ monikerRange: ">=sql-server-ver16||>=sql-server-linux-ver16"
1414

1515
[!INCLUDE [SQL Server 2022](../../includes/applies-to-version/sqlserver2022.md)]
1616

17-
This article introduces the concepts, requirements and components necessary to use S3-compatible object storage as a backup destination.
17+
This article introduces the concepts, requirements, and components necessary to use S3-compatible object storage as a backup destination.
1818

1919
## Overview
2020

@@ -63,15 +63,15 @@ The S3 endpoint must have been configured as follows:
6363

6464
## Performance best practices
6565

66-
It's recommended to check with your S3-compatible object storage provider for guidance on performance best practices optimization as well as initial setup and configuration. Due to a wide variety of solutions and setups, the recommended values for backup and restore parameters and throughput can change.
66+
It's recommended to check with your S3-compatible object storage provider for guidance on performance best practices optimization, initial setup, and configuration. Due to a wide variety of solutions and setups, the recommended values for backup and restore parameters and throughput can change.
6767

6868
By using S3 parts in [!INCLUDE[sssql22-md](../../includes/sssql22-md.md)], you can stripe your backup set to support files size up to 12.8 TB.
6969

7070
## Known issues and limitations
7171

72-
Due to the current limitation of S3 Standard REST API, the temporary uncommitted data files are not removed in case of failures. They may be created in the S3-compatible object store due to an ongoing multipart upload operation while the BACKUP T-SQL command is running. These uncommitted data blocks persist in the S3-compatible object storage in the case the BACKUP T-SQL command fails or is canceled. If the backup succeeds, the object store automatically removes these temporary files to form the final backup file. Some S3-providers handle temporary file cleanup through their garbage collector system.
72+
Due to the current limitation of S3 Standard REST API, the temporary uncommitted data files are not removed in case of failures. They can be created in the S3-compatible object store due to an ongoing multipart upload operation while the BACKUP T-SQL command is running. These uncommitted data blocks persist in the S3-compatible object storage in the case the BACKUP T-SQL command fails or is canceled. If the backup succeeds, the object store automatically removes these temporary files to form the final backup file. Some S3-providers handle temporary file cleanup through their garbage collector system.
7373

74-
## Next steps
74+
## Related content
7575

7676
- [SQL Server backup to URL for S3-compatible object storage](sql-server-backup-to-url-s3-compatible-object-storage.md).
7777
- [SQL Server back up to URL for S3-compatible object storage best practices and troubleshooting](sql-server-backup-to-url-s3-compatible-object-storage-best-practices-and-troubleshooting.md)
@@ -123,7 +123,7 @@ Due to the current limitation of S3 Standard REST API, the temporary uncommitted
123123

124124
[redhat_docs]: https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.8
125125
[redhat_sheet]: https://www.redhat.com/rhdc/managed-files/cl-ocs3-datasheet-f19840wg-201911-en.pdf
126-
[redhat_webs]: https://access.redhat.com/products/red-hat-openshift-container-storage
126+
[redhat_webs]: https://www.redhat.com/technologies/cloud-computing/openshift
127127

128128
[scality_docs]: https://docs.scality.com
129129
[scality_sheet]: https://go.scality.com/l/893901/2021-08-17/23c52m/893901/1629719058hjLdj34t/Artesca_Datasheet_Letter_Web_210818.pdf
@@ -133,4 +133,4 @@ Due to the current limitation of S3 Standard REST API, the temporary uncommitted
133133
[weka_sheet]: https://www.weka.io/wp-content/uploads/files/2020/03/WekaFS-DS-W01R14DS201808.pdf
134134
[weka_webs]: https://weka.io
135135

136-
[Azure block blobs]: /rest/api/storageservices/understanding-block-blobs--append-blobs--and-page-blobs
136+
[Azure block blobs]: /rest/api/storageservices/understanding-block-blobs--append-blobs--and-page-blobs

0 commit comments

Comments
 (0)