Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 04/25/2018 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. 1 point
    Thanks, you found what I was looking for, but didn't find. A bit further down in that article: "LTO uses an automatic verify-after-write technology to immediately check the data as it is being written,[42][43] but some backup systems explicitly perform a completely separate tape reading operation to verify the tape was written correctly. This separate verify operation doubles the number of end-to-end passes for each scheduled backup, and reduces the tape life by half."
  7. 1 point
    Lennart_T is, as usual, correct (second paragraph of the section).
  8. 1 point
    insont, That's good, because I just found a 15 May 2018 Knowledge Base article change confirming what you've been saying. The paragraph "Mac Customers: Please note that Instant Scan is not supported with APFS." has been added below the first paragraph in the KB article "Instant Scan Frequently Asked Questions". which is under the catch-all heading "Resources" in the KB . That first paragraph begins with the sentence "Retrospect 10 for Macintosh and Retrospect 8 for Windows introduced a new feature called Instant Scan." This section of the permalinked old version of the Wikipedia article says those versions were introduced in 2012, so the original article almost certainly dates from sometime shortly after that year up through April 2015—when the companion article "Instant Scan Advanced Options" was published. Sorry to have previously expressed doubt, Martin. Pretty sneaky announcement there, Retrospect Inc. ; you didn't even point Martin to it in your final reply to his Support Case.
  9. 1 point
    Well, I did write support to ask if they had plans to fix Instant Scan in the future or if they'd given up on MacOS, and got some encouraging news: /Martin
  10. 1 point
    derek500, in this 2015 post, gave me the solution. See the remaining posts by me in that thread for further discussion. Although I'm still using Retrospect Mac 14, I routinely use that undocumented dragging-in-the-Details-panel-of-the-script-Summary trick whenever I Remove and re-Add a source. See further posts by me in that thread for an explanation. There's a limitation for local Sources because you can't easily Remove them, as discussed here and in posts that follow it. In any case, the first paragraph of this following post is my explanation of precisely what is the nature of the "alphabetical order" that Retrospect follows in backing up Sources within a script.
  11. 1 point
    I have some fairly complex selectors, and editing these via the UI is somewhat cumbersome. Is there a way to export the selectors in a text format that can be edited and rearranged in a simple text editor, and then reimported? I tried the "export" function, which produces a .rxx (Retrospect Exported Selectors) file. The format is binary and doesn't start with a known file type signature.
  12. 1 point
    David, I copied verbatim what Retrospect support sent me. How can I prove that to you? And yes, I created this login specifically to post about this, since the reply from Retrospect upset me. I didn't expect, however, to be accused of lying in the process. About "recent visitors block is disabled" I know nothing. I haven't touched my profile from the default. I'm sorry if I broke some kind of rule by not doing that. BTW, since you doubt my veracity, I'd suggest you ask Retrospect support if this is true. Either they confirm what I just said, making me somewhat happy, or they backtrack and say they are going to support Instant Scan in the future or that I misunderstood, and I'm even happier. To me their reply seems not quite thought through and not good for the product, so you asking could make them think again. Oh, and the case is nb 00061949 that contains this exchange, including the message I quoted. You're welcome to reference that. Martin
  13. 1 point
    Hi Lennart, Thank you for the quick response and the solution. I hadn't considered marking the other tapes missing but it's a good lateral solution, cheers! In the event of a volume failure we have a mirrored NAS that can be swapped over with replicated content. If THAT volume failed as well (and both are RAID6, so that would be quite unlucky) I'd cherry pick the specific priority active jobs we needed to continue working while slowly restoring the rest later. This backup script is typically more for the odd missing file from older projects and files that are accidentally deleted or overwritten. One recent example is on restoring a large design project we found a few missing assets that lived in another now deleted job. I was able to select those specific files from the catalog, relink and continue working. I think of this backup set as the rings on a tree trunk - it gives us a complete historical copy of every modified and added file over the better part of the last decade and has saved us on a few occasions.
  14. 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.
  15. 1 point
    I will +1 the feature suggestion. In fact, I want to take it further, down a path that other backup software systems HAVE successfully implemented: - Create a hash for each block of each file (They can define the block size :) ) - Store unique content-blocks. - All files with identical content will only be stored once. Doesn't matter what filename, date, attributes, etc.
  16. 1 point
    On Retrospect 15.1.0 I get the same results (I'm viewing the output in Notepad++ instead of Excel) as Lucky_Phil. What I did was: Reports > Session Contents Select Backup Set then select Session File menu then Export... For Select which data to export: choose the Backup Set and click OK In the Export Sessions dialog enter a filename and click Save
  17. 1 point
    Ahari, All those engineers working on a fix for a newly created problem, those engineers need to be paid. Retrospect doesn't stay in business with fresh air and rainbows. They need revenue. Either pay for upgrades. How would you feel if upgrades were "free" because you had to pay a monthly subscription fee to Retrospect? More and more companies are moving to the subscription model because future revenues are more consistent.
  18. 1 point
    In Windows 10 Home, I unlinked the account, turned off OneDrive and in Add / Remove programs, uninstalled it. That allowed me to then delete the OneDrive directories. True, the OneDrive folders returned later as visible in Windows Explorer ... but the issue with the directory is gone. Wonders never cease.
  19. 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.
  20. 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
  21. 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.
  22. 1 point
    Lucky_Phil and others, I am now seeing similar problems. When the script runs from the scheduler on the host (local) computer, it fails during a scan of the C: drive. No problems with other drives on the host computer. Running the script via the Run pull-down will run successfully. I believe this may be a different problem than the client issues, although both are throwing the same -1103 error on the host. The open file backup on the client C: drive is failing and throwing VSS errors in the clients' event logs. The error propagates back to the host as a -1103 error. This problem only occurs on the C: drive, not on other drives on the client. For the problem backing up on the local machine, I can find no related problems in the windows event logs.
  23. 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.
  24. 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.
  25. 1 point
    Assuming you are talking about a "Disk Backup set", this is what you do: Exit Retrospect. Move (not copy) the folder with the *.rdb files to its new location. Launch Retrospect Configure-->Backup Sets. Change the location in the "Members" properties by clicking on the "Browse" button. See attached picture.
×