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: docs/relational-databases/backup-restore/sql-server-backup-and-restore-with-s3-compatible-object-storage.md
[!INCLUDE [SQL Server 2022](../../includes/applies-to-version/sqlserver2022.md)]
16
16
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.
18
18
19
19
## Overview
20
20
@@ -63,15 +63,15 @@ The S3 endpoint must have been configured as follows:
63
63
64
64
## Performance best practices
65
65
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.
67
67
68
68
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.
69
69
70
70
## Known issues and limitations
71
71
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.
73
73
74
-
## Next steps
74
+
## Related content
75
75
76
76
-[SQL Server backup to URL for S3-compatible object storage](sql-server-backup-to-url-s3-compatible-object-storage.md).
77
77
-[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
0 commit comments