{"id":9121,"date":"2022-07-08T15:42:37","date_gmt":"2022-07-08T14:42:37","guid":{"rendered":"https:\/\/blog.capdata.fr\/?p=9121"},"modified":"2023-01-19T11:30:20","modified_gmt":"2023-01-19T10:30:20","slug":"sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws","status":"publish","type":"post","link":"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/","title":{"rendered":"SQL Server 2022 Backup \/ Restore via un bucket S3 sous AWS"},"content":{"rendered":"\"twitter\"<\/a>\"linkedin\"<\/a>\"mail\"<\/a>

I] Introduction:<\/strong><\/em><\/span><\/p>\n

Jusqu’\u00e0 maintenant afin de pouvoir profiter des avantages du cloud AWS pour externaliser ses sauvegardes SQL Server, il fallait les r\u00e9aliser de mani\u00e8re classique sur site (on premise) puis via un deuxi\u00e8me process les uploader dans un compartiment (bucket) S3.<\/span><\/p>\n

Ceci rendait la t\u00e2che plus lourde \u00e0 superviser et \u00e9galement impliquait d’avoir suffisamment d’espace de stockage sur site avant de pouvoir basculer nos fichiers de sauvegarde dans le nuage AWS.<\/span><\/p>\n

L’une des nouveaut\u00e9s de SQLServer 2022 est la possibilit\u00e9 d’effectuer ses sauvegardes directement sur un bucket S3 en transact SQL via la commande classique “BACKUP DATABASE testbdd TO URL” .<\/span><\/p>\n

 <\/p>\n

II] Pr\u00e9requis:<\/strong><\/em><\/span><\/p>\n

    \n
  1. Il faut disposer d’un compte ayant des droits d’administration sur votre environnement AWS au niveau des briques S3 et IAM:<\/span>
    \nDans le cadre de cet article nous utiliserons AWS CLI en v2 pour cr\u00e9er nos ressources que l’on peut r\u00e9cup\u00e9rer ici:<\/span>     https:\/\/aws.amazon.com\/fr\/cli\/<\/a><\/em><\/span><\/p>\n
    # V\u00e9rification de la version install\u00e9e<\/strong>\r\nC:\\Users\\lprou>aws --version<\/em>\r\naws-cli\/2.7.13 Python\/3.9.11 Windows\/10 exe\/AMD64 prompt\/off<\/em>\r\n\r\n# Configuration via une clef d'acc\u00e8s d'un compte administrateur.<\/strong>\r\nC:\\Users\\lprou>aws configure<\/em>\r\nAWS Access Key ID [None]: ****************HPWZ<\/em>\r\nAWS Secret Access Key [None]: ****************Nx67<\/em>\r\nDefault region name [None]: eu-west-3<\/em>\r\nDefault output format [None]:<\/em> json\r\n<\/pre>\n
    Bien entendu il est tout \u00e0 fait possible d’utiliser la console Web…<\/span><\/li>\n
  2. Un bucket S3 devra \u00eatre cr\u00e9\u00e9\/configur\u00e9 au pr\u00e9alable pour h\u00e9berger nos fichiers de sauvegarde.
    \n    cf https:\/\/aws.amazon.com\/fr\/s3\/<\/a><\/em><\/span><\/span>
    \nPour ce genre d’utilisation il faut veiller \u00e0 “Bloquer tous les acc\u00e8s publics”, activer ou non le chiffrement, les versions et le verrouillage d’objets… Pour rappel les co\u00fbts varient l\u00e9g\u00e8rement en fonction de la r\u00e9gion choisi.<\/span><\/p>\n
    # Consultation de l'aide de la commande create-bucket<\/strong>\r\nC:\\Users\\lprou>aws s3api create-bucket help\r\n\r\n<\/em># Cr\u00e9ation du compartiment S3<\/strong>\r\nC:\\Users\\lprou>aws s3api create-bucket --bucket capdata-backupsqlserver --region eu-west-3 --create-bucket-configuration LocationConstraint=eu-west-3 --acl private --object-lock-enabled-for-bucket<\/em>\r\n{\r\n\"Location\": \"http:\/\/capdata-backupsqlserver.s3.amazonaws.com\/\"\r\n}\r\n\r\n<\/em># D\u00e9sactivation de l'acc\u00e8s publique<\/strong>\r\nC:\\Users\\lprou>aws s3api put-public-access-block --bucket capdata-backupsqlserver --public-access-block-configuration \"BlockPublicAcls=true,IgnorePublicAcls=true,BlockPublicPolicy=true,RestrictPublicBuckets=true\"\r\n\r\n<\/em># Activation du chiffrage<\/strong>\r\naws s3api put-bucket-encryption --bucket capdata-backupsqlserver --server-side-encryption-configuration \"{\\\"Rules\\\": [{\\\"ApplyServerSideEncryptionByDefault\\\":{\\\"SSEAlgorithm\\\": \\\"AES256\\\"}}]}\"\r\n\r\n<\/em><\/pre>\n<\/li>\n
  3. Un utilisateur IAM poss\u00e9dant une cl\u00e9 d’acc\u00e8s compos\u00e9e d’une “Access Key ID” ainsi que d’une “Secret Key ID” devra \u00eatre cr\u00e9\u00e9.<\/span>
    \nCet utilisateur devra avoir des droits d’\u00e9criture sur le bucket S3 concern\u00e9.
    \nCes identifiants seront utilis\u00e9s par le moteur SQLServer pour s’authentifier au niveau du point de terminaison (endpoint) S3.
    \nAinsi pour des raisons \u00e9videntes de s\u00e9curit\u00e9 il est important de n’accorder que les droits minimums \u00e0 cet utilisateur:<\/span><\/p>\n
    # Cr\u00e9ation d'un utilisateur IAM<\/strong>\r\nC:\\Users\\lprou>aws iam create-user --user-name monSQLServer2022<\/em>\r\n{\r\n\"User\": {\r\n\"Path\": \"\/\",\r\n\"UserName\": \"monSQLServer2022\",\r\n\"UserId\": \"AIDAQIMXBNKBJZPXAIG4Z\",\r\n\"Arn\": \"arn:aws:iam::018033XXXXXX:user\/monSQLServer2022\",\r\n\"CreateDate\": \"2022-07-08T09:42:56+00:00\"\r\n}\r\n}<\/em><\/pre>\n
    # Cr\u00e9ation d'une clef d'acc\u00e8s pour l'utilisateur \"monSQLServer2022\"\r\n<\/strong>C:\\Users\\lprou>aws iam create-access-key --user-name monSQLServer2022<\/em>  \r\n{ \r\n\"AccessKey\": { \r\n\"UserName\": \"monSQLServer2022\", \r\n\"AccessKeyId\": \"AKIAQIMXBNKBG4BLUJUP\", \r\n\"Status\": \"Active\", \r\n\"SecretAccessKey\": \"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\", \r\n\"CreateDate\": \"2022-07-08T10:01:26+00:00\" \r\n} \r\n}<\/em><\/pre>\n
    # Cr\u00e9ation d'un fichier .json contenant la strat\u00e9gie.\r\n<\/strong>Sauvegarder cet exemple<\/span> de strat\u00e9gie dans une fichier S3_monSQLServer2022.json\r\n{\r\n\"Version\": \"2012-10-17\",\r\n\"Statement\": [\r\n{\r\n\"Sid\": \"VisualEditor0\",\r\n\"Effect\": \"Allow\",\r\n\"Action\": \"s3:ListBucket\",\r\n\"Resource\": \"arn:aws:s3:::capdata-backupsqlserver\"\r\n},\r\n{\r\n\"Sid\": \"VisualEditor1\",\r\n\"Effect\": \"Allow\",\r\n\"Action\": \"s3:ListAllMyBuckets\",\r\n\"Resource\": \"*\"\r\n},\r\n{\r\n\"Sid\": \"VisualEditor2\",\r\n\"Effect\": \"Allow\",\r\n\"Action\": [\r\n\"s3:PutObject\",\r\n\"s3:GetObject\"\r\n],\r\n\"Resource\": \"arn:aws:s3:::capdata-backupsqlserver\/*\"\r\n}\r\n]\r\n}<\/pre>\n
    # Cr\u00e9ation d'une strat\u00e9gie<\/strong>\r\nC:\\Users\\lprou>aws iam create-policy --policy-name S3_monSQLServer2022 --policy-document file:\/\/C:\\Users\\lprou\\S3_monSQLServer2022.json\r\n{\r\n\"Policy\": {\r\n\"PolicyName\": \"S3_monSQLServer2022\",\r\n\"PolicyId\": \"ANPAQIMXBNKBLWEV7ZWBQ\",\r\n\"Arn\": \"arn:aws:iam::018033XXXXXX:policy\/S3_monSQLServer2022\",\r\n\"Path\": \"\/\",\r\n\"DefaultVersionId\": \"v1\",\r\n\"AttachmentCount\": 0,\r\n\"PermissionsBoundaryUsageCount\": 0,\r\n\"IsAttachable\": true,\r\n\"CreateDate\": \"2022-08-11T15:11:21+00:00\",\r\n\"UpdateDate\": \"2022-08-11T15:11:21+00:00\"\r\n}\r\n}<\/pre>\n
    # On attache la strat\u00e9gie \"S3_monSQLServer2022\" \u00e0 l'utilisateur IAM \"monSQLServer2022<\/em> \"<\/strong><\/span>\r\nC:\\Users\\lprou>aws iam attach-user-policy --policy-arn arn:aws:iam::018033XXXXXX:policy\/S3_monSQLServer2022 --user-name monSQLServer2022<\/em><\/pre>\n<\/li>\n
  4. La communication entre votre serveur SQL et AWS S3 se faisant en HTTPS, le certificat permettant d’acc\u00e9der au bucket S3 devra \u00eatre install\u00e9 dans les magasins du serveur SQL.
    \n<\/span><\/li>\n<\/ol>\n
     <\/p>\n
    III] Mise en oeuvre:<\/span><\/strong><\/span><\/p>\n
      \n
    1. Une fois tous les pr\u00e9requis satisfait nous pouvons nous connecter \u00e0 notre instance h\u00e9berg\u00e9e sous SQLServer 2022 via “Microsoft SqlServer Management Studio” (SSMS).<\/span>
      \nIl faut alors cr\u00e9er nos “Credentials” qui permettront au moteur SqlServer de se connecter \u00e0 notre bucket S3:
      \n<\/span>
      \nVous trouverez la documentation pour les m\u00e9thodes d’acc\u00e8s \u00e0 un compartiment S3 via un point de terminaison, \u00e0 savoir s3.MYREGION.amazonaws.com ici:
      \n<\/span>S3 M\u00e9thode d’acc\u00e8s<\/a><\/span><\/em><\/p>\n
      # Cr\u00e9ation des cr\u00e9dentials de type 'S3 Access Key' cf Create credential<\/a><\/em>\r\n<\/strong>CREATE CREDENTIAL [s3:\/\/s3.eu-west-3.amazonaws.com\/capdata-backupsqlserver] \r\nWITH \r\nIDENTITY = 'S3 Access Key', \r\nSECRET = 'AKIAQIMXBNKBG4BLUJUP:<\/span>7TSSsJ5XQVjze4+HI22Am35eeEax3uQfAsOryPj5';\r\n\r\nAttention<\/strong><\/span> le caract\u00e8re s\u00e9parant l'AccessKeyId du SecretAccessKey dans le secret doit \u00eatre un ':<\/span>'\r\n\r\n<\/em><\/pre>\n
      \"\"<\/a><\/li>\n
    2. Ne reste plus qu’\u00e0 lancer une commande de sauvegarde directement dans notre bucket S3:\n
      # Lancement d'une sauvegarde<\/strong>\r\nBACKUP DATABASE TESTBDD \r\nTO URL = 's3:\/\/s3.eu-west-3.amazonaws.com\/capdata-backupsqlserver\/TESTBDD.bak' \r\n<\/em>WITH CREDENTIAL = 's3:\/\/s3.eu-west-3.amazonaws.com\/capdata-backupsqlserver', COMPRESSION, STATS = 10 ; <\/em><\/pre>\n
      \"\"<\/a><\/span><\/em><\/p>\n
      ou alors sur un access point afin de pouvoir par exemple g\u00e9rer une strat\u00e9gie d’acc\u00e8s par applicatif dans le cas ou plusieurs applications \u00e9criraient dans le m\u00eame bucket S3.<\/span>
      \n      cf S3 access point<\/a><\/em><\/span><\/span><\/p>\n
      # Lancement d'une sauvegarde\r\n<\/strong>BACKUP DATABASE TESTBDD\r\nTO URL = 's3:\/\/s3.eu-west-3.amazonaws.com\/capdata-backupsqlser-ftpz1exz9apnsi9cb1834kq8htfsneuw3b-s3alias\/TESTBDD2.bak'\r\nWITH CREDENTIAL = 's3:\/\/s3.eu-west-3.amazonaws.com\/capdata-backupsqlserver', COMPRESSION, STATS = 10 ;<\/pre>\n
      \"\"
      \nNotes:
      \nIl est bien s\u00fbr recommand\u00e9 d’utiliser un nom de fichier unique pour chaque sauvegarde dans le but d’\u00e9viter l’\u00e9crasement d’une sauvegarde pr\u00e9c\u00e9dente.
      \nOn constate que l\u2019URL contient le nom du Bucket S3 ou l’alias de point d’acc\u00e8s ainsi que la r\u00e9gion sur laquelle il a \u00e9t\u00e9 cr\u00e9\u00e9.
      \n      cf S3 M\u00e9thode d’acc\u00e8s \u00e0 un compartiment<\/em><\/a><\/span><\/li>\n
    3. On peut naturellement lancer une commande de restauration depuis notre bucket S3<\/span>:\n
      # Lancement d'une restauration<\/strong>\r\nRESTORE DATABASE TESTBDD\r\nFROM URL = 's3:\/\/s3.eu-west-3.amazonaws.com\/capdata-backupsqlserver\/TESTBDD.bak'\r\nwith replace ;<\/pre>\n
      \"\"<\/a><\/p>\n
      A noter que contrairement \u00e0 ce qui a pu \u00eatre vu dans cet article pr\u00e9c\u00e8dent sauvegardes-sql-server-dans-un-azure-blob-storage,<\/a><\/em><\/span>
      \nil n’est pas possible de r\u00e9aliser une sauvegarde qui soit sur deux emplacements, l’un local et l’autre sur S3 pour l’instant…<\/p>\n
      \"\"<\/a>
      \nIl n’est pas non plus possible de faire une sauvegarde avec l’option FILE_SNAPSHOT qui n’est pas compatible avec S3 mais juste avec Azure Storage:
      \n      cf file-snapshot-backups<\/a><\/span><\/em><\/span><\/p>\n
      # Lancement d'une sauvegarde avec FILE_SNAPSHOT impossible<\/strong>\r\nBACKUP DATABASE TESTBDD \r\nTO URL = 's3:\/\/s3.eu-west-3.amazonaws.com\/capdata-backupsqlserver\/TESTBDD.bak' \r\nWITH CREDENTIAL = 's3:\/\/s3.eu-west-3.amazonaws.com\/capdata-backupsqlserver', COMPRESSION, STATS = 10,FILE_SNAPSHOT;<\/pre>\n
      \"\"<\/a><\/li>\n
    4. Enfin il ne reste plus qu’\u00e0 g\u00e9rer la r\u00e9tention de vos sauvegardes en fonction de votre politique de s\u00e9curit\u00e9 via une r\u00e8gle de cycle de vie sur votre bucket S3. Vous pouvez \u00e9galement faire un changement de classe de vos vieilles sauvegardes pour les d\u00e9placer par exemple sur du Glacier afin de limiter les co\u00fbts de stockage.
      \n      cf R\u00e8gle cycle de vie<\/a><\/em><\/span>
      \n      cf Classes de stockage S3<\/a><\/em><\/span>
      \n<\/span>
      \n      \"\"<\/a><\/li>\n<\/ol>\n
       <\/p>\n
      IV] Conclusion:<\/strong><\/em><\/span><\/p>\n
      Avec cette fonctionnalit\u00e9 de sauvegarder directement depuis sqlServer vers du stockage S3, il devient tr\u00e8s facile et tr\u00e8s comp\u00e9titif en terme de co\u00fbts d’externaliser ces donn\u00e9es. Fini les sauvegardes du we tomb\u00e9es en erreurs en raison d’un manque d’espace disque disponible. Fini \u00e9galement la crainte de perdre ses sauvegardes car AWS garanti leur disponibilit\u00e9 jusqu’\u00e0 99,99% pour la classe standard avec une r\u00e9silience incluse dans la brique<\/span><\/span> S3 qui se base sur la r\u00e9plication du bucket sur des p\u00e9riph\u00e9riques de stockage appartenant au moins \u00e0 trois zones de disponibilit\u00e9s diff\u00e9rentes sur une r\u00e9gion s\u00e9lectionn\u00e9e. Chaque zone \u00e9tant localis\u00e9es dans des endroits distincts, la fiabilit\u00e9 en cas de d\u00e9faillance du mat\u00e9riel de stockage ou de probl\u00e8mes divers tel qu’un incendie est assur\u00e9e. Ce niveau de disponibilit\u00e9 d\u00e9pend bien \u00e9videment de la classe de stockage utilis\u00e9e et \u00e0 un impact sur le co\u00fbt de la solution.<\/span><\/p>\n
      Documentations diverses:<\/span><\/p>\n
      https:\/\/docs.microsoft.com\/en-us\/sql\/relational-databases\/backup-restore\/sql-server-backup-and-restore-with-s3-compatible-object-storage?view=sql-server-ver16<\/a><\/span><\/em>
      \n      https:\/\/docs.microsoft.com\/en-us\/sql\/relational-databases\/backup-restore\/sql-server-backup-to-url-s3-compatible-object-storage?view=sql-server-ver16<\/a><\/span><\/em>
      \n      https:\/\/docs.microsoft.com\/en-us\/sql\/relational-databases\/backup-restore\/sql-server-backup-to-url-s3-compatible-object-storage-best-practices-and-troubleshooting?view=sql-server-ver16<\/a><\/span><\/em><\/p>\n
      https:\/\/aws.amazon.com\/fr\/s3<\/a><\/span><\/em>
      \n      https:\/\/aws.amazon.com\/fr\/s3\/pricing\/<\/a><\/span><\/em><\/p>\n\"twitter\"<\/a>\"linkedin\"<\/a>\"mail\"<\/a>","protected":false},"excerpt":{"rendered":"
      I] Introduction: Jusqu’\u00e0 maintenant afin de pouvoir profiter des avantages du cloud AWS pour externaliser ses sauvegardes SQL Server, il fallait les r\u00e9aliser de mani\u00e8re classique sur site (on premise) puis via un deuxi\u00e8me process les uploader dans un compartiment… Continuer la lecture →<\/span><\/a><\/p>\n","protected":false},"author":23,"featured_media":9125,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[295,5],"tags":[288,408],"class_list":["post-9121","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aws","category-sqlserver","tag-sauvegardes","tag-sql-server-2022"],"yoast_head":"\nSQL Server 2022 Backup \/ Restore via un bucket S3 sous AWS - Capdata TECH BLOG<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SQL Server 2022 Backup \/ Restore via un bucket S3 sous AWS - Capdata TECH BLOG\" \/>\n<meta property=\"og:description\" content=\"I] Introduction: Jusqu’\u00e0 maintenant afin de pouvoir profiter des avantages du cloud AWS pour externaliser ses sauvegardes SQL Server, il fallait les r\u00e9aliser de mani\u00e8re classique sur site (on premise) puis via un deuxi\u00e8me process les uploader dans un compartiment… Continuer la lecture →\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/\" \/>\n<meta property=\"og:site_name\" content=\"Capdata TECH BLOG\" \/>\n<meta property=\"article:published_time\" content=\"2022-07-08T14:42:37+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-01-19T10:30:20+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/07\/BackupToS3.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"958\" \/>\n\t<meta property=\"og:image:height\" content=\"555\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Louis PROU\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"Louis PROU\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/\"},\"author\":{\"name\":\"Louis PROU\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/a4848b0c7faa6956f1a1520d6cc34ae9\"},\"headline\":\"SQL Server 2022 Backup \/ Restore via un bucket S3 sous AWS\",\"datePublished\":\"2022-07-08T14:42:37+00:00\",\"dateModified\":\"2023-01-19T10:30:20+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/\"},\"wordCount\":909,\"commentCount\":1,\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"keywords\":[\"Sauvegardes\",\"SQL Server 2022\"],\"articleSection\":[\"AWS\",\"SQL Server\"],\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/\",\"url\":\"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/\",\"name\":\"SQL Server 2022 Backup \/ Restore via un bucket S3 sous AWS - Capdata TECH BLOG\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/#website\"},\"datePublished\":\"2022-07-08T14:42:37+00:00\",\"dateModified\":\"2023-01-19T10:30:20+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/blog.capdata.fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SQL Server 2022 Backup \/ Restore via un bucket S3 sous AWS\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.capdata.fr\/#website\",\"url\":\"https:\/\/blog.capdata.fr\/\",\"name\":\"Capdata TECH BLOG\",\"description\":\"Le blog technique sur les bases de donn\u00e9es de CAP DATA Consulting\",\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.capdata.fr\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/blog.capdata.fr\/#organization\",\"name\":\"Capdata TECH BLOG\",\"url\":\"https:\/\/blog.capdata.fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp\",\"contentUrl\":\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp\",\"width\":800,\"height\":254,\"caption\":\"Capdata TECH BLOG\"},\"image\":{\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.linkedin.com\/company\/cap-data-consulting\/mycompany\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/a4848b0c7faa6956f1a1520d6cc34ae9\",\"name\":\"Louis PROU\",\"url\":\"https:\/\/blog.capdata.fr\/index.php\/author\/lprou\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"SQL Server 2022 Backup \/ Restore via un bucket S3 sous AWS - Capdata TECH BLOG","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/","og_locale":"fr_FR","og_type":"article","og_title":"SQL Server 2022 Backup \/ Restore via un bucket S3 sous AWS - Capdata TECH BLOG","og_description":"I] Introduction: Jusqu’\u00e0 maintenant afin de pouvoir profiter des avantages du cloud AWS pour externaliser ses sauvegardes SQL Server, il fallait les r\u00e9aliser de mani\u00e8re classique sur site (on premise) puis via un deuxi\u00e8me process les uploader dans un compartiment… Continuer la lecture →","og_url":"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/","og_site_name":"Capdata TECH BLOG","article_published_time":"2022-07-08T14:42:37+00:00","article_modified_time":"2023-01-19T10:30:20+00:00","og_image":[{"width":958,"height":555,"url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2022\/07\/BackupToS3.jpg","type":"image\/jpeg"}],"author":"Louis PROU","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"Louis PROU","Dur\u00e9e de lecture estim\u00e9e":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/#article","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/"},"author":{"name":"Louis PROU","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/a4848b0c7faa6956f1a1520d6cc34ae9"},"headline":"SQL Server 2022 Backup \/ Restore via un bucket S3 sous AWS","datePublished":"2022-07-08T14:42:37+00:00","dateModified":"2023-01-19T10:30:20+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/"},"wordCount":909,"commentCount":1,"publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"keywords":["Sauvegardes","SQL Server 2022"],"articleSection":["AWS","SQL Server"],"inLanguage":"fr-FR","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/","url":"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/","name":"SQL Server 2022 Backup \/ Restore via un bucket S3 sous AWS - Capdata TECH BLOG","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/#website"},"datePublished":"2022-07-08T14:42:37+00:00","dateModified":"2023-01-19T10:30:20+00:00","breadcrumb":{"@id":"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.capdata.fr\/index.php\/sql-server-2022-backup-restore-via-un-bucket-s3-sous-aws\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/blog.capdata.fr\/"},{"@type":"ListItem","position":2,"name":"SQL Server 2022 Backup \/ Restore via un bucket S3 sous AWS"}]},{"@type":"WebSite","@id":"https:\/\/blog.capdata.fr\/#website","url":"https:\/\/blog.capdata.fr\/","name":"Capdata TECH BLOG","description":"Le blog technique sur les bases de donn\u00e9es de CAP DATA Consulting","publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.capdata.fr\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/blog.capdata.fr\/#organization","name":"Capdata TECH BLOG","url":"https:\/\/blog.capdata.fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/","url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp","contentUrl":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp","width":800,"height":254,"caption":"Capdata TECH BLOG"},"image":{"@id":"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.linkedin.com\/company\/cap-data-consulting\/mycompany\/"]},{"@type":"Person","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/a4848b0c7faa6956f1a1520d6cc34ae9","name":"Louis PROU","url":"https:\/\/blog.capdata.fr\/index.php\/author\/lprou\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/9121","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/users\/23"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/comments?post=9121"}],"version-history":[{"count":139,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/9121\/revisions"}],"predecessor-version":[{"id":9965,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/9121\/revisions\/9965"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media\/9125"}],"wp:attachment":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media?parent=9121"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/categories?post=9121"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/tags?post=9121"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}