Comments
Sort by recent activity
Thanks for the better explaination. I think a better implementation would be if the mirror is not available, still go ahead and re-execute the backup to the primary location.
Jason Cook wrote:
Hi,
I've looked for the section in the help you are referring to, and it does seem to be slightly ambiguous:
"During the backup process, if any of the files cannot be written a warning is raised. However, the backup process continues as long as at least one specified backup file can be written. If none of the files can be written, an error is raised and the backup process is stopped."
What this should mean, is that once the actual backing up phase has begun, a subset of the files can fail and the rest should continue. However, if a pre-backup phase failure occurs (for example, the missing directory), the backup task will error out before the backing up phase begins.
Depending on your needs, the COPYTO keyword may be able to help. The difference with COPYTO is that the primary server's backup is done first, and *then* copied to the secondary server. If for any reason the secondary server is unavailable, the backup will succeed with a warning, rather than fail.
The main downside to the COPYTO is that you only have one copy of the file available until the COPYTO completes, compared to 2 or more when the original backup completes.
I'll also pass this on to our developers and they may be able to improve the situation in a future release.
Hope that helps,
Jason
/ comments
Thanks for the better explaination. I think a better implementation would be if the mirror is not available, still go ahead and re-execute the backup to the primary location.
Jason Cook wrote:
Hi...