Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 12/03/2014 in all areas

  1. 3 points
    This document (as of July 31 2018, Retrospect Desktop 15.1.2.100) is intended to augment the information in the official Retrospect 15 User Guide. All errors are my responsibility. I do not guarantee that this applies to any other version of Retrospect; in fact, I don't guarantee anything about this at all! ? YMMV. Buyer Beware. Etc. A few items highlighted below are not certain for me at this time. Insight welcome! Preparing for Disaster A. Crucial Attributes To Record About Each Client/Host System Several crucial attributes must be recorded about any client or host system that you wish to later restore with a DRD (Disaster Recovery Disk): 1) Disk Layout Why: the DRD is currently unable to fully auto-create this info. It's up to you to do so. Get it wrong and Things Can Go Badly Partition Table Type (MBR or GPT) Number and sequence of partitions. (MOST important: is there a "System Reserved" partition, is there a WinRE (Recovery) partition, which partition is Active, and what's the sequence?) (Nice to have: the name of the 'C:' windows partition) 2) Boot method Why: The boot method for recovery must match that of the system that was backed up. The DRD is currently not aware of this when regenerating a system. BIOS or UEFI? (MBR partition tables support both BIOS and UEFI boot. GPT partition tables only support UEFI boot, with a few rare exceptions.) Where is the boot BCD info? (From experience: Retrospect will NOT complain if your boot info is not on the C partition... and it may not be backed up!) For BIOS boot, the BCD info is typically either c:\boot\BCD or on the system reserved partition, at \boot\BCD. For UEFI boot, it's typically in one of those partitions, at \EFI\Microsoft\Boot\BCD or \EFI\boot\BCD. Hint: It's a good idea to save an exported copy of the BCD store while the system is in good shape. From Admin Cmd prompt: bcdedit /export c:\bcd-yymmdd will save it. [7/31/18 update] There is some indication that UEFI but not BIOS boot information is backed up from any appropriate partition. We're in discussion on this. If you have a complex multi-boot (eg using GRUB or even manually-added BCD entries), I would suggest keeping an image of your boot disk. Retrospect uses Microsoft Windows tools for recovery; recovering non-Windows boot information is (quite reasonably) beyond the product's scope. 3) 64 bit drivers required Why: Many environments do not require 64 bit drivers. Some do. If so, you'll need a 64 bit DRD rather than the default 32 bit. I have one: unless extreme measures are taken (see below), access to our Catalog Files is on a RAID 1 internal drive pair, managed by IRST (Intel RAID Storage Tech) which uses 64 bit drivers on 64 bit Windows. 4) Custom drivers required Why: If recovery requires access to devices that need nonstandard drivers, you'll need to prepare ahead. Example: my IRST setup. Typically, custom disk drivers that can be used at boot time are downloadable either in normal "installable" form, or in what is known as "F6 Floppy" form (refers to pre-boot interruptable driver-load... TMI ) The DRD creation instructions tell you to copy these drivers to a particular place on your Retrospect Desktop machine before creating the DRD. Do it. (currently they go in <Retrospect Install Folder>/drsupp/drivers ) 5) Non-hard-drive boot methods fully supported for system recovery Why: Not all machines support USB memory key boot. Windows 7 does not fully support USB for recovery operations. You may need a DVD (even a USB DVD, strangely). B. Crucial Things to Know About the Disaster Recovery Disk This information is not documented elsewhere, AFAIK, other than the first line below 1) The DRD... Why: These attributes determine how many DRD's you may want to create and maintain. AND, you'll want to update the DRD after significant system or Retrospect config changes. Is either 32 or 64 bit, and recovers a certain range of OS versions (eg seven varieties of Win10, etc) Assumes the boot style of the host system (it appears the DRD is intended to boot both UEFI and BIOS. Not yet clear if this works properly. For now I would not make assumptions.) Contains all Retrospect configuration as of when it is created, including Devices, Clients, Backup Sets, Volumes, Selectors, Preferences, Licenses, and Automation Settings Has built-in drivers for network, USB and many other devices Why: These attributes are unknown to the DRD. You'll need to maintain this knowledge separately, available for use in case of disaster Does not know how to auto-restore system Partition Table types (Reserved, Recovery, etc), partition settings, have access to catalog files on other disks, or login info to access network shares 2) Where do you keep your Catalog File? Why: Be sure you can get to the catalog file while recovering from a disaster! It's easy to move the catalog file off of your boot drive. Do it. (Or, make a copy as part of your backup strategy) In our case, to avoid other hassles, we host DRD recovery using a copy of the catalog files loaded into a USB stick. Easy-peasy. C. Before Creating the DRD Do you need custom drivers? Make sure they are in place already (see above)! For Windows 10, you need to download and install the ADK as described in the DRD documentation. These items are not yet documented: For Windows 7, a different kit is needed, the "AIK" You don't need to install the whole kit. When running the ADK setup, uncheck everything other than "Windows Preinstallation Environment (Windows PE)"... which will auto-check "Deployment Tools" Highly recommended: just before you create the DRD, do something to disable or pause all auto-run scripts! The DRD recovery environment is a "real" Retrospect environment, and will attempt to run any active scripts! (I introduced an N month delay in all scripts as a workaround, then removed it) Yes, it is possible to cancel all scripts once the DRD is running, but that can take quite a while as Retrospect goes through "preparing for open file backup" on the active scripts...) D. Creating the DRD The DRD tool wants you to locate a file, "copype.cmd" . The Retrospect team intends to auto-find this, but that's not yet implemented. The file is found in <Kit install dir>/Assessment and Deployment Kit/Windows Preinstallation Environment Bare Metal Recovery A. Preparing the System Ensure the system is set up in a similar fashion to the original system that will be restored. In particular: Boot settings so the system boots into the correct boot type (UEFI vs Legacy/BIOS. For one of our machines that supports both, I had to force it to Legacy to get everything working.) The correct Partition Table Type and Partition Layout (The DRD can create partitions, but has no ability to set Partition Types, special partition formats, detail-level partition sizes, etc.) (At first I reloaded Win10 on a system to be reloaded. The partitions were laid out very differently, and in particular a different count and sequence. Result: the recovery process wanted to wipe the contents of other data drives on the machine! Another time, the recovery immediately failed with strange VSS errors. Only when I correctly pre-set all of these elements did recovery go reasonably well. Tech Support has informed me these are known bugs (eg Bug 6109 about an invalid disk erasure warning)... however, if you have any concern for preserving drives, I urge care in restoring to ensure you don't accidentally make things worse than they already are ) B. Doing the Restore The recovery process involves several steps. Remember, I'm just giving additional notes and hints. The primary steps involve: pre-setup, run retrospect, post-restore Pre-setup: if you've predefined the partitions, you'll mostly just want to erase and reformat the 'C:' windows partition. Give it the same name that it had before to make life simple. Pre-setup: If you'll need network access to your backup sets, this is a good time to do a network-use of any needed shares. The DRD process will remember you're logged in from this point on Pre-setup: if you have other disks (eg USB stick) to attach to the system, eg containing Catalog files, now's the time to plug them in. In retrospect: check the needed catalog file(s) / backup sets. Can they be accessed (double click in 'Backup Sets'). If not, click "More..." then "Open..." to open the catalog file. Drag-and-drop of a catalog file does not work at this point to attach it. In retrospect: to do the recovery, go through the "Restore" process. I find it helpful to click on "Switch to Advanced Mode", and go through the steps one by one to be sure everything is as desired. In retrospect: before rebooting, be sure to remove the DRD disk! You don't want to just run the recovery again Post-restore: (if using Dissimilar Hardware Restore, don't leave the DRD script after finishing with Retrospect!) C. After Restore When my main host restore was complete, after reboot I got "no operating system found"... a bit scary. Solution for my situation: Boot with a Windows Recovery CD, get to a command prompt, and use these commands... bcdedit (shows boot information setup, if any. My system had none! bcdedit /store x:\boot\BCD is good to know about...) bootrec /rebuildbcd (finds windows and builds the correct boot environment) bcdboot c:\Windows /s b: /f BIOS /v [where the drive letters are what's valid in your recovery environment; "c:" is your windows volume, and "b:" is your boot volume, which could be the same as the windows volume, or could be the System Reserved partition.) ALSO of note: for bcdboot to work, you need a valid copy of the following file from the bootable normal windows environment: c:\windows\system32\config\BCD-Template If you get further errors, you're beyond the scope of this hints-doc. Lots of material is out there to assist you. All is NOT lost. Building A DRD After The Fact I didn't have a chance to build a DRD before the boot disk on our primary backup system died. Here's what worked to get around that not-so-little problem: Downloaded a Windows 10 Pro installer from Microsoft (yes, it's free... controlled by license codes and activation keys) Used a separate tool set to predefine the partition structure of the replacement drive, to match the old one. MBR disk with System, C:, WinRE in my case. Didn't put any data in the partitions. Installed Win10 Pro into the C partition. Told it "no license key" since it was already activated. It really did auto-activate when the time came. Downloaded and installed Retrospect. used the c:\ProgramData\Retrospect\Config77.dat file from my almost-totally-dead drive. This gave me a very nice working environment Installed the ADK as described above Modified a few Retrospect scripts as described above Installed the IRST drivers. Then (due to other problems I'll not discuss here) switched tactics and recovered the current catalog files from my RAID to a USB key With the USB key catalogs in place, and all other drives disconnected, created the DRD Bottom Line This all sounds so neat and tidy... I have done this writeup because my actual recovery process involved discovering the hard way that there are many undocumented aspects to the DRD process! I suspect with these notes, a Retrospect Desktop system could be easily recovered in a matter of hours. Mine... well let's just say I began recovery Sunday evening and finished Wednesday morning... (One of those times when I wish I could get paid by vendors who benefit from my bug-sleuthing skills?
  2. 2 points
    Wha is an "august Documentation Committee"? Sounds like fake news, if you ask me.
  3. 2 points
    The QNAP NAS is a new Source to Retrospect which it has never seen before so will try to do a backup of all the files it finds there regardless of whether you think Retrospect has seen them before. The reasons are covered in more detail elsewhere on the forum but in short, without doing a byte-by-byte comparison of the files which Retrospect does not do, Retrospect has no way of knowing if a file now on QNAP is the exact same file that was on the Synology. Once the first full backup of the QNAP NAS is complete normal operations should resume.
  4. 2 points
    Excited to report that I got my Retrospect backups fixed now as well !! So, disabling the "Save space and download files as you use them" setting did not work for me. So in addition to that, I tried disabling OneDrive altogether (Unlink PC/account and then remove the entire OneDrive folder) and then linking my account again which then again downloaded all files. The next Retrospect scheduled (proactive actually) run then succeeded with 0 errors or warnings ! This worked now on 2 machines already, so will try kids laptop next, but pretty confident this will work as well. Thanks to the folks active in this thread !
  5. 2 points
    Ok, I did some additional debugging and I found the issue: It's OneDrive. OneDrive has an option (don't know if it's new with 1803) that gives you the possibility to only actually download a file from OneDrive to your computer if you actually use it. All files in the OneDrive folder are shown as being present, but they are not actually physically present on your computer. So they are some sort of link. The explorer shows a cloud symbol with these files. As long as one such link is present on the drive (even if it is in the Recycle bin) it will cause the -1103 error. Scanning will be interrupted as soon as the scan engine hits the OneDrive folder. On both machines I turned the option off in OneDrive settings, which caused all OneDrive files to be downloaded to the computer, and both are backing up properly now, without errors. Also checked the machines that never showed the issue, they all have this OneDrive option set to off.
  6. 2 points
    Oh well, #sigh I have a few Macs. All on WIFi All on DHCP They have to be this way, because they roam from office-to-office, client-to-client, home-to-work-to-home ... like laptops do. The error -530 and associated -519 has be around in almost every version of retrospect I have used for the past 20 years. I can never find the solution, apart from a full client reinstall, and I can not be doing that every week TBH! Is there ever going to be a stable answer? Each Mac, Client and Server has no firewall or anti-virus FYI. The fixed desktop Laptops that do not leave the office have no issues. The laptops returning to the office login automatically to the WIFI and have no network issues for everyday work; email, www, ftp, server shares, printing ... what so ever. Server: Mac OSX 10.11.6 Client: OSX 10.12.6 Retrospect 13.5 Please don't say 'upgrade to the latest version of Retrospect or I may have to slap you :-) That has never been an answer to this issue.
  7. 1 point
    I'm backing up a couple of Macs and Retrospect seems to place an inordinate load on them. My Macbook Pro 17", for instance, is hyperventilating several hours per day even though I hardly use it. I had Crashplan until they cancelled the service, and even though they backed up every 15 minutes, it was totally inconspicious and effective. Retrospect is a steamroller compared to that. Admittedly, Retrospect backs up more files, but still. Every now and then backups went smoother, and that was when Instant Scan did its work (as verified in the logs), but most of the time Instant Scan simply bogs down the machines but doesn't actually work. I had a week-long exchange with Retrospect support about this, trying to figure out why Instant Scan is totally ineffective, but once they escalated, I was told Instant Scan is no more. Not that it's having problems, no, that it has been abandoned. Does that mean my Mac backups will continue to be so grossly overloading the machines? I'll quote verbatim the last message I did get from Retrospect below. To me it sounds like Retrospect on MacOS will forever remain a dog. (I should mention that Instant Scan already didn't work before I upgraded to 10.13 and APFS. I also assume Retrospect support meant to say "APFS" and not "AFP", which makes no sense in relation to 10.13. And makes no sense in any case on the local machine where Instant Scan works. Or maybe they actually did mean AFP and then I understand even less.) "Dear Martin, Retrospect Engineering Reply can be found below. Instant scan doesn't work on AFP, and most likely customer is using AFP if they are on OSX 10.13.We recommend disabling instant scan in ALL cases, we are disabling instant scan by default in future versions of Retrospect.Thank you for using Retrospect,The Retrospect Support Team "
  8. 1 point
    Hi, It would be real time saver if we would be able select multiple snaphots to forget in a disk based backup set. As it stands now you can only select one at a time, shift or control click doesn't work. Thanks, Johnny Mac
  9. 1 point
  10. 1 point
    To be honest: I really don't understand what's the purpose of all these forum posts about editing a Wiki article about Retrospect... In my opinion these posts all are very lengthy and hard to read and of no use and interest to users of the software.
  11. 1 point
    IMHO what ShadeTek wants is some version of what barup wanted in the OP of this thread. That would probably be because the tapes that are members of a particular Backup Set are not externally labeled as such in ShadeTek's installation. If so, then he/she cannot do "putting in all 8 tapes in one go". There is a facility in Retrospect Mac that allows one to see all the members of a particular Backup Set (called a Media Set in Retrospect Mac), but I don't know if it works for tapes—which I haven't used since 2010—much less what the equivalent facility would be in Retrospect Windows. If ShadeTek wants such an enhancement to Retrospect, here is why and how to submit a Support Case to request it.
  12. 1 point
    Hi All, Just another quick update. We are still investigating these errors, most of which appear to be tied to One Drive, but it seems not necessarily always tied to One Drive. The results from the internal investigation indicates that the problem is a bug introduced by Microsoft. Just to give a simplified overview, when using VSS we aren't ever actually backing up your files, we backup Shadowcopies of your files. In the case where we run into problems, after we access the bundle of Shadowcopies that Microsoft is preparing for us (after using standard VSS calls), we encounter write access violations. So VSS prepares everything, gives us this blob of data, and then says we aren't allowed to access it. What's also strange is we aren't actually writing during the scan, we are just reading the data. We confirmed that this isn't just bad error mapping on our part, we are actually receiving write access violations. We are implementing some changes that will be a part of the next release (v15.1) which should allow the backups to continue beyond this error. This is currently scheduled for release later this week. We will continue to work with Microsoft to address the issue further, whether that means changes on our end, or a patch on their end. We really appreciate the feedback from this forum thread, as well as the all of the information submitted to us via web tickets. Thanks, -jeff
  13. 1 point
    Are you certain that you disabled the OneDrive Files on Demand feature for all users? If the Files on Demand feature is enabled the OneDrive folder becomes a Reparse Point instead of a real folder. To check if the OneDriver folders is a real folder or a Reparse Point use one of the following two command line methods. If PowerShell is set as the default terminal: Right click on Start and select Windows PowerShell (Admin) Once the PowerShell window has opened type cd C:\Users\henkv and press enter Type ls one* and press enter The will return something like: Mode LastWriteTime Length Name ---- ------------- ------ ---- dar--l 2018-05-08 19:15 OneDrive If the last character of the mode string is a "l" (lowercase L) then the Onedrive folder is a Reparse Point If Command Prompt is set as the default terminal: Right click on Start and select Command Prompt (Admin) Once the Command Prompt window has opened type cd C:\Users\henkv and press enter Type ls dir /al and press enter If the result is: 2018-05-08 19:15 <DIR> OneDrive then the OneDrive folder is a Reparse Point If the result is: File Not Found then the OneDrive folder is a real folder Even if exclude folder(s) and/or file(s) in a selector they are still scanned.
  14. 1 point
    Hi x509, This will depend on the results of the investigation. If it looks like something is broken we'll submit a bug report. In fact, depending on what is broken we may have to submit a bug report in order to get it fixed. Cheers, -Jeff
  15. 1 point
    Just to throw out an idea after catching up with this thread, you might also want to investigate the settings in Control Panel | Sync Center in relation to One Drive, as well as anything else. Sync Center might have a bearing on this. I saw a bulletin regarding a completely unrelated application yesterday that encountered errors caused by the Sync Center. Then I read another article today discussing how One Drive syncs files and folders to the MS cloud. Now this thread to bring it full circle. I'm going to continue to watch this thread, and want to say that I really appreciate the extremely professional community discussions on this Forum. Bravo.
  16. 1 point
    I am running Retrospect 15 and I'm having similar problems backing up a Windows 10 (Build 1803) laptop as a client. The client has 2 drives: C: (the OS) and Z: (a recovery partition). There are no issues backing up the host, which is a Windows 10 (Build 1803) desktop computer. No issues backing up 2 other clients that are Windows 7 computers. The first backup of the client laptop was working. It passed through the scan and was backing up files. However, I had to stop the backup midway for unrelated reasons. The next 2 attempts at a backup made it successfully through the scan for drive C: and some files were backed up. However, the -1103 error was thrown for the C: drive and the backup aborted. No issues at all backing up the Z: drive. All subsequent attempts for open file backup on the client resulted in the C: drive failing during the scan and no problems with the Z: drive. I confirmed VSS errors in the event log on the client at the same time as the -1103 errors. I can do a backup with "open files" disabled, although there are several warnings for sharing violations, which I assume would be expected. I have submitted a support ticket.
  17. 1 point
    My testing so far suggests to me that during the upgrade from Windows 10 1709 (16299) to Windows 10 1803 (17134) some security settings related to Windows services are not being carried forward correctly. In the case of the Retrospect Client this is preventing it from correctly interacting with VSS for system volumes. The test machine I have 1803 installed on has two volumes — a system volume and a data volume. The system volume fails with the above error but the data volume completes without error. Initial comparison of some security permissions between a 1709 Client and the 1803 Client show some settings missing. However to be certain it is not something I changed in the past I'll need to do some more checking and do an 1803 clean install on something.
  18. 1 point
    Stu, After a certain amount of playing around, I got Retrospect Mac 5.1 running on my ex-wife's old HDD and seeing my old tape drive attached to her old Digital Audio G4 tower (which she gave me for storage about 13 years ago after she moved to her own apartment). I did a search on one of the Storage Sets, and found 4 files ending in .tiff. However when I tried to Restore them, it turned out that no DAT/DDS tape I have with that Storage Set name matches the date that the Catalog File is expecting. Before I recreate a Catalog File from one of those tapes, please describe step by step what you did.
  19. 1 point
    Sure, I am the Backup, I don't see why not. The only possible glitch I can see is that what you can now purchase is Retrospect Mac 15; Retrospect Mac 14 is obsolete. The cumulative Release Notes for Retrospect Mac 15.0 say "New: Support for LTO-8 tape devices", so the chances are the support for LTO4 devices is still there. In case it isn't, I imagine you can go through Retrospect Sales to get a license code for Retrospect Mac 14.6, which can still be downloaded. The one thing I would caution you about is that the Desktop Edition only supports a single non-autoloader tape drive. If your LTO4 tape drive is fancy-shmancy, you may have to purchase the Single Workstation 20 Client Edition—which is substantially more expensive. You can probably negotiate this with Retrospect Sales, with whom I have no connection other than as a customer.
  20. 1 point
    Andrew Kinnear, I haven't done this myself, just read the User's Guides and half-experimented using my own Retrospect Mac 14.6 "backup server". However, for a media set named "Media Set Example", I think the answers are: [1] It should be fine to use CCC, provided you copy the parent "Retrospect" folder and the "Media Set Example" folder within it as well as the "1-Media Set Example" data file within the "Media Set Example" folder. After you've done the cloning, click the Media Sets category on the left-hand side of the Console, click "Media Set Example" in the list pane, and click the Members button above the detail pane below the list pane. You can then click the the only line in the detail pane (you said you have only one member for each media set), which should be "1-Media Set Example", and after that click the pencil icon at the bottom left of the detail pane; doing so should allow you to redefine the location of "1-Media Set Example"' as being the cloned file instead of the original. After that you shouldn't have to do a Rebuild of "Media Set Example", but if you do the instructions are under the heading "Rebuilding a Media Set"—which is on page 220 of the Retrospect Mac 13 User's Guide (the P.P.P.P.S. of this post explains why I'm looking at that UG instead of the Retrospect Mac 15 UG; the only attempt at an explanation of the functionality I've just described is at the bottom of page 15 of the old version). [2] AFAIK no functionality should be lost for "Media Set ExampleSmall&Cryptic". The reason it shouldn't be is that the snapshot—the basis for most of the functionality—is part of the "Media Set ExampleSmall&Cryptic" Catalog File, which your Copy Media Set script will have created as essentially a duplicate of the "Media Set Example" Catalog File. If there is loss of functionality, IMHO there should be mass developer suicides (insert appropriate smiley here) in Walnut Creek CA, considering that the Copy Media Set type of script was introduced in Retrospect Windows 7.5 by 2008. [3] I don't use software compression or encryption in my humble home installation of Retrospect Mac (I keep last week's rotated USB3 backup disk in my bank safe deposit box), but AFAIK they should be applied if you've specified them when defining "Media Set Example—Small&Cryptic".
  21. 1 point
    Every time a backup is run Retrospect will create a .session file, containing details of the files from that backup, in the same folder as the .rdb files. When Retrospect does a Catalog rebuild it will read these .session files for the necessary information which is faster than reading the individual.rdb files. If you need to perform a thorough rebuild it is necessary to delete the .session files. (During the rebuild the .session files will be recreated.) This feature for faster Catalog rebuilding was added in Retrospect 11 for Windows and Retrospect 13 for Macintosh.
  22. 1 point
    Hopefully your problems are down to a simple typing error. Your folder structure is invalid. It should be \\BONZONAS\PCBackup\Retrospect\Backup Set NAS1(e)\1-Backup Set NAS1(e) (based on your previous posts) not \\BONZONAS\PCBackup\Retrospect\Backup Set NAS1e\1-Backup Set NAS1(e). The member folder name is always the Backup Set folder name with an n- prefix added. You can ignore the following if you like but I'll leave it here for the moment to show how sometimes it easy to overlook what it there in plain sight. I should noticed it in your previous post! I've had a look at the log. Is \\BONZONAS a home-built NAS or a commercial unit such as QNAP or Synology? Retrospect can at least see that there are files in the 1-Backup Set NAS1(e) folder. Retrospect is doing a thorough rebuild of the catalogue by reading the contents of the .rdb files. Had you deleted the .session files from the folder 1-Backup Set NAS1(e) before starting the rebuild? Retrospect is trying to create the AA130340988226970000.session file to a location that does not exist. For some reason that I can't fathom the path for the member folder has been almost duplicated. \\BONZONAS\PCBackup is the NAS and share. \Retrospect\Backup Set NAS1e\1-Backup Set NAS1(e) is as it should be. \Retrospect\Backup Set NAS1(e)\1-Backup Set NAS1(e) is almost duplicated part. ** And this is when I realised it was hopefully a simple typing error **
  23. 1 point
    haggis99, In the "What's New" chapter of the Retrospect Windows 11 User's Guide, page 14 says "Retrospect v11 for Windows and Retrospect v13 for Mac now allow customers to move the member folders of disk sets to new locations and let Retrospect know by simply editing the members and picking the new location. There are scenarios where moving these files is preferable to a set transfer." Presumably this is what you want to do. Unfortunately these sentences were not moved elsewhere in the Retrospect Windows 12 UG, nor were they amplified. Instead they were simply overlaid by the new "What's New" chapter. Being a Retrospect Mac administrator, I don't offhand know how to edit Members in Retrospect Windows. There is an Edit Pencil capability in the Retrospect Mac equivalent of dealing with Backup Sets. I assume that, if you click the Show Members button shown in the dialog on page 410 of the Retrospect Windows 11 UG, you will find something equivalent to that edit pencil that will let you edit the Members and pick their new locations. Retrospect Windows administrators, fee free to chime in with more particulars. BTW you haven't said in this thread what version of Retrospect Windows you are using, but I see from one of your recent posts that you are using Retrospect Windows 12.
  24. 1 point
    Well ... we updated to v14.6.x [SERVER and CLIENT] for Mac OSX and the problem magically went away :-)
  25. 1 point
    The VWMare add-on doesn't support current versions of VMWare and we are no longer selling this add-on unless someone absolutely needs to use it. This old add-on is discontinued. If you would like Virtual Machine support, please look into purchasing Retrospect Virtual which is a complete solution for virtual environments.
×