Do you get any output in daemon.log or see any action in the Operations tab? Maybe no tape is found or no drive can be allocated.

It's not a tape or drive issue, clients in the same group using the same media pools run fine.

I checked the daemon.log again after I started the backup again and there is a issue with the client. It says there is already a machine using the name client_name. Either choose a different name for your machine or delete the NSR peer information entry for the client_name.

There is not a another client with the same name and I believe there never was. I looked inside /nsr/index on the server and there is only one entry for this client..

Could it be talking out on the network?

Fulls are also doing it. When I first noticed it I was checking the bakcups first thing in the morning and the savesets had been sitting there for four hours.

Also backups use to run on this client up until I noticed the problem. I checked and the server has not been rebuilt.

How long are you waiting before you stop the group? Sometimes calcultations for incremental backups eat up a lot of time before beginning backup.

I'm all set. The server is being migrated over to two vm servers. This must have something to do with it. The two vm servers are already being backed up.

Thanks!!!

I'm seeing this behavior on a Windows 2000 Server client with 7.3.2 recently installed; Our server is an HP-UX 11 box with 7.3.2 installed. Does anyone have any explanation as to the actual cause of this hanging error? I notice that our backup (the one scheduled for this Friday evening, for instance) will continue to hang until I terminate it on Monday morning. Using the backup client on the Windows box causes the GUI to freeze the second I click "Start" button. Any help would be appreciated.

Hi Diego,

Is that Itanium or PA-RISC? I did notice that PA-RISC version under Itanium has issues with multiple streams (multiplexing) and it would hang... however I still didn't notice group not starting.

Hello Hrvoje,

It's a PA-RISC box, K-class server. The various Windows clients under the same group generally work very well; it's this one window client that appears "stuck". This morning I saw the same behavior: All of the clients completed successfully on a job that started late on Friday evening; I had to stop the job for the group to complete, with the one client still hanging.

Are you using nsrauth or oldauth?