Unable to restore database links
Symptom
Notes Document Agent is unable to restore the database links.
Cause
Data for restore was selected at the Document level.
Solutions
To restore database links, (using the Database Links Only or Overwrite Database Links check boxes), select the data for restore at the Database level.
Non-full backup operation runs a full backup job
Symptom
All the documents are backed up again even though a non-full backup operation is run.
Cause
After changing the database title, we backup all documents again so that the documents reflect the changed database title.
Solutions
This is the expected behavior by design of the software. There is no need for a solution here.
Notes Document backup operation goes into pending state (on some Linux distribution setup)
Symptom
After upgrading Commvault from version 9 to version 11, backup job goes into pending state on some Linux distribution setup.
This issue occurs on a few Linux environment:
-
32-bit Domino on 64-bit Linux
-
SUSE Linux 10.0
-
Red Hat 6
Cause
Few Linux environment do not install 32-bit libacl.so file by default .
Solution
Run the ldd command to check library dependencies. If you do not find libacl.so.1 library, then install it.
Also, check if 32 bit libacl.so.1 is installed. If not, install the package and retry to run the backup job.
Warning message received while restoring documents outside the data path
Symptom
When restoring documents to a database that is outside the data path, and then attempting to open the database, you may receive a warning message indicating that the database is being used by another user, and to share the access with other users, all users must use Domino instead of a File server.
Solution
Use the following steps as a workaround for this issue:
-
Wait approximately 30 minutes for the server to clear itself.
-
Run the following command on the Domino console to flush the content of the Domino database cache:
dbcache flush -
Shutdown and then start the Domino.
