New Build 7170 is out (use File Connect to download)
Updated: 22 Jun 2010 | 16 comments
FYI,
a new build has been released into the wild, it has all the HF's baked into it as well as fixes for the missed jobs, Exchange restores, etc.
One known issue that I know if is that when restoring messages in Exchange, only messages that are sent from Mapi client to Mapi client will be able to be restored, messages sent via SMTP show up without a message contents, but the subject is there. You should be able to see all the mailboxes during a restore selection.
In addition, this build supports Exchange 2007 (don't hold me to it, that is what I was told). I don't have Exchange 2007 to test with.
Derek
PS: You have to get the build using file connect, meaning you need to login into the license portal and get your fix there.
Discussion Filed Under:
Comments
One more thing, I did install the build last night and other than having to reboot, things went smoothly. A 64 bit version of the build is also available.
Downloads were if I remember correctly:
32bit ~ 550MB
64bit ~ 650MB
Derek
Dennis and David,
in regards to your questions, I don't have the foggiest why Symantec isn't "pushing this release", I got an email from an Engineer @ Symantec as I have an open case with regards of not being able to restore backed up mail.
Yes, it is correct only Mapi to Mapi mail can currently be restored.
I have not pushed agents to other servers as my media server is also my Exchange server and I was trying to fix the problem of not being able to restore. I didn't have time or the desire to reboot all the other servers in my infrastructures as I am using the AOFO with all my agents.
I have not tried the CPS piece, not sure if I ever will, it it works as good as the regular BEX, I think I will pass.
Now who is brave enough to try this on Exchange 2007.
Derek
Jerry,
what do you want to know. Right now the only mail that can be restored is mail NOT sent from outside the Exchange organization, meaning only internal mail (if Mapi to Mapi such as Outlook to Outlook is used). Any message that is sent using SMTP cannot currently be restored. Yes, the message will be there after a restore, but only the subject and sender information, the actuall message and attachments will be blank, attachments actually will show up, but they will be blank.
This is a known issue with Symantec and they are working on a fix for this issue, but as far as I was told there is no ETA, the reason for this problem (as explained by a back line engineer) is that Symantec has to completely reverse engineer the mail process as Microsoft is not documenting how the internals of the exchange server work. I can understand that, why give away your trade secrets.
Hope that helps a little.
Derek
Do legacy backups work with Exchange 2007?
Just wondering.
Derek
Why not Exchange 2003?
Exactly. I'm in a small environment. Since I have to buy new hardware whether I move to 2003 or 2007, I have a very smooth migration path. Build a new server and move the users over. If I built a 32 bit server with '03, then my move to '07 later would be more difficult without another box. Besides all that, this $4000 DST patch woke us up to paying attention to "Mainstream support". It throws "If it ain't broke, don't fix it" thinking out the window!
Is Exchange 2003 will support
Is Exchange 2003 will support New Build 7170 ?. i am little confusion that our symantec 11 d is runing with build 6235. the backup is completed with exemptions saying that "The Backup Exec Remote Agent on the resource does not support the option to enable the restore of individual items. A backup was run, but you will not be able to restore individual items from this backup set."
Any suggestions?. is symantec 12 d will solve the problem?. i can see the induvidual mails when i click in the restore? but i haven't try to restore it because of message given above?
i am looking forward good solution for that
thank in advance
wilson
Backup Exec 11D rev. 6235 and
Backup Exec 11D rev. 6235 and rev. 7170 both support Exchange 2003.
I think your agent on that Exchange server is old, so look at upgrading it.
PS: This is a really old post...it would have been better to open a new forum query instead.
If you find this is a solution, please mark it as such.
Would you like to reply?
Login or Register to post your comment.