How can we help you today? How can we help you today?
guant
Activity overview Badges (0) Posts (3) Comments (8)

Activity overview

Latest activity by guant

interesting, we do not get these memory errors when running sql native backups / comments
  1. Community
  2. SQL Backup Previous Versions
  3. VDI error 1010
interesting, we do not get these memory errors when running sql native backups
0 votes
My question is that even with these memory warnings I'm I at any risk of getting bad backups/restores? / comments
  1. Community
  2. SQL Backup Previous Versions
  3. VDI error 1010
My question is that even with these memory warnings I'm I at any risk of getting bad backups/restores?
0 votes
Thank you for the information, we are running sql 2000 enterprise, if we arent ready to upgrade to sql 2005/2008 at this point. We will have a probably with these memory warnings? Will it affect our backups/restores? Even know they say they completed with warnings. This is the log from a backup: PHIF04V\IFORCE01: Backup - Successful ===================================== Performing full backups - Successful This operation completed with warnings. Backing up CDB_Model (full database) on IFORCE01 instance to: \\phif14\daily full\CDB_Model\20090716\FULL_CDB_Model_20090716_1036.sqb VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed. SQL Backup required 12,582,912 bytes of free SQL Server memory, which was not available. You can reduce the memory requirements by reducing the number of threads used in the backup. VDI error: An abort request is preventing anything except termination actions. SQL error 3013: BACKUP DATABASE is terminating abnormally. Memory profile Type Maximum Minimum Average Blk count Total Commit 266199040 4096 48739 23031 1122521088 Reserve 15728640 4096 148616 21175 3146956800 Free 1478656 4096 97409 261 25423872 Private 266199040 4096 96590 43512 4202856448 Mapped 1585152 4096 138208 66 9121792 Image 7581696 4096 91559 628 57499648 Warning 300: Backup failed. Retry attempt: 1 VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed. SQL Backup required 6,291,456 bytes of free SQL Server memory, which was not available. You can reduce the memory requirements by reducing the number of threads used in the backup. VDI error: An abort request is preventing anything except termination actions. SQL error 3013: BACKUP DATABASE is terminating abnormally. Memory profile Type Maximum Minimum Average Blk count Total Commit 266199040 4096 49090 23044 1131245568 Reserve 15728640 4096 148172 21185 3139031040 Free 1478656 4096 95446 258 24625152 Private 266199040 4096 96558 43535 4203655168 Mapped 1585152 4096 138208 66 9121792 Image 7581696 4096 91559 628 57499648 Warning 300: Backup failed. Retry attempt: 2 VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed. SQL Backup required 3,145,728 bytes of free SQL Server memory, which was not available. You can reduce the memory requirements by reducing the number of threads used in the backup. VDI error: An abort request is preventing anything except termination actions. SQL error 3013: BACKUP DATABASE is terminating abnormally. Memory profile Type Maximum Minimum Average Blk count Total Commit 266199040 4096 49451 23155 1145053184 Reserve 15728640 4096 146751 21296 3125223424 Free 1478656 4096 95446 258 24625152 Private 266199040 4096 96068 43757 4203655168 Mapped 1585152 4096 138208 66 9121792 Image 7581696 4096 91559 628 57499648 Warning 300: Backup failed. Retry attempt: 3 VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed. SQL Backup required 1,572,864 bytes of free SQL Server memory, which was not available. You can reduce the memory requirements by reducing the number of threads used in the backup. VDI error: An abort request is preventing anything except termination actions. SQL error 3013: BACKUP DATABASE is terminating abnormally. Memory profile Type Maximum Minimum Average Blk count Total Commit 266199040 4096 49498 23193 1148026880 Reserve 15728640 4096 146363 21333 3122380800 Free 1478656 4096 94938 258 24494080 Private 266199040 4096 95905 43831 4203655168 Mapped 1585152 4096 138102 67 9252864 Image 7581696 4096 91559 628 57499648 Warning 300: Backup failed. Retry attempt: 4 Database size : 334.500 MB Compressed data size: 40.356 MB Compression rate : 87.94% Processed 18736 pages for database 'CDB_Model', file 'CDB_Model_Data' on file 1. Processed 1 pages for database 'CDB_Model', file 'CDB_Model_Log' on file 1. BACKUP DATABASE successfully processed 18737 pages in 3.502 seconds (43.828 MB/sec). Verifying files: \\phif14\daily full\CDB_Model\20090716\FULL_CDB_Model_20090716_1036.sqb The backup set is valid. SQL Backup exit code: 300 Updating SQL Server information - Successful This operation completed successfully. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. VDI error 1010
Thank you for the information, we are running sql 2000 enterprise, if we arent ready to upgrade to sql 2005/2008 at this point. We will have a probably with these memory warnings? Will it affect ...
0 votes
Commit 4096 266199040 48229 23206 1119211520 Reserve 4096 15728640 147827 21325 3152416768 Free 4096 786432 88157 264 23273472 Private 4096 266199040 95899 43833 4203556864 Mapped 4096 1585152 151025 70 10571776 Image 4096 7581696 91559 628 57499648 / comments
  1. Community
  2. SQL Backup Previous Versions
  3. VDI error 1010
Commit 4096 266199040 48229 23206 1119211520 Reserve 4096 15728640 147827 21325 3152416768 Free 4096 786432 88157 264 23273472 Private 4096 266199040 95899 43833 4203556864 Mapped 4096 1585152 1510...
0 votes
When we get this warning, it still will backup successfully and we are able to restore the database, is there any risk of just ignoring this warning? / comments
  1. Community
  2. SQL Backup Previous Versions
  3. VDI error 1010
When we get this warning, it still will backup successfully and we are able to restore the database, is there any risk of just ignoring this warning?
0 votes
the sql server has 32gb of memory, and is currently set to use 12gb / comments
  1. Community
  2. SQL Backup Previous Versions
  3. VDI error 1010
the sql server has 32gb of memory, and is currently set to use 12gb
0 votes
Native SQL Backups & RedGate Backups
  1. Community
  2. SQL Backup Previous Versions
Were planning on switching over all of our sql backups to redgate, but in the meantime were testing both first to make sure we want to purchase. Is it ok to run both sql and redgate backups or wil...
2 followers 3 comments 0 votes
Would this be the memory on the database server itself? I have a separate machine with sqlbackup installed that is performing the backups, would this be the machine that would need the extra memory? Our database server has 36gb of memory and the machine running sqlbackup has 8gb. Thanks, / comments
  1. Community
  2. SQL Backup Previous Versions
  3. VDI error 1010
Would this be the memory on the database server itself? I have a separate machine with sqlbackup installed that is performing the backups, would this be the machine that would need the extra memor...
0 votes
Thank you! That did the trick!! / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Backup Folder
Thank you! That did the trick!!
0 votes
VDI error 1010
  1. Community
  2. SQL Backup Previous Versions
I keep getting this error when running backups, the job finishes and appears to have backed up, anyone know what I need to do to get rid of this warning?? Thank you! VDI error 1010: Failed to get ...
5 followers 18 comments 0 votes
Total activity
13
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
2