Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

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

Posted on 2013-11-20
4
Medium Priority
?
914 Views
Last Modified: 2013-11-27
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,
0
Comment
Question by:marpanet
  • 2
4 Comments
 
LVL 9

Expert Comment

by:Sai Prasad Kinnera
ID: 39665046
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
 
LVL 2

Accepted Solution

by:
marpanet earned 0 total points
ID: 39666522
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
 
LVL 6

Expert Comment

by:donnk
ID: 39671247
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
 
LVL 2

Author Closing Comment

by:marpanet
ID: 39680241
This worked, maybe not the optimal solution but managed to start making backup again.

Thank you for everything!
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A Bare Metal Image backup allows for the restore of an entire system to a similar or dissimilar hardware. They are highly useful for migrations and disaster recovery. Bare Metal Image backups support Full and Incremental backups. Differential backup…
In this article we will learn how to backup a VMware farm using Nakivo Backup & Replication. In this tutorial we will install the software on a Windows 2012 R2 Server.
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …
Suggested Courses

963 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question