Comments
Sort by recent activity
Now try the restore again using the GUI.
These should all be running with the account that runs SQLBackup so it doesn't look like a permissions issue.
I am leaving now so I look forward to reading this thread on Monday.
Chris / comments
Now try the restore again using the GUI.
These should all be running with the account that runs SQLBackup so it doesn't look like a permissions issue.
I am leaving now so I look forward to reading ...
Just a thought.
If MyDB2 seems recovered then run DBCC CHECKDB with PHYSICAL_ONLY then try using the GUI to take a LOG backup to see that you have the permissions correct.
Chris / comments
Just a thought.
If MyDB2 seems recovered then run DBCC CHECKDB with PHYSICAL_ONLY then try using the GUI to take a LOG backup to see that you have the permissions correct.
Chris
That was for two databases in one execution.
Chris / comments
That was for two databases in one execution.
Chris
I hope that wasn't a typo but it should be BACKUP LOG not BACKUP LOGS.
Chris / comments
I hope that wasn't a typo but it should be BACKUP LOG not BACKUP LOGS.
Chris
Try running a log backup on MyDB2 before you try the restore.
Chris / comments
Try running a log backup on MyDB2 before you try the restore.
Chris
Try replacing the MyDB2 rather than just restoring to it. As it exists there could be a taillog that would need to be offloaded first.
The other option is to take a log backup of MyDB2 before you try and replace it.
HTH
Chris / comments
Try replacing the MyDB2 rather than just restoring to it. As it exists there could be a taillog that would need to be offloaded first.
The other option is to take a log backup of MyDB2 before you t...
JoshDBGuy,
We have used SQLBackup for a number of years but don't use the DISCONNECT_EXISTING because it might take longer than 20 seconds to rollbackup any active transactions. We try an ALTER DATABASE xxxx SET SINGLE_USER with ROLLBACK IMMEDIATE and wait for this to finish. Most servers now run with multiple CPU's but rollback is single threaded. So if you try and rollback a transaction that has run for 5 minutes on say 4 CPU's in parallel it could take 20 minutes to rollback.
My 2 cents
Chris / comments
JoshDBGuy,
We have used SQLBackup for a number of years but don't use the DISCONNECT_EXISTING because it might take longer than 20 seconds to rollbackup any active transactions. We try an ALTER DAT...
Actually just had this problem happen. My alter database set single_user had not finished in over 6 minutes so I cancelled it and tried it again. I am not sure what was holding the database but it can take time under some circumstances.
Chris / comments
Actually just had this problem happen. My alter database set single_user had not finished in over 6 minutes so I cancelled it and tried it again. I am not sure what was holding the database but it ...
Pete,
You meant that SQLBackup will wait up to 30 seconds for a response to the initialization request as a lot of my backups taken less than that amount of time to run (Logs mostly) and I have a delay of 8 seconds (VERIFYINTERVAL) to make sure that the verify part does not get caught by buffer to disk cache type activity.
Chris / comments
Pete,
You meant that SQLBackup will wait up to 30 seconds for a response to the initialization request as a lot of my backups taken less than that amount of time to run (Logs mostly) and I have a d...
Pete,
Your note had said 'It then waits 30 seconds for SQL Server to respond' when it could wait for up to a maximum of 30 seconds as this is the default for DISKRETRYINTERVAL. I am not trying to be pickey.
Chris / comments
Pete,
Your note had said 'It then waits 30 seconds for SQL Server to respond' when it could wait for up to a maximum of 30 seconds as this is the default for DISKRETRYINTERVAL. I am not trying to b...