Unsolved

This post is more than 5 years old

22 Posts

2247

April 1st, 2007 02:00

savegroup: saveset had error indication at completion

Hi,

When doing backup for a client (Backup server and client are W2003, SP1), one of the five saveset give me the following error "had error indication at completion", the other 4 saveset succeeded, whereas the fifth saveset do the backup and once it reach the end it stop and the error is shown.

Any idea.

Thanks

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 1st, 2007 04:00

Try backup of only that saveset and see what happens (client initiated).

22 Posts

April 1st, 2007 05:00

I did a client initiated backup for that saveset as you suggested and it success, no error, so please what i have to do when doing automatic backup.

22 Posts

April 1st, 2007 05:00

I did a client initiated backup for that saveset as you suggested and it success, no error, so please what i have to do when doing automatic backup.

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 1st, 2007 06:00

OK, try now only that saveset, but as server initiated. If that works, try it with other savesets from that box and as last thing together with other clients in group.

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 1st, 2007 09:00

Well, it could be few things. If you can, stop NW server and delete content of /nsr/tmp on server and try again after starting server. This is to see if some cached value is causing server side backups to fail. You can also enable verbosity on backup to see where it fails exactly. Make sure to test this with full and not incremental backup.

22 Posts

April 1st, 2007 09:00

I tried to backup only that saveset as server initiated but still facing the same error.

22 Posts

April 2nd, 2007 08:00

I stop the services and deleted the content of tmp folder and restart the services, when i backed up the saveset i am still getting the same error.

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

April 2nd, 2007 09:00

Ask support to give you dbgcommand, raise debug on server side and try again to see where it breaks and why.
No Events found!

Top