Activity overview
Latest activity by meastland
The Log Copy Queue
To whom it may concern:
We are currently running SQL Backup 7.6.0.29. We use the log copy queue to support log shipping for a system that experiences high month-end transaction volume. As a resul...
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
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?
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
I have yet to hear back on this. Since I have a support contract, would I be better served by opening a formal ticket?
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
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 ...
Missing functionality - RESTORE LOG...WITH MOVE
I believe there is a bug in version 6.5.2.21 of SQL Backup. The problem is that the WITH MOVE construct is not available to the SQL Backup implementation of the RESTORE LOG command as it is with th...
Thanks, Peter. I will deploy and test the patch as time permits. / comments
Thanks, Peter. I will deploy and test the patch as time permits.
Peter,
Thanks for the quick response. Is it possible to be notified when the fix is available?
Thanks,
-Mike / comments
Peter,
Thanks for the quick response. Is it possible to be notified when the fix is available?
Thanks,
-Mike
High CPU on VERIFY
We have a backup configured against a ~ 300GB database to use the following options: CHECKSUM, COMPRESSION = 4, COPY_ONLY, FILECOUNT = 4, INIT, THREADPRIORITY = 1.
The backup appears to run fine, a...
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
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...
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
Petey,
Thanks for the quick response. Are there any plans to allow this error to be skipped without requiring the MOVETO parameter?
Thanks,
-Mike