Save set NOTES: aborted and removed , why?

Question

Hi! It is my first post here I have question about newly configured Lotus Domino backup. During backup I've got following error: 07/23/06 16:42:24 nsrd: lotusdomino:NOTES: saving to pool 'diskpool' (diskpool.001) 07/23/06 16:45:50 nsrmmd #1: save set NOTES: for client lotusdomino was aborted and removed from volume diskpool.001 07/23/06 16:45:50 nsrd: media info: save set NOTES: for client lotusdomino was aborted and removed from volume diskpool.001 07/23/06 16:45:50 nsrd: lotusdomino:NOTES: done saving to pool 'diskpool' (diskpool.001) 2651 MB 07/23/06 16:45:51 nsrd: lotusdomino:NOTES: saving to pool 'diskpool' (diskpool.001) pools supported: diskpool; Why do I see aborted message? What is the cause of this? About config: NML v3.0 NW 7.3.1 server&client Lotus Domino 7.0.1 here is configuration of NML client (variables I added/modyfied): NSR_DEBUG_LEVEL=3 NSR_DEBUG_FILE = C:\Progra~1\Legato
sr\applogs\lotus.log NSR_COMPRESSION = TRUE NSR_SKIPDBERRORS = TRUE NSR_BACKUP_ALL_EXTENSIONS = TRUE NSR_BACKUP_PATHS = D:\Lotus\Domino\,E:\Lotus\Domino\data\ NSR_CATALOGFILE = C:\Progra~1\Legato
sr\applogs\catalog.txt Notes_ExecDirectory = 'D:\Lotus\Domino' PATH = 'E:\Lotus\Domino;E:\Lotus\Domino\data;D:\Lotus\Domino' When I look into the lotus.log, there in no sign of aborting! Help please!

ble1 · Answer

Yes, it is a bit strange to see it aborted after 3 minutes. It looks like server side action, but no idea why. If you try again do you see it fail again? Unless someone stop it and unless there is anything else in the log everything remains upon guessing. However, if it happens again enable debug mode and I guess log should have more details then.

I would also try to avoid NSR_COMPRESSION as it is usually CPU intensive on client side - if you have enough horse power then fine...

abartosz · Answer

On secont try, here is what I've found in lotus.log file:

(pid = 5880) (date = 2006-07-23 18:16:35) Could not open file E:\Lotus\Domino\data\P21\PStatMail.ns5, error = bmlOpenForRead: Could not open file: E:\Lotus\Domino\data\P21\PStatMail.ns5.
(pid = 5880) (date = 2006-07-23 18:16:35) Skipping file: E:\Lotus\Domino\data\P21\PStatMail.ns5, Failed to open the file, error = bmlOpenForRead: Could not open file: E:\Lotus\Domino\data\P21\PStatMail.ns5.

There is no other errors

abartosz · Answer

Here it is

07/23/06 18:16:48 nsrmmd #1: save set NOTES: for client lotusdomino was aborted and removed from volume diskpool.001
07/23/06 18:16:48 nsrd: media info: save set NOTES: for client lotusdomino was aborted and removed from volume diskpool.001
07/23/06 18:16:48 nsrd: lotusdomino:NOTES: done saving to pool 'diskpool' (diskpool.001) 60 GB
07/23/06 18:16:48 nsrd: lotusdomino:NOTES: saving to pool 'diskpool' (diskpool.001)

After 60GB!!! of data

Is there any timeout? Lotus databases are quite large (about 20GB each)

Regards

abartosz · Answer

Thanks,'Yes, it is a bit strange to see it aborted after 3 minutes. It looks like server side action, but no idea why.'It also happened after transferred currently of data.'If you try again do you see it fail again?'Yes.'Unless someone stop it and unless there is anything else in the log everything remains upon guessing.'No, As You see server retires NOTES: save set, which is curently being backuped (I currently waiting for completion), so group wasn't aborted and there is no failed save set in the group's details.' However, if it happens again enable debug mode and I guess log should have more details then.'Ok, how can I turn debug mode and which Networker daemon?'I would also try to avoid NSR_COMPRESSION as it is usually CPU intensive on client side - if you have enough horse power then fine...'Ok, if it fails now, I'll try turn it off, but Lotus server is rather powerful Thanks again.

ble1 · Answer

I assume above NSR parameters are from config file which is called via backup command, right?

In that case obviously SKIPDBERRORS does not apply to error you listed above (as it is critical and not non-critical). Can you have DB admin check that file? I can't say if this error is the problem as previously it failed much earlier. One way of perhaps seeing that is by doing manual save from client of smaller parts one after another (thus identifying faulty db files).

When I said debug I was referring to debug of module itself - check admin guide pg 143&144 for NSR_DEBUG_FILE and NSR_DEBUG_LEVEL options.

abartosz · Answer

Ok, after some more observations, here is what I've found:
1. As You've seen this problem apperas ranadomly (after 2GB or 50GB or 64GB)
2. NSR_COMPRESSION doesn't work IMO. I've backuped 16GB NSF file with comperssion set to true and it has 16GB on backup disk.
3. When I removed following parameter NSR_BACKUP_ALL_EXTENSIONS = TRUE, backup of 84GB has been successful!!!.
4. The problem is that we have some more files which don't have typical file extensions such as *.ns5 and *.ns4. As You see NML 3.0 can't backup this files, but they are used by Lotus Domino 7.

ble1 · Answer

As for compression part - perhaps DB data is already in shape that cannot be compressed. Try to make zip copy and see how much it gets compressed.

As for backup part problem, I would suggest to open this with support at this point - they should be in position to get this fixed once they confirm what you claim (perhaps it is already known issue - you never know).

StefanHa1 · Answer

Unfortunately I have to raise this thread from the dead, but has this problem been addressed and / or solved in some way?

Currently with the NMDA Module 1.2 backing up with NSR_BACKUP_ALL_EXTENSIONS:"TRUE" still produces errors similar to those above. In my case the backup process trips over transaction log files of Notes (*.txn) as well as some regular Logfiles (*:log)

NetWorker

Save set NOTES: aborted and removed , why?

Was this post helpful?