Comments
Sort by recent activity
I wrote something to run native SQL backup then zip and ftp the file. That works, it just takes longer. I have been swamped with other things, so I will do some testing later. I read in some other threads where it was suggested to try setting the compression to 2, but I have not tried that yet. / comments
I wrote something to run native SQL backup then zip and ftp the file. That works, it just takes longer. I have been swamped with other things, so I will do some testing later. I read in some other ...
It looks like sometimes it gets an error, but it retries then everything is successful. On the 3rd, which is when the fiile I was working with was created, there were no errors in the log. On the 4th, there was an error: 11/4/2007 4:00:15 AM: VDI error 1010: Failed to get configuration from server. Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator server role. Error code: (-2139684861: The api was waiting and the timeout interval had elapsed.)
11/4/2007 4:05:46 AM: SQL error 3013: BACKUP DATABASE is terminating abnormally.
11/4/2007 4:05:46 AM:
11/4/2007 4:05:46 AM: Memory profile
11/4/2007 4:05:46 AM: Type Maximum Minimum Average Blk count Total
11/4/2007 4:05:46 AM: ---------------- ----------- ----------- ----------- ----------- -----------
11/4/2007 4:05:46 AM: Commit 657653760 4096 2275445 787 1790775296
11/4/2007 4:05:46 AM: Reserve 1028096 4096 341584 147 50212864
11/4/2007 4:05:46 AM: Free 161755136 4096 2070472 148 306429952
11/4/2007 4:05:46 AM: Private 657653760 4096 3524985 510 1797742592
11/4/2007 4:05:46 AM: Mapped 1060864 4096 132585 46 6098944
11/4/2007 4:05:46 AM: Image 6156288 4096 98271 378 37146624
11/4/2007 4:05:46 AM:
11/4/2007 4:05:46 AM: Warning 300: Backup failed. Retry attempt: 1
After the retry, it was successful. / comments
It looks like sometimes it gets an error, but it retries then everything is successful. On the 3rd, which is when the fiile I was working with was created, there were no errors in the log. On the 4...
685MB. However, allowing others to access the data is basically impossible because of the type of data we're storing. / comments
685MB. However, allowing others to access the data is basically impossible because of the type of data we're storing.
11/3/2007 2:54:57 PM: VDI error 1010: Failed to get configuration from server. Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator server role. Error code: (-2139684861: The api was waiting and the timeout interval had elapsed.)
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. / comments
11/3/2007 2:54:57 PM: VDI error 1010: Failed to get configuration from server. Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator server role. E...
I believe it's towards the end, but can't be sure. Since the file is large, everything takes a while, so I don't sit and watch it the whole time.
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. / comments
I believe it's towards the end, but can't be sure. Since the file is large, everything takes a while, so I don't sit and watch it the whole time.
It happens with all of the new files. Anything olde...
Thanks for the response.
Interesting, the error was:
File read error for 46800 bytes. Backup file is incomplete or corrupted. / comments
Thanks for the response.
Interesting, the error was:
File read error for 46800 bytes. Backup file is incomplete or corrupted.