How can we help you today? How can we help you today?
meastland
Activity overview Badges (0) Posts (10) Comments (27)

Comments

Sort by recent activity
Peter - Are there any plans to include an option in a future release to force the removal of a source file even if the destination file already exists in a MOVETO configuration? / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Warning 130: MOVETO error: Failed to move file
Peter - Are there any plans to include an option in a future release to force the removal of a source file even if the destination file already exists in a MOVETO configuration?
0 votes
I have yet to hear back on this. Since I have a support contract, would I be better served by opening a formal ticket? / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Missing functionality - RESTORE LOG...WITH MOVE
I have yet to hear back on this. Since I have a support contract, would I be better served by opening a formal ticket?
0 votes
Chris - Any update on this? Can we expect the functionality to be included in 7.3? I am still running on version 6.5 and will likely wait for this to be addressed before upgraded to 7.x. Thanks in advance. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Missing functionality - RESTORE LOG...WITH MOVE
Chris - Any update on this? Can we expect the functionality to be included in 7.3? I am still running on version 6.5 and will likely wait for this to be addressed before upgraded to 7.x. Thanks ...
0 votes
Peter, Thanks for the quick response. Is it possible to be notified when the fix is available? Thanks, -Mike / comments
  1. Community
  2. SQL Backup Previous Versions
  3. High CPU on VERIFY
Peter, Thanks for the quick response. Is it possible to be notified when the fix is available? Thanks, -Mike
0 votes
Thanks, Peter. I will deploy and test the patch as time permits. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. High CPU on VERIFY
Thanks, Peter. I will deploy and test the patch as time permits.
0 votes
Petey, Thanks for the quick response. Are there any plans to allow this error to be skipped without requiring the MOVETO parameter? Thanks, -Mike / comments
  1. Community
  2. SQL Backup Previous Versions
  3. MOVETO option not deleting large log backup files
Petey, Thanks for the quick response. Are there any plans to allow this error to be skipped without requiring the MOVETO parameter? Thanks, -Mike
0 votes
Peter, My reasoning for wanting to skip the 4326 error without the MOVE command is when we have multiple standby databases restoring log backups from the same primary. If the files are in the same network location and the restore commands can be directed to skip 4326 errors, I can point the restore jobs for both standby databases to the same directory. However, if I have to move the files, then it complicates matters for any standby database other than the first, in addition to not keeping the files in the expected location for a possible production restore / recovery. Thanks, -Mike / comments
  1. Community
  2. SQL Backup Previous Versions
  3. MOVETO option not deleting large log backup files
Peter, My reasoning for wanting to skip the 4326 error without the MOVE command is when we have multiple standby databases restoring log backups from the same primary. If the files are in the same...
0 votes
Petey, If this functionality already exists within the tool, please let me know. Would it be beneficial to add an optional parameter to the RESTORE LOG command within SQL Backup that would instruct the application to "skip" over any files that return error 4326 (SQL error 4326: SQL error 4326: The log in this backup set terminates at LSN xxx, which is too early to apply to the database. A more recent log backup that includes LSN xxx can be restored.)? Perhaps it could work something like a LATEST_* clause for logs by determining which logs can be restored. I've written custom code around SQL Backup to accomplish this in the past, but it seems like it would be a powerful option to include. Thanks, -Mike / comments
  1. Community
  2. SQL Backup Previous Versions
  3. MOVETO option not deleting large log backup files
Petey, If this functionality already exists within the tool, please let me know. Would it be beneficial to add an optional parameter to the RESTORE LOG command within SQL Backup that would instruct...
0 votes
Peter, I have seen the issue occur on log backup files anywhere from 2GB to 6GB. In terms of logged errors, I am seeing the following: From the initial backup log file: 7/2/2011 8:43:06 AM: Warning 130: MOVETO error: Failed to move file: <source_directory_and_file_path> (The system cannot find the file specified.) This path references a UNC share, but it is local to the server from which the backup is being executed. 7/2/2011 8:43:14 AM: Moved <source_file> to <destination_directory>. The file is getting to the destination directory at some point, as indicated by subsequest error messages. From the next log restore attempt: 7/2/2011 10:10:19 AM: Warning 170: Log files are not in sequence: 7/2/2011 10:10:20 AM: SQL Server error 7/2/2011 10:10:20 AM: SQL error 3013: SQL error 3013: RESTORE LOG is terminating abnormally. 7/2/2011 10:10:20 AM: SQL error 4326: SQL error 4326: The log in this backup set terminates at LSN 959142000003918900001, which is too early to apply to the database. A more recent log backup that includes LSN 959142000004032400001 can be restored. 7/2/2011 10:10:20 AM: Warning 130: MOVETO error: Failed to move file: <source_directory_and_file_path> (The file exists.) From subsequent log restore attempts until problem file is manually removed from source directory: 7/2/2011 12:10:22 PM: Warning 170: Log files are not in sequence: 7/2/2011 12:10:23 PM: SQL Server error 7/2/2011 12:10:23 PM: SQL error 3013: SQL error 3013: RESTORE LOG is terminating abnormally. 7/2/2011 12:10:23 PM: SQL error 4326: SQL error 4326: The log in this backup set terminates at LSN 959142000003918900001, which is too early to apply to the database. A more recent log backup that includes LSN 959142000004032400001 can be restored. 7/2/2011 12:10:23 PM: Warning 470: Transaction log has already been restored. 7/2/2011 12:10:23 PM: Warning 130: MOVETO error: Failed to move file: <source_directory_and_file_path> (The file exists.) 7/2/2011 12:10:23 PM: Restoring Newsletter (transaction logs) from: 7/2/2011 12:10:23 PM: SQL Server error 7/2/2011 12:10:23 PM: SQL error 3013: SQL error 3013: RESTORE LOG is terminating abnormally. 7/2/2011 12:10:23 PM: SQL error 4305: SQL error 4305: The log in this backup set begins at LSN 959143000007452500001, which is too recent to apply to the database. An earlier log backup that includes LSN 959142000004032400001 can be restored. 7/2/2011 12:10:23 PM: Mail sent successfully to: <notification_email_address> It appears that each of the error and/or warning codes you referenced are represented in the error log chain. I guess my next question is, do I need to look to further customize the log shipping implementation to handle this condition? Thanks again for your time. -Mike / comments
  1. Community
  2. SQL Backup Previous Versions
  3. MOVETO option not deleting large log backup files
Peter, I have seen the issue occur on log backup files anywhere from 2GB to 6GB. In terms of logged errors, I am seeing the following:From the initial backup log file: 7/2/2011 8:43:06 AM: Warning...
0 votes
Linda, Will there be a patch back-ported for 6.x? My company did not purchase the support agreement, so I think we'd have to pay for 7.0. Thanks, -Mike / comments
  1. Community
  2. SQL Backup Previous Versions
  3. STOPAT with LATEST_ALL
Linda, Will there be a patch back-ported for 6.x? My company did not purchase the support agreement, so I think we'd have to pay for 7.0. Thanks, -Mike
0 votes
Total activity
46
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
9