This post is more than 5 years old

1 Rookie

 • 

47 Posts

8058

July 12th, 2011 08:00

How to setup and run backup of Lotus Domino Server with NMDA software

Hello

Can someone help by below questions please?

What is the proper way to setup/run backup of Lotus Domino Server with NMDA software


Is it required to have two or three config files (e.g.: nmda_full.cfg, nmda_incr.cfg etc) one for Full Backup, one for Incr. Backup and one for Recovery use?

Or can I put all settings in only one config file. But how about NSR_BACKUP_LOGS_MODE ="1" for incr. backup. Use of this parameter

by old NML software for incr. backup was not possible...

Backup schedule should be:”Daily Incr. full Sundays” and the transaction logs should be marked as reusable / deleted after the backup is successfully completed.

-------------
How about recovery of saved data that were backed up duringthe incr. backup,
since I can see only version of Full Backup when I use NMDA Gui to run a recovery.,

For example:
Last full backup of nwclient-01 was on Sunday, but user requires file “userdata.nsf” from last Friday. 

When I check for backup version of “userdata.nsf” with NMDA user for lotus, only the full backup (Sundays) are listed

Thanks.

334 Posts

July 18th, 2011 10:00

This is the expected behavior.  The recovery is driven by Domino. When you specify a recovery time for Jun 12, NMDA finds the latest full backup before that time (in this case Jul 8) and restores it. Then, it asks Domino to recover the database to Jun 12 date. Domino goes through all logs generated between Jun 8 & 12 to find changes specific to that database and applies them. If a given log is not in the log directory, Domino asks NMDA to restore it, then goes through it, then it may ask for another log.

To speed up the recovery process, NMDA supports NSR_PREFETCH_LOG parameter that allows NMDA to restore extra logs in addition to the one requested by Domino in anticipation that these logs will be needed any way.

The incremental backups shorten the backup time at the expense of longer recovery. If you can, running nightly full backups is the best solution (you may still want to back up logs to be able to restore to any point of time between full backups).

Finally, backing up to a Data Domain device with DD Boost on a Storage Node (NW 7.6.1 & up) may improve the full backup performance making it comparable to incremental backup’s performance with better recovery time.

Hope this helps.

Allan (and Dorota )

334 Posts

July 12th, 2011 10:00

Hi Vucko,

You can use the NetWorker Schedule resource to specify full & incremental  backups and have a single config file and single client resource for both (it works for scheduled backups, for manual, it would require separate configuration file).

The NSR_BACKUP_LOGS_MODE can be set for incremental backups; the parameter will be ignored and a warning message to that effect will be printed.

Also, you can use the backup config file to perform a restore (you couldn’t with NML). However, it may be good practice to have a separate config file for restore to prevent config mistakes.

The recovery of a database in the archived log mode means restoring the full backup from last Sunday and then apply the transaction logs (which also will be restored from NetWorker) until the specified time (e.g.,Friday). User just needs to specify the db file as a file to be restores, applying the logs will happen automatically.

Hope this helps.

Allan

1 Rookie

 • 

47 Posts

July 18th, 2011 09:00

Hi Allan

Many thanks for your clear and understandable answer.
But, I would like to ensure myself for one thing more.

I've started a few hours ago, one test restore of one mailbox.nsf from 12th July the full backup of this mailbox was on 8th. July  Restore is running fine,
but according the messages that are provided in NMDA user for lotus (see below) for one file of  9 MB, NMDA is restoring 25985 MB of transaction log file, and the restore will took probably around 5-6 hours to complete, because the Lotus Notes transaction logs are always 65 MB.

Is this really correct way of running backup/restore with NMDA software?
Are there any other best practices to run backup of Lotus Notes database, which could enable fast backup and time point recovery in reasonable time?

PID(5184) - Received  8960 KB  1 file(s) from NSR server.
Using 12.07.2011 14:00:00 as upper time limit.
Applying Transaction logs for logged database(s) ...
comp = 11, fnc = 82, tracePt = 102
3D000000 Media Recovery Replay (25985 MB): comp = 11, fnc = 82, tracePt = 102
3D000000 comp = 11, fnc = 82, tracePt = 102

3D000000 comp = 11, fnc = 82, tracePt = 102

3D000000 comp = 11, fnc = 82, tracePt = 102

.. and etc…

1 Rookie

 • 

47 Posts

July 19th, 2011 05:00

So that means that in order to speed up the restores from incr. backup I should use

NSR_PREFETCH_LOGS=5
Is it actually possible to set this Integer number on 10 or higher?

And I have 2 questions more related to the NMDA …

1).
When the paramterer NSR_BACKUP_LOTUS_DIR is set to False for example

LOTUS {       

Notes_ExecDirectory = "D:\Program Files\Lotus\Domino"

NSR_BACKUP_LOTUS_DIR = FALSE

NSR_NOTES_INI_PATH = "D:\Program Files\Lotus\Domino\notes.ini"

PATH="D:\Program Files\Lotus\Domino;C:\Program Files\Legato\nsr\bin"

NSR_SKIPDBERRORS=TRUE

NSR_BACKUP_LOGS_MODE ="1"

NSR_PREFETCH_LOGS=5
}

And done a full backup only the transaction logs are going to be backed up and also marked for Domino as reusable. Are those Transaction logs still valid for the proper recoveries (for the case that the disk used for transaction logs on domino server goes full)


2.)
Any idea how to solve this error


The transaction log recovery failed with the error message:

The call to NSFRecoverDatabases() failed with the error:
Recovery Manager: Log scan in progress. Reboot of Domino server doesn’t help….

Thank you.

334 Posts

July 19th, 2011 15:00

Yep, it's possible to set the NSR_PREFETCH_LOGS to a larger value. We witnessed a customer setting it to 50 when restoring 700 logs.

  1. 1)  Yes, the log backup is valid and will be used for recovery as needed.

  2. 2)  The error message comes from Domino. Usually, restarting the Domino server solves the issue. Ensure that all Domino processes, especially the log process (nlogaiso.exe) are restarted.

  3. Allan

1 Rookie

 • 

47 Posts

July 22nd, 2011 03:00

Thank you Allan,

evth. is working fine now.

No Events found!

Top