Did a small test; I created group and did put inside client with many DIRs to backups (thus creating multiple savesets). When stopping it few times in the middle of the job and restarting it I could not see the problem you are experiencing.

I have seen this same problem on our upgrade. I'm seeing numerous other problems as well. From my point of view, this upgrade has not gone well. It's broken!

Hello,

I just upgraded to v7.3 (from v7.2.1) and everything is working fine. Also tried restart of group and it works OK. From which version have you upgraded to 7.3?

Regards, Ojo

What problems are those?

Why do you believe it rebuilds the work list? What symptoms draw you to this conclusion?

Ask support if changing to oldauth would change some of the errors you see. During beta I had seen those and by disabling nsrauth they were gone.

For me, as I watch the daemon.log it says "Cannot restart group". It then proceeds to complete the entire group again. I upgraded from 7.2 RTM.

As for other problems, I can't clone from a command line (nsrclone), it hangs for a half hour (literally), then finally says something about authentication; SQL backups have an impersonation error in the daemon.log; skip savesets simply hang and won't resolve; my jukebox has been disabled twice and can't be re-enabled without restarting nsrexcd; I have an active support case on many of these. It may be my environment specifically, but these are all issues that were not previously there.

As for the skip problem, Legato now has a hotfix for that. I have it loaded. We'll see if it fixes the problem.

I have seen authentication errors, too. Particularly, "authentication type 0 not adequate." I see this consistently if the server is rebooted. But after restarting the service, backups seem to work again. Still going back to 7.2.1.

For example, I have a group with 10 clients scheduled to do a full backup on Sunday. Nine of the ten clients complete successfully, but one client fails. If I restart the group, all nine clients start a new full backup along with the one failed client. If it resumed from the worklist, only the one failed client should be backing up. At least this was the behavior in 7.2.1.


Message was edited by: mronquillo1

I have same problem in 7.4.1 version. It's seems like BUG.