Comments
1 comment
-
Hi
Thank you for your forum post and sorry that you have encountered a problem.
The COPY TO process for T-Log Backup operates differently for the process used for Full and Differential backups.
When you perform a Full and Differential backup using the COPYTO keyword, if the backup task is successful the backup file is then copied to the location specified by the COPYTO keyword.
When you perform a T-Log backup using SQL Backup with the COPYTO keyword, on completion of a successful transaction log backup the backup file created is not copied immediately. An entry is placed into the Log Copy Queue and the SQL Backup Agent service copies the backup file created outside of the backup job. The Log Copy Queue has a retry schedule that takes place over a 24 hour period.
The first thing to check, is to ensure that the account given to the SQL Backup Agent service has Read, Write and execute permissions to the COPYTO location. Please run this query to confirm:USE master GO EXECUTE master..sqbutility 999, 'RWE', '<COPYTO location>' GO
If this is successful and the SQL Backup Agent service has read (R), write (W), and execute (E) permissions, the query will return: <SQBUTILITYRESULT>:1:
If there is a problem, the query will return a value of 0, followed by a message, for example:
<SQBUTILITYRESULT>:0:Folder does not exist :
<COPYTO location>
If the service does have permissions to the COPYTO location, using the SQL Backup GUI ->Select the Log Copy Queue Tab.
Are there entries indicating that there are backups files waiting to be copied? If the answer is yes, if you write click an entry does it indicate a reason for the copy failure?
Many Thanks
Eddie
Add comment
Please sign in to leave a comment.
Thansk