Comments
Sort by recent activity
J,
Both SQLBackup and any CLR routines use the SQL MemToLevae memory space. SQLBackup needs at least 7Mb of contiguous memory to run. If this space is limited then either SQLBackup may fail or your CLR routines get pushed out of the memory. In SQL2005 this memory is set to 256Mb. To increase it add the -g parameter to the startup of SQL.
We have had this problem so run with -g360 up to -g440 depending on how many database are getting backed up at the same time.
Chris / comments
J,
Both SQLBackup and any CLR routines use the SQL MemToLevae memory space. SQLBackup needs at least 7Mb of contiguous memory to run. If this space is limited then either SQLBackup may fail or your...
Troy,
SQLBackup uses the MemToLeave part of the SQL memory space. Unless you add the -g startup parameter at the startup SQL2005 allows 256Mb of MemToLeave memory. If you are running a number of SQLBackups at the same time and/or using the CLR then these processes all use the MemToLeave memory. We ran into this problem and had to add -g360 or -g400 to give SQLBackup 5.2/3 enough memory to run in.
Chris / comments
Troy,
SQLBackup uses the MemToLeave part of the SQL memory space. Unless you add the -g startup parameter at the startup SQL2005 allows 256Mb of MemToLeave memory. If you are running a number of SQ...
Brian,
We would do this one database at a time because we would want the dbid to stay the same as it was before we restore.
You confirmed why the restore problem so we will create scripts to do the restore after a delete from master.
Thanks
Chris / comments
Brian,
We would do this one database at a time because we would want the dbid to stay the same as it was before we restore.
You confirmed why the restore problem so we will create scripts to do the...
Brian,
Our experience was this.
We started SQL in single user mode and restored master.
We then restored msdb.
When we started SQL it had the application databases all marked as suspect because master knew about them but the database files did not exist.
We tried to use the SQLBackup GUI to restore them from the backup saying Existing and it errored with file in accessible
We tried to use the SQLBackup GUI to restore them from the backup saying New and it errored with database already exists.
This means that SQLBackup read master so it thought the actual database existed but the files were not there.
We eventually had to delete the database so master had no information on it and then restore saying New.
Chris / comments
Brian,
Our experience was this.
We started SQL in single user mode and restored master.
We then restored msdb.
When we started SQL it had the application databases all marked as suspect because mas...
Brian,
We don't use SQLBackup for our system databases only our applications ones. This is why the master knows about the application DB's bu they come up suspect as the database files don't exist.
Thanks
Chris / comments
Brian,
We don't use SQLBackup for our system databases only our applications ones. This is why the master knows about the application DB's bu they come up suspect as the database files don't exist....
I have more info now.
Because the database was defined in master it could not be added as new or replace using the GUI. We deleted the database from master and then added it as a new database. This was the only way to restore from the RedGate backup.
Chris / comments
I have more info now.
Because the database was defined in master it could not be added as new or replace using the GUI. We deleted the database from master and then added it as a new database. This...
Petey,
Seems this was the end result from a lack of memory to run SQLBackup. I am increasing the MemToLeave memory to cope with this.
Thanks
Chris / comments
Petey,
Seems this was the end result from a lack of memory to run SQLBackup. I am increasing the MemToLeave memory to cope with this.
Thanks
Chris
Thanks Petey.
I am running some test with THREADCOUNT of greater than 1, we have servers with multiple CPU's and THREADPRIORITY = 1 to reduce the need for wanted CPU. This is working well on a lightly used server.
Thanks
Chris / comments
Thanks Petey.
I am running some test with THREADCOUNT of greater than 1, we have servers with multiple CPU's and THREADPRIORITY = 1 to reduce the need for wanted CPU. This is working well on a ligh...
Petey,
What is the THREADPRIORITY default value? I created the backup jobs using the GUI so I had not entered any THREADPRIORITY value.
Thanks
Chris / comments
Petey,
What is the THREADPRIORITY default value? I created the backup jobs using the GUI so I had not entered any THREADPRIORITY value.
Thanks
Chris
Thanks Brian. As I mentioned I have had to use this with SQL2005 because of a number of CLR processes also using the same memory.
I did look in the Redgate log and I see no entries when the failures happened. I will monitor the jobs on the server to see if it happens again.
Chris / comments
Thanks Brian. As I mentioned I have had to use this with SQL2005 because of a number of CLR processes also using the same memory.
I did look in the Redgate log and I see no entries when the failure...