Windows SBS 2011 Backup failed and can´t add another destiny drive

I got have Windows SBS 2011 with backups to two external drive (intercalated)
Yesterday, I got an error on my Backup status, I reviewed the event viewer and found out that there was a Disk Error 2, bad sector, or something like that, I supposed that my external drive failed, so, I bought a new drive, opened up my failed usb external disk, and swap the “failed” disk with the new one, then, I connected the new drive (with the same usb external case) and tried to add a new destiny of my backup….. suprice, I get an error while trying to add the new destiny..
The warning I'm seeing is Event ID 57, Ntfs - "The system failed to flush data to the transaction log. Corruption may occur." This is repeated multiple times during the wizard process.
What could it be?, a bad external usb case?

Best regards,
LVL 2
marpanetAsked:
Who is Participating?
 
marpanetConnect With a Mentor Author Commented:
Didn´t work....
I added a new drive and still got the same error....

What I did, did not want to, was to remove all backups destiny, and just add the new one, then it seems it worked.

I will post results,
0
 
Sai Prasad KinneraSupport Delivery ManagerCommented:
The NTFS file system uses transaction logging to provide a level of fault tolerance, Event ID 57 is logged if the NTFS drive is disconnected before transaction logging is completed.

Did you try running check disk?

Click Start, click Run, and then type cmd
At the command prompt, type chkdsk /R /X Drive:

if that doesnt work safely remove the connected disks, remove any native drivers for the disk via device manager and reboot the machine, reconnect the disk and let the os install the drivers again and then try.

if this step doesnt work either, as the drive is new try reformatting it and then perform the task.

Keep me posted of the outcome..
0
 
donnkCommented:
its a known bug. When adding a new destination after the first one has been created you HAVE to have the original destination drive connected as well.

Its a wizard only issue, if you use windows backup it lets you do it.

Amazing MS let these slip through testing really.
0
 
marpanetAuthor Commented:
This worked, maybe not the optimal solution but managed to start making backup again.

Thank you for everything!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.