Comments
Sort by recent activity
I have this error in there:
SQL Backup log file
11/8/2006 7:15:01 PM: Backing up Command (transaction log) to:
\\192.168.11.30\backups\DB4\Command\Log\LOG_(local)_Command_20061108_191501.sqb
11/8/2006 7:15:01 PM: BACKUP LOG [Command] TO DISK = '\\192.168.11.30\backups\DB4\Command\Log\LOG_(local)_Command_20061108_191501.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', COPYTO = '\\Dc1\logshipping\Command', COMPRESSION = 1, THREADS = 1
11/8/2006 7:15:01 PM: Error 510: Backup file exists. Will not overwrite. File name: (\\192.168.11.30\backups\DB4\Command\Log\LOG_(local)_Command_20061108_191501.sqb)
and this:
SQL Backup log file
11/8/2006 8:15:01 PM: Backing up Command (transaction log) to:
\\192.168.11.30\backups\DB4\Command\Log\LOG_(local)_Command_20061108_201501.sqb
11/8/2006 8:15:01 PM: BACKUP LOG [Command] TO DISK = '\\192.168.11.30\backups\DB4\Command\Log\LOG_(local)_Command_20061108_201501.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', COPYTO = '\\Dc1\logshipping\Command', COMPRESSION = 1, THREADS = 1
11/8/2006 8:15:01 PM: Error 510: Backup file exists. Will not overwrite. File name: (\\192.168.11.30\backups\DB4\Command\Log\LOG_(local)_Command_20061108_201501.sqb)
and it continues with that... / comments
I have this error in there:
SQL Backup log file
11/8/2006 7:15:01 PM: Backing up Command (transaction log) to:
\\192.168.11.30\backups\DB4\Command\Log\LOG_(local)_Command_20061108_191501.sqb
11/8/2...
It wasnt in there, but it was in the directory that the logs should be backing up to then copying across. It had 3 small failed log files (~5kb) then it got a bigger one. I copied all 4 across and reran the job and it was sucessfull. This is why its failing. Should I slow down the log backups or could this be another problem?
Thanks / comments
It wasnt in there, but it was in the directory that the logs should be backing up to then copying across. It had 3 small failed log files (~5kb) then it got a bigger one. I copied all 4 across an...
I'll check tomorrow if it happens again.
Thanks / comments
I'll check tomorrow if it happens again.
Thanks
Thanks for the reply.
Now it seems like everynight it fails from an error that says the log file is to late for the restore, and I copy one log file previous back into the shared folder and rerun the job successfully.
Is it moving the file even if it fails, or is it somehow not copying the file over at all and causing the failure. If its not copying the file over, how do I determine if it isnt and setting it to try again? I have both jobs set to try 4 times before failing.
Am I running the log shipping too much by shipping it every 15 minutes and restoring it every hour? Would it be better to slow it down (the db is about 30gbs big and grows rapidly) / comments
Thanks for the reply.
Now it seems like everynight it fails from an error that says the log file is to late for the restore, and I copy one log file previous back into the shared folder and rerun t...