Mbx Archiving State / Mbx Exchange State
Often the question of what is the different states of MbxArchivingState and MbxExchangeState in the ExchangeMailboxEntry table. The Archiving State translates as follows: 0 = Not Enabled 1 = Enabled 2 = Disabled 3 = Re-Link To view the Archiving State you can use the following:
Support for Exchange 2010 with Symantec Enterprise Vault™ - coming!
We’re currently working very hard on full support of Microsoft Exchange 2010, at a level that our 13,000+ customers are used to and expect from us. Nevertheless, the questions are coming thick and fast about when and how Microsoft Exchange 2010 will be supported. We therefore decided that it’s time for an update, and here’s what we can tell you today: We plan to release full support for Exchange 2010 SP1 with Enterprise Vault 9.0 We plan to run a Beta program for EV 9.0 beginning in March this year* Following that, we plan to run a First Availability program prior to General Availability Enterprise Vault 9.0 is currently on schedule to be available in the second half of this year** There are many fundamental changes to the Exchange store (DAG), OWA and the connection mechanisms (via the CAS servers) in Exchange Server 2010 which all require major engineering efforts to support. Symantec is fully committed to providing these changes to continue to provide the the best support for Microsoft Exchange 2010,and acontinued strong partnership with Microsoft,at the level of quality our customers have come to expect.We strive to consistently deliver at this level of quality as we have a roadmap that affects many, many organisations around the world, asthe market leader in archiving. So, stay tuned, as we’ll be releasing more information about full and complete support for Microsoft Exchange 2010 with Symantec Enterprise Vault in the coming weeks. * disclaimer; as always, features and release schedules are subject to possible change ** for more information, and to join the Beta, please see this technote. ***Attention: Please note that Enterprise Vault 9.0 Beta and First Availability registration is now closed. Meantime, Happy New Year from the whole Enterprise Vault Team at Symantec!
Unable to see the exchange information store.
Setup. Master Server 6.5.3 Windows server 2003 Client 6.5.3 Windows server 2003 Exchange 2007. Trying to backup exchange mailboxes but they are failing with status 41 and this is failing only when he runs the fullbackups the differential backups are running fine. The exchange server is clustered. And the information store backups run fine. On BAR FOUND that the customer was not able to not see the information store and was also not able to see anything after expanding the exchange maiboxes. Than tried creating a test account gave the domain admin credentials,also assinged the exchange server role, activated the mailbox, after that started the netbackup services with the new test account but still was not able to expand the exchange mailboxes and was also not able to see the information store. Also asked him to do a failover of his cluster. Please help.
Backup Exec // B2D media used for Exchange 2007 Information Store associated to scratch media
Hello, I am new to Symantec BEWS and I have just created a new Disk-to-Disk-to-Tape backup job copying predefined policy "Duplicate Backup Sets 00001". BE Media Server is running Windows Server 2003 R2 SP2 while the Exchange Server is running Windows Server 2008 SP1 with MS Exchange Agent. Target device for the Disk-to-Disk job is a newly created Backup-to-Disk folder, target media set is a newly created media set with 1 week OPP and 8-hour AP. Last night the Disk-to-Disk backup job ran the first time and completed successfully without errors. This morning I went through the device and media information section under job history. This section showed "B2D000006", "IMG000004" and "IMG000005" as used media, but how comes that "B2D000006" media belongs to pre-defined Scratch Media set while both "IMG000004" and "IMG000005" belong to the newly created media set according to Template properties ? I know that GRT-enabled backup jobs result in IMG folders being created during job execution, but how comes that media created during the same backup job is associated to different media sets ? Furthermore how comes that used capacity for that media is not shown under Devices -> Backup-to-Disk folders -> My Backup-to-Disk folder while used capacity for other media under different Backup-to-Disk folders used for normal file backup jobs is displayed ? Any help is much appreciated. Have a great day. Regards, Massimiliano
