Highlighted
8 Krypton

Re: The clients are auto restarting backup after concluded. How can I fix it?

Jump to solution

Hi Gouvea,

I would go in the direction of bingo, check the interval set in the group configuration, and also, despite autorestart is oriented for failed backups, check if you have that option enabled.

Also, based on the output of the mminfo command I don't see any duplicated backups, in other words, you have one backup per day, and not 2 or more, as it should be based on the description of your issue.

Thank you,

Carlos

0 Kudos
gouvea2
1 Nickel

Re: The clients are auto restarting backup after concluded. How can I fix it?

Jump to solution

Hi..

Only LI1sfsr30001 E: \ is restarting 3 times before recording the Index, other clients in the same group end with success.

Does the client to record a certain file cannot write and enters in looping and back to save the file?

Is there a Set to not let  it get into looping?

Follow bellow the Set (client and group).

sets_li1.jpg

0 Kudos
8 Krypton

Re: The clients are auto restarting backup after concluded. How can I fix it?

Jump to solution

First of all, could you please explain which mmminfo parameter you use to show the column DAI|EEE ?

-----------------------------------

Let's assume then that NW does not start the group - otherwise it should restart more than this client. Correct?

The only logical consequence would be that the NW client itself starts the backup. And this is possible.

There could be a forgotten Windows task to backup E:\ and associate the backup to a group  ("save -g <groupname> E:\"   is in fact a valid command). That would make the backup appear like a saveset which has been created by running the group.

However, it would have the level 'manual' because you are not allowed to use the level along with the 'save' command.

On the other hand, that would also explain why the index is only saved once.

At least i would check the Windows task scheduler as well ...

0 Kudos
8 Krypton

Re: The clients are auto restarting backup after concluded. How can I fix it?

Jump to solution

gouvea wrote:

Hi, I did extract of mminfo as requested to better show, but I changed the real name to preserve right of customer.

I also do not see timestamp which was requested in original query, but ok.  Let's see what do we have...

  • on 22nd E drive run fine - it completed within same day it was started
  • on 23rd E drive run twice; once it completed within same day it was started and second run completed next day
  • on 24th E we have similar picture as on 23rd except that second run either failed or it was aborted
  • on 25th E drive run 4 times, last run went into next day
  • on 26th E drive run twice

I do not think this is an issue with group interval as some have proposed as then we would see other savesets following same pattern - obviously not in this case.

Next thing to do is to check logs.  Run mminfo command, but this time make sure to include those (20) value so you get exact timestamps and check daemon.raw if it has anything inside around that time.  Also, consider update as it has been said before.  You mentioned Windows NT which bring me to question - which OS is affected client?  Now, if this client is something normal and more modern, it is not a problem to have that client only updated for NW version.  Which version of server do you run?  Last, but not least, is this pure file system backup or you also use kind of savepnpc?

0 Kudos
gouvea2
1 Nickel

Re: The clients are auto restarting backup after concluded. How can I fix it?

Jump to solution

reply from crazyrov : 


Do you have the savegroup competition notification or extract from the daemon.raw that says why the saveset is being started from the beginning? Also is this behavior with only one group or multiple groups. Can you keep the retry change the retry attempts on the Group properties to 0 and see what the result is ?


 

Fixed. I did your clue with Successful. Thx a lot...(everyone)

We can conclude that is a not an error, because when is detected that some files could not be opened and was not backed up. (The process cannot access the file because it is being used by another process.) and the value is set >0 is re-executed again and retrying the clients.

Retrying_fixed.jpg