rwstarkey

Anyone have anything more on this? I have emailed Retrospect. Am I the only one having this issue? Thanks.

John I'm not sure but I don't think so. It has sent me notifications of every completed script normally but didn't yesterday. I really need it to notify me when any script completes. I wasn't aware of any limitation on that for notifications. I average 4 scripts every 24 hours but they are all different scripts. It acts more like Retrospect is just skipping notifications randomly.Thanks.

Hello, Retrospect windows 8 latest often is failing to send email notifications. Not reliable at all. Very sporadic. When will this be fixed? I am charter which is a national cable company, surely it should work fine. I have $50 FTP programs that do fine on notification. We have thousands invested here and it's very frustrating that this feature is not reliable. What can you tell me? What is the most reliable set up? Gmail? What is the best smtp server if I use gmail. Thanks. --Randy Starkey

Right. I already have multiple backup sets and they are rotated offsite. My drives are hard disks in carriers. From what you are saying it appears I can't just easily remove a member, so I will simply delete the backup set and create a new one and do a fresh backup. I prefer one clean member per set. I don't need to transfer any source backups as I don't care about any older backups on this set. A recycle would be fine. But I think just creating a new set is easier. I'll delete the old set and make a new set by the same name. Will make sure the scripts pick that up. Thanks.

goal - I have 2 drives listed as members. I want to only have one. So I want to choose a new member and do a recycle.

In looking at my backup sets, the members tab, the option to remove them is always grayed out. what am I missing? I simply want to remove some set members and replace them with one member. I assume I'd have to recycle after that. So can't I do this without having to redo the whole backup set? Version 6.5 multi-server. Thanks. --Randy Starkey

OK.

Hello? Any answers for me on this one? Thanks.

Hi, Is there an ETA on a fix for the issue when a grooming script is run and the drive is not present, tha tthe only way of canceling out is to hit choices and mark the memebr as missing. This is a royal pain as then you have to go back and uncheck the member as missing to be able to use the drive again later. Thanks, --Randy Starkey

Russ, Believe me, I'm familiar with every backup pref and NONE of them solve the problem. As you said in your second paragraph, it's way too sensitive in some areas somehow - who knows where - and those areas need to be brought out front into GUI options. I'm windows, so with all their MAC issues now I don't expect this to get addressed for awhile unfortunately. It just MUST be addressed in the next windows release, IMHO.

Re: Wikipedia and Google. Right. Thanks. I use them of course. But I really want to hear from Retrospect on it because I have no idea what they consider or look at in their backup process related to metadata or how it's treated. Somehow Retrospect is considering something a "new" file when it really shouldn't. --Randy

maurice - what exactly is block level de-duplication? Thanks, --Randy Starkey

Robin, What is meta data? What is included in it? We need some options on this. If Retrospect is so sensitive that the same file is backed up again over things that don't matter, that is a royal pain. what exactly is included in meta data? Thanks, --Randy Starkey

Robin, When you get to it please fix 2 things... 1) when a grooming job can't reach a disk for some reason so often you have to do choices and mark the disk damaged just to cancel the operation. Ugh! otherwise it just hangs. 2) figure out why retrospect insists on backing up files that are identical just because they have been moved to a new disk. The disk should not matter. the files are the same. This is WITH the location does not matter option checked. Thanks, --Randy Starkey

This is the exact type of problem I am having. I had a data drive go bad - replaced it - was able to move the files from the bad drive to the new drive - and retrospect insisted on backing them all up again. I have the same check boxes checked as Lennart which should stop this, but it doesn't. So there is something Retrospect is seeing causing it to reback up all these files when in reality none of them have changed. The disk info should be totally irrelvant, it should be file info only that is considered. So what is Retospect seeing that is triggering this? Whatever it is, it's wrong.