데이터베이스 마이그레이션 서비스는 Cloud Storage 버킷에 업로드하는 SQL Server 백업 및 트랜잭션 로그 파일의 데이터를 복제합니다. 이 페이지에서는 마이그레이션 절차를 위해 버킷을 준비하는 방법과 데이터베이스 마이그레이션 서비스에서 백업 파일을 인식하는 데 필요한 폴더 구조를 설명합니다.
마이그레이션을 위해 저장소 버킷을 준비하려면 다음 단계를 따르세요.
버킷 만들기
대상 SQL Server용 Cloud SQL 인스턴스를 만들 리전과 동일한 리전을 사용해야 합니다.
Database Migration Service는 완전히 지역별 제품이므로 마이그레이션과 관련된 모든 항목 (소스 및 대상 연결 프로필, 마이그레이션 작업, 대상 데이터베이스, 백업 파일의 스토리지 버킷)을 단일 리전에 저장해야 합니다.
이 예시에서 Database Migration Service는 대상 Cloud SQL 인스턴스에 my-business-database 및 my-other-database라는 두 데이터베이스를 만듭니다.
각 데이터베이스는 개별 full, diff, log 폴더에서 가져온 데이터로 채워집니다.
전체 백업 파일과 차등 백업 파일의 단일 파일 또는 스트라이프된 파일 규칙을 혼합할 수 있습니다. 차등 백업 파일은 선택사항이므로 diff 폴더를 비워 두어도 됩니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 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)."]]
