What version of Lotus and is the backup successful or do you see it fail? 

As a standard, NetBackup uses the Lotus API's to run backups/restores so I wouldn't expect NetBackup to 'lock' the file on the Lotus backup.  The Windows backup are you using VSS or VSP as the Open File Backup method for that client?  I'd switch to VSS just to clear up any random issue with VSP.

I'm hoping their schedules do not overlap; that one job is finished before the other starts

could be that you are backing up your frontend instead of your backend server for lotus notes? it´s recommended to take backups from the backend.

On the other hand verify that the snapshot option for that server is turned off.

Both Policys are running at the same time. 

I will change that now, and I will check if it is VSS or VSP.  what do you mean frontend, or backend?

Currently we are not running Shadow copy on this server due to space.  Does this need to be enabled for VSS to work.  I just add our lotus server to the Client Attributes and checked VSP. 

VSS needs Shadow Copy and is a lot more stable than VSP which was EOL'd after the 6.x version of NetBackup.  Just out of curiosity, do you know what process has the lock on LOG.NSF? 

^ not sure what Process logs the Log.NSK.  what would be the best way to figure this out.  If I could find that out I should be able to back track what is doing this.  Last night backup ran fine with no isses.

I have changed the policys to not run at the same time.

the backup server didn't have VSS, or VSP on when I went to the master server, and then Client Attributes I added it.

I have been told there isn't surficient space on the server to turn on Shadow Copy.  Should I turn removed the server from Client Attributes and make sure VSP?

Thank you for all your help.  I didn't set this netbackup system up so I am slowly, very slowly trying to figure out what the last Admin did.

If you have space limitations, I'd undo VSP as well as that has a cache requirement as well to capture the files. 

next time this happens, I'd have Process explorer ready and handy to figure who exactly is locking Log.nsk, could be netbackup, could be unrelated but happening overnight who knows.  Here's a nice tutorial on how to capture the info and from there you'll have a good idea what/where to target. 

http://www.microsoftnow.com/2008/10/unlocking-file...

You can also download SysInternals utilities such as 'handle' or 'process explorer' :

http://technet.microsoft.com/en-gb/sysinternals/bb...

Backups ran fine last night.  I will keep an eye on this and if it happens again I will check to see what process is holding up this file. 

Might give Sysinternals a try also to see what is going on.

I also unchecked VSP.

I have a feeling that maybe both backups running at the same time was the issue but we will see.

I will report back if there is a issue.

Well it happened again.

This time i was opening my backup and restore windows on my Master/Media server and the host files seemed to lock up on the Lotus server. "Was still pointing to the lotus client before I changed it"

We find this error every time the LOG files locks up.

Netbackup San Client Fiber Transport service.

Here is what we are seeing.

at 1:10 Netbackup Client service is started  "about when I opened the backup and restore program"

1:10 netbackup client has been started

1:10   Started the version control agent "normal startup"

1:10  Symantec Private branch exchange service started   "source is VxPBX Service"

1:10  Service is stopping  "Netbackup SAN Client Fibre transport service

1:10  Service is stopped

and then hell breaks lose.

1:10  SDGetPortDatabase returned non-standard error while querying count

1:10  RetrieveLunDataForTargets  Unable to get Lun Data (0x45d) (the request could not be preformed because of and I/O device error"

and then we reboot.

HELP me please.

looks like Qlogic HBA driver or hardware issue

did you get this figured out?