Exchange Server Agent in Retrospect 6.5

[Mayoff]

The Exchange Server Agent add-on provides fast, precise backups of Microsoft Exchange 2000 Server and Exchange Server 5.5 while they are up and running twenty-four hours a day. It can protect individual mailboxes - or the entire Exchange Server-- with full backups, or with log/incremental or differential backups of the Exchange database, which are significantly faster than full backups because only new and changed data is backed up. The Exchange Agent add-on is unique in its ability to simplify the procedure of restoring an Exchange server to a specific point in time. The Exchange Agent add-on is licensed for use on one Exchange server. The server that is running Exchange Server must also be running the Retrospect application or the Retrospect Client. Use this add-on with Retrospect Multi Server to run backups over the network for a server that is running Exchange Server and the Retrospect Client.

 

 

[DrStern]

... I have written to support about this problem a couple of times, but have not yet received a response, so I figured I would post it here, and see if anyone else has any ideas...

 

This problem has persisted, even after applying the new update to the 6.5 version.

 

When I attempt to apply a license to my Exchange server, I get the following error message:

 

"Retrospect has encountered a Serious Error: Assertion Failure

at 'elem.cpp-855'"

 

"A log of this error has been written to the file

'assert_log.utx'" (obtainable at http://www.copi.com/.dantz/assert_log.utx)

 

"Please tell Dantz about this problem."

 

The above is a direct quote. My instructions to contact you

got more explicit in the attached utx file.

 

Now some background:

 

I just upgraded from Retrospect 6.0 to 6.5, due to the "blue

screen of death" error from open file backup issues. Under

both installations, my components have included:

Retrospect Multiserver

Disaster Recovery

Open File Backup

Exchange Agent

 

The software is running on a workstation running Win2kPro/SP3.

 

 

I am running MS Exchange 2000 - I thought I was running SP3,

but apparently I was not (I definitely am running MSXS-SP3

now -- more on that later.)

 

Exchange is running on a Win2k Server box, running SP3.

 

There is an oddity about my Network and workstation logins,

due to some inherited IDs and a desire to maintain my

desktop. I log into my workstation LOCALLY using the same

user name that I use on the network as a super-administrator.

I have never had any problems from this really, but thought I

should mention it.

 

Immediately after installing/upgrading the Retrospect program

from 6.0 to 6.5, I entered the software, and set it up to run

using my network/all-everything administrator &

backup-operator account when it runs.

 

Then I upgraded all of the client installations, including

that on the Exchange Server.

 

Then I attempted to license the Exchange Server, and got the

error paragraph quoted in the opening of this post. (Bear

with me here - I think I know what you are going to say next,

and I have addressed it. Sorry to be re-emptive, but I have

had esperiences before with tech support folks offering quick

pre-fabricated solutions that I have already tried and told

them about, and then they've disappeared. Of course, that has

never happened with Dantz.)

 

If you were thinking I should go back and follow the

instructions word-for-word in building a user account for

Exchange Agent, well, that's what I did next. Everything from

setting the user account up on the Exchange Server/Domain

Controller, to making sure it was a member of each and every

group mentioned, to setting up its mailbox, to priming that

mailbox with a message - I did it.

 

Then I set up Retrospect to run using this new user account.

and re-started.

 

Then I attempted to license the Exchange Server again - and

got the same result. (I figured I would, since the user

account I had it using before had all of the necessary

components and then some for backing up the network and

Exchange.)

 

Then I tried all sorts of permutations of the above - I

changed login accounts from a local to network (domain

administrator) account for logging in as a user. I added a

few more high-powered admin memberships to the designated

Retrospect account. I re-booted. ..

 

... and I always got the same result. Most of the times, I

elected to have the file sent to Dantz.

 

And so now I am here.

 

Please help.

 

[Mayoff]

THis is documented in our knowledgebase

 

http://www.dantz.com/index.php3?SCREEN=kbase&ACTION=KBASE&preview=y&id=27944

[DrStern]

I will study and attempt to implement the problem. However, I am not running Exchange 5.5, I am running Exchange 2000.

[MLJuno]

Does installing the Exchange v6.5 agent prevent you from doing offline Exchange backups if these are still desired on occasion?

[natew]

Hi

 

Yes it does.

 

Once the exchange agent is licensed it excludes the exchange data base files from standard backups. This is by design and is also true with the SQL agent.

 

If you want to do off line backups of your databases you can either unlicense the server temporarily or do a drag and drop copy of the files and then rename them.

 

Nate