Feature Request for Log shipping
grambowk
Posts: 8
I'd like to make a feature request that I feel is essential for log shipping to work more effectively.
Currently, the COPY process is embedded into the BACKUP command but I feel you should seperate the COPY process entirely (as Microsoft have done in their implementation of log shipping).
At present, if the COPY process fails (due to a network failure, for example) then that file will never be copied to the secondary server unless I do it manually.
However, if you seperated the COPY process and had a seperate job that handled the COPY process then any file that wasn't copied across to the secondary would be picked up the next time the copy job ran.
Thanks,
Karl
Currently, the COPY process is embedded into the BACKUP command but I feel you should seperate the COPY process entirely (as Microsoft have done in their implementation of log shipping).
At present, if the COPY process fails (due to a network failure, for example) then that file will never be copied to the secondary server unless I do it manually.
However, if you seperated the COPY process and had a seperate job that handled the COPY process then any file that wasn't copied across to the secondary would be picked up the next time the copy job ran.
Thanks,
Karl
