Jump to content
bcssomadude

Error -557 Transaction already complete

Recommended Posts

I'm starting a new thread on Error -557. I believe it's a code thrown by Exchange in process of the RS-Exchange dialogue.

 

Exchange Storage Group (Full) backup: No errors

Exchange Storage Group (Differential) backup: Error -557 on first storage group

Exchange Mailbox Backups (Full): Error -557 at 20% failure rate.

 

It's almost like Exchange is saying "that's already backed up, go away", at which point Retrospect bombs on that box and moves on to the next.

 

Thoughts? I keep forgetting RS support is closed at 3PM my time.

 

RS 7.7 with latest patches & hotfixes

Windows Server 2003 32-bit w/ Exchange 2007 SP2

 

Could this be related to the fact that I'm using Recovery Storage Groups? Perhaps the RSG is conflicting with RS' efforts?

Share this post


Link to post
Share on other sites

This is not an error we expect to see, but if you contact tech support we can work with you to collect a debug log and narrow down what is happening.

Share this post


Link to post
Share on other sites

I am also seeing this on our Exchange server mailbox backups both on Exchange 2003 and 2007. this only started with the after the 7.7 upgrade.

 

I've seen other reports of this in the forum. Is there any information on a fix?

Share this post


Link to post
Share on other sites

Dominique,

 

What OS and architecture (32/64) of the server hosting Retrospect? ... for the server hosting Exchange 2007?

 

Are you also backing up Exchange using the client software?

Share this post


Link to post
Share on other sites

Mike,

 

both systems are running Windows Server 2003 x64. We are not backing up the local drives. Within the client we chose "Selected Volumes" as Client source. There "Echxange Server Exchange Server" is selected containing two Storage Groups and "Exchange Mailboxes" containing roundabout 50 Mailboxes. So far I can see the error only shows up with some of the mailboxes. I did not see if always the same...

 

And the error started right the day we upgraded retrospect 7.6 to 7.7.

 

Many greetings

Dominique

Share this post


Link to post
Share on other sites

We have Retrospect 7.7 running on Win 2000 server SP4, Exchange 2007 on Win Ser 2003 Ent x64, Exchange 2003 on Win Ser 2003 x32

 

Well over half of the 20 or so individual mailboxes are showing this error, more on the Exch 07 box, but still some on Exchange 03.

Note that a full Exchange storage backup completes without problem.

Share this post


Link to post
Share on other sites

Is the Retrospect 7.7 program installed on Windows 2000? 7.7 only supports Windows 2000 as a client not as a backup server.

Share this post


Link to post
Share on other sites

Thanks, yes, the plan is to retire that server in the next month or two. However, I doubt this has any bearing on the -557 Transaction errors that have started since the upgrade to Retrospect 7.7. Today the error appeared with the backup of the full storage set, not just an individual mailbox. It does seem to happen with much greater frequency to Exch 07 mailboxes.

 

This is a serious bug in a main feature of the product and I'm looking at rolling back to version 7.6 as EMC hasn't responded with any information about a fix.

Share this post


Link to post
Share on other sites

You said it is happening to you when you backup a full storage set. Are you using Differential backup for the Exchange storage groups when this happens?

 

I have noticed that it does not happen if I run a Normal: Full backup of the storage groups, but I find that I get the -557 error upon attempting differential.

 

Share this post


Link to post
Share on other sites

Same error here only we're still on 6.7.

 

RS is on Win2003 R2 SP2 and error occurs trying to backup Exchange 2007 running on 2003 x64 R2 SP2

using client on Exch

Share this post


Link to post
Share on other sites

We are experiencing the same error:

"Trouble reading files, error -557 (transaction already complete)"

 

Retrospect Server:

Windows Server 2008 Service Pack 2 x64 running Retrospect v7.7.208

 

Exchange Server:

Windows Server 2008 Service Pack 2 x64 running Exchange 2007 SP2 (v8.2 Build 176.2)

 

Backup selections:

"Exchange Server Exchange Server" with First and Second Storage Groups

"Exchange Mailboxes"

 

The Datastore backups succeed, the mailboxes succeed for about 80%, only a few mailboxes experience the -557 error. The error appeared when we upgraded to 7.7 as well.

 

Thanks,

Sean

Share this post


Link to post
Share on other sites

Exchange server: Win 2003 R2 x64

Exchange 2007 SP1

Retrospect server: Win 2003 R2 x86

Version 7.7.208

Driver Update and Hot Fix:7.7.1.102

Backup Exchange Server(Full): OK!

Backup MailBoxes(Full): several mail boxes with error: "Trouble reading files, error -557 ( transaction already complete)"

Only happens with big mail boxes. Some examples:

 

07-03-2010 21:07:34: Execution incomplete

Remaining: 4693 files, 750,0 MB

Completed: 696 files, 74,3 MB, with 13% compression

07-03-2010 21:20:22: Execution incomplete

Remaining: 2499 files, 1,3 GB

Completed: 1422 files, 839,8 MB, with 0% compression

 

I am trying EMC Retrospect. The errors began in the very first backup I have made.

 

Share this post


Link to post
Share on other sites

We believe that this 557 error is fixed based on feedback from some of our beta testers. The release should be next month.

Share this post


Link to post
Share on other sites

Experiencing the exact same issue with an identical environment.

 

So I understand, at current, no workaround exists and in order to perform brick-level, mailbox backups, we have to wait until April 2010?

Share this post


Link to post
Share on other sites

Thank you for responding.

 

When is this pre-release beta scheduled for production/stable release???

 

Sorry for my confusion - I'm perplexed a 7.7 version of a product can't backup Exchange 2007 mailboxes. It seems odd we have to use a beta release to run a core functionality.

 

Share this post


Link to post
Share on other sites

This is a bug that impacts a small number of customers. We will have a final release of an updated version next month.

Share this post


Link to post
Share on other sites

Robin,

 

I see.

 

Final question. For the benefit of this thread - can you define "small number of customers" i.e. operating system, exchange version, etc.

 

The reason I ask is - my implementation of Retrospect involves newly installed servers running all the latest patches and services packs. Very vanilla and very straight forward, hence my confusion why 7.7 doesn't "just work".

 

Thanks again Robin,

Edited by Guest

Share this post


Link to post
Share on other sites

Any update on a fix release date? Same error on backup server running Server 2008 R2 OS release.

 

Retrospect Server:

Windows Server 2008 R2 SP0 x64 running Retrospect v7.7.208 (64-bit)

 

Exchange Server:

Windows Server 2008 Service Pack 2 x64 running Exchange 2007 SP2 (v8.2 Build 176.2)

 

Thanks~

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×