Is this a cold backup or hot backup? Do you use any script to backup?

Do you have any other related error message?

What database is this?

Are you using any NetWorker module to backup database?

Prajith,

These are Sybase files being backed up. No Module is being used.

Thanks

Bob

Try to run a manual backup from the client with this command, you might find some error message there. Paste it here.

save -vvv -D9 -s

Example:

save -vvv -D9 -s bkpserver /var/db/

This is a hot backup. They use a script for scheduled backups and they also run manual backups

No more error info is available

Thanks

Bob

Backup ran….. here is the log…

Thanks

Bob

I don't see any specific error in log.

Can you try backing up some other file or folder, other than this database. See if it works.

If I understand correctly, someone is using script which does Sybase dump and then you call NetWorker to save that dump with file system backup. Right?  If so, I assume error from your first message comes from script and to know where it breaks we would need to know what script does at that point (as error doesn't look like anything that comes from save command).

Can you check if the file in question is available on the system? Looks like it might have deleted after the backups of the saveset was initiated.

The file is there after the backup……could it be some type of warning?

Thanks

Bob

Here is the script we are running…..

We are running this across 5 clients. All are getting this error…. Nothing has changed in the script

Thanks

Bob

Error you get is caused by condition as seen in line 680.  It says that $dsmcfilesize is 0.

This comes from dsmcfilesize=`echo $dsmcfilesize2 | tr -d ','` and that comes from dsmcfilesize2=`echo $filestri | cut -d " " -f1,1` and filestri=`grep  ${STRIPE_file[fnum]}  $LOGFILE1`.  We can go further down the road, but to get an idea where the script fails you need to test it manually and enable debug logging on it (-vx) to see what values do you get and verify them.

You should also check with mminfo if backup is there for the sake of verification.

Hrvoje,

Well the script dump size and networker dump size are the same. But we are not sure why the error flag is being thrown out. This is not my script so I am having the owners look at it to see if they see anything that might cause false error.

Thanks

Bob

Exactly my point - you can place set -vx or if particular function needs to be isolated, just copy it and run it to see where exactly does it pick up the value which leads to error being reported. But of course, script owner should be the one to check it.