Memorizzare i file di backup in un bucket Cloud Storage
Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Database Migration Service replica i dati dai file di log delle transazioni e di backup di SQL Server che carichi in un bucket Cloud Storage. Questa pagina descrive come preparare il bucket per le procedure di migrazione e la struttura delle cartelle necessaria per consentire a Database Migration Service di riconoscere i file di backup.
Per preparare un bucket di archiviazione per la migrazione, svolgi i seguenti passaggi:
Crea il bucket.
Assicurati di utilizzare la stessa regione di quella in cui intendi creare l'istanza Cloud SQL per SQL Server di destinazione.
Database Migration Service è un prodotto completamente regionale, il che significa che tutte le entità correlate alla migrazione (profili di connessione di origine e di destinazione, job di migrazione, database di destinazione, bucket di archiviazione per i file di backup) devono essere salvate in un'unica regione.
Database Migration Service prevede una struttura di cartelle in cui ogni cartella presente al livello principale del bucket rappresenta un database da migrare.
La cartella del database deve contenere almeno due cartelle: full per il file di backup completo e log per i file di backup del log delle transazioni caricati successivamente per la fase di caricamento incrementale.
La cartella del database può contenere facoltativamente anche una cartella diff per il
file di backup differenziale.
Se utilizzi file di backup differenziali o completi a strisce, le rispettive cartelle full
o diff devono contenere una cartella aggiuntiva il cui nome è un timestamp Unix
in secondi.
Ad esempio, se utilizzi un singolo file di backup completo, inseriscilo direttamente nella
full cartella. La stessa regola si applica al file di backup differenziale:
Se utilizzi file di backup completo a strisce, utilizza una cartella aggiuntiva nella cartella full. La stessa regola si applica al file di backup differenziale:
In questi esempi, Database Migration Service crea due database nell'istanza Cloud SQL di destinazione: my-business-database e my-other-database.
Ogni database viene compilato con i dati estratti dalle singole cartelle full,
diff e log.
Puoi combinare le convenzioni per i file singoli o a strisce per i file di backup completi e differenziali. I file di backup differenziale sono facoltativi, quindi puoi anche lasciare vuota la cartella diff:
Inserisci il file di backup completo nella cartella full.
Inserisci il file di backup differenziale nella cartella diff.
Inserisci i file del log delle transazioni nella cartella log.
Assicurati che i file di backup completo, differenziale e dei log delle transazioni seguano le convenzioni di denominazione richieste da Database Migration Service. Consulta
Requisiti relativi alla denominazione dei file di backup.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-05 UTC."],[[["\u003cp\u003eDatabase Migration Service utilizes a Cloud Storage bucket to replicate data from SQL Server backup and transaction log files.\u003c/p\u003e\n"],["\u003cp\u003eThe storage bucket must reside in the same region as the Cloud SQL for SQL Server instance, and must contain a specific folder structure for each database being migrated.\u003c/p\u003e\n"],["\u003cp\u003eEach database folder should contain at least \u003ccode\u003efull\u003c/code\u003e and \u003ccode\u003elog\u003c/code\u003e folders for full and transaction log backups respectively, and optionally a \u003ccode\u003ediff\u003c/code\u003e folder for differential backups.\u003c/p\u003e\n"],["\u003cp\u003eStriped backup files require an additional folder within the \u003ccode\u003efull\u003c/code\u003e or \u003ccode\u003ediff\u003c/code\u003e folders, named as a Unix timestamp, to contain the individual stripe files.\u003c/p\u003e\n"],["\u003cp\u003eBackup files should be uploaded to their respective folders, and the database migration service will use the \u003ccode\u003efull\u003c/code\u003e, \u003ccode\u003ediff\u003c/code\u003e, and \u003ccode\u003elog\u003c/code\u003e folders to create and populate each database.\u003c/p\u003e\n"]]],[],null,["# Store backup files in a Cloud Storage bucket\n\nDatabase Migration Service replicates data from SQL Server backup and transaction\nlog files that you upload to a Cloud Storage bucket. This page describes\nhow to prepare your bucket for migration procedures, and what folder structure\nis required for Database Migration Service to recognize your backup files.\n\nTo prepare a storage bucket for migration, perform the following steps:\n\n1. [Create your bucket](/storage/docs/creating-buckets).\n Make sure you use the\n same region as the one where you intend to create your destination\n Cloud SQL for SQL Server instance.\n\n Database Migration Service is a fully-regional product, meaning that all entities\n related to your migration (source and destination connection profiles,\n migration jobs, destination databases, storage buckets for backup files)\n must be saved in a single region.\n2. [Create the folder structure](/storage/docs/objects#simulated-folders) to hold your backup files.\n\n - Database Migration Service expects a folder structure where every folder present at\n the bucket's root level represents one database to migrate.\n\n - The database folder at minimum must contain two folders: `full` for the full backup\n file, and `log` for transaction log\n backup files that you later upload for the incremental load phase.\n\n - The database folder can also optionally contain a `diff` folder for the\n differential backup file.\n\n - If you use striped full or differential backup files, their respective `full`\n or `diff` folders must contain an additional folder whose name is a Unix timestamp\n in seconds.\n\n For example, if you use a single full backup file, put it directly in the\n `full` folder. The same rule applies to the differential backup file: \n\n Cloud Storage bucket root/\n |- my-business-database/\n | |- full/\n | | |- full_backup_file\n | |- diff/\n | | |- diff_backup_file\n | |- log/\n | | |- transaction_log_file\n |- my-other-database/\n | |- full/\n | | |- full_backup_file\n | |- diff/\n | | |- diff_backup_file\n | |- log/\n | | |- transaction_log_file\n\n If you use striped full backup files, then use an additional folder in the `full`\n folder. The same rule applies to the differential backup file: \n\n Cloud Storage bucket root/\n |- my-business-database/\n | |- full/\n | | |- 1712649600/\n | | | |- my_full_backup_file_stripe1\n | | | |- my_full_backup_file_stripe2\n | |- diff/\n | | |- 1706967833/\n | | | |- firstDiffStripe.bak\n | | | |- other_diff_stripe.diff\n | |- log/\n | | |- transaction_log_file\n |- my-other-database/\n | |- full/\n | | |- 1715250742/\n | | | |- my_full_backup_file_stripe1\n | | | |- my_full_backup_file_stripe2\n | |- diff/\n | | |- 1706967833/\n | | | |- firstDiffStripe.bak\n | | | |- other_diff_stripe.diff\n | |- log/\n | | |- transaction_log_file\n\n In these examples, Database Migration Service creates two databases in your destination\n Cloud SQL instance: `my-business-database` and `my-other-database`.\n Each database is populated with data pulled from their individual `full`,\n `diff`, and `log` folders.\n\n You can mix the single file or striped file conventions for\n full and differential backup files. Differential backup files are optional,\n so you can also leave the `diff` folder empty: \n\n Cloud Storage bucket root/\n |- my-business-database/\n | |- full/\n | | |- full_backup_file\n | |- diff/\n | | |- 1706967833/\n | | | |- firstDiffStripe.bak\n | | | |- other_diff_stripe.diff\n | |- log/\n | | |- transaction_log_file\n |- my-other-database/\n | |- full/\n | | |- 1712649600/\n | | | |- my_full_backup_file_stripe1\n | | | |- my_full_backup_file_stripe2\n | |- diff/\n | | |- diff_backup_file\n | |- log/\n | | |- transaction_log_file\n |- third-database/\n | |- full/\n | | |- full_backup_file\n | |- log/\n | | |- transaction_log_file\n\n In this example, the `third-database` doesn't use a differential backup file\n for migration, so it doesn't have the `diff` folder.\n3. [Upload your backup files](/storage/docs/uploading-objects)\n to their respective folders:\n\n - Put the full backup file in the `full` folder.\n - Put the differential backup file in the `diff` folder.\n - Put the transaction log files in the `log` folder.\n\n | **Note:** You can upload the differential backup file at a later time - after you create the migration job, but before you start uploading transaction log files.\n\n Make sure your full backup, differential, and transaction log files follow the naming\n conventions required by Database Migration Service. See\n [Backup files naming requirements](/database-migration/docs/sqlserver/export-backup-files).\n\nWhat's next?\n------------\n\n- [Schedule regular transaction log transfers](/database-migration/docs/sqlserver/automate-backup-exports)."]]
