IBM Support

Known problems and limitations: Version 7.1 Data Protection for Domino

Preventive Service Planning


Abstract

This document details the Known Issues & Limitations for Data Protection for Domino 7.1.x.
These issues and limitations apply to the Data Protection component when used with Lotus Domino, IBM Domino or HCL Domino.

Content


This document is divided into linked sections for ease of navigation. You may use the links below to jump to the desired section of the document.

Problems and Limitations Common to All Platforms
Problems and Limitations Related to DB2 - All Platforms
Problems and Limitations Specific to Unix and Linux Platforms Only
Problems and Limitations Specific to the Windows Platform Only



Problems and Limitations Common to All Platforms
 
  • With the release of the Domino 9 Server, the product branding changed from Lotus Domino Server to IBM Domino Server.
  • With the release of the Domino 11 Server, the product branding changed from IBM Domino Server to HCL Domino Server.
  • The Data Protection for Lotus Domino documentation (installation and user's guides, and many tech notes) for the 7.1 release will identify this component as:
    • Data Protection for IBM Domino 7.1
  • However, the runtime code will continue to identify this component as:
    • Data Protection for Lotus Domino 7.1
  • Domino 10 and 11 Servers only provide support on 64 bit for Windows, 32 bit is not supported.
  • The Domino Administration Client allows your to create directory names that include special characters, such as the directory name:
    • iis??is
  • which are not supported by the Domino C/API interface. Data Protection for Domino uses this interface during backup. Therefore, once a directory path that includes these characters is encountered during a Data Protection for Domino backup, the following error will be added to the dsmdsmerr.log:

    ACD0151E Errors occurred while processing the request.

    Workaround: None. Do not create Domino directory paths which include special characters. (90719)
 
  • Command line output may have incorrect formatting in non-English languages.
  • This is a known problem for all of the following commands:
    domdsmc query logarchive
    domdsmc query dbbackup
    domdsmc query pending

    For example, in Polish, the columns in the header don't exactly match the data.

    domdsmc query dbbackup "*"
    IBM Tivoli Storage Manager for Mail:
    Data Protection for Lotus Domino
    Wersja 6, Wydanie 3, Poziom 1.0
    (C) Copyright IBM Corporation 1999, 2013. Wszelkie prawa zastrzeone.

    Lista kopii zapasowych baz danych
    ---------------------------------

    Serwer Domino: lpar4base
    --------------

    Data kopii zapas. Wielko A/I Protoko. Nag.bazy dan. Plik bazy danych
    ----------------- -------- --- --------- -------------- ------------ ----
    03/11/13 03:58:10 864.00KB A Nie DBcostin DBcostin.nsf
    03/11/13 04:11:46 5,632.00KB A Nie Domino Domain M ddm.nsf
    03/11/13 04:11:06 448.00KB A Nie Homepage (8.5) homepage.nsf

    Workaround: There is no work around. (91625) (91590) (91208)
 
  • When regional settings are updated in the GUI preference editor, the GUI needs to be restarted before the changes become effective.
  • For example:
    1. Run "domdsm.exe" from default install path.
    2. Select Edit -> Preferences... -> Regional tab.
    3. Select "Time Format" = hh:mm:ss and "Number Format" = xxx xxx,dd
    4. Perform a selective backup.
    5. Open the domdsm.log file.

    08/09/2011 04.46.22 Throughput rate: 5,718.21 Kb/Sec
    08/09/2011 04.46.22 Total bytes inspected: 3,407,872
    08/09/2011 04.46.22 Total bytes transferred: 3,407,872

    Workaround: Restart the GUI after changing the regional settings using the GUI Preference Editor. (75546)












  •  
  • When both COMPRESSION=YES and COMPRESSALWAYS=NO are used, and a file grows during backup, the file is properly backed up in an uncompressed format and the program properly displays the following message:
 
    • ANS2101E (RC155) Compressed data grew.

  • However, the following message is also displayed by mistake:
    • ACE0004E unknown error message

    Workaround: None. Please ignore the extraneous ACE0004E message in this case. (91403)
 
  • SESSions option is ignored from the Java GUI & Web Client GUI
  • When backing up Domino NSF databases from the Web client GUI, the SESSions option is ignored and only a single TSM server sessions is used.
 
  • Under certain circumstances, backups will fail if the TSM Domain, associated with the TSM Node that performs the DP for Domino backup, is changed.
 
  • When performing DB2 backups associated with a Domino server, and change the TSM Domain associated with your TSM Node during the backup, the backup may fail. You must wait until the backup has completed before changing the TSM Domain or the backup will fail and generate a message like:
    • ACD0004E An unknown error has been detected.

  • Scenario That Causes This Backup Failure:
    1. Issue the command:
    • UPDATE NODE tdpnode domain=standard
    2. Issue the command:
    • domdsmc db2selective -full
    3. While the backup is running, create a new Domain on the TSM Server
    4. While the backup is running, issue the command:
    • UPDATE NOTE tdpnode domain=new_domain_name
    5. The backup will fail with error "ACD0004E An unknown error has been detected."

    An incorrect Product ID (PID) is reflected in the header information of some Data Protection for Domino files

    Header information associated with some Data Protection for Domino files, such as:
    domdsmc
    dominstall
    libTdpDOM64.so

    may display the Product ID 5608-APE instead of 5608-E06.

    For example:

    IBM Tivoli Storage Manager for Mail, Data Protection for Lotus Domino
    Licensed Materials - Property of IBM
    5608-APD (C) Copyright IBM Corporation 1990, 2013 All Rights Reserved.
    US Government Users Restricted Rights - Use, duplication or
    disclosure restricted by GSA ADP Schedule Contract with IBM CORP


    Workaround: None. This issue does not affect the functionality of the software. (93270)














  •  



Problems and Limitations Related to DB2 - All Platforms
 
  • An archive copy group is required to archive the Domino DB2 database log
  • If an archive copy group is not defined on the target management class, the db2archivelog command completes successfully, but the log is not archived to the Tivoli Storage Manager server.
 
  • DB2 Group backup fails
  • When backing up multiple DB2 groups, the db2selective command may fail with the following error:
    • "SQL2025N An I/O error "-50" occurred on media "TSM".

    This error indicates that the session with the Tivoli Storage Manager server was terminated due to a timeout. The COMMTIMEOUT option value must be increased on the Tivoli Storage Manager.
 
  • Inplace restore when DB2CONTAINERPATH is specified
  • When the Domino DB2 database is configured to store DB2 data on a directory other than the Domino DB2 database directory (see DB2DIRECTORY in notes.ini) and an inplace restore is performed, the DB2 data is restored to the directory specified by the DB2CONTAINERPATH option.

    The DB2 data can be restored to its original location by setting the DB2CONTAINERPATH option to blank. If the DB2CONTAINERPATH is set and the directory is already being used by an alternate DB2 database, the restore will fail unless the DB2CONTAINERPATH is updated.
 
  • Multiple tablespace directories
  • Domino DB2 enablement allows the user to specify multiple directories in which tablespaces can store Domino databases with the DB2DIRECTORY option. However, the Data Protection for Domino DB2CONTAINERPATH option (specified with the db2restore command) allows only one directory in which tablespaces can store Domino databases. If the amount of data being restored exceeds the size of the volume specified by the DB2CONTAINERPATH option, the db2restore command will fail with an insufficient space available error.
 
  • When specifying the restore destination using the Java GUI & Web Client , the activation of db2nsf may fail unless the relative path is specified
  • Error ID "ANS1617E" may be displayed when attempting to activate a restored DB using the following steps:

    1. Issue a command like:
    • db2restore and db2roll one db2grp1
    2. Attempt to activate db2nsf using the GUI
    3. In the “activate destination” options, click "following destination"
    4. Then use the select button to specify the destination
    5. Then select "activate"

    Note: If the relative path is specified, the activate process is successful.



Problems and Limitations Specific to Unix and Linux Platforms Only
 
  • Installing the backup-archive client and Data Protection for IBM Domino® on RHEL 7.x or SUSE 12.x distributions causes a conflict













  •  
  • If you want to enable the Tivoli Storage Manager web client for IBM Tivoli Storage Manager for Mail: Data Protection for IBM Domino, you must install the Tivoli Storage Manager API, backup-archive client, and Data Protection for IBM Domino on the same system in a specific sequence.

    To avoid an installation conflict on Red Hat Enterprise Linux 7.x or SUSE Linux Enterprise Server 12.x distributions, complete the installation in the following order:
    1. Uninstall the backup-archive client (if already installed).
    2. Install the API if it was uninstalled with the backup-archive client in the previous step/
    3. Install Data Protection for IBM Domino.
    4. Install the backup-archive client with the --replacefiles option. For example, to install the Linux x86_64 client, issue the following command:
    • rpm -ivh --replacefiles TIVsm-BA.x86_64.rpm

    For more information about installing and uninstalling the backup-archive client and API, see http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.4/client/c_inst_baunix.html

    For more information about installing Data Protection for IBM Domino, see http://www.ibm.com/support/knowledgecenter/SSTG2D_7.1.0/com.ibm.itsm.mail.dom.doc/t_protect_dpmaildom.html
    (108360)
 
  • When installing Data Protection for IBM Domino 7.1.0 and the Tivoli Storage Manager API is not already installed, the resulting popup message:













  •  
  • "API Not Installed"

    will indicate that 6.3.1 is the minimum required level of the TSM API. However, with Data Protection for IBM Domino 7.1.0.x, the minimum requirement level of the TSM API is 7.1.0.0. (99811)
 

The following scenario provides instructions that you can use to view a license agreement online. In this scenario, the product is Tivoli Storage Manager for Mail 7.1.

  • For non-English environments, the Tivoli Storage Manager for Mail: Data Protection for IBM Domino 7.1 installation on AIX will only display the license in English when UTF8 locales are used. The license can be reviewed online, prior to installation, using the following steps:
    1. From a web browser, enter the address for the IBM License site: http://www.ibm.com/software/sla/sladb.nsf
    2. From the IBM License site homepage, click Search for a specific program license agreement.
    3. In the search criteria field, enter the product name. For example, Tivoli Storage Manager Databases.
    4. Select the link for IBM Tivoli Storage Manager for Mail V71 5608-E06. For this particular example, the option is toward the bottom of the page.

  • After the license is selected, the license can be displayed in any of the following languages:
    • English
    • Chinese - Simplified
    • Chinese - Traditional
    • Czech
    • French
    • German
    • Greek
    • Italian
    • Japanese
    • Korean
    • Lithuanian
    • Polish
    • Portuguese
    • Russian
    • Slovenian
    • Spanish
    • Turkish
    (99545)
 
  • The Data Protection for Domino on Unix install tool (dominstall) allows configuration of a web client for use with Data Protection for Domino even when the web client does is not installed.
    • Note: The web client used with Data Protection for Domino is a part of the TSM Backup-Archive Client.

  • Though this does not cause a functional issue with Data Protection for Domino, when it is uninstalled, the following directory structure is not removed:

    /usr/tivoli
    /usr/tivoli/tsm
    /usr/tivoli/tsm/client
    /usr/tivoli/tsm/client/ba
    /usr/tivoli/tsm/client/ba/bin64
    /usr/tivoli/tsm/client/ba/bin64/plugins
    /usr/tivoli/tsm/tivinv

    Workaround:
    1) Do not configure web client as part of dominstal before installing the TSM Backup-Archive Client.
    2) Manually remove the directories listed above once DP for Domino has been uninstalled (92000)
 
  • If the Domino Administrator has created path names or data bases for a Unix Lotus Domino Server that differ only by case, Tivoli Storage Manager for Mail: Data Protection for Lotus Domino will not properly backup all instances of the data bases.
  • For example, the Domino server may have these databases in the data directory:
    mail1/db1.nsf
    MAIL1/db1.nsf

    Data Protection for Lotus Domino will fail to properly backup the two data bases due to case sensitivity issues within the Lotus Domino application programming interface that is used by Data Protection for Lotus Domino. This is a permanent restriction for Data Protection for Lotus Domino based on the requirements of the application programming interface provided by Lotus Domino.
  • Correction measures:

    Inspect your Unix Lotus Domino Server directory structure starting from the data directory. Path names and Domino database names that differ only by case need to be renamed so they have unique names that are not based on case sensitivity.
 
  • Providing an file name containing an invalid character using the CONFIGFILE option can lead to unwanted output. The error only occurs with AIX and Linux command line clients.
  • For Example:
    domdsmc query adsm /config=:

    Unrecognized or duplicate preference options were found.
    02/25/09
    02/25/09
    02/25/09
    02/25/09
    02/25/09
    02/25/09
    02/25/09
    . . .
    03/10/09
    03/10/09

    IBM Tivoli Storage Manager for Mail:
    Data Protection for Lotus Domino
    Version 6, Release 3, Level 0.0
    (C) Copyright IBM Corporation 1999, 2011. All rights reserved.

    Tivoli Storage Manager Server Connection Information
    ----------------------------------------------------
    Nodename ............................... CVTLPAR1_NOTES1
    NetWork Host Name of Server ............ FVTSERIES5.STORAGE.USCA.IBM.COM
    TSM API Version ........................ Version 6, Release 3, Level 0.55

    Server Name ............................ FVTSERIES5_SERVER1_5541_348
    Server Type ............................ Windows
    Server Version ......................... Version 5, Release 5, Level 4.1
    Compression Mode ....................... Client Determined
    Domain Name ............................ STANDARD
    Active Policy Set ...................... STANDARD
    Default Management Class ............... STANDARD

    Workaround: Do not use invalid characters for the file name when using the CONFIGFILE option. (77754)
 
  • dominstall silent configuration
  • dominstall silent configuration fails if the environment where the silent configuration file was recorded differs from the environment where the silent install is being performed. For example, the silent configuration created during a first time installation can not be use to reconfigure an existing installation.
 
  • Characters typed after Yes/No responses are recorded during dominstall silent configuration.
  • When additional characters are entered after a valid Yes/No response, the characters are recorded in the silent configuration file.
 
  • GNU JVM not supported by InstallAnywhere
  • GNU JVM is not supported by InstallAnywhere and cannot be used to install Data Protection for Lotus Domino. Support incident #SIOA-000089928 is opened with Macrovision.
 
  • Backup operations may fail when using the Java GUI or Web GUI to back up Domino servers configured to use DB2 data stores
  • When using DB2 Server 9.1.2 with a Domino server on an AIX or Linux x86 machine, the AIX LIBPATH or Linux LD_LIBRARY_PATH environment variable must be set to include the DB2 instance directory (sqllib/lib32) before launching the Web client GUI.

    When the path is not correctly set, backup operations via the GUI will fail and an error message similar to the following may be seen when attempting the backup operation:
    • Domino server is not DB2-enabled or DB2 services were unable to initialize when the server started up.
 
  • Some DP for Domino Interim Fix READMEs do not specify when dominstall must be executed
  • Some Data Protection for Domino README.FTP files include installation instructions. However, these instructions do not indicate that you need to run the dominstall program for each Domino server partition.

    After applying maintenance, such as a fix pack or interim fix, you must configure the Domino environment by running the dominstall program for each Domino server partition.



Problems and Limitations Specific to Windows Platforms Only
 
  • Using /CONFIGfile option with the DOMDSMC SET command does not assume the path to the config file is the directory where Data Protection for Domino is installed.
  • When issuing the a command like:
    • domdsmc set DOMTXNGROUPmax=2 /CONFIGfile=domdsm.cfg

    the command will complete successfully with the following message:
    • ACD5217I The preference has been set successfully.

    However the config file will be in the root of the filesystem because no path was given. To avoid this, please give a fully qualified path and config file name when using the /configfile option. This issue is not limited to the DOMTXNGROUPmax option. The issue applies to all options that can be set with the DOMDSMC SET command.
 
  • 64-bit versions of Data Protection for Lotus Domino on Windows cannot restore Domino databases if they are backed up from 32-bit Windows environment using DP for Domino V5.5.0.0 - 5.5.2.0

From APAR IC60425.

  • This problem has been corrected in Data Protection for Domino V5.5.2.1 and later releases. However, the following important information should be considered:

    Once the fix is applied, all 32-bit Windows Data Protection for Domino backups created after the application of V5.5.2.1 can be restored using Windows 64-bit Data Protection for Domino code.

    However, any 32-bit Windows backup created prior to the application of the fix can not be restored using 64-bit Data Protection for Domino. For customers who have already migrated from using 32-bit Windows Data Protection for Domino to 64-bit Data Protection for Domino, recover your 32-bit backups as follows:

    Install a 32-bit version of Data Protection for Domino on a 32-bit machine running a 32-bit Domino Server.

    Use the method for restoring Domino data to an alternate partition or server as documented in the section titled:

    "Alternate server and alternate partition restores for NSF databases" located in the Data Protection for Domino User's Guide. This information is available via the following URL

    http://pic.dhe.ibm.com/infocenter/tsminfo/v6r3/index.jsp?topic=%2Fcom.ibm.itsm.mail.dom.win.doc%2Fconcept_domcarp.html

    Note 1: Though the title of this section references Domino NSF databases environments, the same method applies to Domino DB2 database environments as well.

    Note 2: This limitation is lifted once the fix for APAR IC82911 is applied. This fix is contained in the 6.3.0.2 interim fix and subsequent 6.3.1 fix pack.
 
  • GUI will not launch and errors are displayed when the LANGuage option in domdsm.cfg is defined but the corresponding language pack is not installed on the system
  • If LANGuage option in domdsm.cfg is defined but the corresponding language pack is not installed on the system, the Native GUI can not be launched and the following message may be displayed multiple times:
    • ANS0101E Unable to open English message repository 'tdpdchs.txt'

    To resolve the issue, either install the DP for Domino language pack that corresponds to the domdsm.cfg file or remove the LANGuage option from the configuration file.
 
  • ANS0106E Errors displayed when starting the Native GUI
  • When activating a database using the Native GUI, a pop up windows is generated which does not close once the operation has completed. When activating a database using the DP for Domino Native GUI, an new window will be generated that has a title like:
    • domino_server:DOMDSM

    After the activate operation completes, the new window does not close. Attempts to close the window manually results in the exit from the entire Native GUI.
 
  • DP for Domino may terminate when the Windows Locale setting does not match the DP for Domino language setting
  • When the DP for Domino language is set to $LANG_A and the Windows Locale setting is for $LANG_B, DP for Domino may terminate and cause the Windows debugger to display on the screen with the a message like:
    followed by debugger output.

    An example of the language mismatch is when DP for Domino is set for Russian but the Windows local is set to Chinese.
    • domdsm stopped working
  • When issuing the following command:
            Domdsmc query domino
            The command fails with the following error.
    ACD5218E The Lotus Domino API could not be loaded. Could not load the nnotes.dll
             Warning! Error initializing the connection to the TDP library
Workaround:  The registry path has been changed at Domino 11.0 so that TDP cannot find the path containing nnotes.dll. However, it is possible to run TDP Domino after issuing the following command:
REG COPY HKLM\SOFTWARE\HCL\Domino  HKLM\SOFTWARE\Lotus\Domino /s

[{"Product":{"code":"SSTG2D","label":"Tivoli Storage Manager for Mail"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"Data Protection for IBM Domino","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"7.1","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
18 August 2020

UID

swg21644480