Activity overview
Latest activity by Bryant
Use orginal paths in "Filegroups and Files" Restore GUI
When I use the SQL Backup 5.x Restore Wizard, the Filegroups and files section of step 2 appears to set the paths to whatever is in the Database Data/Log paths set on the server. It would be nice t...
I can confirm that defragmenting the hard drive that contains the cache files takes care of the SQL Backup 5 startup performance issue I was having. SQL Backup appeared having trouble connecting to servers and gathering information this morning so I closed SQL Backup and ran my defrag utility. Once it finished, I opened SQL Backup and it's working fine now.
It sounds like the caching algorithms do not tolerate disk fragmentation very well. To be honest, I am not really interested in looking back much more than a few hours (maybe 12) unless I need to do a restore. Perhaps there needs to be an option that allows the user to specify the time period to keep the cached data around and have any older data purged. / comments
I can confirm that defragmenting the hard drive that contains the cache files takes care of the SQL Backup 5 startup performance issue I was having. SQL Backup appeared having trouble connecting to...
I ran into this problem at the beginning of the week and followed the advice to clear out the SQL Backup cache files. They were using over 480 MB before I deleted them all. However, even after deleting them SQL Backup was bogging my PC down with high CPU utilization and a bit more memory usage than I would like. It just so happens that I did this yesterday and I start my disk defrag utility before I leave work (almost) every Thursday. When I came in this morning and the drives had been defragged, SQL Backup was back to it's normal behavior without taxing the CPU and memory reserves.
I don't know if that helps anyone very much. If I have the problem again I will try defragging before I delete the cache files to see if that helps. / comments
I ran into this problem at the beginning of the week and followed the advice to clear out the SQL Backup cache files. They were using over 480 MB before I deleted them all. However, even after dele...
Thanks, I wasn't aware of that but I will remember it now! / comments
Thanks, I wasn't aware of that but I will remember it now!
Suggestion: SQB Service Management in GUI
I had a problem this morning with the GUI not being able to connect to one of my servers that is running SQL Backup 5.2. I was able to connect with SQL Management Studio but not with the SQL Backup...
That will do just fine. / comments
That will do just fine.
Import/Export Server List
Is there any way to conveniently import/export the server listing in SQL Backup 5? I would like to keep my laptop in sync with my desktop computer for when I am not in the office and need to check ...
It's back again this morning. It's creating a backup file but fails and leaves the file corrupt when run from a job or from the SQL Backup GUI. Running the backup manually (using the command above) creates a good backup.
This is only occurring on the master database. / comments
It's back again this morning. It's creating a backup file but fails and leaves the file corrupt when run from a job or from the SQL Backup GUI. Running the backup manually (using the command above)...
Running the backup manually (like below) cleared up the previous issue but I seem to have run into another problem with the SQL Backup Repository. This time I got a Warning 210 (error writing to backup file/System Error (the parameter is incorrect) with an Error 620 whenever the master database (and only the master db) was backed up via a job or through the SQL Backup GUI. Running the following backup statement via Management Studio (connected to a SQL 2000 instance) cleared up the problem again. EXEC master..sqlbackup '-sql "BACKUP DATABASE master TO DISK = [E:\Data\MSSQL\Backup\master.sqb] WITH INIT"'
Any idea what might be causing this? I will send Pete a debug file after I submit this post to see what you can make of it. This server is getting old but we won't have everything moved to new equipment until at least April so I would like to see what can be done to prevent these issues in the future. I am wide open to the possibility that there is something goofy on this server and I can provide detailed server information to Red Gate support. / comments
Running the backup manually (like below) cleared up the previous issue but I seem to have run into another problem with the SQL Backup Repository. This time I got a Warning 210 (error writing to ba...
Warning 166: Failed to delete old entries in local history
Yesterday afternoon my transaction log backup jobs started failing with the following message:
8/9/2007 8:03:41 AM: Warning 166: Failed to delete old entries in local history tables: Error running...