Archive Manager 5.0. How to Diagnose & Troubleshoot. Spencer Pelley Technical Team Lead May 2014

Transcription

1 Archive Manager 5.0 How to Diagnose & Troubleshoot Spencer Pelley Technical Team Lead May 2014

2 Learning Objectives How To Diagnose & Troubleshoot Upon completion of this lesson, the student should have an understanding of the product use case, the product components, and be able to troubleshoot and collect the correct diagnostic material to supply to support.

3 Product Overview Architecture Dell Archive Manager lets become a true asset for the organization. Archive Manager has been specifically designed to meet the needs of these key stakeholders by enabling organizations to automatically capture, retrieve and analyze all messages and attachments that are processed by the system. The product has five key components: Website(s) Services Databases Attachment Store Index The product also has many additional Tools and Utilities, such as: Recovery Manager for Exchange Archive Manager Edition Retention abilities PST Importer Search Exporter Remote ESM

4 High Level

5 Archive Manager Website Single point of access for authenticated users to see all of their archived items. Single point of access for administrators to perform searches across all items in the archive. Can be installed on the same server as the Archive Manager services and/or the SQL database or on a separate server. Can have multiple instances of the website all pointing to the same Archive Manager instance. Can use Windows authentication to appear seamless to end users Forms authentication can also be used to make it available for users who are not authenticated to the domain. Provides a means to administer the components of Archive Manager Provides a means to control access within Archive Manager Offers a method for 3 rd party application integration via.net API s Has additional Virtual Directories to allow Tools and Utilities to connect using different authentication methods and configurations

6 Troubleshooting the Website Supported on IIS6 (W2K3), IIS7.5 (W2K8R2), IIS8 (W2K12), and IIS8.5 (W2K12R2) Note: Windows Server 2003 will not be supported in the next release. When using IIS6 the Authentication method must match between the Directory Security tab and the ASP.NET tab. Multiple websites can be setup on the same IIS installation or across multiple machines. Log files are saved in C:\Windows\System32\LogFiles on W2K3 and in %SystemDrive%\inetpub\logs\LogFiles on W2K8 but these files can be redirected in the properties of the website. Redirecting them is a good idea when troubleshooting website issues as the logs will only contain information that pertains to Archive Manager and not all of IIS. Additional Web Logs are also saved into the Logs directory configurable in Configuration Console IIS is not installed by default on all W2K8 or W2K12 machines, be sure to install this prerequisite before running the Archive Software Manager Support Installer. For W2K12 it is highly recommended that the.net

7 Services Store Manager refers to GroupWise Store Manager or Exchange Store Manager Directory Connector refers to Active Directory Connector or GroupWise Directory Connector

8 Services continued Archive Manager has 7 services by default. Two of these services will be different depending when installing for Exchange vs installing for GroupWise. Archive Manager Active Directory Connector Service; Syncs Archive Manager s login account and mailbox information with Active Directory Archive Manager Alert Service; Runs SQL queries on the Archive Manager database, WMI queries on your server and sends Alert s. Archive Manager Data Load Service; Loads XML data files from the file system into the Archive Manager database, and processes MAPI, POP3 and IMAP journal mailboxes.. Archive Manager Exchange Store Manager Service; Scans Exchange mailboxes for new messages and data, adding them to the archive or linking them to folders.

9 Services continued Archive Manager Full Text Index Service; Builds an index of Archive Manager s stored messages and attachments for efficient key word searching. Archive Manager Full Text Search Service; provides access to full text searching of Archive Manager s stored messages and attachments. Archive Manager GroupWise Store Manager Service; Scans GroupWise mailboxes for new messages and data, adding them to the archive or linking them to folders. Archive Manager GroupWise Directory Connector Service; Syncs Archive Manager s login account and mailbox information with NDS. Archive Manager Message Retention Policy Service; Implements the retention policy rules on Archive Manager s database.

10 Troubleshooting Services All accounts running Archive Manager services need to be a member of the Local Administrators group on the server. They also need to have the Logon as a Service permission and this permission is sometimes restricted via GPO. All services have a config file (file_name.exe.config) which should only be updated if necessary. Any configurations needed to change the way a service works should be added in the Configuration Console (explained below). All services also have a log file which records all transactions done by the service. If there is an error when the service is running it will log all details about its current process here. The location of these log files is determined in the Configuration Console > General Settings for the current version. Older versions log to the default installation directory (C:\Program Files\Quest Software\ArchiveManager) and this can be manipulated by updating AfterMail.Logging.Config.XML. The account running the Active Directory Connector (ADC)service needs to have the ability to read all items in Active Directory and this is often restricted by Network Administrators. If this account cannot see all items

11 Troubleshooting Services continued The account running the Alert Service needs to be able to run SQL and WMI queries. By default the account running this service is the ArchiveMgr_Service account which is a local admin and db_owner on the Archive Manager databases so it should have the permissions it needs. The Alert Service logs to the Event Viewer as well as it s own log file (AlertService.wlog) The account running the Data Loader (DL) service (default: ArchiveMgr_Journal) needs to have full access permissions to all Export directories (additional Export directories are specified under Administration on the website). It also needs to have Exchange View Only Administrator (2003 and 2007) or View Only Organization Management (2010 and 2013) permissions in Exchange. This account also needs to have the Receive-As permissions to the Journal mailbox in Exchange. The DL service will log to Event Viewer and it s own log file (DL.wlog). The account running the Exchange Store Manager (ESM) service (default: ArchiveMgr_ESM) needs to have Receive-As permissions to all mailboxes in Exchange as well as Exchange View Only Administrator (2003 and 2007) or View Only Organization Management (2010 and 2013) permissions.

12 Troubleshooting Services continued Both the ArchiveMgr_Journal and the ArchiveMgr_ESM accounts must not be a member of Domain Administrators or Enterprise Administrators groups as these groups have a specific Deny to Send- As and Receive-As in Exchange. The account running the Full Text Index (FTI) service needs to have full permissions to all Index locations which are specified under Administration > Index Rollover Policy in the website. The FTI service logs to Event Viewer and it s own log file (FTI.wlog). It also spawns RemotingHost.exe threads for the current version and FTIAttachmentWorker.exe threads for the older versions. Each of these threads creates their own logs (RemotingHost32.exe.wlog). The account running the Full Text Search (FTS) service needs to have read permissions to all Index locations which are specified under Administration > Index Rollover Policy in the website or in Config Editor for older versions. The FTS service logs to Event Viewer and it s own log file (FTS.wlog). The account that runs the GroupWise Store Manager (GSM) service needs to be a local administrator on the Archive Manager server. The NDS account specified in the Configuration Console Software and Support the Trusted App are used for accessing GroupWise and NDS resources.

13 Troubleshooting Services continued The account running the GroupWise Directory Connector (GDC) service needs to be a local administrator on the Archive Manager server. The NDS account specified in Configuration Console and the Trusted App are used for accessing GroupWise and NDS resources. The GDC service logs to Event Viewer and it s own log file (GDC.wlog) The account running the Message Retention Policy service (aka Retention) needs to be a local administrator. The Retention service logs to Event Viewer and it s own log file (RPS.wlog also see: RetentionWebService.wlog). If the Archive Manager services are installed on the same machine as the SQL server that houses the Archive Manager database then the services should be made dependent on the SQL server service. This is because the SQL server service takes awhile to start after a server reboot and this will cause some of the Archive Manager services to fail to start as they depend on the SQL Server service.

14 Archive Manager databases There are two Archive Manager databases installed on the SQL server, the ArchiveManager database and the AfterMail_TEMP database. ArchiveManager This database is the main repository for all messages that have been exported from Exchange or GroupWise. It also houses all linking to determine which mailboxes and which folders these messages are associated to and to enforce security on these messages. This database can be renamed so it may be necessary to ask the customer which database is the Archive Manager database. Typical alternate names are: AM, Archive, Archive AfterMail_TEMP This database is used to house search results when users are searching via the website(s) as well as Retention search results when the retention service runs the configured retention policies. The database name can not change.

15 Troubleshooting Database issues SQL 2005 and SQL 2008 and SQL 2012 are currently supported (see Release Notes for exact versions) SQL 2000 support was dropped after version The Archive Manager server uses the SQL Native Client to communicate with SQL. A quick test to be sure that this client is working is to create a Test.UDL file on the Archive Manager server (just create a test.txt file with Notepad and rename the extension to UDL). When you double click on this file it will open up a small utility, choose the Native Client on the first tab, enter credentials if required, and click the Test button. If it does not work then start looking at the Native Client. All Archive Manager service accounts need to be listed under Security > Logins in SQL Management Studio with db_owner and public role membership for the ArchiveManager database and the AfterMail_TEMP database. The Default Schema for each of these accounts must be dbo or Searching will have issues and Retention will not work properly and will throw errors about its inability to drop tables. If a customer attempted to manually apply permissions Software then Support you may run into an issue where you may need to remove the Archive

16 Troubleshooting Database issues The collation of the ArchiveManager database is important so be sure that it is set to SQL_Latin1_General_CP1_CI_AS Validate the Server Authentication Mode as often this is set to Windows Authentication only and you re trying to use an SA account. The maximum number of connections is also configurable (seen on the Connections tab of the server Properties in SSMS) so be sure that this is not set too low. A good working knowledge of SQL is required to support Archive Manager.

17 Attachment Store During the initial installation of Archive Manager an Attachment Store is created. This Attachment Store is actually a folder on disk with the default name of Data and it has a share name which by default is ArchiveManagerAttachment. All attachments to messages which have been exported from Exchange or GroupWise will reside here under one of the directories that are created. The directories are created in a sequential order starting with 000\000\000\000 for the first attachment ingested and incrementing upwards as new attachments are ingested. You can determine the file location of an attachment with it s AttachmentFileID like so: If the AttachmentFileID is then the file on disk will be in 000\000\003\844. It is possible to have multiple Attachment Stores but only one can be active at any given time. Additional Attachment Stores can be specified in the website under Administration > Storage Location which is a reflection of the dbo.storagelocation table in the ArchiveManager database. The Archive Manager Service accounts need to have access to this directory and share.

18 Troubleshooting the Attachment Store If the Attachment Store location as specified in the website and dbo.storagelocation is invalid then you will see errors in Event Viewer as well as the DataLoader.exe.log file. These errors will indicate that the network location cannot be found. Verify that the correct Storage Type is specified and that the connection string is in the correct format for the Storage Type and that the path specified is valid. Only one Storage Location can be the default at any given time and the Archive Manager accounts need full access to the share for the Attachment Store as well as the Data directory itself.

19 Troubleshooting the Attachment Store The Storage Location section also has a Storage Migration tab. Here you can migrate your attachments from one location to another. The blue, green, and red boxes at the bottom of the screen provide a quick overview of the move progress. Here you can do all of the things you can do directly in the SQL table as well as moving/migrating attachments and adding new Storage Locations. Splitting the attachment store up into multiple

20 Installer The Archive Manager installer also has tabs for documentation, prerequisites, contacts, etc. The Installer should be run with a Domain Admin account. During the install you can choose which components to install and which to leave out. This is useful when installing an Archive Manager website on a separate server.

21 Troubleshooting the Installer Run the Installer as a Domain Admin account to avoid permission issues. The account running the Installer also needs to have permissions to create Databases in SQL. The ArchiveManager database is called ArchiveManager by default but you can change this. It is good practice to stop all Archive Manager services before running an Upgrade as a non responding service will not be properly upgraded. The Installer does not log by default so if it errors then run the MSI at a command prompt with this: /l* logfilename.log Most Installer issues are due to permissions.

22 Index The Index allows for the search of items based on key words, phrases, word relationships, etc. in messages and in attachments. Attachment indexing is accomplished via ifilters. The Archive Manager Index is a Lucene database. During the initial installation of Archive Manager a set of disks are selected to be used to house parts of the Full Text Index (aka FTI). These disks (max 4) should be as fast as possible as they are accessed often and will have a direct impact on searching performance. Detailed information on the index and how to implement it are found on page 44 of the 5.0 Admin Guide. This info is found on page 69 of the previous versions Admin Guides. Historic versions of Archive Manager (4.5 and older) simply have a single location for the entire Index which is specified in the Configuration Editor. This old index style was prone to failure in the form of corruption and often required extensive maintenance.

23 Troubleshooting the Index With the current version of Archive Manager the Index can be split across multiple locations on disk and permissions to those locations needs to be maintained. If permissions are changed to any of these locations then indexing and searching will be affected. You can view the health of the overall Index or the health of each piece in the Archive Manager website under Administration. Here you will find three sections; Index Dashboard, Index Operation Log, and Index Rollover Policies. These correspond to the dbo.ftpartition, dbo.ftoplog, and dbo.ftrolloverpolicy tables in the database. The Index Dashboard will give you a view to the health of the index pieces and allow you to run process on those items such as Itemizing, Moving, and Splitting. It will also show you the size on disk and locations, etc. The Index Operation Log shows all scheduled operations, operations currently in progress, and completed operations and provides a method to search through them. The Index Rollover Policies is where you configure how the index

24 Configuration Console The Configuration Console is used to configure most of the settings that Archive Manager requires immediately after installation and occasionally during operations when a significant change needs to be made. Here you can add or update the License file (.ASC), change paths used for operations, edit the ability to connect to additional Domains, etc.

25 Configuration Console continued The Advanced Settings section will look very familiar to the Configuration Editor used in previous versions of Archive Manager. These items are stored in dbo.config in the database The Advanced Settings section contains configuration items for the services as well as some Stored Procedures. Items can be added and edited here but should only be done if you fully understand the implications of doing so as they can have adverse effects on Archive Manager. There are hundreds of potential Configuration Items which are generally used by Support when troubleshooting issues or by Development when new methods are created. The items that are listed here by default are self-explanatory such as paths to components, number of threads, etc.

26 Exchange Utility The Exchange Utility is used to perform one-time operations to items in Exchange mailboxes such as: Creating the Archive Manager folder in Outlook Installing the Outlook form Update Archive Manager URL Reconstruct Stripped Messages Update Stripped Message CheckSums This utility should always be Run-As the account that is running the Archive Manager Exchange Store Manager Service (default: ArchiveMgr_ESM). It is found in the Archive Manager installation directory.

27 Exchange Utility continued When using the Exchange Utility (sometimes referred to as the EU) the first thing you will need to do it to Get Mailboxes which will be the mailboxes that you wish to perform an action on. When you choose to Get Mailboxes you will have the ability to choose them by one or more criteria as shown here.

28 Troubleshooting the Exchange Utility This tool always should be run as the ArchiveMgr_ESM account (or the account running the ESM service). If it is not run as the ESM service then you will see it run and will not throw any errors but it will also not do the expected tasks. The Exchange Utility is run from the Archive Manager server by default but can be copied to another server and run from there if required. Running the Exchange Utility against multiple mailboxes simultaneously can cause the threads to slow down or potentially hang, it is always a good idea to run it against a small number of mailboxes first (2 or 3) as a test and increase as the specific environment will allow. Also keep in mind Exchange Throttling as well as this may prevent the EU from running properly after the throttling threshold is hit. The Exchange Utility creates a log in the Logs directory called ExchangeUtility.wlog It also has a config file (Exchange Utility.exe.config) where you can add specific variables to manipulate the way this tool works. This is most commonly used when working with Exchange servers and accounts in different domains.

29 Search Exporter The Search Exporter is a tool which used to export the results of a search from the website. This tools is useful for ediscovery and legal discovery purposes. It first needs to be downloaded from the Archive Manager website and installed on the local machine where the search is being performed and the user performing the export needs permissions to do so (Export security action). It connects to Web Services under the Archive Manager website and can export to PST, XML, HTML, and MIME formats

30 Troubleshooting the Search Exporter This tool connects to the Default Instance under the Archive Manager website, which is also known as Web Services. The Authentication Mode in the Default Instance needs to be set the same between the Directory Security tab and the ASP.NET tab (IIS6). Often it is required to use Forms Authentication if Windows credentials cannot be passed. Validate that your Security Role in Archive Manager has the appropriate Security Actions set to allow search exporting. Often you will run into an issue when exporting to PST files if you have a GPO that disallows PST file creation and/or PST file growth. You can look for these items in the local registry of the workstation you are running the search exports from: DisablePST and DisablePSTgrow. This tool requires Outlook so this cannot be installed on the Archive Manager server. It should be noted that exporting to PST is significantly faster than exporting to any other format.

31 PST Import Wizard The PST Import Wizard (aka The PST Importer) can be used to merge the contents of existing PST files into Archive Manager mailboxes. It first needs to be downloaded from the Archive Manager website and installed on the local machine where the PST This tool can scan multiple drives and import Import multiple is being PST performed. files at once. You can choose to merge the contents Launch of the the tool PST from files with Start the users existing Archive Manager mailbox All Programs or you can Dell choose Archive to create a pseudo root and have the PST contents Manager displayed PST Importer. under that. This tool connects to Web Services under the Archive Manager website.

32 Troubleshooting the PST Importer This tool connects to the Default Instance under the Archive Manager website, which is also known as Web Services. The Authentication Mode in the Default Instance needs to be set the same between the Directory Security tab and the ASP.NET tab (for IIS 6). Often it is required to use Forms Authentication if Windows credentials cannot be passed. A common issue is a missing prerequisite; C Runtime. Often people will have the 2005 or the 2008 version installed which does not work properly. The PST Importer can only look for PST files on drives which are local or mapped with a drive letter. This tool logs to PSTImporter.wlog which is in the same directory as the executable. It also creates a separate wlog for each PST that it processes and saves these in the Log Directory that you specify when performing the import. This tool requires Outlook so this cannot be installed on the Archive Manager server.

33 Outlook Offline Client The Archive Manager Offline Client is a plugin for Outlook which allows for offline access to archived mail. It is downloaded from the Archive Manager website and installed on the users workstation where offline The Offline Client also requires that a access template to Archive be added Manager to Group Policy to provide the Offline Client with messages connection is required. information and Offline Access must be enabled in Archive Manager. This tool is configurable to allow the user to specify which folders they would like to have offline access to and provided the ability to automatically switch to Cached Mode if required. Age limits can also be set to avoid the synchronization to too many items

34 Troubleshooting the Offline Client The Offline Client does not work with Outlook 2010 previous to version 4.7, this is one of the most common issues with this tool. Only specific versions of Outlook are supported and only on specific operating systems so always check the Release Notes to be sure. The more recent versions of the Offline Client support most versions of Outlook in 32 and 64 bit. The Offline Client connects to the default instance under the Archive Manager website, more specifically; which is pushed via GPO (or manual registry entry). There are a number of steps required for this tool to function so follow the Admin Guide closely (starting on page 23) to be sure none are missed. The offline client puts a heavy load on the IIS server where it is connecting and can slow the Outlook it is installed with so this tool should only be used when required.

35 Retention Policy Editor The Archive Manager Retention Policy Editor lets you specify a retention period for the archived messages using retention rules, or policies and to temporarily stop deleting expired messages during amount of drive space the archived messages and investigations. attachments consume. This is useful to control the amount The Delete policy controls which items are removed of items and retained when for and the Keep policy controls which items are kept legal regardless purposes of and to subsequent Delete policies. control the

36 Troubleshooting the RPE The Retention Policy Editor (RPE) controls what the Retention service will act upon but caution should be used as this is a permanent change and the only undo option is a restore from backup. The Retention Policy Service will run each policy in order from top to bottom. Any items that are affected by a policy will not be affected by any subsequent policies. This can cause confusion as some people will expect a policy lower in the list to remove an item, however it will not if that item is affected by a policy closer to the beginning of the list. It is good practice to have all the Keep (green) policies above all the Delete (red) policies so that nothing will be Deleted when it was expected to be Kept. Retention has the ability to remove many (millions) of items in a single pass however, the hardware that the Retention service is running on (as well as IIS and SQL) will mostly likely not be able to handle the load. The RPE has the ability to do a dry run to see how many items will be removed by retention, this is known as safe mode and it a good test to determine what the Retention Software policy Support should be. In general Retention can remove thousands to hundreds

37 Archive Retrieve for BlackBerry The Archive Retrieve for BlackBerry tool allows Archive Manager users with a BlackBerry device to read their archived from the BlackBerry without using a Web interface. When this tool is in place, users do not have to follow a link to the Archive Manager Web Site to retrieve More recent versions of archived Archive Retrieve mail. Archived support messages SSL connections. appear on Older versions did not, check the BlackBerry the Release device Notes in the for the same current format as version. messages that have not been archived. The machine running Archive Retrieve must be the same machine as the BlackBerry Enterprise Server, which must be a separate server from the Exchange Server. This tool is configurable to allow for maximum cache sizes, log level and path, etc. by way of the Archive Retrieve Editor. This tool also has a Performance Counter which allows the Administrator to monitor items such as number of messages processed, message bytes/sec, cache size, etc.

38 Troubleshooting the BES utility BES 5.0, 4.1.4a, and have been explicitly tested. The server OS must be 32-bit for BES 4.1.X. BES 5 has been tested on a 64-bit OS with 32-bit software. The log files can grow rather large on the BES server as this tool passes information so you may need to redirect the log eslewhere. Do to so navigate to c:\program files\dell\archivemanager\archive Retrieve folder and run the file named ArchiveRetrieveConfig.exe. It may be required to stop all BES services prior to installing this tool. Of course, verify that this is OK with the customer first as this will be customer impacting. Keep in mind that by default BES will only sync a low number of days to the BlackBerry devices so if your Archive Manager Strip Policies are set for a greater number of days then the default BES policy then there is no need to have this tool installed. Example; if your Archive Manager Strip Policy is set to 180 days, and your BES is only synchronizing 30 days of to the devices then you do not need this tool. You would only need this if your Archive Manager Strip Policy was set to 15 days and your BES sync was still 30 days, then you would have 15 days of stubbed items to include.

39 Remote ESM The Remote ESM extracts data out of Exchange so that it can be loaded into Archive Manager. The Remote ESM can be used if your Exchange Server is in a different location than your Archive Manager server and you have low network bandwidth. The Remote ESM needs to be configured to only crawl specific Exchange servers This tool provides the ability and to store it will the need archived a connection items locally string to until a predetermined time of communicate day (usually during with the low Archive network Manager usage hours) then bulk load database them to the and Archive related Manager directories. server via a File System Data Loader or a VB script or 3rd party file mover.

40 Troubleshooting the Remote ESM The Remote ESM logs to the same directory as the executable. Sometimes the Remote ESM Editor will not save the ESM group you specify and it ll default back to default. If this happens then you will need to manually set this group in the Archive Exchange Store Manager Service.exe.config file by opening this file and locating the ESMgroup section. When using this tool you have a couple of options on how you want to get the created XML files into the ArchiveManager database. You can use a local directory to store the XML files and then move them to the Export directory on the main Archive Manager server via batch file, or VBS script, or 3rd party app. This will allow you to control when the network traffic occurs. You could also create another File System Data Loader in the Archive Manager website and point it to this remote location where the XML s are housed. This will also let you configure when to allow this network traffic to happen. A third but less ideal option would be to send all the XML s that the RemoteESM creates directly to the Export directory on the main Archive Manager server. This is not ideal as you cannot control the time of day this traffic happens and is generally much slower as each item needs to establish a connection.

41 Alert Service Editor The Archive Manager Alert Service Editor allows you to run SQL queries on the Archive Manager database, and WMI queries on your server. The administrator can configure the Alert Service Editor to instruct the Alert Service to send out alerts based on the results of the query. For example, the administrator can query on the status of the services (running or stopped), the administrator can configure the Alert Service Editor to have the Alert Service send out an when the services are stopped

42 Troubleshooting the Alert Service Editor If the Alert service is sending out alerts erroneously then have a look at the dbo.alertqueries table in the ArchiveManager database to see if the operators and thresholds are saved correctly as sometimes they may not be. There is also a known issue where the threshold for a Service is saved as 1 but it should be saved as 0 and this causes an Alert constantly even when it should not be sending one. See SOL77814 for resolution.

43 URL Redirect When multiple Archive Manager servers are deployed, the Archive Manager URL Redirect website allows users to go to a single URL that redirects them to the Archive Manager server that has their active login. If a user has more than one active login, the user can select the desired Archive Manager server from a list of servers with active logins. Users with Forms authentication need to enter a user name on the URL Redirect page the first time they log in, and a user name and password to log in to Archive Manager. They will have to do this periodically when they log in after that. Users with Windows authentication do not need to enter a user name when they go to the URL Redirect page. Depending upon whether user authentication is set to prompt for a user name and password,

44 Troubleshooting the URL Redirector The RedirectConfig.xml file contains the configuration you will need to configure. This file is found in the directory where you unzipped the UrlRedirect.zip file on the IIS server used for this redirection. It s use is very basic and troubleshooting this tool is the same as troubleshooting a website (example: inetmgr, IIS logs, etc) but keep in mind that the URL for this should be published in DNS and end users will need to know that they need to go to that URL.

45 Archive Manager Software Development Kit - SDK The Archive Manager SDK is provided to allow customers to write applications that directly interface with the archive. Dell Support does not provide support for using this SDK or creating/supporting a third party application

46 Search Client The Search Client is not available from the Archive Manager website, it needs to be provided by Support after a Support case has been created. Availability will be limited and it is not a supported tool as it was created for the 4.2 release of Archive Manager (circa 2009 and was never officially released). This tool is also known as the Mass Tagging Tool as it has the ability to search for items in Archive Manager and tag all the search results with an existing Message Tag for future searching or for use with Retention

47 Troubleshooting the Search Client This tool has the ability to create Tags however this should not be used, instead create the Tags in the Archive Manager website. The Search Client will be able to use those already created tags. Mass-tagging can take a significant amount of time so set the expectation with the customer that tagging a large amount of items can take hours or days (multiple days if tagging a large number). It may be more feasible to narrow the search down and apply a Tag to a smaller number of items at a time. This tool logs to the internal-errors.log file which is in the same directory as the executable.

48 Recovery Manager for Exchange Archive Manager Edition Recovery Manager for Exchange is a separate piece of software which is downloaded from support.quest.com and the license is what controls the available features. Customers who have a valid Archive Manager support contract are entitled to RME-AD at no extra charge. This tool is used to search for items in Archive Manager and has the ability to export items to PST, or back to Exchange and retain

49 Troubleshooting RME the AD edition This is the full version of the RME software but its features are restricted by the license file. This product comes with its own set of documents and should be referenced to learn its features and uses. RME has the ability to create extended logging which is very detailed and can take up a lot of disk space. Extended logging is set under Settings > Logging in RME. Reference: &category=solutions&skb=1 &category=solutions&skb=1

50 Archive Manager Directories During the initial installation of Archive Manager there are directories created to house different items for Archive Manager, they are as follows: Data This is the Attachment Store and explained earlier in this file. DL This folder contains a wlog for each MAPI DataLoader for each day up to 7 days. This is useful when troubleshooting issues with the Journal mailbox. Error Any XML file that the File System Data Loader cannot ingest into SQL is moved to this folder. You can open this folder to get an idea of how many items were not able to be ingested. Items can be moved from this folder back to the Export folder to try to reprocess them. ESM - This folder contains a wlog for each ESM enabled mailbox for up to 7 days. This is useful when troubleshooting issues with individual users mailboxes. Exclusion Any items which are not ingested into SQL because of an Exclusion Rule are housed here.

51 Archive Manager Directories continued Export This is the directory where XML s are created by the ESM service and the MAPI DL service. The File System Data Loader is responsible for clearing the XML s out of this directory and ingesting them into SQL. FullText This is a share which is used during searching and during Retention runs. This share is usually located on the SQL server to allow the SQL server service to bulk upload to it. Index There can be multiple directories created to house the Index partitions both for Messages and for Attachments. Permissions for these directories need to be maintained and drive space should be monitored.

52 Summary In this lesson we learned: What Archive Manager is and who uses it What all the services do How the websites work What the database looks like and how it works What the Attachment Store is and how it works What the Index is and how it works What all the add-on tools look like and how they work What the working directories are for and how they re used We also learned how to troubleshoot each of the above

53 Thank you