Backing up Enterprise Vault in a clustered environment
I got this from Symantec Web site. But if you search the knowledgebase you wont see this in the result. It took me awhile to find this document. I'm putting it here so others will get easily.
DEC 11, 2007
Symantec Enterprise Vault 7.0 - Backing up Enterprise Vault in a clustered environment Size: 117 KB
285839.pdf
Utility - Sample batch file template for use with backing up in a clustered environment Size: 2 KB
Friday, September 26, 2008
Wednesday, September 24, 2008
VCS fail to bring down MSMQ service on EV 7
https://forums.symantec.com/syment/board/message?board.id=106&message.id=7711&query.id=88254#M7711
Disable the MSMQ service on all nodes of the cluster. Modify the dependency of the EV storage and task manager services to the VCS MSMQ instance on all nodes.Modify the string value DEPENDONSERVICE in the following keys:
HKLM\SYSTEM\CurrentControlSet\Services\EnterpriseVaultTaskControllerService
HKLM\SYSTEM\CurrentControlSet\Services\EnterpriseVaultStorageService
to include the VCS MSMQ (MSMQ$EVSG-MSMQ) and remove the default MSMQ instance.
Reboot both nodes.
You may also want to check for event (error) id 2124 as the VCS MSMQ service may be installed with AD integration (which is not best practices for EV).
Disable the MSMQ service on all nodes of the cluster. Modify the dependency of the EV storage and task manager services to the VCS MSMQ instance on all nodes.Modify the string value DEPENDONSERVICE in the following keys:
HKLM\SYSTEM\CurrentControlSet\Services\EnterpriseVaultTaskControllerService
HKLM\SYSTEM\CurrentControlSet\Services\EnterpriseVaultStorageService
to include the VCS MSMQ (MSMQ$EVSG-MSMQ) and remove the default MSMQ instance.
Reboot both nodes.
You may also want to check for event (error) id 2124 as the VCS MSMQ service may be installed with AD integration (which is not best practices for EV).
How to use the IgnoreArchiveBitTrigger.txt file for devices that do not support the Archive bit when using Symantec Enterprise Vault (tm)
How to use the IgnoreArchiveBitTrigger.txt file for devices that do not support the Archive bit when using Symantec Enterprise Vault (tm)
http://seer.entsupport.symantec.com/docs/273151.htm
http://seer.entsupport.symantec.com/docs/273151.htm
upgrading exchange 2003 to exchange 2007 using evault 2007
https://forums.symantec.com/syment/board/message?board.id=106&thread.id=19159
1. Disable all the enabled users.
2. Migrate the users to Exch2007(Keep their legacy DN names same)
3. Add the new exchange 2007 server as target.
5. Reenable the users from the new exchange server
1. Disable all the enabled users.
2. Migrate the users to Exch2007(Keep their legacy DN names same)
3. Add the new exchange 2007 server as target.
5. Reenable the users from the new exchange server
EV Tip:How to move Enterprise Vault to a new server
https://forums.symantec.com/syment/board/print?board.id=106&message.id=16529&format=one
Overview:
The objective of this technical note is to address the steps to move a single Enterprise Vault (EV) directory server environment
Resolution:
Procedure for Same Name Server
1. Allow the Microsoft Message Queue (MSMQ) to empty before moving Enterprise Vault to another server. Stopping the Task Controller service will normally allow the MSMQ's to be processed by the Indexing and Storage services.
2. Once the MSMQ's are empty, stop all EV services.
3. Export the registry key 'HKEY_Local_Machine\Software\KVS\Enterprise Vault' from the original server.
4. Examine the following registry keys. If they exist, make the appropriate changes to the new server:
- Opportunistic LockingHKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\DWord: OplocksDisabledValue:
- Memory management registry keysHKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\DWord: PoolUsageMaximum Value: DWord: PagedPoolSize Value:
5. If using Journaling Connector, copy the file:\Program Files\Enterprise Vault\JournalTask.exe.config.
Note: Unless otherwise stated, do not start any Enterprise Vault service until all the steps of this recovery procedure have been completed.
Things to consider:
By default there are certain files that are typically located on the EV server and thus must be placed on the new server in the same location (that includes the drive letter). Those items are:
· Vault Stores· Indexing files· Shopping files· Reports
If any of these items are currently located on the original EV server, they must be restored to the new server.
6. Installing software on the servers. All the data relating to your previous Enterprise Vault installation needs to be recovered onto new servers. For each server that has failed, set up a new computer. Ideally, set up each computer with the same name as the original computer that it is replacing. Note: If this is not possible, the recovery steps 'Procedure for Renamed Servers' indicate what to do to accommodate a change in computer name. Build each new system, starting with the installation of Windows and then all the prerequisites for Enterprise Vault. Refer to the Enterprise Vault documentation if unsure which prerequisite software that needs to be installed on each computer. When the correct prerequisite software has been set up on each server, install Enterprise Vault on the server.
Notes:
· Install Enterprise Vault on each new server, into the same folder as on the original server.· Install the same version of Enterprise Vault as is being used in the current environment.
Do not run the Configuration Program at the end of completing the installation of the Enterprise Vault software.
7. Point the EV Alias entry in DNS to the new server Internet Protocol (IP) address
8. Start the EV services
9. If using Journaling Connector, Install the Journaling Connector and restart the EV services.Note: If the Journaling Task fails after installing the Journaling Connector, copy the file from step 5 to its original location.
10. Verify the services are running correctly
11. Export the registry key 'HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault' from the new server and keep in a safe place in case it becomes necessary to restore.
12. Restore the registry key from step 3 'HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault' from the original server onto the new server
13. Restart the EV services
14. Verify the services are running correctly
Procedure for Renamed Servers
Ideally, each server should set up with the same name as the original server that it is replacing. However, if this is not the case, the following extra procedure must be performed.
· Warning: If Enterprise Vault is running in a clustered environment, do not perform this operation unless Symantec Support advises to do so.
1. Repeat the following steps for each server that is being recovered:
a. Run SQL Query Analyzer and connect to the server that is running the Enterprise Vault Directory service.
b. Enter and run the following SQL command:
USE EnterpriseVaultDirectoryUPDATE ComputerEntrySET ComputerNameAltername = ''WHERE ComputerNameAlternate = ''
2. Check that the DNS alias that was set up for the old server points to the name of the new server. If unsure what the DNS alias is, run the following SQL query against the EnterpriseVaultDirectory database.
USE EnterpriseVaultDirectorySELECT ComputerName FROM ComputerEntry
3. If recovering the system that used to run the Directory service, and this server has been renamed, point the vault site alias (a DNS alias that points to the Directory computer) at this new server. To do this:
a. Run SQL Query Analyzer and connect to the server running the Enterprise Vault Directory service.
b. Enter and run the following SQL command:
USE EnterpriseVaultDirectorySELECT SiteEntryIdFROM SiteEntry
The value returned contain the vault site alias at the end of a long string of numbers. For example, if the command returns the following then the vault site alias is alias.example.local:
10354B15D38FE5B41BAAC212490EBA5351d10000alias.example.local
· In DNS, change the DNS alias so that it points at the server running the Directory service.
Overview:
The objective of this technical note is to address the steps to move a single Enterprise Vault (EV) directory server environment
Resolution:
Procedure for Same Name Server
1. Allow the Microsoft Message Queue (MSMQ) to empty before moving Enterprise Vault to another server. Stopping the Task Controller service will normally allow the MSMQ's to be processed by the Indexing and Storage services.
2. Once the MSMQ's are empty, stop all EV services.
3. Export the registry key 'HKEY_Local_Machine\Software\KVS\Enterprise Vault' from the original server.
4. Examine the following registry keys. If they exist, make the appropriate changes to the new server:
- Opportunistic LockingHKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\DWord: OplocksDisabledValue:
- Memory management registry keysHKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\
5. If using Journaling Connector, copy the file
Note: Unless otherwise stated, do not start any Enterprise Vault service until all the steps of this recovery procedure have been completed.
Things to consider:
By default there are certain files that are typically located on the EV server and thus must be placed on the new server in the same location (that includes the drive letter). Those items are:
· Vault Stores· Indexing files· Shopping files· Reports
If any of these items are currently located on the original EV server, they must be restored to the new server.
6. Installing software on the servers. All the data relating to your previous Enterprise Vault installation needs to be recovered onto new servers. For each server that has failed, set up a new computer. Ideally, set up each computer with the same name as the original computer that it is replacing. Note: If this is not possible, the recovery steps 'Procedure for Renamed Servers' indicate what to do to accommodate a change in computer name. Build each new system, starting with the installation of Windows and then all the prerequisites for Enterprise Vault. Refer to the Enterprise Vault documentation if unsure which prerequisite software that needs to be installed on each computer. When the correct prerequisite software has been set up on each server, install Enterprise Vault on the server.
Notes:
· Install Enterprise Vault on each new server, into the same folder as on the original server.· Install the same version of Enterprise Vault as is being used in the current environment.
Do not run the Configuration Program at the end of completing the installation of the Enterprise Vault software.
7. Point the EV Alias entry in DNS to the new server Internet Protocol (IP) address
8. Start the EV services
9. If using Journaling Connector, Install the Journaling Connector and restart the EV services.Note: If the Journaling Task fails after installing the Journaling Connector, copy the file from step 5 to its original location.
10. Verify the services are running correctly
11. Export the registry key 'HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault' from the new server and keep in a safe place in case it becomes necessary to restore.
12. Restore the registry key from step 3 'HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault' from the original server onto the new server
13. Restart the EV services
14. Verify the services are running correctly
Procedure for Renamed Servers
Ideally, each server should set up with the same name as the original server that it is replacing. However, if this is not the case, the following extra procedure must be performed.
· Warning: If Enterprise Vault is running in a clustered environment, do not perform this operation unless Symantec Support advises to do so.
1. Repeat the following steps for each server that is being recovered:
a. Run SQL Query Analyzer and connect to the server that is running the Enterprise Vault Directory service.
b. Enter and run the following SQL command:
USE EnterpriseVaultDirectoryUPDATE ComputerEntrySET ComputerNameAltername = '
2. Check that the DNS alias that was set up for the old server points to the name of the new server. If unsure what the DNS alias is, run the following SQL query against the EnterpriseVaultDirectory database.
USE EnterpriseVaultDirectorySELECT ComputerName FROM ComputerEntry
3. If recovering the system that used to run the Directory service, and this server has been renamed, point the vault site alias (a DNS alias that points to the Directory computer) at this new server. To do this:
a. Run SQL Query Analyzer and connect to the server running the Enterprise Vault Directory service.
b. Enter and run the following SQL command:
USE EnterpriseVaultDirectorySELECT SiteEntryIdFROM SiteEntry
The value returned contain the vault site alias at the end of a long string of numbers. For example, if the command returns the following then the vault site alias is alias.example.local:
10354B15D38FE5B41BAAC212490EBA5351d10000alias.example.local
· In DNS, change the DNS alias so that it points at the server running the Directory service.
How to view Clustered Microsoft Message Queues (MSMQ's) in a clustered Enterprise Vault installation
Document ID: 295585 http://support.veritas.com/docs/295585
How to view Clustered Microsoft Message Queues (MSMQ's) in a clustered Enterprise Vault installation
Details:
By default the Computer Management snap-in only shows Microsoft Message Queues (MSMQ's) for the local computer. VERITAS Cluster Server (VCS)Run the following command to review the MSMQ queues.VCSVMMCVIEW –target MSMQMicrosoft Cluster Server (MSCS)1 Ensure the Enterprise Vault virtual server is online on the node the queues need to be viewed for. 2 Open a command prompt window and change to the Enterprise Vault installation folder, typically C:\Program Files\Enterprise Vault.3 Enter the following command: ClusterCompMgmtThis launches the Computer Management snap-in with the environment variables set so that it displays the clustered message queues.4 Expand Services and Applications, then expand Message Queuing. The Enterprise Vault virtual server queues are listed under Private Queues.
Products Applied: Enterprise Vault for Microsoft Exchange 2007 7.5, 2007 7.5 SP1, 2007 7.5 SP2
Last Updated: July 09 2008 07:39 PM GMT Expires on: 07-09-2009 Subscribe to receive critical updates about this document
Subjects: Enterprise Vault for Microsoft Exchange Administration: Advice Clustering: Mscs - Advice Msmq: Configuration
Languages: English (US)
Operating Systems: Windows 2000
Advanced Server SP3, Advanced Server SP4, Datacenter Server SP3, Datacenter Server SP4, Server SP3, Server SP4Windows Server 2003 R2,
How to view Clustered Microsoft Message Queues (MSMQ's) in a clustered Enterprise Vault installation
Details:
By default the Computer Management snap-in only shows Microsoft Message Queues (MSMQ's) for the local computer. VERITAS Cluster Server (VCS)Run the following command to review the MSMQ queues.VCSVMMCVIEW –target MSMQMicrosoft Cluster Server (MSCS)1 Ensure the Enterprise Vault virtual server is online on the node the queues need to be viewed for. 2 Open a command prompt window and change to the Enterprise Vault installation folder, typically C:\Program Files\Enterprise Vault.3 Enter the following command: ClusterCompMgmtThis launches the Computer Management snap-in with the environment variables set so that it displays the clustered message queues.4 Expand Services and Applications, then expand Message Queuing. The Enterprise Vault virtual server queues are listed under Private Queues.
Products Applied: Enterprise Vault for Microsoft Exchange 2007 7.5, 2007 7.5 SP1, 2007 7.5 SP2
Last Updated: July 09 2008 07:39 PM GMT Expires on: 07-09-2009 Subscribe to receive critical updates about this document
Subjects: Enterprise Vault for Microsoft Exchange Administration: Advice Clustering: Mscs - Advice Msmq: Configuration
Languages: English (US)
Operating Systems: Windows 2000
Advanced Server SP3, Advanced Server SP4, Datacenter Server SP3, Datacenter Server SP4, Server SP3, Server SP4Windows Server 2003 R2,
Client Extensions installed on a machine running Outlook 2007 and Exchange System Manager (ESM) will not load
Document ID: 292462
http://support.veritas.com/docs/292462
Client Extensions installed on a machine running Outlook 2007 and Exchange System Manager (ESM) will not load
http://support.veritas.com/docs/292462
Client Extensions installed on a machine running Outlook 2007 and Exchange System Manager (ESM) will not load
Exact Error Message
The Add-in "Enterprise Vault" (C:\Program Files\Enterprise Vault\EVClient\Valkyrie.dll) cannot be loaded and has been disabled by Outlook. Please contact the Add-in manufacturer for an update. If no update is available, please uninstall the Add-in.
The Add-in "Enterprise Vault" (C:\Program Files\Enterprise Vault\EVClient\Valkyrie.dll) cannot be loaded and has been disabled by Outlook. Please contact the Add-in manufacturer for an update. If no update is available, please uninstall the Add-in.
Details:
Overview:
Enterprise Vault Client Extensions that are installed on a machine with Outlook 2007 and Exchange System Management installed will not load.
As per Microsoft Knowledge base, Microsoft does not support installing Microsoft Outlook and Microsoft Exchange Server 2003 (including Exchange System Manager), Microsoft Exchange 2000 Server (including Exchange System Manager), or Microsoft Exchange Server 5.5 on the same computer.
For more details about this limitation, please visit the following link: http://support.microsoft.com/kb/266418/en-us
Several common scenarios for the error to be displayed include the following:
Scenario 1
Exchange System Manager 2003 and Outlook 2007 are installed on the same machine.
Resolution:
1. Uninstall the Exchange System Manager on the client machine.
2. Re-install the Exchange System Manager on the client machine.
3. From a command prompt, type "fixmapi" and press "Enter". The "fixmapi" command generates no output and runs silently.
NOTE: Outlook and Microsoft Office Communicator should be closed prior to running the "fixmapi" command.
4. Restart the machine.
Scenario 2
Outlook 2007 is installed but the MAPI Profile in the Registry has become inconsistent
Resolution:
1. Open Outlook and navigate to Help -> Office Diagnostics (in Outlook 2003 this was "Detect & Repair").
2. When Office Diagnostics completes open a command prompt
Enterprise Vault Client Extensions that are installed on a machine with Outlook 2007 and Exchange System Management installed will not load.
As per Microsoft Knowledge base, Microsoft does not support installing Microsoft Outlook and Microsoft Exchange Server 2003 (including Exchange System Manager), Microsoft Exchange 2000 Server (including Exchange System Manager), or Microsoft Exchange Server 5.5 on the same computer.
For more details about this limitation, please visit the following link: http://support.microsoft.com/kb/266418/en-us
Several common scenarios for the error to be displayed include the following:
Scenario 1
Exchange System Manager 2003 and Outlook 2007 are installed on the same machine.
Resolution:
1. Uninstall the Exchange System Manager on the client machine.
2. Re-install the Exchange System Manager on the client machine.
3. From a command prompt, type "fixmapi" and press "Enter". The "fixmapi" command generates no output and runs silently.
NOTE: Outlook and Microsoft Office Communicator should be closed prior to running the "fixmapi" command.
4. Restart the machine.
Scenario 2
Outlook 2007 is installed but the MAPI Profile in the Registry has become inconsistent
Resolution:
1. Open Outlook and navigate to Help -> Office Diagnostics (in Outlook 2003 this was "Detect & Repair").
2. When Office Diagnostics completes open a command prompt
3. Type "fixmapi" and press "Enter". The "fixmapi" command generates no output and runs silently.
NOTE: Outlook and Microsoft Office Communicator should be closed prior to running the "fixmapi" command.
4. Restart the machine.
Scenario 3
The Enterprise Vault Client has not been registered correctly
Resolution:
1. Open a command prompt and navigate to "C:\Program Files\Enterprise Vault\EVClient"
2. If Enterprise Vault 7 Client or later has been installed, type "EVResetClient" and press "enter" (one of the steps taken is to re-register "Valkyrie.dll").
3. If Enterprise Vault 6 Client or earlier has been installed, type "regsvr32 Valkyrie.dll" and press "enter".
If the error still occurs or the "Valkyrie.dll" cannot be registered, reinstall the Enterprise Vault client from the installation media.
Scenario 4
Windows Desktop Search, Exchange System Manager and Outlook 2007 have been installed on the same machine
Resolution:
After installing Windows Desktop Search (Instant Search in Outlook 2007) the "Valkyrie.dll" fails to load due to inconsistencies with the Messaging Application Programming Interface (MAPI) profile in the Windows registry.
This can occur when uninstalling Windows Desktop Search 2.6 and installing Windows Desktop Search 3.0.1 without performing the required reboot.
1. Uninstall the Enterprise Vault client.
2. Uninstall Outlook and restart the machine.
3. Reinstall Outlook and restart the machine once more.
4. Install the Enterprise Vault Client
5. From a command prompt type "fixmapi" and press "Enter".
NOTE: Outlook and Microsoft Office Communicator should be closed prior to running the "fixmapi" command.
6. Restart Outlook and full functionality should be restored.
Note: In some environments running the Fixmapi utility will resolve the issue. (For more information on the Fixmapi utility refer to Microsoft article http://support.microsoft.com/kb/228457/ )
Related Documents:
http://support.veritas.com/docs/297031
Acknowledgements
Microsoft Corporation
Products Applied:
Enterprise Vault for Microsoft Exchange 2007 7.5, 2007 7.5 SP1, 2007 7.5 SP2, 6.0 SP4, 6.0 SP5, 7.0 SP1, 7.0 SP2, 7.0 SP3, 7.0 SP4
Last Updated: August 27 2008 09:59 PM GMT
Expires on: 04-30-2009
Subscribe to receive critical updates about this document
NOTE: Outlook and Microsoft Office Communicator should be closed prior to running the "fixmapi" command.
4. Restart the machine.
Scenario 3
The Enterprise Vault Client has not been registered correctly
Resolution:
1. Open a command prompt and navigate to "C:\Program Files\Enterprise Vault\EVClient"
2. If Enterprise Vault 7 Client or later has been installed, type "EVResetClient" and press "enter" (one of the steps taken is to re-register "Valkyrie.dll").
3. If Enterprise Vault 6 Client or earlier has been installed, type "regsvr32 Valkyrie.dll" and press "enter".
If the error still occurs or the "Valkyrie.dll" cannot be registered, reinstall the Enterprise Vault client from the installation media.
Scenario 4
Windows Desktop Search, Exchange System Manager and Outlook 2007 have been installed on the same machine
Resolution:
After installing Windows Desktop Search (Instant Search in Outlook 2007) the "Valkyrie.dll" fails to load due to inconsistencies with the Messaging Application Programming Interface (MAPI) profile in the Windows registry.
This can occur when uninstalling Windows Desktop Search 2.6 and installing Windows Desktop Search 3.0.1 without performing the required reboot.
1. Uninstall the Enterprise Vault client.
2. Uninstall Outlook and restart the machine.
3. Reinstall Outlook and restart the machine once more.
4. Install the Enterprise Vault Client
5. From a command prompt type "fixmapi" and press "Enter".
NOTE: Outlook and Microsoft Office Communicator should be closed prior to running the "fixmapi" command.
6. Restart Outlook and full functionality should be restored.
Note: In some environments running the Fixmapi utility will resolve the issue. (For more information on the Fixmapi utility refer to Microsoft article http://support.microsoft.com/kb/228457/ )
Related Documents:
http://support.veritas.com/docs/297031
Acknowledgements
Microsoft Corporation
Products Applied:
Enterprise Vault for Microsoft Exchange 2007 7.5, 2007 7.5 SP1, 2007 7.5 SP2, 6.0 SP4, 6.0 SP5, 7.0 SP1, 7.0 SP2, 7.0 SP3, 7.0 SP4
Last Updated: August 27 2008 09:59 PM GMT
Expires on: 04-30-2009
Subscribe to receive critical updates about this documentSubjects:
Enterprise Vault for Microsoft Exchange
Client: Ev Toolbar Icons Missing
Languages: English (US)
Operating Systems:
Windows XP Pro 5.1 SP2
Symantec World Headquarters:
20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com/,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or ftp://ftp.entsupport.symantec.com
20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com/,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or ftp://ftp.entsupport.symantec.com
Symantec Enterprise Vault 2007 Service Pack 4 (SP4) - Installation Media (Build 7.5.4.2534)
http://seer.entsupport.symantec.com/docs/308768.htm
Symantec Enterprise Vault 2007 Service Pack 4 (SP4) - Installation Media (Build 7.5.4.2534)
This download contains the install kit for Symantec Enterprise Vault 2007 Service Pack 4.
Information
Service Pack 4 for Enterprise Vault 2007 should be considered a recommended update for the following products:
Symantec Enterprise Vault for Microsoft Exchange
Symantec Enterprise Vault for Lotus Domino
Symantec Enterprise Vault for File System Archiving
Contents
This release includes the following key updates:
FSAUtility update
Improved Performance of the Lotus Mailbox Task
FSA Cluster support on Windows Server 2008
For further information, consult the file Updates_EN.htm included in this download or online at http://entsupport.symantec.com/docs/308842
Download Now - 293008 KFile Name: EV2007_SP4_2534_308768.zip File Type: Install
Symantec Enterprise Vault 2007 Service Pack 4 (SP4) - Installation Media (Build 7.5.4.2534)
This download contains the install kit for Symantec Enterprise Vault 2007 Service Pack 4.
Information
Service Pack 4 for Enterprise Vault 2007 should be considered a recommended update for the following products:
Symantec Enterprise Vault for Microsoft Exchange
Symantec Enterprise Vault for Lotus Domino
Symantec Enterprise Vault for File System Archiving
Contents
This release includes the following key updates:
FSAUtility update
Improved Performance of the Lotus Mailbox Task
FSA Cluster support on Windows Server 2008
For further information, consult the file Updates_EN.htm included in this download or online at http://entsupport.symantec.com/docs/308842
Download Now - 293008 KFile Name: EV2007_SP4_2534_308768.zip File Type: Install
Tuesday, September 23, 2008
NEW! Enterprise Vault 2007 for Exchange Certification Exam
New Exam Coming in 2008!
Although each product varies in complexity and depth, all certification exams are created specifically for customers and cover core elements measuring technical knowledge against factors such as installation, configuration, product administration, day-to-day maintenance, and troubleshooting.This program consists of a technical exam at a product/version level that validates that the successful candidate has important knowledge and skills necessary to plan, deploy, manage, and monitor Symantec Enterprise Vault 2007 for Exchange.
For the Enterprise Vault certification exam, no specific version of Exchange is emphasized.
To achieve this level of certification, candidates must pass the technical exam and accept the Symantec Certification Agreement.
Suggested Preparation
Below includes the recommended preparation to achieve this level of expertise.- Exam Objectives
- Sample Exam (Coming early November 2008)
- The study guide is targeted for those who have attended the recommended 5 day training course. This self-study guide summarizes the key lessons and topics in the corresponding certification exam.
- Recommended minimum 9 – 12 months working with Windows and Symantec Enterprise Vault 2007
- Knowledge of Windows system and network administration
- Administrator-level knowledge of Microsoft Windows operating systems
- Basic understanding of implications and ramifications of archiving and compliance
- Basic understanding of database concepts
- Basic understanding of storage concepts
- Product documentation for Symantec Enterprise Vault 2007
- Symantec Web sites (Symantec Technology Network, Backup Exec Tech Center, Symantec Support, and product pages)
http://www.symantec.com/business/theme.jsp?themeid=yellowbooks
http://edm.symantec.com/enterprisevault/
http://www.symantec.com/business/support
http://www.symantec.com/business/products/overview.jsp?pcid=2244&pvid=322_1 http://www.symantec.com/business/support/index.jsp - Preparation Time for Certification Exams
- For information on the format of our exams, please visit our Certification FAQs
Recommended Courses:
Other Recommended Courses:
Note: Be cautioned that, attendance in a training course does not guarantee passage of a certification exam.
Contact the Symantec Certification Team
Can't find what you're looking for? If you have questions or need further assistance, send an email to customer_certifications@symantec.com."Insufficient Resources" and Symantec Enterprise Vault
Insufficient Resources" and Symantec Enterprise Vault
This is an extension to last year's blog about Insufficient Resources.
Item 6 covers when the MSMQ message is too large.
The first thing that needs to be mentioned is that we need to distinguish between the size of the message and the size of the message body. The 4MB size limit includes all the information needed for delivery as well as the data you are trying to deliver. The message is structured as follows:- Base header (priority, packet size, TTRQ,...)
- User header (sender QM's GUID, destination QM's GUID, sent time, message GUID, destination queue, admin queue,...)
- Property header (Ack mode, correlation ID, class, privacy level, message body,...)
The overhead (everything apart from the body) is normally just a few hundred bytes but some properties, such as the message label, can be that big on their own. Some allowance, therefore, needs to be made by the application to ensure the message body can fit into the remaining space.
Symantec's Enterprise Vault has one approach to avoiding this problem. In the registry is a value that caps the maximum size of messages that the application will generate:
HKLM\Software\KVS\Enterprise Vault\Storage\MaxMSMQMessageSize
This is a DWORD and is measured in bytes so if, for example, you wanted a maximum size of 3MB then assign a value of 3145728.
If you find that Enterprise Vault logs "Insufficient Resources" exceptions and there are not bazillions of messages in the system (the usual cause of the exception) then you may want to experiment with reducing this value. It could be that the overhead that MSMQ creates exceeds 1,024 bytes.
Published Thursday, March 08, 2007 1:25 PM by JohnBrea
Comment Notification
If you would like to receive an email when updates are made to this post, please register here
Subscribe to this post's comments using RSS
Comments
Saturday, September 20, 2008
instead of buying why not swap your stuff
instead of buying new stuff like DVD, CDs, Video games, why not swap them? you can do it from this site:
http://www.swaptree.com
http://www.swaptree.com
Tuesday, September 16, 2008
eva 8100
HP StorageWorks 8100 Enterprise Virtual Array
http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&cc=us&taskId=101&contentType=SupportManual&docIndexId=179911&prodSeriesId=3664583&prodTypeId=12169#4
http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&cc=us&taskId=101&prodClassId=-1&contentType=SupportManual&docIndexId=64180&prodTypeId=12169&prodSeriesId=3664583
HP StorageWorks SAN
http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&locale=en_US&docIndexId=179911&taskId=101&prodTypeId=12169&prodSeriesId=406734
HP StorageWorks
SAN design reference guide
http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c00403562/c00403562.pdf
http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&cc=us&taskId=101&contentType=SupportManual&docIndexId=179911&prodSeriesId=3664583&prodTypeId=12169#4
http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&cc=us&taskId=101&prodClassId=-1&contentType=SupportManual&docIndexId=64180&prodTypeId=12169&prodSeriesId=3664583
HP StorageWorks SAN
http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&locale=en_US&docIndexId=179911&taskId=101&prodTypeId=12169&prodSeriesId=406734
HP StorageWorks
SAN design reference guide
http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c00403562/c00403562.pdf
Subscribe to:
Posts (Atom)
# The message format has changed in MSMQ 4.0 so re-test all your applications
http://blogs.msdn.com/johnbreakwell/archive/2007/03/08/insufficient-resources-and-symantec-enterprise-vault.aspx