Maintenance and Repair - Revision history

Bmeyn at 10:26, 15 June 2015

2015-06-15T10:26:15Z

Bmeyn at 10:24, 15 June 2015

2015-06-15T10:24:42Z

Dweuthen at 12:41, 12 June 2015

2015-06-12T12:41:02Z

Dweuthen at 17:06, 25 June 2014

2014-06-25T17:06:20Z

Admin: /* Logical Verification */

2012-05-09T16:38:15Z

Logical Verification

Admin: /* Databases */

2012-05-09T16:37:52Z

Databases

Admin at 16:35, 9 May 2012

2012-05-09T16:35:18Z

Admin at 08:54, 12 August 2011

2011-08-12T08:54:11Z

Admin at 08:53, 12 August 2011

2011-08-12T08:53:40Z

Admin at 13:06, 20 October 2010

2010-10-20T13:06:27Z

@@ Line 4: / Line 4: @@
 == Archive Stores ==
-The commands described further in this article can be executed by a MailStore administrator through the MailStore Client under ''Administrative Tools > Storage > Storage Locations'', the [[MailStore Server Management Shell|Management Shell]] or scheduled as a [[Jobs|Job]].
+The commands described below can be executed by a MailStore administrator through the MailStore Client under ''Administrative Tools > Storage > Storage Locations'', the [[MailStore Server Management Shell|Management Shell]] or scheduled as a [[Jobs|Job]].
-=== Determine the archive store ID ===
+For these commands the ID of an archive store often needs to be specified as parameter <tt>id</tt>. You can find these IDs at ''Administrative Tools > Storage > Storage Locations'' in the row ''ID'' of the table ''Archive Stores''.
 [[File:Maintenance_repair_01.png|500px|center]]
 Alternatively, you can use the Management API command <tt>GetStores</tt>, for example at the [[MailStore Server Management Shell|Management Shell]], to get a list of all archive stores.

@@ Line 1: / Line 1: @@
-MailStore products are developed to require minimal administrative work. Although it is advisable to execute some maintenance tasks from time to time in order to ensure data integrity of the archive.
+MailStore products are developed to require minimal administrative work. It is advisable nonetheless to run some maintenance tasks from time to time in order to ensure the archive's data integrity.
-Occasionally, however, errors do occur due to system crashes or accidental manipulation of the file structure, for example. This section will provide the information necessary to perform certain maintenance and repair works without having to contact MailStore Support (for example if some contents of the archive becomes inaccessible because of such an error).
+Another reason to use the maintenance and repair facilities can be errors that do occasionally occur because of system crashes or accidental manipulation of the file structure, for example, due to which some contents of the archive may have become inaccessible. This section will provide the information necessary to perform certain maintenance and repair tasks without having to contact MailStore Support.
 == Archive Stores ==
-The commands described below can be executed by a MailStore administrator through MailStore Client under ''Administrative Tools'' > ''Storage'' > ''Storage Locations'', the [[MailStore Server Management Shell|Management Shell]] or based on a scheduled as a [[Jobs|Job]].
+The commands described further in this article can be executed by a MailStore administrator through the MailStore Client under ''Administrative Tools > Storage > Storage Locations'', the [[MailStore Server Management Shell|Management Shell]] or scheduled as a [[Jobs|Job]].
 === Check Data Integrity ===
-A data integrity check is used to determine if all emails located in MailStore are still complete and in their original state. For example, if a content file (.dat) was modified by hand, this will be censured by logical verification.  Use the Management API command <tt>VerifyStore</tt> to check a single archive store. Replace the number 1 with the actual number of the archive store to be verified. Use the Management API command <tt>VerifyStores</tt> to check all archive stores. For both commands, the parameter <tt>includeIndexes</tt> controls whether the full text indexes should be included in the check routine.
+A data integrity check is used to determine if all emails located in MailStore are still complete and in their original state. For example, if a content file (.dat) has been modified manually, this will be reported by the check.
    VerifyStore --id=1 --includeIndexes=true
-   VerifyStores --includeIndexes=true
+   VerifyStores --includeIndexes=false
 === Maintain all FDB Files ===
-Maintaining all Firebird Embedded Database files (FDB files) used by MailStore Server optimizes the internal data structure and remove no longer needed database pages and transaction logs where necessary.
+Maintaining all Firebird Embedded Database files (FDB files) used by MailStore optimizes the internal data structure and removes obsolete database pages and transaction logs where necessary.
    MaintainFileSystemDatabases
-=== Cleanup (Compact)
+=== Cleanup (Compact) ===
-Compacting of master database:
+Compacting of the master database.
    CompactMasterDatabase
-Compacting of an archive store incl. databases, container and index files. Replace the number 1 with the number of the archive store:
+Compacting of an archive store incl. database, container and index files.
    CompactStore --id=1
 == Search Indexes ==
-Generally, it is an indication that an index is defective if emails cannot be located through the tree structure or by executing a search. A defective index is not critical - it can be completely rebuilt at any time and without any loss of data.
+If emails cannot be located in the tree structure or by executing a search, this generally indicates a defective index. A defective index is not critical - it can be completely rebuilt at any time and without any loss of data.
-To rebuild an index by using MailStore Client, follow the instructions in [[Search Indexes#Rebuilding Search Indexes|Rebuilding Search Indexes]] in the MailStore Server manual.
+To rebuild an index by using the MailStore Client, follow the instructions in [[Search Indexes#Rebuilding Search Indexes|Rebuilding Search Indexes]] in the MailStore Server manual.
 The appropriate Management API command to rebuild all search indexes marked as ''Needs rebuild'' is:
@@ Line 36: / Line 43: @@
     RebuildSelectedStoreIndexes
-Also there is a template for creating a corresponding job available at ''Administrative Tools'' > ''Management API'' > ''Jobs'' in order to rebuild broken search indexes regularly.
+There is also a template for creating a corresponding job available at ''Administrative Tools > Management API > Jobs'' in order to rebuild broken search indexes regularly.
 [[de:Wartung und Reparatur]]
 [[en:Maintenance and Repair]]

@@ Line 3: / Line 3: @@
 Occasionally, however, errors do occur due to system crashes or accidental manipulation of the file structure, for example. This section will provide the information necessary to perform certain maintenance and repair works without having to contact MailStore Support (for example if some contents of the archive becomes inaccessible because of such an error).
-'''Please note:''' The commands described below can be entered and executed by a MailStore administrator through the Management Shell. All commands are also available in the MailStore Client software under ''Administrative Tools'' > ''Storage'' > ''Storage Locations''.
+== Archive Stores ==
-== Logical Verification ==
+=== Check Data Integrity ===
-Logical verification is used to determine if all emails located in MailStore are still complete and in their original state. For example, if a content file (.dat) was modified by hand, this will be censured by logical verification. Replace the number 1 with the actual number of the archive store to be verified:
+A data integrity check is used to determine if all emails located in MailStore are still complete and in their original state. For example, if a content file (.dat) was modified by hand, this will be censured by logical verification.  Use the Management API command <tt>VerifyStore</tt> to check a single archive store. Replace the number 1 with the actual number of the archive store to be verified. Use the Management API command <tt>VerifyStores</tt> to check all archive stores. For both commands, the parameter <tt>includeIndexes</tt> controls whether the full text indexes should be included in the check routine.
-   VerifyStore --id=1
+   VerifyStore --id=1 --includeIndexes=true
 Compacting of master database:
    CompactMasterDatabase
-Compacting of an archive store incl. databases, container and index files. Replace the number 1 with the number of the file group:
+Compacting of an archive store incl. databases, container and index files. Replace the number 1 with the number of the archive store:
    CompactStore --id=1
-== Indexes ==
+== Search Indexes ==
-Generally, it is an indication that an index is defective if emails cannot be located through the tree structure or by executing a search. A defective index is not critical - it can be completely rebuilt at any time and without any loss of data. To rebuild an index, please proceed as follows:
+Generally, it is an indication that an index is defective if emails cannot be located through the tree structure or by executing a search. A defective index is not critical - it can be completely rebuilt at any time and without any loss of data.
-* Using MailStore Client, log on to MailStore Server as administrator.
+Also there is a template for creating a corresponding job available at ''Administrative Tools'' > ''Management API'' > ''Jobs'' in order to rebuild broken search indexes regularly.
 [[de:Wartung und Reparatur]]
 [[en:Maintenance and Repair]]

@@ Line 5: / Line 5: @@
 '''Please note:''' The commands described below can be entered and executed by a MailStore administrator through the Management Shell. All commands are also available in the MailStore Client software under ''Administrative Tools'' > ''Storage'' > ''Storage Locations''.
-= Logical Verification =
+== Logical Verification ==
 Logical verification is used to determine if all emails located in MailStore are still complete and in their original state. For example, if a content file (.dat) was modified by hand, this will be censured by logical verification. Replace the number 1 with the actual number of the archive store to be verified:
    VerifyStore --id=1
-= Databases =
+== Databases ==
 Compacting of master database:
@@ Line 21: / Line 19: @@
    CompactStore --id=1
-= Indexes =
+== Indexes ==
 Generally, it is an indication that an index is defective if emails cannot be located through the tree structure or by executing a search. A defective index is not critical - it can be completely rebuilt at any time and without any loss of data. To rebuild an index, please proceed as follows:
@@ Line 31: / Line 28: @@
 [[de:Wartung und Reparatur]]

@@ Line 7: / Line 7: @@
 = Logical Verification =
-Logical verification is used to determine if all emails located in MailStore are still complete and in their original state. For example, if a content file (.dat) was modified by hand, this will be censured by logical verification. Replace the number 1 with the actual number of the file group to be verified:
+Logical verification is used to determine if all emails located in MailStore are still complete and in their original state. For example, if a content file (.dat) was modified by hand, this will be censured by logical verification. Replace the number 1 with the actual number of the archive store to be verified:
    VerifyStore --id=1

← Older revision		Revision as of 08:54, 12 August 2011
Line 1:		Line 1:
−	MailStore products are developed to require minimal administrative work. Although it is advisable to execute some maintenance tasks from time to time in order to ensure data integrity of the archive. .	+	MailStore products are developed to require minimal administrative work. Although it is advisable to execute some maintenance tasks from time to time in order to ensure data integrity of the archive.

	Occasionally, however, errors do occur due to system crashes or accidental manipulation of the file structure, for example. This section will provide the information necessary to perform certain maintenance and repair works without having to contact MailStore Support (for example if some contents of the archive becomes inaccessible because of such an error).		Occasionally, however, errors do occur due to system crashes or accidental manipulation of the file structure, for example. This section will provide the information necessary to perform certain maintenance and repair works without having to contact MailStore Support (for example if some contents of the archive becomes inaccessible because of such an error).

@@ Line 1: / Line 1: @@
 MailStore products are developed so that they work correctly without requiring any maintenance.
-Occasionally, however, errors do occur due to system crashes or accidental manipulation of the file structure, for example. This section will provide the information necessary to perform certain maintenance and repair works without having to contact MailStore Support (if, because of such an error, some contents of the archive become inaccessible, for example).
+Occasionally, however, errors do occur due to system crashes or accidental manipulation of the file structure, for example. This section will provide the information necessary to perform certain maintenance and repair works without having to contact MailStore Support (for example if some contents of the archive becomes inaccessible because of such an error).
 '''Please note:''' The commands described below can be entered and executed by a MailStore administrator through the Management Shell.
@@ Line 34: / Line 34: @@
 * Using MailStore Client, log on to MailStore Server as administrator.
-* Click on Administrative Tools and select Index Options.
+* Click on ''Administrative Tools'' and select ''Index Options''.
-* Select the file group and the user index and click on Rebuild Now.
+* Select the file group and the user index and click on ''Rebuild Now''.
 * Repeat this process for all affected file groups and user indexes.
 [[de:Wartung und Reparatur]]