Ericfoos

Does anyone running Windows version 10 know if you can bind the client to a specific address again? Thanks

Yeah, thanks for your input.

Yeah, the pattern of leaving a group of snapshots behind is what I'm used to seeing when some bit changes to make the server think it is a new client. The backups don't complain at all for any client that does not groom.

It's a new set. Had a disk failure a few weeks ago so I started from scratch on the new disk. Dates are 8/13,14,20,21,22,25,26,27 The dates for the 8 snapshot client in the restore area that have a human head are 8/20,21,25,26 The other 4 snapshots have a computer icon.

Unfortunately not. I have seen taht behavior before when moving users to new computers. I have purged the offending snapshots to the grooming specifications and subsequent backups continue to not be groomed requiring me to manually groom again. I did notice in the "Restore" area that some backup clients have human heads instead of computers. Not sure if that is part of the problem or not.

I have a backup set called Desktops. It runs overnight to disk. In the morning a groom script runs. The backup set preference for grooming is the last 4 backups. Onlycertain clients groom correctly. I have to go in and manually forget the old snapshots for the clients that do not groom automatically. Has anyone else seen this? Is there an easy solution? Manually removing snapshots is very time consuming.

I found out the 8.5 client does not have this functionality yet. I am using the 7.7 client which does. It is on the "things to do" list.

I also tried 'retroclient -ipsave xxx.xxx.xxx.xxx'

I upgraded my client on Exchange from 7.6 to 8.5. Removed 7.6 client. Installed .NET 4.0 Rebooted. Installed 8.5 client. Need to bind the client to a different interface than it is grabbing. With the old client you would modify BindListener in the registry but I am unable to find that value after the new client install. Looked in the manual and searched but only found the BindListener instructions. Thanks!

Good to know. Grooming has been awesome since 8.2. Thanks!

I'm running 8.2 and it's working for me.

I got the same error in Retro 8.1 with 2 windows clients that are running in a VM. They work fine in my 7.6 installation.

This helped me out too! New install, using local server to relay. The error message is not much help.

I am trying to restore some files. The restore log says member is "Reported missing by user" I go to the backup set and look at the member in question and it not marked as lost or damaged or to be skipped. Meanwhile, backups have been working to this member, grooming has been working, and I can browse the snapshot to see the files. But I cannot restore them! MultiServer 7.6.123 Update and hot fix 7.6.2.101 Member is a disk.