Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by jotrago

  1. I have a customer with Retrospect Server 9.5 on Windows. A Mac client has been running happily until the user upgraded to the latest MacOS El Capitan Client for Mac 12.5 supports El Capitan and is officially supported on Server 10.5 What are the changes of it working with Server 9.5? At least temporarily until the customer decides on upgrades etc. Thanks
  2. Cobbler's shoes! The screen shots in the above links are no longer available. I accidentally deleted a bunch of files in my "Box" including those. No Backups! Sorry
  3. There are occasions when you need to force tasks to run sequentially, and as quickly as possible, ideally immediately one after the other. {EG: Each morning you might want to Verify the previous nights' backups, then initiate a Snapshot Transfer Task to Tape for offsite copy.} The usual compromise is to take a guess at how long each Task will need and then schedule them in time sequence with a gap in between to allow for variation in run time. Whilst this works (provided you at least have an estimate of the run time for each job) it is not very efficient or fast, and very difficult if you have no idea how long a task may take. Try this method to force tasks to run sequentially with each one starting immediately the previous one has finished. The trick is in forcing them all to use the same execution unit. Schedule each job to start a short time, (say 1 minute) after the previous one. This is just to get them in the right order. It doesn't matter how long they may actually take to run. At the bottom left of the Script window for each task is the Execution Unit selector, which defaults to ANY. Set it to the highest numbered Execution unit, (so it won't clash with any other task which will pick the lowest numbered available unit by default) for each of your Sequential Tasks. At the appointed time the first of your sequential tasks will start with the specific Execution unit. 1 minutes later the next one will try to start, but since the execution unit is in use, it cannot, and will be added to the Waiting Queue. The rest of your sequential tasks will follow at 1 minute intervals. You should now see them in the Waiting Tab of the Activity Monitor, all waiting, in order, for the Execution unit to become free. As soon as the first task completes, releasing the Execution unit, the next one will start. Your tasks will now execute, sequentially, as quickly as possible. See the User Guide, Chapter 7, Controlling Operations > Multiple Concurrent Executions > Assigning Execution Units.
  4. I see one of the links didn't come through in my first post Was referring to this link http://www.retrospect.com/en/blog/2014/01/19/tape_device_updates LTFS was originally developed by IBM, who released their Driver as Open Source, it is still available on their site if you want to experiment. It has since been taken up by most other LTO manufacturers and tape based storage companies, and there are now many products based on it. https://en.wikipedia.org/wiki/Linear_Tape_File_System
  5. Just a long shot, but one thing that I admit confuses me every time with retrospect whether creating or accessing backups sets is figuring out exactly what to point to. I get the impression that Retro wants you to point to the "Parent" folder. It then creates the subfolders with Backupset names etc. SO When rebuilding catalogs from the raw Backupset data try specifying the folder ABOVE the one with the backupset name.
  6. The trick is having separate copies of your catalog files. Consider creating separate duplication jobs for your config file and catalogs, so they are available as normal files (not a backup set) in the event of a Disaster. See the User Guide > CH10 Management > Catalog & Config backups and User Guide > CH10 Management > Moving Retrospect. HTH
  7. LTFS is a driver which uses an LTO5 or later drive and presents it as a disk to the OS, just as your Xendata system does. This item indicates that you can use an LTFS Disk Target with the Duplicate function, which simply copies files, in their original format to another disk location. In this post, Mayoff indicates you should NOT use LTFS as a Retrospect Disk Target Device due to the way Retrospect writes its Backupsets, allowing for deduplication etc. http://forums.retrospect.com/index.php?/topic/147996-retrospect-and-ltfs/ Alternatively I believe the Xendata system can present the LTFS file system as a NAS Share on the network. You may also be able to use that as a target for Duplication.
  8. My recommendation is Firstly check out the Upgrade Technote, The Retrospect 10 Documentation section discusses upgrade procedures, and check the release notes for anything which may apply to your environment. The key thing with the backupsets is that once you have brought them in to V10 they cannot be used in the old versions. To gain an understanding of how Retro handles Moves and Upgrade see the Manual - Chapter 10 > Management > Moving Retrospect. Here it discusses how to backup the configs and catalogs . In My experience when upgrading a major version Retro installs it in a new folder named for the version, but retains access to your existing configs and catalogs.
  9. Ok so Desktop only has one execution unit, (Server version has up to 8 ) so you can skip that step. Schedule your jobs for a short time apart, eg 1 minute, just to get them in the right order. Do you have a "Waiting" tab on your Monitoring WIndow? You should see the jobs queued up in there I've never actually used Desktop so there may be some other more subtle differences. My scheme works on the Server version.
  10. See my article http://forums.retrospect.com/index.php?/topic/151254-how-to-run-tasks-sequentially-as-quickly-as-possible/ for more detailed explanation
  11. jotrago

    Can the New Version Back Up to an FTP Site?

    There are third party utilities that can mount an FTP site as local drive. I guess that might be an option. Google "ftp mount" How reliable that might be is another matter
  12. jotrago

    Unable to Create Client - Error 560

    Glad you came right
  13. jotrago

    Unable to Create Client - Error 560

    I just realised we are in the Professional forum and Professional doesn't support automated Login with certificates. So it is strange that it is complaining. Check the Public Key folder under the Retro Installation folder and move anything out of there. Maybe there is a file there which it is trying to interpret as a certificate. The most common issue with clients is firewalls. The installer should offer to put the entries into the windows firewall for you. If you have any other firewalls (especially part of your AV) try turning them off. Manually enter a firewall rule for retroclient.exe allowing all protocols for any source or destination. Testing from the Retro Server Click the Client with the greyed out Icon Click Test Button & enter name or IP If Client is Up and Has Retro Client Installed - It reports the Retro version number Error 541 - IP Address is UP but No Retro Client is responding - This is most likely then a firewall issue Error 530 - No Response from IP address - this is most likely a network issue - check you can ping in both directions
  14. jotrago

    Unable to Create Client - Error 560

    There are two methods to join a new client to Retrospect. Manual, whereby you provide a password when you install the client, and use the same password when you join the client to Retrospect. Automatic, where you create a certificate in Retrospect, and embed that into your installer or manually copy it into the Public Key folder under the Retro Client Install directory. This is a cool feature. Automatically added clients appear in the "Automatically Added" clients Source Group. If you have a script set to backup this group then simply installing a client is sufficient to have it backed up. Sounds like your client is not enjoying the key provided. See User Guide Chapter on Networked Clients for detailed instructions on setting creating the Certificate and deploying it
  15. jotrago

    Duplicate / Scripts / Exclude Directory

    See my post here regarding using execution unit to force sequential operations without waits. http://forums.retrospect.com/index.php?/topic/151254-how-to-run-tasks-sequentially-as-quickly-as-possible/
  16. I have a small site (retro 9.5) with a dozen windows laptop clients (Win 7 & 8), no Open File Agent. We are using Proactive backup with a separate script and backup set for EMail which has Block Level Incremental and Force Backup of MS Outlook Data enabled in the options. A selector looks for .pst and .ost files Some of the clients gracefully shut down Outlook and backup happily , others do not, and consistently give the usual Any Ideas?
  17. We're busy trying to build a table of that info. I support the site remotely so have to rely on the local people to gather that info.
  18. jotrago

    Duplicate / Scripts / Exclude Directory

    With Duplicate you can only select One Source Volume at a time, whereas with Backup you can select multiple, so yes you would need two scriptsf or two Volumes You can build elaborate Selectors to handle files and folders within that Volume Duplicate copies files in their native format to a target. Backup gathers the data into a backup set, and must be restored
  19. jotrago

    Duplicate / Scripts / Exclude Directory

    First, in Retrospect "Duplicate" & Backup are two different things, but the procedure is the same Create a Selector; Configure > Selectors > New Call it ExcludeTwo In the Exclude Section click + Click Name Uncheck File > Does > End With or Contain (whichever is best suited) and enter "\temp\two" Leave "Enclosed Folders" checked OK CLick the Blue Tick and point to your volume to see the effect Once you are happy then :- Go to Backup and select Duplicate or Backup Select your your Source Volume(s) EG; C & D Select your destination - wherever Click "Selecting" and choose your ExcludeTwo Selector Preview to check that it works as expected Set Your options Off you go
  20. jotrago


    Under the Restore Menu Try the "Find Files" option. Once you have chosen your BackupSet and a destination to recover to, you can setup a search to find the files you need. The search uses the Selector mechanism which is very powerful (once you get the hang of it) It includes ability to search by date & range, types of files, parameters like created, modified, backed up etc. With a bit of experimentation you should be able to do what you require. Take Note of the Blue Tick in the Find Menu. you can use this to test your search criteria to ensure they are finding the correct files. Once you are happy with your selection proceed, and you will be presented with a summary, including the number of matching files, which you can browse before actually committing to the restore. Check the manual Chapter 5 > Immediate Operations > Restore > Restore by Search Chapter 11 > Tools > Selectors will help with setting up the Search criteria
  21. jotrago

    How to use Source Groups in a Selectro

    OK So you would create your Source Group "Data Volumes" and then drag all the Data Volumes from the Computer, Network & Clients sections as required. Then Create a Selector which Excludes Folders containing "2015" and Folders containing "Outlook" You may need to specify those a little more precisely depending on your exact environment In your backup Job or Script specify your Data Volumes Source group as the Source Then specify your Selector in the "Selecting" section. Another approach may be. If your "Data Volumes" are actual physical volumes mounted on your clients, then by default they will be included in any backup anyway. Check the Properties fo your Clients in Retro check the Volumes Tab, the default is Desktop which will include every volume visible to the Client OS, you can also make other selections here. In which case all you need is a Selector which excludes "Data\2015" & "Data\Outlook"
  22. jotrago

    How to use Source Groups in a Selectro

    I should also mention that Items in Source Groups are only "Aliases" of items in the Computer, Network & Clients sections so you can create as many as you like in various folders/Groups. You can also Nest Groups in a tree-like structure if necessary. My notes on Selectors may also be useful http://forums.retrospect.com/index.php?/topic/151365-how-to-nesting-selectors/
  23. jotrago

    How to use Source Groups in a Selectro

    Perhaps there is some confusion over the term Volume. Items in the "Volumes" database seen under configuration are intended to be used as the Sources orDestinations of Backups & Restores. If you want to Exclude a Source Group from a backup then don't include it in your Source Selection. Or create another one with only the items you require. Selectors affect the way Retrospect operates in a filesystem. Here "Volume" refers to a disk volume EG D:\ /Home/ Volumes specified in a selector must match an item Retrospect will come across when "Walking" the filesystem during a backup
  24. You don't fully specify your setup but I'm guessing from the version number that Retrospect is on Windows. Mounting mac drives, sharing over SMB to windows sounds risky and slow to me. GIven the huge task facing you I would seriously consider installing Retrospect on a Mac, and pulling the data directly from USB to Tape. I know that sometimes attaching tape drives to Macs can be a challenge (Interface cards etc) In that case at least install a Mac Client on the system with the drives, and backup to your WIndows system with the tape drive. At least that way the data is being extracted on a mac, and then transported across the lan in "Retrospect" format. Should be more reliable. Even if that involves a little expense for some licenses. Failing that the Assert-Log.utx on Windows 7 or later is in c:/Program Data/Retrospect (Program Data is a Hidden Folder) Drag and Drop it on to Retro and it will open in Retro's UTX viewer or it will be reasonably readable in Notepad or other text viewer You may have to compare it with the Retro Ops Log (which you will find in the same folder) and Windows Event Logs to see if you can find some correlation at the time the crashes happen.
  25. jotrago

    Can't back up host drive from virtual machine

    Since you are just testing, perhaps rather create an extra virtual disk or two in VBox and mount them in your Retro Test VM, and use those as sources and targets for your backup tests. You could copy some of your files from host to VIrtual disk I use VBox extensively and always mount my host home folder (linux) in my VMs. They have always worked reliably, although I have not actually tried running a backup on them.