How can we help you today? How can we help you today?
bill.wehnert
I'm trying to backup a single database on my server (here's the command): master..sqlbackup N'-SQL "BACKUP DATABASE [LLReports] TO DISK = ''E:\Backups\MSSQL\FULL_(local)_LLReports_20070326_132632.sqb'' WITH NAME = ''<AUTO>'', DESCRIPTION = ''<AUTO>'', COMPRESSION = 1"' The SQL Server instance is running, the account I was logged in with as well as the account that the service uses are both Admin accounts. I've tried this about five times now and I get the same thing each time. I've seen a few posts that this may have to do with contiguous free memory and there not being enough of it. That doesn't sound like a good solution to me. This is a production server and It's under load at all times (yes I know I need more hardware - that isn't going to happen at the moment) - so this backup needs to run in the environment I have. A SQL Server backup ran just fine. I saw another request asking that SQL Backup be turned off for a week or so to see if that is the problem. That's a nice idea, but I'm dependent now on the compression and encryption I get from this product, I don't want to be without it for a week (I know - whine whine whine <G>). Here is the log file that was generated: SQL Backup log file 3/26/2007 1:47:57 PM: Backing up LLReports (full database) to: E:\Backups\MSSQL\FULL_(local)_LLReports_20070326_132632.sqb 3/26/2007 1:47:57 PM: BACKUP DATABASE [LLReports] TO DISK = 'E:\Backups\MSSQL\FULL_(local)_LLReports_20070326_132632.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', COMPRESSION = 1 3/26/2007 1:48:12 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.) 3/26/2007 1:48:12 PM: SQL error 3013: BACKUP DATABASE is terminating abnormally. 3/26/2007 1:48:12 PM: 3/26/2007 1:48:12 PM: Memory profile 3/26/2007 1:48:12 PM: Type Maximum Minimum Average Blk count Total 3/26/2007 1:48:12 PM: 3/26/2007 1:48:12 PM: Commit 891027456 4096 1704659 1053 1795006464 3/26/2007 1:48:12 PM: Reserve 1073676288 4096 6375593 181 1153982464 3/26/2007 1:48:12 PM: Free 164048896 4096 1163123 234 272171008 3/26/2007 1:48:12 PM: Private 1073676288 4096 4549053 639 2906845184 3/26/2007 1:48:12 PM: Mapped 1536000 4096 178806 52 9297920 3/26/2007 1:48:12 PM: Image 5808128 4096 60489 543 32845824 3/26/2007 1:48:12 PM: 3/26/2007 1:48:12 PM: Warning 300: Backup failed. Retry attempt: 1 3/26/2007 1:48:14 PM: BACKUP DATABASE [LLReports] TO DISK = 'E:\Backups\MSSQL\FULL_(local)_LLReports_20070326_132632.sqb' WITH NAME = 'Database (LLReports), 3/26/2007 1:47:57 PM', DESCRIPTION = 'Backup on 3/26/2007 1:47:57 PM Server: PULSITY-SQL1 Database: LLReports', INIT, COMPRESSION = 1 3/26/2007 1:48:29 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.) 3/26/2007 1:48:29 PM: SQL error 3013: BACKUP DATABASE is terminating abnormally. 3/26/2007 1:48:29 PM: 3/26/2007 1:48:30 PM: Memory profile 3/26/2007 1:48:30 PM: Type Maximum Minimum Average Blk count Total 3/26/2007 1:48:30 PM: 3/26/2007 1:48:30 PM: Commit 891027456 4096 1704659 1053 1795006464 3/26/2007 1:48:30 PM: Reserve 1073676288 4096 6375593 181 1153982464 3/26/2007 1:48:30 PM: Free 164048896 4096 1163123 234 272171008 3/26/2007 1:48:30 PM: Private 1073676288 4096 4549053 639 2906845184 3/26/2007 1:48:30 PM: Mapped 1536000 4096 178806 52 9297920 3/26/2007 1:48:30 PM: Image 5808128 4096 60489 543 32845824 3/26/2007 1:48:30 PM: 3/26/2007 1:48:30 PM: Warning 300: Backup failed. Retry attempt: 2 3/26/2007 1:48:32 PM: BACKUP DATABASE [LLReports] TO DISK = 'E:\Backups\MSSQL\FULL_(local)_LLReports_20070326_132632.sqb' WITH NAME = 'Database (LLReports), 3/26/2007 1:47:57 PM', DESCRIPTION = 'Backup on 3/26/2007 1:47:57 PM Server: PULSITY-SQL1 Database: LLReports', INIT, COMPRESSION = 1 3/26/2007 1:48:47 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.) 3/26/2007 1:48:47 PM: SQL error 3013: BACKUP DATABASE is terminating abnormally. 3/26/2007 1:48:47 PM: 3/26/2007 1:48:47 PM: Memory profile 3/26/2007 1:48:47 PM: Type Maximum Minimum Average Blk count Total 3/26/2007 1:48:47 PM: 3/26/2007 1:48:47 PM: Commit 891027456 4096 1699886 1056 1795080192 3/26/2007 1:48:47 PM: Reserve 1073676288 4096 6343061 182 1154437120 3/26/2007 1:48:47 PM: Free 164048896 4096 1170873 232 271642624 3/26/2007 1:48:47 PM: Private 1073676288 4096 4521576 643 2907373568 3/26/2007 1:48:47 PM: Mapped 1536000 4096 178806 52 9297920 3/26/2007 1:48:47 PM: Image 5808128 4096 60489 543 32845824 3/26/2007 1:48:47 PM: 3/26/2007 1:48:47 PM: Warning 300: Backup failed. Retry attempt: 3 3/26/2007 1:48:49 PM: BACKUP DATABASE [LLReports] TO DISK = 'E:\Backups\MSSQL\FULL_(local)_LLReports_20070326_132632.sqb' WITH NAME = 'Database (LLReports), 3/26/2007 1:47:57 PM', DESCRIPTION = 'Backup on 3/26/2007 1:47:57 PM Server: PULSITY-SQL1 Database: LLReports', INIT, COMPRESSION = 1 3/26/2007 1:49:04 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.) 3/26/2007 1:49:04 PM: SQL error 3013: BACKUP DATABASE is terminating abnormally. 3/26/2007 1:49:04 PM: 3/26/2007 1:49:05 PM: Memory profile 3/26/2007 1:49:05 PM: Type Maximum Minimum Average Blk count Total 3/26/2007 1:49:05 PM: 3/26/2007 1:49:05 PM: Commit 891027456 4096 1699886 1056 1795080192 3/26/2007 1:49:05 PM: Reserve 1073676288 4096 6343061 182 1154437120 3/26/2007 1:49:05 PM: Free 164048896 4096 1170873 232 271642624 3/26/2007 1:49:05 PM: Private 1073676288 4096 4521576 643 2907373568 3/26/2007 1:49:05 PM: Mapped 1536000 4096 178806 52 9297920 3/26/2007 1:49:05 PM: Image 5808128 4096 60489 543 32845824 3/26/2007 1:49:05 PM: 3/26/2007 1:49:05 PM: Warning 300: Backup failed. Retry attempt: 4 3/26/2007 1:49:07 PM: BACKUP DATABASE [LLReports] TO DISK = 'E:\Backups\MSSQL\FULL_(local)_LLReports_20070326_132632.sqb' WITH NAME = 'Database (LLReports), 3/26/2007 1:47:57 PM', DESCRIPTION = 'Backup on 3/26/2007 1:47:57 PM Server: PULSITY-SQL1 Database: LLReports', INIT, COMPRESSION = 1 3/26/2007 1:49:22 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.) 3/26/2007 1:49:22 PM: SQL error 3013: BACKUP DATABASE is terminating abnormally. 3/26/2007 1:49:22 PM: 3/26/2007 1:49:22 PM: Memory profile 3/26/2007 1:49:22 PM: Type Maximum Minimum Average Blk count Total 3/26/2007 1:49:22 PM: 3/26/2007 1:49:22 PM: Commit 891027456 4096 1696797 1058 1795211264 3/26/2007 1:49:22 PM: Reserve 1073676288 4096 6343061 182 1154437120 3/26/2007 1:49:22 PM: Free 164048896 4096 1170308 232 271511552 3/26/2007 1:49:22 PM: Private 1073676288 4096 4507759 645 2907504640 3/26/2007 1:49:22 PM: Mapped 1536000 4096 178806 52 9297920 3/26/2007 1:49:22 PM: Image 5808128 4096 60489 543 32845824 3/26/2007 1:49:22 PM: / comments
I'm trying to backup a single database on my server (here's the command): master..sqlbackup N'-SQL "BACKUP DATABASE [LLReports] TO DISK = ''E:\Backups\MSSQL\FULL_(local)_LLReports_20070326_132632....
0 votes
We are migrating to a scenario where we will have a "reporting/processing" database that will be on a different physical server. If we could specify LinkedServer.Database to be cached, that would be a bonus. / comments
We are migrating to a scenario where we will have a "reporting/processing" database that will be on a different physical server. If we could specify LinkedServer.Database to be cached, that would ...
0 votes
It took 1263.665 seconds to do the full restore, but it did finally work. I haven't tried the step recommended above to restore the header, that's not going to mess up my database - is it? If not, I'll test it to see what happens. [image] / comments
It took 1263.665 seconds to do the full restore, but it did finally work. I haven't tried the step recommended above to restore the header, that's not going to mess up my database - is it? If not, ...
0 votes
I had a backup failure with the same error codes the other day and looking at the log it said this: 9/8/2007 12:37:26 AM: Backing up MYDATABASE (full database) on PROD instance to: E:\Backups\MSSQL\MYDATABASE\FULL_PROD_MYDATABASE_20070908_003726.sqb 9/8/2007 12:37:26 AM: BACKUP DATABASE [MYDATABASE] TO DISK = 'E:\Backups\MSSQL\MYDATABASE\FULL_PR OD_MYDATABASE_20070908_003726.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', PASSWORD = 'XXXXXX XXXX', KEYSIZE = 256, ERASEFILES_ATSTART = 4, COMPRESSION = 3, THREADS = 1 9/8/2007 12:37:27 AM: Deleting old backup file: E:\Backups\MSSQL\MYDATABASE\FULL_PROD_MYDATABASE_2 0070903_002916.sqb 9/8/2007 1:36:23 AM: Thread 0 error: Error 620: Error writing to backup file(s). Process terminated unexpectedly. Error code: -2139684860 Thread 0 warning: Warning 210: Error writing to backup file: E:\Backups\MSSQL\MYDATABASE\FULL_PROD_MYDATABASE_20070 908_003726.sqb Warning: System error code: (Insufficient system resources exist to complete the requested service) 9/8/2007 1:36:23 AM: Server: Msg 3013 BACKUP DATABASE is terminating abnormally. 9/8/2007 1:36:23 AM: Server: Msg 3271 A nonrecoverable I/O error occurred on file "SQLBACKUP_1E4CD5EC-5A80-4ECC-961E-870A26F5860D:" 995(The I/O operation has been aborted because of either a thread exit or an application request.). 9/8/2007 1:36:23 AM: Server: Msg 3202 Write on "SQLBACKUP_1E4CD5EC-5A80-4ECC-961E-870A26F5860D" failed: 112(There is not enough space on the disk.) The error claims that I had insufficient disk space. But checking the drive, I had over 199gb of disk space free. The backup worked (at least according to the UI and I see a file there - it's 10gb (compressed/encrypted) and the other backups after it continued without a problem. I didn't look in the directory to see if it had actually deleted the old backup that supposedly failed above that day - so I don't know if it got deleted then or on the next backup cycle. Anyway - thought you would like to know that this happened. Using version 5.1.0.2781. / comments
I had a backup failure with the same error codes the other day and looking at the log it said this: 9/8/2007 12:37:26 AM: Backing up MYDATABASE (full database) on PROD instance to: E:\Backups\MSSQL...
0 votes
1. Dependency graph. A visual representation with a diagram showing all of the entities (color coded by type) that depend on this entity. 2. An Foreign Key graph that shows all related tables. Maybe with an arrow showing which way the dependency is going. 3. I'll also agree that I'd love to see the Diagrams be imported if possible. Don't know if SMO lets you export to an image via the API, but if you could embed that in the help file, that would be huge. I don't care right now if you made the diagram linkable (I click on a table - it takes me to that part of the help) -just having the diagram(s) would be a huge bonus I think. 4. Ability to add other types of data on a table. Basically the ability to create my own Extended properties - maybe define them at a project level and say that they are a Table/Field/Sproc/View/Function/etc property and then the editor would let me fill in the values at the appropriate spot. Even cooler would be to specify the data type and length so that you could have some mask fields available (say for capturing only a date, etc). 5. Ability to store all of the extended properties outside of the database so that if something were to happen and you had to rebuild your docs on a backup or on another server, you'd have all of your information available. This would be helpful too if while you are designing you would rather drop the table and rebuild it to put the fields in the order you want. It's a small thing, but would be helpful to me. / comments
1. Dependency graph. A visual representation with a diagram showing all of the entities (color coded by type) that depend on this entity. 2. An Foreign Key graph that shows all related tables. Ma...
0 votes