Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Posts posted by anield

  1. I misread your (original) question. 


    A NAS can not be a destination, per se. A destination is always a Media Set. You can have the volume on the NAS as a Member of a Disk Media Set.


    So mount the NAS volume in the Finder.

    Create a new Disk media Set and make the NAS volume as a member. (Do not store the catalog file on the NAS.)

    Now you should be able to create a script which has your newly created Media Set as its destination.


    I can create a new media set but then can't add the NAS as a member of the media set.  The NAS volume is not listed on the 'add a new member' dialog, so I can't add it...


    Have tried with the volume mounted in finder [tried afp and smb] and with it not mounted.

  2. From what I have read, you should NOT have the device mounted in Finder.




    I'm not sure precisely what's going on in this case, but I have had the same frustrations.  The conditions under which a network-attached volume is "visible" to Retro is not well defined, and sometimes volumes that should be visible are not. I have had success with internal, AFP, and direct attach (firewire). Whether/how SMB, NFS, ".dmg" volumes, and others work is not well specified.


    I would like to see these things either documented or disallowed. At present, they just don't work, and produce strange (or silent) errors.


    Thanks, I've put in a support ticket.


    Is a bit annoying when a backup program doesn't recognise a backup device...   :rolleyes:

  3. How do you add a NAS as a backup device?


    I click add on the device page, fill in the name etc, click add, then on the next screen there is no way to select the NAS share.


    All the screen shots I've seen show an add share button bottom left of dialog, but I don't have that button and the share isn't shown in the list of drives.


    Netgear ReadyNas if that makes a difference.

    Retrospect 10.5 multi-Server

    Mac OSX 10.6.8


    Have tried with connecting with finder first and without connecting first, using SMB and AFP but can't find any way to get the device added.



    • Like 1

  4. You should only need one media set on the NAS unless you want break your clients into different groups...


    According to Retrospect tech support (during our conversations with them over the last several years) you definitely may need multiple media sets.  Though there is nothing to be found in the (aging) Retrospect user manuals about backup set size limitations, tech support has indicated rough guidelines to us as follows:...


    Thanks for the help.


    I don't mind having multiple backup sets for different servers and usergroups.  The main thing is to know if it's enough to rely on just one media set for each Server/group.  We are below the 3 million file count.  So looks good  B)


    If you are using only one disk media set and it becomes corrupt and unrecoverable then you will lose everything and have to start over from scratch.


    Do Retrospect disk backups become corrupted often?

    • Like 1

  5. From the docs:


    Retrospect uses an archival method of backup that ensures backed up files are not deleted or written over until you request it. That way, they stay on the backup media indefinitely. For example, if you have been working on a particular document over a period of time, Retrospect backs up a different version of the document each time you back up. If necessary, Retrospect lets you retrieve a previous version of the file from any point in time it was backed up.


    We are using NAS as the backup device, and the NAS is sync'd to a second NAS on another physical site.

    We also do a monthly full backup archive to tape.


    As the NAS is synced off site we should only need one media set?


    Adding media sets increases the disk space used.


    Is there any need/point/advantage in having more than one media set (e.g. multiple daily or weekly media) for the backup?



    • Like 24