save script problems

[Till]

Hi All

I cannot get a self defined script running in a group. I have entered the name of the script(i.e.save.cmd) in the backup command field and the path to the executables in the executable path field i.e. "C:\program files\legato\nsr\bin"
of the client in the group.
But I always get the error message "attribute save set must have a value"
As far as I know the save set is defined in the script but it simply does not work.
We are running Legato NetWorker 7.1.3 on Windows2003

Thx in advance

Till

 

[NWNinja]

You must have an entry in the saveset field, "All" for example. You want to perform some actions before the client
is backed up, like taking down a database, is that correct?
In that case, you should use savepnpc as backup command and then call your script in the savepnpc script.
Take a look at savepnpc in the admin guide for more info.

http://web1.legato.com/infodev/publications/NetWorker/WINDOWS/7.2/winag.pdf

Cheers!
Maverick

 

[Till]

Thanks Maverick

No, it is not about stopping and starting databases, I want to backup network drives attached to a Win2k3 server. I know that this is not easy but a workaround is mentioned in a previous thread


cheers till

 

[NWNinja]

Ah, ok, then you could probably use the UNC path in the saveset field. If the client has W: mounted to \\server\folder
you use \\server\folder in the saveset field, W: will ofcourse not work. Have you tried this?

 

[Till]

Hi Maverick

It is strange. If I execute the batchfile from the command line with a simple doubleclick it works fine. The starts and backs up the mapped drives mentioned in the input file like \\server\share.
But if I start the script via a group I get the error message "invalid save operations resource string cannot be processed" and "save: cannot stat \\server\share: invalid argument"
Do you have a clue about this ?

Thx Till

 

[Skippi]

I think that reason is simple: save command is running usually under SYSTEM account, which doesn't have access to network.
Try to change "remote user" and "remote password" entries in client definiton.

 

[NWNinja]

I agree with Skippi, it might be caused by an access problem.
But... The "Cannot stat" error messages *usually* indicates that NetWorker does not have a clue as to what you want to do, like if you add E: to the saveset field but the machine does not have a fixed E: drive. Try just adding the \\server\folder in the saveset field and give it a try, if you haven´t already tried this. Also, try not to use the "share name", but rather the actual path to the share.

Cheers!
Maverick

 

[Till]

Hi All

News about the call. Meanwhile I managed to start the script wia the group, group runs successful but only 1Kb gets backed up...
Has anybody seen this behaviour before ?

Thx Till

 

[TDun]

Try posting the script. The way a backup command works is that it will be passed the parameters from the examination of the client. So, fo a Save Set attribute of All, i would return eac of the hard drives.
If your script is using parameters, this could be the problem.
Otherwise, it could be permissions, try setting the Administrator (or whoever you are logged in as when it works from the command line) and password on the Remote tab of the client.
The main thing is, if you are not taking the feedback of the saveset attribute, you don't ned to schedule it in Networker, use scheduled tasks in Windows.