The Migration errors says ...
"Full backup can not be found."
Can this be a problem?
All Backups in the Azure Blob are encrypted during backup.
And the whitepaper has no restriction for this!
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
we are in a process to migrate a OnPremise SQL Server 2019 with Azure SQLData Studio.
I have a default database "AdventureWorks2019" with a Full and Log Backup into a Azure Storage Blob.
Backup of the database is fine, backup is encrypted.
With the help of Azure SQL Data Studio, i could create a Migration with all information required.
All preflight checks are fine, i can select the storage account, the blob and the container with the backup files.
Data Migrations starts and after a few minutes it´s stalled.
The state is Restoring (1 warninig), Duration is at 2.5hrs now.
The only warnings i see in the logs and in the Developer Ext. Log Files is this ...
main.log
[2023-03-27 16:26:46.207] [main] [info] update#setState idle
[2023-03-27 16:26:46.218] [main] [info] ExtensionHostStarterWorker created
[2023-03-27 16:26:48.994] [main] [info] Starting extension host with pid 2472 (fork() took 134 ms).
[2023-03-27 16:26:48.994] [main] [info] ExtensionHostStarterWorker.start() took 136 ms.
[2023-03-27 16:26:53.182] [main] [info] Enabling inspect port on extension host with pid 2472.
[2023-03-27 16:26:53.930] [main] [info] update#setState checking for updates
[2023-03-27 16:26:54.096] [main] [info] update#setState idle
[2023-03-27 16:26:56.079] [main] [info] Enabling inspect port on extension host with pid 2472.
[2023-03-27 16:27:16.209] [main] [info] update#setState checking for updates
[2023-03-27 16:27:16.376] [main] [info] update#setState idle
sharedprocess
[2023-03-27 16:26:49.758] [sharedprocess] [info] Starting worker process with pid 15952 (type: fileWatcher, window: 1).
[2023-03-27 16:26:49.968] [sharedprocess] [info] WSL is not installed, so could not detect WSL profiles
renderer1
[2023-03-27 16:26:48.856] [renderer1] [error] An unknown error occurred. Please consult the log for more details.
[2023-03-27 16:27:14.119] [renderer1] [info] Creating new connection connection:providerName:MSSQL|applicationName:azdata|authenticationType:Integrated|database:|server:SQL01|user:|group:
[2023-03-27 16:27:14.119] [renderer1] [info] Adding connection connection:providerName:MSSQL|applicationName:azdata|authenticationType:Integrated|database:|server:SQL01|user:|group:
[2023-03-27 16:27:14.119] [renderer1] [info] Successfully added connection connection:providerName:MSSQL|applicationName:azdata|authenticationType:Integrated|database:|server:SQL01|user:|group:
[2023-03-27 16:27:15.156] [renderer1] [info] Adding connection with DB name connection:providerName:MSSQL|applicationName:azdata|authenticationType:Integrated|database:master|server:SQL01|user:|group:
[2023-03-27 16:27:15.207] [renderer1] [info] Creating new connection dashboard:providerName:MSSQL|applicationName:azdata|authenticationType:Integrated|database:master|server:SQL01|user:|group:
[2023-03-27 16:27:15.208] [renderer1] [info] Adding connection dashboard:providerName:MSSQL|applicationName:azdata|authenticationType:Integrated|database:master|server:SQL01|user:|group:
[2023-03-27 16:27:15.208] [renderer1] [info] Successfully added connection dashboard:providerName:MSSQL|applicationName:azdata|authenticationType:Integrated|database:master|server:SQL01|user:|group:
[2023-03-27 16:27:15.541] [renderer1] [info] Creating new connection dashboard:providerName:MSSQL|applicationName:azdata|authenticationType:Integrated|database:master|server:SQL01|user:|databaseDisplayName:master|group:
[2023-03-27 16:27:15.541] [renderer1] [info] Adding connection dashboard:providerName:MSSQL|applicationName:azdata|authenticationType:Integrated|database:master|server:SQL01|user:|databaseDisplayName:master|group:
[2023-03-27 16:27:15.541] [renderer1] [info] Successfully added connection dashboard:providerName:MSSQL|applicationName:azdata|authenticationType:Integrated|database:master|server:SQL01|user:|databaseDisplayName:master|group:
[2023-03-27 16:27:38.031] [renderer1] [error] An unknown error occurred. Please consult the log for more details.
[2023-03-27 16:27:40.134] [renderer1] [error] An unknown error occurred. Please consult the log for more details.
Where is this log File?
Please consult the log for more details.
All other logs under
AppData\Roaming\azuredatastudio\logs\20230327T162645
have a file size of Zero
The Migration errors says ...
"Full backup can not be found."
Can this be a problem?
All Backups in the Azure Blob are encrypted during backup.
And the whitepaper has no restriction for this!
Thanks for sharing an error, @Jürgen Barth
I also encountered a similar error.
Please make sure below point during the migration.
If migrating multiple databases using the same Azure Blob Storage container, you must place backup files for different databases in separate folders inside the container.
Here are the limitations for migrating in Azure Data Studio
Thank you.
I tried with seperate folders and no encryption, but it still fails.
I need to do some more testing.