How to Use the Lotus Domino utility (updall, compact, fixup) for normal and abnormal maintenance.

This article Article The purpose is to describe how to use Lotus Domino Program (Updall, compact, fixup) for normal and abnormal maintenance.

Answer:

Directory

I. Utility: updall, compact, fixup
A. updall
B. Compact
C. fixup
Ii. Utilities for weekly maintenance
Iii. utility for restoration

**************************************** ***************
I. Three utilities: updall, compact, and fixup

A. updall

Updall is similar to update, but it does not run continuously and does not need to be queued in a queue. Instead, you can run updall as needed. You can specify parameters when running updall. However, if this parameter is not specified, updall updates all view indexes and full-text retrieval indexes to be updated on the server. To save disk space, updall clears the delete tag in the database and deletes view indexes that are not used for more than 45 days, unless the delete View index has other restrictions. You can set default_index_lifetime_days in notes. ini to change the time when updall deletes the View index.

Like update, updall reconstructs all the corrupted view indexes and full-text indexes it executes.

By default, updall is included in the notes. ini configuration file servertasksat2, so it runs at a.m. Running updall every day will help save disk space because it clears the deleted tag and unused view indexes. At the same time, it ensures that the full-text index search that needs to be updated every day is updated.

Updall: basic options

Option in the task-start Tool	Command line options	Description
Index all databases Index only this database or folder	Databasepath	"Only this database" only updates the specified database. To update a database in the domino data directory, enter the file name XXXX. nsf. To update a database in a folder in the data directory, you must specify the database path relative to the data folder, such as Doc \ readme. nsf. "Index all databases" (or no database path) updates all databases on the server.
Update this view only	Database-T viewtitle	Update the specified view in the database. You can use-R to fix the damage.

Updall-update Option

Option in the task-start Tool	Command line options	Description
Update: All built views	-V	Update view without updating full-text index
Update: Full text indexes	-F	Update full-text indexes without updating views
Update: Full text indexes; only those with frequency set to immediate	-H	Only the full-text index frequency is updated to "immediate.
Update: Full text indexes; only those with frequency set to immediate or hourly	-M	Update the full-text index frequency to "immediate" or "hourly.
Update: Full text indexes; only those with frequency set to immediate, hourly or daily	-L	Update the full-text index frequency to "immediate", "hourly", or "Daily ".

Updall-rebuilding options

Option in the task-start Tool	Command line options	Description
Rebuild: Full text indexes only	-X	Rebuild the full-text index, but not the view. Used to reconstruct databases with full-text indexes damaged.
Rebuild: All used views	-R	Recreate all accessed views. This option occupies a large amount of resources, so it is the last option to solve a database corruption.
Rebuild: Full-text indexes and additionally: all unused views	Database-C	Rebuild a view and full-text index that has never been accessed. You must specify a specific database.

Updall-location search options

Option in the task-start Tool	Command line options	Description
Update database deployments: Incremental	-	Rebuild the full-text index, but not the view. It is used for reconstruction when the full-text index is damaged.
Update database deployments: Incremental	-B	Completely update the database configuration of the search location

B. Compression
When a document or attachment in a database is deleted, Domino will reuse unused space instead of reducing the file size immediately. Sometimes, Domino can reuse unused space fragments only after you compress the database.

There are three compression methods:
-Only space recycling on-site Compression
-Space recycling and field compression with reduced File Size
-Copy Compression

Only the field compression mode for space recovery is available.

This compression method restores unused space in the database, but does not reduce the size of the database on the disk. The database retains the same database instance IDS (dbiids), so the relationships between the compressed database and transaction logs are still complete. During compression, users and servers can still access and edit databases. You can select this compression mode when you want the database size to remain unchanged or increase.

When you do not specify the option to run compact, Domino uses this method to compress all databases with transaction logs enabled. Domino also uses this method when you specify-B (case sensitive) to compress any database.

Tip:This compression method is most commonly used because it runs the fastest and has the least impact on the system.

Field compression-reuse space and reduce File Size

This compression method reduces the size of the database and recycles unused space in the database. This compression method is slower than the compression method for space reuse only, and a new dbiids is assigned to the database. if you want to use an authenticated backup tool to record it in the log database, perform a full backup of the database after compression. This compression method allows users or servers to access or modify databases during database compression.

When you do not specify any options to run compact, Domino will use this method to compress all databases that have not enabled transaction logs. Domino also uses this compression method when you specify the-B option. To optimize disk space, we recommend that you use the-B option once a week or once a month to perform compact.

Copy Compression
Copy compression copies the database and deletes the original database after compression. Therefore, this compression method requires sufficient extra space on the disk to store the copied database. This compression method actually creates a new database identified by the new database ID. If you use the copy compression method on the log database (with the-C option), the compression will create a new dbiids. Therefore, when using an authenticated backup tool, back up all databases immediately after compression. When you use the copy compression method, neither the user nor the server can edit the database, but you can only browse the database with the-L option selected.

When compression causes structural changes to the database, Domino uses the copy compression method by default. The same is true when the database Properties window causes unexecuted structural changes to the database. Activating or disabling the database attributes "optimizing Document Table ing" and "specifying reply levels not supported" both require structural changes to the database.

When to compress the database
We recommend that you compress the database every week or every month and use the-B Option to save disk space. If you want to use an authenticated backup tool, compress it before running.

Compact-Basic

Option	Command Line Parameters	Description
Only compress the specified database or folder. Select the first option card to specify the database to be compressed, and select the database in the first panel.	Database path You can specify other options after the database path.	To compress the database in the domino data folder, first enter the file name, such as sales. nsf. Compress a folder in the domino data path. Specify the relative path of the data folder. For example, compress all databases in data \ sales and specify sales. If you select "compressing all databases" or do not specify the database path, the Compact command compresses all folders and databases in the data folder.

Compact-Option

Option	Command Line Parameters	Description
Only compression is performed when the unused space is greater than X %.	-SPercent	Compress the database with the specified proportion of unused space. For example, if you specify a ratio of 10, databases with unused space of 10% or more will be compressed. Note that the calculation of unused space is not always reliable.
Delete all view Indexes	-D	Delete the created View index. Use this option before backing up the database to tape. Compression is a replication method.
Maintain or reply to the database in the previous format	-R	Compress the database but does not convert it to the file format of the server that stores the database, or convert it to the previous file format. For example, on the domino6 server, this option compresses the databases of Domino 5 but does not convert them into the file format of Domino 6, and converts the databases of domino6 to the format of Domino 5. This option is compressed in copy mode.

Compact-Method

Option	Command Line Parameters	Description
In-Place (recommended)	-B	Using on-site compression and recycling of unused space does not reduce the file size, unless the database structure changes. When there is a structural change, it will lead to compression of the replication mode. This is our recommended compression method.
In-Place with file size limit ction	-B	Use on-site compression to restore unused space and reduce the file size, unless there is a change in the database structure caused by copy compression. If you enable transaction logs, back up all databases after compression is complete.
Copy-style	-C	Copy compression. This method is used to solve the problem of database corruption.
Copy-style: Allow access while Compacting	-L	Allows users to continuously access the database during database compression. If you edit the database during the compression process, the compression will be canceled. This parameter is valid when compression in replication mode is complete.
Copy-style: Ignore errors and proceed	-I	Enable compression and ignore errors (such as document corruption ). Only applies to copy compression.

Compact-advanced
Note that the advanced compression option is not available in the file tab of the domino administrator.

Option *	Command Line Parameters	Description
Document Table bitmap optimization: Off	-F	Disable the "optimize Document Table bitmap" attribute of the database. Copy compression.
Document Table bitmap optimization: On	-F	Enable the "optimize Document Table bitmap" attribute of the database. Copy compression.
Don't support specialized response hierarchy: Off	-H	Disable the "do not support specified reply level" attribute of the database. In other words, the specified reply level is supported. Copy compression.
Don't support specialized response hierarchy: On	-H	Enable the "do not support specified reply hierarchies" attribute of the database. That is, the specified reply hierarchies are not supported. Copy compression.
Enable transaction logging: Off	-T	Disable transaction logs.
Enable transaction logging: On	-T	Enable transaction logs.
Don't maintain unread marks: Off	-U	Disable the "do not retain unread mark" attribute of the database; that is, retain the unread mark.
Don't maintain unread marks: On	-U	Enable the "do not retain unread mark" attribute of the database; that is, do not retain the unread mark.

Note:Before you enable or disable any of the preceding attributes, select "set advanced attributes ".

C. fixup

When you restart a server, the server will quickly search for all unrecorded databases. These edited databases are not properly shut down due to server errors, power supply errors, hardware errors, and so on. Within a few minutes after the server is started, the fixup task will try to fix the inconsistency caused by some write operations. This write operation is caused by the error mentioned above. When the user tries to access these databases but the fixup task is not completed, the user will see a prompt message "consistency check is in progress, this database cannot be opened ". When you restart a Lotus Notes client, a similar fixup process is triggered.

When the server is started, multiple fixup tasks run at the same time to reduce the time for restoring the database. By default, Domino starts a fixup task that doubles the number of processors on the server. Although this default processing method applies to most cases, you can modify the fixup_tasks settings by modifying the notes. ini file. The actual number of running tasks is the smaller number of tasks you configured and the number of databases to be repaired. For example, if you set fixup_tasks to 4, but only one database needs to be repaired, only one fixup task will run.

Remember that after you set up transaction logs, you do not need to use the repair function to maintain database consistency.

Fixup-Option

Fixup options in fixup tools and tasks	Command Line Parameters	Description
Fixup all databases Fixup only this database or folder	Databasepath	"Only fix this database or folder" only performs repair tasks on all databases in a database or a specified folder. Run fixup in a database in the domino data directory And enter the file name, such as sales. nsf. Run fixup on the database in the folder under the Data Directory and enter the relative path to the data folder. For example, run fixup on all databases in the data \ sales folder and specify sales. "Fixup all databases" or no command line Database path is specified, all databases on the server are repaired. DescriptionTo specify a database or folder to run the fixup tool, select the specified database or folder.
Report all processed databases to log file	-L	Record all corrupted databases opened and inspected by fixup to log files. Without this parameter, fixup only records the actual problems encountered.
Scan only since last fixup	-I	When you run fixup on a specified database, fixup only checks the modified document after the previous command is run. If this option is not available, fixup will check all documents.
Scan all documents	-F	When you run fixup on all databases, fixup checks all documents in the database. If this option is not available, fixup only checks the modified documents after the previous operation. DescriptionUse the fixup tool to specify this parameter and cancel the "scan only since last fixup." option.
Perform quick fixup	-Q	Quick document check, but not comprehensive. Without this option, fixup will fully check each document.
Exclude views (faster)	-V	The organization fixup runs on The View. This option can reduce the running time of fixup. Use this option when the view is not damaged.
Don't purge your upted documents	-N	Prevent fixup from clearing corrupted documents, so that when the next fixup is run or when the next user opens the database, fixup must check the database again.
Optimize user unread lists	-U	Restore the ID tables in the database to the previous version format. Do not select this option unless recommended by the customer service personnel.
Fixup transaction-logged Databases	-J	The database that runs on which transaction logs are enabled. Without this option, fixup is usually not run. If you are using an authenticated backup tool, plan the backup immediately after the fixup is executed.
Fixup open databases	-O	If you run fixup on the opened database, fixup will take the database offline and re-execute. This is the default situation where you specify a database to run fixup. If this option is not available, the database is not specified and in the Enabled state, and fixup does not run.
Don't fixup open databases	-Z	Run fixup only on a single database. Fixup does not run when a database is in use and is not offline. This is the default value when fixup runs on multiple databases.
Verify only	-C	Check the database integrity and report errors. Do not modify the database (for example, do not clear corrupted documents)
Fixup subdirectories	-Y	Run fixup on the database in the subdirectory.
Don't fixup subdirectories	-Y	Fixup is not performed on the database in the subdirectory.

II. The most common weekly maintenance
If you have not enabled transaction logs, run the following command to Perform weekly maintenance. We recommend that you perform maintenance when the server workload is not heavy on weekends:

Compact-B-S 10

If you enable transaction logs, run the following command for weekly maintenance:

Compact-B-S 10

The above command compresses the database with more than 10% of the remaining space. Parameters "-B" and "-B" indicate on-site compression. "-B" is used with transaction logs, so no new dbiids are specified for the database.

There is no need to run fixup or updall every week. Fixup is run only when the database shows signs of damage. Updall runs automatically every night by default. When view corruption may occur, run updall with parameters.

Note:It is a good habit to reconstruct a full-text index through updall-x periodically through updall-R.

III. The most common restoration program
When the database needs to be repaired, use the following steps to restore the database. This section also includes instructions for running the domino maintenance tool through command lines on different operating system platforms.

When should we use irregular maintenance?
As the name suggests, there is no fixed period for irregular maintenance, including database repair and Database Upgrade. The specific maintenance depends on the maintenance task and database type. If the Domino Directory is damaged, the Domino server must stop running and maintain it.

Database corruption
Database crashes are caused by some unconventional causes, rather than common user complaints or error messages. For example, when the server generates a message indicating that the database is damaged (sometimes causing a system crash), the following output is displayed:

-- "Database. nsf is damaged ....
-- Dbmarkupt (dbfixup: Invalid slot found, cocould not be retried red )...
-- Database. nsf is already upt-now read-only! "

If transaction logs are enabled for the database
If you use transaction logs to record changes to the domino database, the server will automatically use a transaction log to restore and restore any database with transaction logs enabled after a system error occurs. Databases without transaction logs are checked through regular consistency checks. If a disk error is generated and the archived transaction log is enabled, you can restore the database by using the transaction log and authenticated backup tools.

If these steps fail, try the following method:

1. fixup database. nsf-J-F
2. compact database. nsf-B
3. updall database. nsf-r-x

These programs change the dbiid of the database related to the transaction log. Therefore, if you run the archive transaction log, you must immediately perform a complete database backup.

If the database does not have transaction logs
If the database has no transaction records, run the following command:
1. fixup database. nsf-F
2. compact database. nsf-c-I
3. updall database. nsf-r-x

Another option
If the above steps are not successful, try to create a copy of the database to replace the original database. Creating a copy will force the whole database to be rebuilt, which can repair some database damages or remove some unrecoverable elements.

Process database corruption on workday
1. run fixup in the following way to check the integrity of the damaged database, and report the check problem without any modification: "fixup database. NSF-l-f-o-c"

2. It is generally not recommended to use the fixup tool during working hours. If you cannot wait for non-working hours to restore the database, run the Compact task in the following way:

Compact database. nsf-C-l-I

Note:We strongly recommend that you enable transaction logs to ensure database integrity. If transaction logs are enabled, fixup is unnecessary.

3. After running any of the preceding commands, run the following command to recreate the view and index (if possible, it is best to wait until the off-peak hours ).

Updall database. nsf-r-x

For more information, see document #1193738, "Managing upload uption recovery during the business day ."

Server upgrade
When the Domino server is upgraded to the next version, the physical storage mode (disk structure) of the database on the disk is also upgraded. Ensure that the database structure is effective and consistent before the upgrade. This avoids errors during Database Upgrade. When a database error occurs during the upgrade, the new domino version of the tool will be helpful. Although this is optional, it is easy to upgrade the full-text index of each database. Therefore, we recommend that you select to execute it so that you can use the latest full-text search engine on the new Domino server.

Before upgrade
1. Before upgrading, we recommend that you clean up the database by running updall on the current server as follows:

Updall-r-x

You can execute multiple options before the upgrade. Running updall-r-X is the best option to avoid database corruption, because it completely reconstructs the View index and full-text index. Other options include:

Updall-V (update View index)
Updall-R (View index Reconstruction)
Updall-X (full text index Reconstruction)

2. You should run "fixup-F" to complete the consistency check.

Note:If you enable transaction logs, you do not need to run fixup, but if you want to do so, remember to add the-J parameter.

3. Run compact: "Compact-c-I"

Note:If you enable transaction logs, remove the-C and-I parameters. Remember to add-B. This is completely different from the uppercase-B.-B will change the dbiid of any database that enables transaction logs.

If the email file is damaged after the server is upgraded
1. Run "fixup-F ".

2. Run "Compact-c-d-I-k" (copy-style, delete view indexes, ignore errors, set large unk table bit ).

3. Run "updall-r-X ".

For more information, see document #1201020, "error: 'database is using upt; cannot allocate space 'when opening database after server upgrade ."

After Upgrade
After the upgrade, we strongly recommend that you upgrade to the latest search engine. It is still a good idea to upgrade to the latest version with "updall-X", even if Domino is compatible with all previous full-text engines. The new engine reconstructs all full-text indexes and enables new features.

When should non-periodic maintenance be used?
Domino automatically detects and fixes database problems, or the database may not be faulty. Therefore, even if your first response is to detect an affected database, consider the following before doing so:

Time when the first crash occurred
Although a system crash may cause Database Inconsistency, Domino will perform consistency check (if the transaction log is not enabled) at restart to fix the consistency problem. In the consistency check, Domino tries to repair any corrupted database/document. If there are no errors, you do not need to run fixup. We recommend that you do not run fixup for routine maintenance. If the server crashes repeatedly and the NSD displays a database, it is necessary to run fixup. In this case, it is recommended to run fixup when the Domino service is stopped.

If the system crashes because of a database
If the crash stack does not display any information related to the database, it should be able to exclude database corruption (except for the possible inconsistencies mentioned above), and there is no need to run the database repair.

How to run the domino maintenance program from the command line
The methods and syntax for running and maintaining programs through the command line are different on different platforms. The following example shows how to run a fix on names. nsf on Windows, iseries, and Unix/Linux/zseries. These examples can also guide how to run compact and updall through the command line.

Note:If the Domino Directory is damaged, you must run fixup when the Domino server is stopped.

InWindowsUse "nfixup names. nsf-F ". Note: If you enable transaction logs, remember to add the-J parameter.

InIseries, Use the following:

Rundomcmd server (servername) cmd (call PGM (qnotes/fixup)
Parm ('names. nsf '''-F') Batch (* No)

If you enable transaction logs, remember to add-J after-f. Of course, it must run from qsecofr or equivalent qsecofr.

ForUnix/Linux/zseries, Use "<path>/fixup names. nsf-F ". Note that if you run the transaction log, you must add the-J parameter. In addition, you must Log On As A Notes user and use the notes data directory as the current directory.