UNSOLVED

Tomi

updated

20 years ago

T

Tomi

36 Posts

0

1468

December 25th, 2006 07:00

Legato Networker fails to backup Lotus Notes

Hi there,

Just to say I'm pretty new to backing up Lotus Notes with networker. Figuring out the problems isn't very easy. But here's some stuff I've seen so far.

I got a problem with networker backing up 1 notes instance. The server has 3 notes instances and the other 2 work just fine. All are timed to backup at different times. The one with the problem starts to backup nicely and then suddenly stops when ~200MB has been backed up.

Anyone has any ideas about this problem (logs posted below)? Btw, is there any switches to make networker do backup even if it receives errors?


--------------------------
Dec 24 02:43:18 networker_server logger: --- Unsuccessful Save Sets --- Dec 24 02:43:18 networker_server logger:
Dec 24 02:43:18 networker_server logger: * lotusnotes01.server.com:NOTES:E:\Lotus\Instance03 savegrp: suppressed 4 lines of output - Dec 24 02:43:18 networker_server logger: check daemon.log for details.
Dec 24 02:43:18 networker_server logger: * lotusnotes01.server.com:NOTES:E:\Lotus\Instance03 nsrnotesv: Exit code: 3 Dec 24 02:43:18 networker_server logger: * lotusnotes01.server.com:NOTES:E:\Lotus\Instance03 nsrnotesv: Parent Process had been terminated.
Dec 24 02:43:18 networker_server last message repeated 2 times Dec 24 02:43:18 networker_server logger: * lotusnotes01.server.com:NOTES:E:\Lotus\Instance03 nsrnotesv: The operation was aborted Dec 24 02:43:18 networker_server logger: * lotusnotes01.server.com:NOTES:E:\Lotus\Instance03 nsrnotesv: Backup failed for E:\Lotus\Instance03\file1.nsf
Dec 24 02:43:19 networker_server logger: * lotusnotes01.server.com:NOTES:E:\Lotus\Instance03 nsrnotesv: The operation was aborted Dec 24 02:43:19 networker_server logger: * lotusnotes01.server.com:NOTES:E:\Lotus\Instance03 nsrnotesv: Backup failed for E:\Lotus\Instance03\file2.nsf
Dec 24 02:43:19 networker_server logger: * lotusnotes01.server.com:NOTES:E:\Lotus\Instance03 nsrnotesv: The operation was aborted Dec 24 02:43:19 networker_server logger: * lotusnotes01.server.com:NOTES:E:\Lotus\Instance03 nsrnotesv: Backup failed for E:\Lotus\Instance03\file3.nsf
Dec 24 02:43:19 networker_server logger:
--------------------------

Also when I tested to backup it at a different time I got pretty much same errors except this line.

--------------------------
Dec 24 18:17:46 networker_server: * lotusnotes01.server.com:NOTES:E:\Lotus\Instance03 nsrnotesv: Error returned for E:\Lotus\Instance03\file4.nsf by Notes API, error = 265 (File truncated - file may have been damaged)
--------------------------

Versions:
NML 2.2
NW 7.2 build 15
Lotus Domino 6.5.5

O/S: Win2003 Server SP1
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    468

    0

    Posted December 25th, 2006 09:00

    7.2 build 15? That sounds more as beta1 to me than a proper version. Are you sure about that?

    Try to run backup of each db individually. In first example file1 to file 3 are aborted (I assume inactivity) while in second example we see file4. By running backup individually you will probably find that certain or even single db is causing a trouble and you should eliminate it then.
  • Tomi

    36 Posts

    468

    0

    Posted December 25th, 2006 14:00

    The server has 7.1.3 version of networker. That 7.2 was for the client which I guess doesn't have anything to do with notes backups?

    Anyway today I updated the client to 7.2 build 172.

    I'm wondering if the problem is client side or server side?
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    468

    1

    Posted December 26th, 2006 05:00

    You really wish to be on 7.2.2 or 7.2.2 jumbo and not 7.2.

    Problem seems to be client side related - and blind guess would be Notes db itself, but for that you need to run several tests to verify it.
  • Tomi

    36 Posts

    468

    0

    Posted December 26th, 2006 08:00

    What kind of tests are we talking about?

    I'll get the client updated to 7.2.2 then.
  • amediratta

    2 Intern

    •

    2014 Posts

    468

    0

    Posted December 26th, 2006 08:00

    I recently resolved one such issue by upgrading to 722 aqnd nml 221.

    Try this out.
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    468

    0

    Posted December 27th, 2006 03:00

    What kind of tests are we talking about?

    Testing (backup) database files individually.

    As suggested before, try to update environment first and see if that will help (even if this is something on db end it won't).
  • Tomi

    36 Posts

    468

    0

    Posted December 29th, 2006 00:00

    There was one .NSF file damaged and that was why the backup didn't complete succesfully. We replicated the file from another location and now backups are running fine.

    Thanks all for your help!