Backup group did not start, get interrupted or fail

Question

We have around 40 servers backed up as full backups onto a backup server using a tape library with 2 drives. All of the backups completed fine this weekend just gone, until I looked closer. One of our servers did not complete. This server's backup was enabled and scheduled at the right time, it uses the same schedule as 15-20 other servers. It was not interrupted, it did not fail, it just didn't attempt to run. Checking the logs does not show anything for this server - in Networker. Both the server nor the backup server was rebooted. All other save groups completed fine. Anyone have any experience of this having happened to them? Any ideas why?

dugans1 · Answer

Check Forward and Reverse NDS for this box,
Also check the Status of the Networker remote backup service.

How did you investigate this problem? did you get an email save group report from the server group?

you could also try and do a small backup from the client to see that there are no problems. If this works.

Create a group called a test group with a test pool. Give it a retension period of 1 day and add this server to this group. Ammend the selection list to just backup a really small directory to test sucking the backup from the client rather than pushing it from the client.

Also chech the scedule on the client setup that it is not set to skip.

Let me know how you go

Also whjat version are you running? and any patch levels.

HabibG2 · Answer

Try a manual backuup from the server.Try a client initiated backup.Let us know the outcome.Do you have defferent group for each backup.Could it be that the client has been accidently removed from the group?Check your client configuration.

DavidHampson · Answer

I have seen similar things before which seem to happen when the server has a lot going on at once; try spreading out the start times of your backups.

dugans1 · Answer

yeah thanks mate for repeating what i said.

HabibG2 · Answer

Was not intentionally I can assure you . I have more important thing to do. Its just that sometime message does not get refresh soon enough.My apologies if you are affended.

ble1 · Answer

(happens quite often here actually)

MarcLewis · Answer

Thanks for all your responses.We are running networker 7.4.2 on this server.The backups are checked by the PC support, firstly visually where they just look for the ticks, and then all the backup groups send an email which is when they noticed the backup didn't send a failure or a warning, and that it appears not to have run.I completed the backup manually last night without any problems.We already have our backups spread out over the course of Friday evening to Sunday morning start times, so there is usually no more than 2 or 3 servers backing up at the same time over the weekend.Was just a very strange occurrence that I was wondering if anyone else had seen!

dugans1 · Answer

Marc,Thanks for the update.I have around 90 servers and i have seen some strange things. I have seen a situation where a group will start and for some reason not complete. This could have been due to the library could not load a tape or the job timed out due to and index destination not being available. In my environment i have indexes go to a disk location and then cloned off to tape and replicated to our Second Data center for DR purposes. as for just not starting maybe it is a glitch in the matrix and you should call Neo.all the best

NetWorker

Was this post helpful?