Activity overview
Latest activity by Powerway
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...
Mirrored backup failure
We are doing mirrored full, diff, and log backups. We had the mirror server down for maintenance and when the log backup was done on the primary server, the job failed and it didn't even create th...
Restore error after conversion from sqb to bak
We used the SQLBackupC command to extract the bak files out of a sqb.
When we attempted to restore these files, we got this. Any ideas?
Restore failed for Server 'dev-strsdb1'. (Microsoft.SqlServ...
Not urgent at all. We have people restore in our SQA department and they were asking why a restore took 20 minutes to do the checking password.
I'll tell them something is in the works for the next release.
Thanks / comments
Not urgent at all. We have people restore in our SQA department and they were asking why a restore took 20 minutes to do the checking password.
I'll tell them something is in the works for the nex...
Dan J Archer wrote:
Thanks for your replies.
Can I confirm you're both using SQL Backup 5? Backup 5 should indeed generate one file regardless of the number of threads.
All the best,
Dan
Yes SQL Backup 5.1. The multiple file thing I was referring too was I read that inside the one file there were actually multiple streams/files. Is this true? / comments
Dan J Archer wrote:
Thanks for your replies.
Can I confirm you're both using SQL Backup 5? Backup 5 should indeed generate one file regardless of the number of threads.
All the best,
Dan
Yes S...
Our backups are at compression 2, 128-bit encryption, 4 threads, no verify.
Like I said, if just 1 thread is used, the password seems to be validated immediately.
I realize that when threads are used, multiple files are created. Not sure if this has something to to do with it. / comments
Our backups are at compression 2, 128-bit encryption, 4 threads, no verify.
Like I said, if just 1 thread is used, the password seems to be validated immediately.
I realize that when threads are us...
Checking Password takes a long time
We have a 40 gig SQL Backup file created with 4 threads. When we go to restore it, the checking password phase takes 25 minutes of high I/O. This is almost instantaneous when threads are not used...
Brian Donahue wrote:
Thanks for writing back.
Is it all working now, including the fix for ERASEFILES?
Thanks.
I'm getting ready to start my tests over with verify ON and the latest version. I'll let ya know on Monday / comments
Brian Donahue wrote:
Thanks for writing back.
Is it all working now, including the fix for ERASEFILES?
Thanks.
I'm getting ready to start my tests over with verify ON and the latest version. ...
Brian Donahue wrote:
Hi,
Thanks for writing. Please make sure that you have applied the upgrade to the server components as well as installing the UI. If you've already done this, did you get any warnings from the server components? In particular, the one that mentions that you need to run DBCC sqlbackup (FREE). You may still have the old version of the stored procedure 'stuck' in the SQL Server memory.
Please let us know if you have any questions about this.
Yes the server components hadn't been updated.
Thanks / comments
Brian Donahue wrote:
Hi,
Thanks for writing. Please make sure that you have applied the upgrade to the server components as well as installing the UI. If you've already done this, did you get an...
Supplying path on differential restore
Let's say I restored a full backup from one server on another server. Put the database files in a different location. I left the database in recovering state.
I then go to restore a differential....