Jump to content

Search the Community

Showing results for tags 'media set'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements, News and Resources
    • Latest News
  • Windows Products-Retrospect
    • Professional
    • Server, SBS and Multi Server
    • Device and Hardware Compatibility-Windows
    • Exchange Server Add-On Support
    • SQL Server Agent
    • Linux, Unix and Netware Clients
    • Express for Windows
    • Product Suggestions-Windows
  • Mac OS X Products-Retrospect
    • Retrospect 9 or higher for Macintosh
    • Retrospect 8 For Macintosh
    • Retrospect 6: Desktop, Workgroup and Server for Mac OS X
    • Device and Hardware Compatibility-Mac OS X
    • Linux Clients
    • Product Suggestions-Mac OS X
  • Macintosh OS 9 and Earlier-Retrospect
    • Express, Desktop, Workgroup and Server for Pre-OS X
    • Device and Hardware Compatibility Pre OS X
  • General Discussion-Retrospect
    • Networking and Clients
    • Strategy, Scripts and General Use
    • Retrospect iPhone App
  • Retrospect 8.x for Mac
  • Retrospect 6.1 for Mac
  • Retrospect 7.7 for Windows
  • Retrospect 7.6 for Windows
  • Retrospect Express
  • General Discussion


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 17 results

  1. Background: I have 2 Synology NAS's, one that is strictly the storage for my media (photo) files, the other is the main backup destination for the media drive as well as other local drives in my system. For reasons unknown, no software changes of any kind made in over a year, the media NAS began to experience errors and crash when Retrospect (v 15.6.1 for Mac) ran its daily backup script. Synology support suggested changing the mounting of the media NAS from AFP to SMB. I did this and it seemed to fix whatever issue was at play with the media NAS crashing. I had to add the SMB media NAS share to my Retrospect backup script, which regarded it of course as a "new" drive and began to back it up in its entirety. During this process I discovered that due to operator error on my part the grooming options on the backup NAS hadn't been enabled and it began to run out of space. Retrospect prompted me mid-backup to add a new member to the Media Set that formerly consisted of the backup NAS only. I selected a local disk drive as a stopgap measure. After the backup was complete I enabled the grooming options on the backup NAS so that it should not run out of space in the future. The issue that I now find is that I need to remove the disk drive I added as a stopgap, and can't find any way to do so. I've looked through the manual, adding a member to a storage set is covered, removing a member is not. I've marked the stopgap drive as "lost" within Retrospect, but now the Activity pane shows each daily backup with a red 'x' for an execution error because of this. I have to look at each days' backup log to determine that the only error is the lost drive and nothing more, ideally I'd like to return to each backup pass being reported with the green check so that any real errors stand out and a quick glance at the Activity pane is all that's required. Is there a way to accomplish this without losing the groomed backups already present on the backup NAS? I don't have enough local storage to temporarily cache the backup NAS (~9.6TB) nor the media NAS (3.7TB) so need an in-place solution if possible. Thank you in advance, Andre (Retrospect 15.6.1 for Mac, MacOS 10.14.6 [Mojave])
  2. I don't see anything in the forum about this, but it appears to me to be a serious bug. I cannot seem to "move" a disk media set. I have - many times in the past - moved a disk media set from one disk to another. Manually changing the path name in the "member" and/or rebuilding the catalog would restore the "moved" set to be usable. In Retro 14.6.1 (mac) _and_ Retro 12.6.1 (Windows) I am having the same problem. If the files of a disk media set are copied from one disk to another, it is not possible to "restore" it to health. It seems quite impossible. I've tried several permutations of repair, rebuild, manual manipulation of the path(s), and even removing the catalog before rebuild. The best I can do is get it to show "green" in the console and then when I try to use it, the execution gets stuck on "waiting for media". If I try to "find" the media (member(s)), it either ignores me (Mac) or fails with an error (Windows). Has anyone else seen this? I'm guessing it is a new bug in a recent upgrade, because this used to work. No, I have not tried to re-install an old version to see if that would work.
  3. So I am trying to understand how using multiple disk media sets with a normal backup script will work. Scenario: I have setup two disk media sets, A and B. I have created a backup script that has a schedule to backup to media set A on M, W, F. The same script that has another schedule to backup to media set B on T, Th, Sat. So what I am looking to figure out is if the backup script is striping the data across both media sets? Or is it simply copying all of the same data to both media sets on a rotating bases? The reason I ask is that the source volume is larger than the destination media sets. So, I would like to stripe the backups across both media sets to accommodate for the size difference. If the above scenario is not appropriate for this, how should I do it instead? Thanks!
  4. Seems like my Media Set (the backup destination file) is no longer reachable. The file is stored on a networked HD, the file is there, but in Retrospect this Media Set hasn't the "green light semaphore" and in the information panel it is described as "Status: no element". I tried to Verify, Repair and Rebuild this Media Set without success, it is not reachable. Any suggestion ? Retrospect Mac 12, Mac OS 10.11
  5. I have seen this before, but I thought it was pilot error. Now that Retro 10 does not allow me to "accidentally" change my scripts, I am now certain that this bug is real, and it's nasty. I have have scripts that "rotate" the backups on the first of the month. I have the options set so that the media set X is copied to X_last, recycliing X_last first, and recycling X if the copy is successful. When I do this manually, it seems to work fine. (Doing this I can "rotate" my media sets without changing the scripts.) This last June 1st, these scripts ran, and my 50 GB media sets produced X_last copies that are only 200 MBytes!!! I don't know exactly what it's copying, but it's only copying a small fraction of the data I wanted copied. Note that I am copying from a disk media set to a file media set. Retro is throwing my data away. Is this a known bug? Is there a workaround? Do I have to run these rotations manually to be safe? Retro 10.1.0 (221) engine on Mac OS X 10.8.3 - Mac Mini with 16 GB memory
  6. Version 13.0.1 (106) I have a Media Set with 'Groom to keep this number of backups: 2' set. But the Backups tab shows six. See attached screenshot. I Groomed the media set, but still have 6 backups, not 2. The Groom complete successfully - no errors: + Executing Grooming at 29/07/2016, 1:42:38 PM (Activity Thread 1) Grooming Backup Set PP Backup, optimizing for storage... 29/07/2016 1:42:40 PM: Execution completed successfully I feel I'm missing something or something has got corrupted. Any ideas? Thanks, James.
  7. I am having some problems rebuilding a media set from members located on two SMB NAS shares. So I want to move them to a couple of USB disks and so off the network. Unfortunately although the total size of my 2 USB disks is more than adequate (2x 4TB), one of the NAS shares that contains most of the data has 4.2TB of retrospect data. i.e. 200 GB more than will fit on either of the USB drives. I wondered whether, given that the rdb files that make up the data are in 630 MB chunks, can I redistribute them across the 2 USB disks and still have a chance of rebuilding a media set out of them?
  8. Hello, I just ran into nasty bug regarding 'Bindings' option in Media Sets. I have two tape libraries - older DLT-S4 and newer LTO5 one. When I try to change Media Set 'Bind to specific tape drives' option from default 'Any tape drive' to 'Selected tape drives', select specific drive and press Save - the option reverts itself to 'any' after a few seconds. I tried creating new Media Set, resetting Retrospect.app preferences, relaunching engine - nothing helps. Running any backup with two tape libraries connected makes Retrospect to archive alternating between two different formats on one Media Set. A nightmare. Is there any way to fix that? Now I have to manually disconnect or power down each library depending on a backup I want to commit. Thanks, W.
  9. Hi there, I can't verify my media set, which has one member marked as lost. During backup one of the tapes gone bad, so I trashed it, marked as lost in media set and restarted the backup. Now, I want to verify this set - and I can't, because Retrospect asks for member which is marked as lost and I don't have it. What is the purpose of this option then? How can I verify if my set is readable? Best, W.
  10. This has happened on several backups lately. Retrospect 10.5 is backing up both the computer it's installed on (iMac 2006 model running OS 10.7.5) and a Mac laptop. The media sets are all kept on a 4TB Drobo, connected to the iMac. The backups for iMac run at 1am, and the backups for the laptop run at 2am. So I'm not there to watch them run. Checking in the morning, I found that the iMac backup failed due to "error -1101 ( file/directory not found)" I selected the media set, and clicked verify. The response window said that "An error has occurred," and no verify operation ensued. Then I looked at the Summary window. It reported that the set contained no members. I didn't really know what to do at that point, so I quit the application and worked on getting to a place where I could call tech support. A few hours later, I sat down at the computer again, and lo and behold, there was a member in the media set! I quickly selected the script to do the backup into that set, and it ran with no errors, completing in just about six minutes. Does anyone have a clue how a media set manages to "lose" a member, what I can do to recover from it, and/or how does the media set later "find" that member, with no intervention by me? Thanks, everyone, for whatever insight you may be able to provide. Elaine Poe elaine@natca.net
  11. Hi, I have a few disk media sets set up and so far running fine. When the drive fills, according to the documentation, " Retrospect asks for a new member, adds it to the Media Set and continues appending data. It automatically uses any available new or erased media. If the media has the name Retrospect is looking for, Retrospect will erase and reuse it. However, Retrospect will never automatically use a medium with the wrong name if it has data on it." What specific name will it look for? I want to be sure it does not decide to erase a drive with live data on it! Will it be the name of the original disk with a "-2" appended to it or something? If I want an additional disk to be "ready to go" in case the first disk fills up, what should I name it? Do I need to explicitely tell it for every media set I created, the second disk's name? I'm running Retrospect 8 on a Mac, backing up weekly to alternating 4TB drives, which will likely fill up in the coming month. Thanks! Jeff
  12. Okay. Here's my current dilemma... I've run into this issue and have tried to go around it as many ways as I can, but I somehow fall short each time. When trying to backup an external hard-drive to a tape, it has my Tape mistaken for another tape. It started off like this... 1) Switched out tape that was filled up pretty well. 2) Inserted tape to backup. 3) Created a new media set for that tape. 4) Made sure script was set up so that I did not do verification. 5) First job backed up successfully. 6) Tried to back up tape subsequently, but it said, "Needs Member Device." 7) Modified bindings by selecting a specific tape drive and tape, but it only backed up folders without their contents. 8) Resorted to restoring contents to an external hard-drive, which worked. 9) Erased tape COMPLETELY. 10) Shut down Quantum Drive. 11) Detached Quantum Drive. 12) Shut down iMac. 13) Turned on Quantum Drive. 14) Turned on iMac. 15) Started over Media Set--> Script --> Backup processes. 16) Successfully backed up files until I switched out external hard-drives. --> "Media Set Already In Use" Error message Have completed steps 8-16 a few times, but have decided that this isn't working very well. Here are some pictures as well.
  13. (environment retro 10.2.0 (201) running on mac os x 10.8.x on mac mini, 4 core) I am following a sort of "manual grooming" path with my backups. I keep a couple of "current" sets, and copy off specific backups to a separate media set, and copy that off to tape. For instance, I have "myset"(disk), and "myset_2013"(file). I run the backups weekly to "myset" and then use a "copy backup" to copy just one backup per month to "myset_2013". Sometimes "myset" has several months of backups, so I do a "copy backup" operation and "copy selected backups" to copy just the backups I want to the "2013" set. In the past, this seems to have been working. Yesterday, I tried to do this, and ran into a problem selecting more than one backup on a media set for retrieval. (you can't copy the sets unless they are "retrieved". Today, I had a more alarming result. I did the "copy backup" operation and it resulted in a media set that appeared to contain no backups. I verified it - OK I "repaired" it. - OK I "rebuilt" it - THAT restored the backups in the output media set. This means three things to me. 1. THe copy backup operation can sometimes produce a corrupted output. Note that the log for this copy operation did not indicate any errors, but the "yellow triangle" DID appear on the "activity" when it was done. 2. The "verify" operation does not verify an important aspect of media set integrity. 3. A rebuild op will rescue the media set.
  14. I have a limit of 2 active tasks in my engine (10.2.0 (221)) and I had two busy recently, and tried to verify a media set via the "verify" button on the media set pane. The media set went "busy", and the verify didn't happen. I don't think the media set is going to get un-busy unless I restart the engine. I'll wait for idle and do that. Bug. It should refuse the request, not permanently busy the media set.
  15. I have just started backing a 4TB USB disk (with 1.9 TB of data) to a NAS disk using a new install of Retrospect 10. I added the 4.5 TB NAS disk as a share and added it as a disk media set containing just one member, configured to use 90% of the available space. The backup got a good way through the process of backing up (1.7 TB) but then threw up an error saying "needs media". I created a new member to the set on the same disk, and it finished the backup after a couple of retries. However, running the backup again it keeps demanding new media, even though the disk is not half full. As far as I can see it is configured to append to the media set, not to try to start on a new member. I wonder if I am missing something fundamental that is causing it to fail. I have read through the documentation but can't find anything that addresses this, as the "needs media" error seems to be more related to tape drives. Any help appreciated!
  16. Version: Retrospect 10.0.1 Media Set Type: Disk My on-site backups (OSX 10.6.8 XServe Xeon) to attached storage (Drobo) function without any problems. For off-site storage, I added a AFP Share to the Source list that comes from my off-site AFP server (OSX 10.6.8 XServe Xeon) with attached storage (Drobo). I can successfully Browse the contents of and create Disk Media Sets to the off-site Share from within the Retrospect console. My intention is to use a Copy Media Set script to make a weekly copy of my on-site Media Sets to the off-site location. However, when I start the Copy Media Set script, I'm always prompted with Needs Media. When I click the Choose Media button, the window says Can't find '1-myoffsitemediaset'. Locate Member or add a new one. I can clearly see the 1-myoffsitemediaset and I can use the Add button to make a new one, but the script still says Needs Media. Additional details: -The Catalogs for my on-site and off-site disk media sets are saved on my on-site server. -A restart to the on-site and off-site server has no effect. -I deleted the script, Disk Media Set, Catalog and recreated them all w/o success. -I've successfully used this method on a previous Retrospect 8.2 server but it became unreliable with 9 50% of the time (same Needs Media error). I upgraded to 10 in hopes it would work again. If my approach to making an off-site copy of the Media Set's is flawed, do you have any suggestions? Attached is a screenshot of the Summary screen to this particular script.
  17. I have recently become aware of a flaw in which one of my scripts is backing up erroneous data. The script is working fine, it's just that the corrupt data takes up huge amounts of space and consequently I am running out of room for my media sets. Essentially, a media set that until November was around 30 GB has ballooned up to over 100 GB, all due to some files that I am now purging from the client's computer. The script backs up multiple clients, so I don't want to recycle the media set if I can avoid it. Plus, I have it scheduled such that it launches a new media set member at the start of each month. Now that we are in December, the bloated November media set is sitting there, plump full of unwanted backed up data. I've gone into "Past Backups" to see about Removing the November 1 backup of the affected client, but I get a tooltip warning me that clicking "Remove" will not delete any data, it will just remove it from the list. Of course, I had "retrieved" the Nov. 1 backup in order to get it on the list, since that appears to contain all the junk files - later backups of the same client don't show many files, and are of reasonable size. In other words, it sounds like clicking "Remove" will only undo what I just did, which was to populate the Past Backups list with the Nov. 1 instance. My intention, though, is to actually destroy the backed up data. Is there a way for me to do so? I don't think Grooming is the right thing to do, as the corrupt files were just created once then not modified thereafter (in other words, they were only backed up once).
  • Create New...