Can't restore from backup
R J
Posts: 12
Recently I have not been able to restore from our backup files which are about 685MB in size. I have a feeling the size is the problem, but not sure how to resolve it. I have searched the forums, but didn't find the same situation as mine, with a solution.
The backup is created on the server, then stored on a backup location. I am using my desktop system to restore the file. My desktop and the server are using SQLBackup 4.2
When I try to restore to my desktop, it runs for several hours and I finally just give up. I don't restore these files very often, but I believe in the past they usually have restored in about 45 minutes.
I tried installing the trial for SQLBackup 5 on another machine, and I tried restoring again. This time, I got the "VDI Error 1010: Failed to get confirmation from the server." message. It runs for quite a while before returning this message. And, yes, the permissions are fine and nobody else is using the database.
My backup application uses the following command to create the backup:
I saw some posts about MAXTRANSFERSIZE, but not sure how to use it. Any help would be appreciated. Currently, I am using native SQL backup which takes hours...
The backup is created on the server, then stored on a backup location. I am using my desktop system to restore the file. My desktop and the server are using SQLBackup 4.2
When I try to restore to my desktop, it runs for several hours and I finally just give up. I don't restore these files very often, but I believe in the past they usually have restored in about 45 minutes.
I tried installing the trial for SQLBackup 5 on another machine, and I tried restoring again. This time, I got the "VDI Error 1010: Failed to get confirmation from the server." message. It runs for quite a while before returning this message. And, yes, the permissions are fine and nobody else is using the database.
My backup application uses the following command to create the backup:
objCommand.CommandText = "master..sqlbackup N'-SQL ""BACKUP DATABASES [" & strDatabaseName & "] " & _ " TO DISK = ''" & strLocalBackupPath & "<AUTO>'' WITH NAME = ''<AUTO>'', " & _ " DESCRIPTION = ''<AUTO>'', PASSWORD = ''<ENCRYPTEDPASSWORD>" & strBackupPassword & "</ENCRYPTEDPASSWORD>'', " & _ " KEYSIZE = 128, ERASEFILES = 30, COMPRESSION = 3, THREADS = 1""'"
I saw some posts about MAXTRANSFERSIZE, but not sure how to use it. Any help would be appreciated. Currently, I am using native SQL backup which takes hours...
Comments
Thanks.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
Interesting, the error was:
File read error for 46800 bytes. Backup file is incomplete or corrupted.
Thanks.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
It happens with all of the new files. Anything older than a couple weeks ago seems to be fine. I have a feeling it is because of the size. I saw some people mention changing compression to 2 instead of 3 for large files. So, I might try that.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
11/3/2007 2:55:02 PM: SQL error 3013: RESTORE DATABASE is terminating abnormally.
11/3/2007 2:55:02 PM: SQL error 3101: Exclusive access could not be obtained because the database is in use.
---
The database was not in use. The error message is the same, even after rebooting, or when trying to restore to a brand new database. If I select an older file, I can restore with no problem.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
After the retry, it was successful.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
Is your situation now as follows:
- every backup that you have created for that database in the last 2 weeks cannot be restored on your workstation
- no errors were reported for the backups (error codes >= 500). Backups that suceeded on retries are ok.
Do you restore directly from the original backup file, or from a copy? If it is from a copy, could you please compare if the original and copy are identical (e.g. using a hash generator).
Would it also be possible to create the backups on another disk, to eliminate the possibility that it is a disk issue?
Thanks.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8