November 23, 2010 at 2:07 am
Lindsay
Go to a command prompt and type net helpmsg 64. This will tell you what the error message means. Looks like your network is somewhat flaky.
John
November 23, 2010 at 2:14 am
John, thanks for the quick reply.
I thought it might be something along those lines.
But I don’t understand is why it is always on the same db?
I've change the backup sequence many times. Sometimes this db is taken first, second, third,...
But it always fails on the same db. And the backup is successful.
So why do I get that error?
Lindsay
November 23, 2010 at 3:44 am
Lindsay
Is the database in question significantly larger than the others? Have you done a RESTORE VERIFYONLY on the backup file? Is this done as part of the backup job (if not, it should be)?
John
November 23, 2010 at 4:07 am
John,
The database is not that big (3,5 GB). There are other, bigger db's (10 GB) and they don't give errors.
I've just performed a RESTORE VERIFYONLY, the result was: The backup set on file 1 is valid.
This is not part of the backupprocedure.
Lindsay
February 1, 2011 at 12:54 am
Hi, we found the solution to out problem.
It turns out our .trn backup files where corrupt.
By adjusting our maintance plan ( the one that makes the trn backups ) we no longer have this problem.
Viewing 5 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply