We have had some problems a while ago (NW 7.5.x). Since we updated to NW 
7.6.2.5 and later to NW 7.6.3.5 the environment is pretty stable. The majority 
of our clients are Windows based.

Almost every time, a 'missing communication' between client and server was the 
obvious problem. A save set appears as 'waiting to run' but will never get 
started.

Our best practice is:
  - Restart the NW services at the client. This will bring the savegroup into a 
failed state.
  - Restart the group (for this client: savegrp -c <client> -R <group>)
      Yes, it is a command line operation but it will cut the runtime and save 
unnecessary index backups from the other clients.

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------