HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Backup of file extensions *.n85 and so on is now possible (bug was fixed in 12.0.1)
You can define a directory or a single database to be backed up, which is a selective backup but a full backup because "full" means everything on that server.
For a full backup you can define an exclusion list.
Please STOP using file extensions like *.n85 or *.n10 - there is no technical reason to use them on a server anymore.
The idea originated from the fact that I could not back up databases with ODS-only extensions such as .n85 and .ns10.
I have confirmed that I can back up databases with this ODS-only extension using the command "load backup sample.n85".
However, there are multiple databases with the ODS-only extension.
So I tried the following, using the .ind file I created, using wildcards, etc., but these resulted in errors.
load backup indfile.ind
load backup sample.*
load backup sample.n??
We have already reported to support that some databases cannot be backed up. (STAAC3J8X9)
The ODS-only extension may be a special case, but there are some applications where you may want to selectively back up only important databases. In such a case, not all important databases may be in the same folder.
This isn't a standard use case for a backup solution.
When you look into other backup solutions it's mostly a full backup with exclusions.
If you want an adhoc backup of single databases or folders, you can specify the database name or folder to backup.
This is called a "selective backup" and isn't a full backup of the server.
All the standard processes work with full backups and incremental backups for all databases taking into account your excludes -- which by the way can be extended or replaced on command-line.
We would really like to understand the use-case in more detail. Why does an exclude not work for you. And what is the business cases behind just backing up selected folders?
The is a big different between excluding and including. The logic is completly different.
You would either need to search each directory separate or search once and flip around the exclude logic to match only the included databases instead of the excluded databases.
Still this would be significal work in development and testing.