Jump to content
anchornet

7.6.123 Exchange Backup Takes 1 Second!

Recommended Posts

Upgraded a working SBS Retrospect to 7.6.123 and Exchange backup (separate script) now takes 1 second to complete. Obviously that's incorrect for a 12GB Exchange database.

 

Something broke! At least I think so. Anyone else seeing this issue?

 

Tried to unlicense, and re-license. Successful.

Have special RBU account and Retrospect can see all the individual mailboxes. Successful.

 

All with the same result.

 

Here is the log...

 

+ Normal backup using Exchange at 12/17/2008 10:04 PM (Execution unit 1)

* Resolved container Exchange Server to 1 volumes:

First Storage Group

To Backup Set Exchange...

 

- 12/17/2008 10:04:01 PM: Copying First Storage Group

12/17/2008 10:04:01 PM: No files need to be copied

12/17/2008 10:04:05 PM: Execution completed successfully

Duration: 00:00:04 (00:00:01 idle/loading/preparing)

 

 

Share this post


Link to post
Share on other sites

Please try an immediate backup. Select just the 1st storage group and not the exchange server container. Does it work? Does it do the same thing with a new backup set?

 

If you downgrade to the prior version does it work immediately without making any other changes?

Share this post


Link to post
Share on other sites

Based on the suggested problem solving test, it would seem I have figured this out.

 

My Exchange scripts have always had the selector set to "No Files". This worked just fine prior to the latest release. Once I upgraded, it would seem I needed to change those scripts to "All Files".

 

Curious, since Exchange is a database, why do I need to set a Selector? My scripts for just Exchange have been fine with it set to "No Files".

Edited by Guest

Share this post


Link to post
Share on other sites

Customers wanted the ability to exclude databases by using a selector. It looks like the engineers figured out how to make that work.

 

All Files is the default. I have never seen anyone select No Files for a database backup. It is like saying "backup no data"

Share this post


Link to post
Share on other sites

Yes, but why backup a "database file" when all you want to do is backup a "database"? Unless there is something about the mechanics that I'm missing, you would duplicate your backup storage requirements. One copy that you can restore from and one that you can't.

 

We have drives that only have Exchange or SQL databases and we exclude those from normal file backups as they get personal attention with their respective database agents.

 

Should we not do this?

Share this post


Link to post
Share on other sites

When you license Exchange/SQL Retrospect should be automatically excluding files on the drive letter that should not be recopied.

 

We wouldn't make "all files" the default, if it was the "wrong" way to backup your databases. You can pretend that "all files" means "all databases".

Share this post


Link to post
Share on other sites

I'll think I'll grab a Gourmet Burrito just outside your offices in p-town in celebration of clearer understanding (I'm just down the street.). I raise my cup of Diet Coke to you Robin!

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

×