Activity overview
Latest activity by kmadsen
Intermittant Transaction Log Backup Failures
I get intermittant backup failures when trying to backup the transaction logs. the following is the error a typical error in the SQL Errorlog.
BackupVirtualDeviceSet::Initialize: Open failure on ba...
SQL Server Hardware Upgrade
I wil lbe upgrading the hardware on one of my production SQL Servers soon that has SQL BAckup installed and need to know what steps I need to take to move the license/activation from the old hardwa...
I deleted 12K+ of the log files and now it runs much faster. Is there ever going to be an option to delete older log files like the erase files option? / comments
I deleted 12K+ of the log files and now it runs much faster. Is there ever going to be an option to delete older log files like the erase files option?
No significant change in backup time without the logto option. One thing I have seen while manualy running them is I get the following rowcounts back after the backup log successfull message...
1 row effected
9 rows affected
12829 rows affected (This number keeps increasing) / comments
No significant change in backup time without the logto option. One thing I have seen while manualy running them is I get the following rowcounts back after the backup log successfull message...
1 r...
Yes these are the timestamps as recorded on the remote machines. I did sync times on the two machines just before executing the backups to ensure that we were working off a common clock. I will be running without the logto option shortly. / comments
Yes these are the timestamps as recorded on the remote machines. I did sync times on the two machines just before executing the backups to ensure that we were working off a common clock. I will be ...
In my case I am seeing approx a 2 minute difference between the log reported time and the actual amount of time. My currently group of regular transaction log backups is taking 20-25 minutes using SQLBackup while native it is in the 2-5 minute range.
What is the next step for correcting this? / comments
In my case I am seeing approx a 2 minute difference between the log reported time and the actual amount of time. My currently group of regular transaction log backups is taking 20-25 minutes using ...
The log states the backup takes 3 seconds, while actually timing the backup it takes 2-3 minutes. I am willing to try backing up localy, but that is not a fix for this issue. / comments
The log states the backup takes 3 seconds, while actually timing the backup it takes 2-3 minutes. I am willing to try backing up localy, but that is not a fix for this issue.
So what is the next step for solving this? Native backups to network shares don't have this issue. In fact native transaction log backups currently complete 2x-3x faster than compressed ones.
FYI - Server is a quad 1.4Ghz with an average CPU utilization while backups are occuring of 15-30%. / comments
So what is the next step for solving this? Native backups to network shares don't have this issue. In fact native transaction log backups currently complete 2x-3x faster than compressed ones.
FYI -...