Backup Failing with Return Code 1 Error

[ee01akk]

I was wondering if you could help me on the problem below. Logs attached to email.

The following message is appearing in the daemon.log:

12/02/08 23:41:08 savegrp: command ' save -s 3ccbackupserver -g DailyMail -LL -f - -m lndom01 -l full -q -W 78 -N
"D:\Lotus\Domino\Data\MAIL\emea" "D:\Lotus\Domino\Data\MAIL\emea"' for client lndom01 exited with return code 1
12/02/08 23:41:08 savegrp: Log file D:\nsr\tmp\gDailyMa000004 is empty.
12/02/08 23:41:08 savegrp: lndom01:\Lotus\Domino\Data\MAIL\emea unexpectedly exited.
12/02/08 23:41:08 savegrp: lndom01:\Lotus\Domino\Data\MAIL\emea will retry 1 more time(s)

12/02/08 00:08:38 savegrp: Aborting inactive job (197176) lndom01:\Lotus\Domino\Data\MAIL\emea
12/02/08 00:08:38 savegrp: command ' save -s 3ccbackupserver -g DailyMail -LL -f - -m lndom01 -l full -q -W 78 -N
"D:\Lotus\Domino\Data\MAIL\emea" "D:\Lotus\Domino\Data\MAIL\emea"' for client lndom01 exited with return code 1
12/02/08 00:08:38 savegrp: Log file D:\nsr\tmp\gDailyMa000003 is empty.
12/02/08 00:08:38 savegrp: lndom01:\Lotus\Domino\Data\MAIL\emea unexpectedly exited.
12/02/08 00:08:38 savegrp: lndom01:\Lotus\Domino\Data\MAIL\emea will retry 1 more time(s)

It appears to be happening around the time the meesages.logs stops receiving messages.

Using Win 2003 SP2 and Networker 7.3.3 for the server.

Any ideas on what could be causing this error?

I have also noticed the following errors below in the daemon.log, but I have got the user to check the clients below in the hosts folder on the Networker Management Console and delete them so Networker can re-create them when they try to connect to the Networker server again.

12/03/08 01:34:24 nsrexecd: SYSTEM error: There is already a machine using the name: "emeafs02.global.corp.3com.com". Either choose a different name for your machine, or delete the "NSR peer information" entry for "emeafs02.global.corp.3com.com" on host: "3ccbackupserver"

12/02/08 21:51:38 nsrexecd: SYSTEM error: There is already a machine using the name: "leiconnector.eur.3com.com". Either choose a different name for your machine, or delete the "NSR peer information" entry for "leiconnector.eur.3com.com" on host: "3ccbackupserver"

12/02/08 20:45:00 nsrexecd: SYSTEM error: There is already a machine using the name: "eurworkgroup1". Either choose a different name for your machine, or delete the "NSR peer information" entry for "eurworkgroup1" on host: "3ccbackupserver"


Any ideas on these errors?



Regards,
Anil.

 

[605]

I can not explain the backup problem but the "NSR peer information issue". It has to do with the Local Hosts resource and its associated peers. Obviously there is a name resolution problem this causes the problems. Worst case, exchange the appropriate peer information for the local host "3ccbackupserver" as suggested.

 

[ee01akk]

emeafs02.global.corp.3com.com is a backup client of 3ccbackupserver but its also a storage node.

So can I just delete these client entries under host 3ccbackupserver, in the local hosts section of the NMC, and Networker will re-create them if their name/names have changed??

 

[a060463xyz]

It looks like your Backup Problem occurs in the Data directory of your Notes Server. Is the Notes process running during your backup ?
If yes maybe there are locks on some important files.
If you use a notes modul for Lotus the you can skip the Notesdata directories using a directive.
If you dont use a notes modul you should consider it or shut down the notes Process with a savepnpc script.