Hello Sarah,

I have a couple of questions. When you say "Duplicated save sets"

- Do you mean that the save set ID is the same?

- What kind of save sets are we talking about, are they file system backups or is there any module involved?

- Could you please provide us with some example?

Thank you.

Carlos.

Can you confirm that these are not fragments of the same savesets that may be spanning tapes (check the ?  You may want to use mminfo and post the results here if the results look suspect:

mminfo -v -q "ssid=ssid"

You want to look at the flag which indicates if the saveset is (c)omplete, (h)ead, (m)iddle or (t)ail.

This is happening every 2 hours so have you set your group run interval to be 2 hours instead of the default of 24 hours?

Hi Carlos,

I tried to post the screenshots here, but didn't work =/

The backup job are file system with diferent SSID, but the same job (once executed) create 2 or more savesets in the same midia with different sizes or not.

See mminfo output below:

volume        type   client             date           time       size      ssid             fl  lvl   name

000053         LTO Ultrium-4 pavo     26/04/2011 08:44:34  173 GB 3702963931 cb full /u01/app/backup
000053         LTO Ultrium-4 pavo     26/04/2011 10:44:35  182 GB 3686193809 cb full /u01/app/backup
000053         LTO Ultrium-4 pavo     26/04/2011 12:44:36  182 GB 3669423795 cb full /u01/app/backup

This backup job was performed only once but in exact range of two hours ( as you can see in time field ) this created 3 savesets with different ssid in output above.

It would be useful to see the log output for this job.  I am wondering if the file system backup completes but somehow the group decides it hasn't and restarts, I've seen something similar in the past though I cannot remember the details at present!

When you say the event only occurs with some of the clients in the group I am making the assumption that it is the same clients each time and they consistently show this behaviour.  Is the 2 hour separation we see in the example consistent too or is that just coincidence (and does this correspond to the inactivity timeout on the group)?

David,

The scheduled interval follows the default configuration (24:00).

Another important detail : this event occurs only with some clients of the group and not with the whole group.

So, I've seen this event occur to the same set of clients. However, sometimes only one make this duplication...in other cases two or more clients of this set (problematic clients) create a duplicated savesets in the same midia.

In the case previously reported, the time is two hours ... but in other cases identified it can vary, see examples below

000069         LTO Ultrium-4 birro    28/06/2011 02:48:52  100 GB 3305732595 cb full /u01/app/backup

000028         LTO Ultrium-4 birro    27/06/2011 11:37:57   38 GB 3607667725 cb full /u01/app/backup

(same client, different midias, same job - running once time -  )

000053         LTO Ultrium-4 anhuma   25/04/2011 16:30:19   88 GB 4155890051 cb full C:\Backup

000053         LTO Ultrium-4 anhuma   25/04/2011 20:28:53   88 GB 3853914476 cb full C:\Backup
000053         LTO Ultrium-4 anhuma   26/04/2011 00:28:57   22 GB 3753265623 tb full C:\Backup

(same client, same midias, same job - running once time - interval for 4 hours )

Hello Sarah,

I agree with David that would be interesting to check the output of this job.

As far as I know we have clarified that the interval set for the group is 24:00, correct?

Is this happening with only some clients within the same group or separate groups?

What is the OS of the clients having this "issue"?

Could you please run the group for those affected clients in one group, and provide us with the output? (Please compress and attach in your next reply /nsr/tmp/sg/group_name_folder)

Thank you.

Carlos.

Hi Rfreund

I discard the possibility of backup job has been executed/started by any user through software interface or even command line.

I really believe that this event is a critic problem from the moment at duplicate savesets process consumes my network bandwidth, storage media and time.

=/

@sarah

In general, there is nothing wrong to have multiple save sets on the same media - due to the different ssids. It is only an issue when you do not expect this not to happen.

Now when NW does not initiate the backup, somebody else could do that. Do not forget that somebody at the client could create manual backups even with levels (save -l level ...). And if he schedules this via Windows then you will not see these jobs in the savegroup report although the backups are alike. Also look at the scheduler on the server - there might also be a forgetten task.