Is there any firewall between the backup server and your domino server ?

And as Hrvoje already mentioned try to stick to the latest supported version of modules. 

Which version of client and module do you use?  Error seems to indicate oldish NML and I believe current version for Domino backup should use NMDA.

Yes, both commands work.

Does it matter that it says rocup0330, if the server is connecting as "rocup0330-mgmt127"?

You should use name reflecting interface you can use from that client.  Otherwise it might use wrong interface (eg, which is not reachable) and then you may get what you see.

From your client, can you do rpcinfo -p rocup0330 and rpcinfo -t rocup0330 390113 1?  Try also to comment out NSR_DEVICE_INTERFACE.

Networker 7.6.3.Build.840

Loaded NMDA module 1.1. Now upgraded to 1.2 and trying again.

Here is the configuration file I'm trying to use:

Lotus

{

NSR_SERVER = rocup0330

NSR_BACKUP_ALL_EXTENSIONS = TRUE

NSR_BACKUP_LOTUS_DIR = TRUE

NSR_CROSS_MOUNT_POINTS = TRUE

NSR_FOLLOW_LINKS = TRUE

NSR_LOTUS_DATA_DIR = D:\Domino\Data

NSR_NOTES_CONNECT_TIMEOUT = 60

NSR_NOTES_INI_PATH = C:\IBM\Domino\notes.ini

NSR_PARALLELISM = 8

NSR_SKIPDBERRORS = TRUE

Notes_ExecDirectory = C:\IBM\Domino

NSR_DEVICE_INTERFACE=DATA_DOMAIN

#NSR_DIRECT_ACCESS=Yes

NSR_DATA_VOLUME_POOL="LotusNotes"

NSR_BACKUP_LOGS_MODE = 1

#NSR_RETAIN_NUM_LOGS = 0

#NSR_DPRINTF=TRUE

#NSR_XBSA_DEBUG=TRUE

#NSR_DEBUG_LEVEL=2

#NSR_DIAGNOSTIC_DEST= E:\nsrlogs

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

}

One of the reasons you are seeing repeated save sets is a result of the Client Retires value.  If it is > 0, then if any of the 8 NMDA threads failed as the log excerpts describe, then all 8 sessions will be restarted.

You may want to consider:

Changing Client Retries to 0 to help isolate your backup failure.

OR

Leave Client Retries = 1+ in order and enable Checkpoint Restart for the NMDA client,  This will allow the backup to pickup from where it left off and can at least protect your Domino data.

ANother item that I can see is the browselist save set appears to be failing.  The browselist architecure changed in NMDA 1.2 and you need to ensure that it can always have an open device session so it can get saved throughout the backup.  This differs from NMDA 1.1 and now 1.6 as browslist gets backed up after the data as opposed to 1.2 where it gets backed up concurrently.

Also, you may want to consider increasing the debug level and using NSR_DPRINTF=TRUE.  If the backup is failing as a result of a communciation based issue, this change will help expose that error messaging for a root cause.

Review the log that has the 4904 PID in its name.  It should conatin the reason the backup exited.

Keep me posted as I am one of the EMC Support SME's that focus on NMDA\Domino issues.

Thanks,

Duncan

Is rocup0330 resolved and accessible form the Domino ?

Is there any reason you didn't try the most current NMDA 1.6?  I believe I had to upgrade ours to 1.6 to get the DAOS backups to work properly (which may not be a big deal if they aren't using it).