Daniels Posted May 18, 2010 Report Share Posted May 18, 2010 (edited) Have you made sure that both the Finder and Retrospect know that the shares you are using as members are mounted? If the share is not mounted in the Finder, Retrospect may not be able to connect to it properly and report it as missing. You may also want to check permissions on the shares to make sure you can store the backup on them. I would also try mounting the shares in Retrospect and the Finder using smb instead of afp. We have a Snap Server and in order to connect to it properly we have to use the smb protocol since afp will not validate the user name and password correctly. Edited May 18, 2010 by Guest Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted May 18, 2010 Report Share Posted May 18, 2010 Have you made sure that both the Finder and Retrospect know that the shares you are using as members are mounted? If the share is not mounted in the Finder, Retrospect may not be able to connect to it properly and report it as missing. This is entirely inaccurate; I would advise readers to disregard. Dave Quote Link to comment Share on other sites More sharing options...
Daniels Posted May 18, 2010 Report Share Posted May 18, 2010 (edited) Missing maybe was the wrong word but I have found that if shares are not mounted in the Finder then Retrospect has trouble backing them up. I know this was especially true in 6.1 and I have experienced it in 8.1 as well. The Windows 2000 Server I back up used to use mounted shares and anytime these were dismounted Retrospect could not access them for backup. Maybe in the newer OSes it might sufficient to just be logged into the NAS. Edited May 18, 2010 by Guest Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted May 18, 2010 Report Share Posted May 18, 2010 I have found that if shares are not mounted in the Finder then Retrospect has trouble backing them up. If you read the entire thread you'll see that the Original Poster is attempting to use the NAS as a Member of a Disk Media Set, meaning the Destination, not the Source. Mounting the same share as a Finder user on the Engine host machine that you want Retrospect to also use as a Member of a Disk Media Set has the potential to lead to mountpoint naming issues that can cause backups to fail. All of this is discussed up-thread and in many, many other posts here on the Forum. It is entirely unrelated to any behavior seen in Retrospect "Classic." Dave Quote Link to comment Share on other sites More sharing options...
Daniels Posted May 18, 2010 Report Share Posted May 18, 2010 I guess the rules are different when using NAS as a destination as opposed to a source. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted May 18, 2010 Report Share Posted May 18, 2010 Hate the though of dishing out around $70.00 for support If your data is not worth a $70.00 support call, it's not worth backing up. Good support costs money. Anyone using this product to back up their valuable data should buy an annual maintenance contract. It's worth the money. Russ Quote Link to comment Share on other sites More sharing options...
Thomas Drolett Posted May 19, 2010 Author Report Share Posted May 19, 2010 I called tech support on Tuesday (May 17) and spoke with Scott Safreed. Although my inability to back up to "Disk" still persists, Scott assured me that I could use "File" backups as long as they don't exceed 1TB in size. So far, so good. Thanks Scott. Oh, and the call was free. Tom Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.