Jump to content

russellg

Members
  • Posts

    17
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling

russellg's Achievements

Newbie

Newbie (1/14)

  • Dedicated Rare
  • Conversation Starter Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. How should I create a selector to exclude the following shared network folder: \\192.168.1.12\russellg\temp In the backup script, the source is shown as "russellg on 192.168.1.12". It's a shared folder on a Unix machine, and I'm trying to exclude it from a backup being run on my Windows 10 PC. I've tried lots of combinations for creating the selector, but when I test it by pointing it to "russellg on 192.168.1.12", it selects the entire temp folder for backup when it shouldn't. It shows each of the files in the test results window like this: \\192.168.1.12\russellg\temp\filename Thanks, Russell
  2. I replaced the motherboard, CPU, and RAM in my Windows 10 PC and I'm having trouble restoring the C drive from a NAS backup using Retrospect 18.1. The first problem was that with the old motherboard, I was using the legacy BIOS mode with MBR disks, and now with the new motherboard (ASRock Z590 Taichi) I want to use UEFI with GPT disks. The second problem is that the C drive was actually a RAID-1 mirror with two 500 GB SATA SSD drives (not m.2). After several attempts before understanding the first problem, I lost the data on the RAID volume. But I created a full backup of it on a NAS drive a couple of days ago, before upgrading the motherboard. To convert the two SSD drives from MBR to GPT, I found that the easiest way was to install Windows 10 on each of them separately, and it takes care of it as well as creating the reserved and system partitions. Next, I set the motherboard to disable CSM and Fast Boot, and changed the SATA Mode from AHCI to RAID (actually "Intel RST Premium With Intel Optane System Acceleration (RAID Mode)"). I then created the RAID-1 volume with the two SSD drives. My plan was to then restore the whole C drive back to the RAID volume. That's when the problems with Retrospect started. I booted from a Retrospect Disaster Recovery USB drive but it didn't see any of the local hard drives (neither the RAID volume nor the 3 other non-RAID SATA drives). It only saw the X drive and the 32 GB USB drive with WinPE. I also tried having Retrospect load the Intel Rapid Storage Technology driver that came with the motherboard, and it loaded ok but it still wasn't able to see the local hard drives. (Side note: Retrospect DR isn't able to load drivers from folders that contain spaces in the name. It returns an error for each individual word in the folder name.) To get it to see the local drives, I had to change the SATA Mode back to AHCI. But of course then I lost the RAID volume again. After multiple failed attempts at various things, I got the idea to leave CSM disabled but set the SATA Mode to AHCI (for Retrospect DR), install Windows 10 on each of the SSD drives (to setup GPT and the partitions), and then use Retrospect DR to restore the whole C drive back to each of the two SSD drives individually. My thinking was that if that worked, I could then switch the SATA Mode to RAID and create the RAID-1 volume again. However, when I tried to do the restore using the DR drive, it started by deleting the files that didn't need to be there, and then it just stopped the restore process without copying any of the files that needed to be restored. The history didn't explain why, but it showed 1 error: "The system state could not be restored": So instead of using the Retrospect DR drive, I decided to just boot into Windows 10 from one of the other non-RAID drives, install Retrospect, and do the restore from there. I remembered that you can't restore the C drive while you're booted off of it, but in this case I was booted off of a different drive. I set the SATA Mode back to RAID, created the RAID-1 volume, and then used Retrospect in Windows to do the restore to that volume. It copied all the files, but then ended with the same error above, saying the System State couldn't be restored. When I try to boot the restored volume, it gives a blue screen error 0xc000000e saying, "A required device isn't connected or can't be accessed". So now I'm stuck. Question 1: What's the best way to convert an MBR drive to GPT, and get all the partitions setup correctly? Question 2: When I create the RAID-1 volume in the UEFI settings, how much of the two SSD drives have to be identical first? Can I just have data on one of them, and it'll copy it to the other drive? If so, which one is the parent? Or will it even keep the existing data? Question 3: Why isn't Retrospect restoring the System State? I have a perfectly good backup of the entire C volume but I can't restore it, either while booted off a different Windows drive, or from the DR drive. Thanks! Russell
  3. Update: This seems to happen when the backup set isn't available. The backup set I was using for this backup was on a NAS that wasn't responding. When I got the network drive working again and could see it in File Explorer, Retrospect was able to back up to it with no problem. Russell
  4. I'm getting the following error when trying to start a backup: Retrospect has encountered a serious error: Assertion failure at "tstring.cpp-2385" A log of this error has been written to the file "assert_log.utx". I'm running Retrospect Desktop version 18.0.0.444 on Windows 10 version 20H2 build 19042.985. I tried rebooting as well as uninstalling and reinstalling Retrospect. I created a support ticket and included the zipped directories created by the Retrospect Support Tool. Thanks, Russell
  5. Problem solved. It turned out to be that the 100 MB SYSTEM partition on the netbook didn't have enough free space. I don't exactly understand why that would cause a problem, but it does. I found out because Windows Backup has the same problem, and someone else found out how to fix it. The solution is to increase the SYSTEM partition from 100 MB to 450 MB using a partition manager program. Then both Retrospect and Windows Backup work fine. A full description of how to change the partition is here: How to fix Error code: 0x81000033 when using Windows 7’s Backup and Restore Note that in his description on page 2 (where the actual solution starts), he mentions two partition manager programs. One requires a bootable CD, which won't work in this case since the netbook doesn't have a CD drive. The second program, EASEUS Partition Master, worked fine for me. Russell
  6. While trying to do a backup in Retrospect 7.7 on a new netbook with Windows 7 Starter, I'm getting the following error: After some searching, I've discovered that the error is a bit misleading. The problem is more evident in the Event Viewer, where I found the following error: From looking in the registry, I can tell that the volume in question is the Q: drive, which is labeled "Microsoft Office Click-to-Run 2010 (Protected)". Apparently that partition is created by Office 2010 Starter, which came with the netbook. Trying to look at its security settings gives the error, "You do not have permission to view or edit this object's permission settings", even though I'm logged in as an administrator. Therefore, I can't even get to the screen where I could take ownership, or make any other security changes. I am only backing up the C: drive, not the Q: drive. My guess is that when Retrospect tries to access VSS, VSS somehow wants access to all local drives, even though Retrospect may not need them all -- but I don't know for sure. I tried following the instructions on Microsoft's page about Event ID 12348 ( http://technet.microsoft.com/en-us/library/dd364979%28WS.10%29.aspx ), which says to run "icacls C:\ /grant system:f", but it didn't help, even though the command said it was successful. After discovering that the error is actually complaining about the Q: drive, I tried it on that drive as well, but received an "access denied" error. I don't want to uninstall Office 2010 Starter, which seems to be the only way to get rid of the Q drive. But if I could figure out how to give VSS access to the Q drive, it might solve the problem. Suggestions welcome. Thanks!
  7. Tibo, I'm not sure you're understanding the problem correctly. Just to be clear, I'm not saying that folders are being backed up as empty when I should be seeing files in them. I'm saying that folders that I've excluded with a selector are being included in the backup anyway, but without any actual files backed up -- just empty directories. But according to the selector rule I setup, even the folder names themselves shouldn't be appearing in the backup, and that's what I'm trying to figure out how to prevent. Thanks, Russell
  8. Assume I have files like this: C:\path1\path2\path3\file1 C:\path1\path2\path4\file1 And I create a selector to exclude all files and folders contained in: C:\path1\path2\ When I look at the snapshot after the backup, I see the following empty folders -- they don't contain any files, but the folder names are there: C:\path1\path2\path3\ C:\path1\path2\path4\ Why is it backing up path3 and path4? I see that it's not backing up the files inside those paths, but I don't want the folders themselves included in the backup either, even if they're empty. I've tried every possible combination of Windows Path selector lines, using "matches", "contains", "starts with", etc., but it's always the same. Thanks, Russell
  9. I noticed today that back on June 18th 2010, Retrospect started a backup at midnight like usual, but the History log reported the current time as: "4/8/2031 7:54:17 AM" (that's in mm/dd/yyyy format). But after about 3 hours, the backup finished and it reported the time correctly again, in 2010. Here are the first two lines of the log entry: 4/8/2031 7:54:17 AM: Copying D1-P1 300G XP (C:) 6/18/2010 3:20:38 PM: Snapshot stored, 295.1 MB I then noticed that the scheduled backups all changed to 2031 as well, and no further backups have been done since June 18th. Currently the next scheduled backup is 4/9/2031, and all other backups are scheduled onwards from that date. When I look at the backup script, it's been changed to the following: "Every day, starting 4/9/2031 at 12:00 AM" I wondered if the date had been changed on my PC, but there are no records in Event Viewer of any events taking place in 2031. And even if the PC's date had been changed, I don't see how the backup script would have been modified. Anyone else ever see something like this? Thanks, Russell
  10. I had this same error on one of the two internal drives I backup with Retrospect. Running a chkdsk on the drive didn't help, but doing a defragment on it did. Now it's finally backing up ok again without errors.
  11. I see in my backups that the following file is often being included, which is 111 MB in size: C:\Documents and Settings\All Users.WINDOWS\Application Data\Retrospect\RtrSec.dir\My Computer.dat I think this file includes some kind of archive bit info? Does it need to be backed up?
  12. I recently did a full volume restore with Retrospect Pro 7.0 and was then horrified to learn that a lot of my files were missing. It seems like it lost just the very oldest files, probably from the initial full backup. But everything that was backed up in at least one incremental since then was restored ok. I've had several problems with Retrospect when the backup drive fills up -- the "auto grooming" option has never worked for me, and I always just get errors saying the drive is full. I then have to try a manual grooming, which runs for hours and then fails with some other error. I've had several long conversatoins with tech support, and exchanged several emails with them, but it was never resolved, and I was never able to get a single support person to tell me that they've even tried to duplicate it. So I'm guessing that in one of those many problems with the grooming, Retrospect groomed away part of the very first full backup. I'm absolutely positive I never manually deleted any of the backup files. I did a full re-catalog of the backup files (it's a disk backup, to one directory), but wasn't able to find any more of the missing files. One thing I did that probably wasn't a good idea (as I think about it now) was that I did one initial full backup and then did incrementals for about a year. This probably isn't a very safe way to do things, but certainly Retrospect should have been able to handle it, as implied by the auto-grooming feature. Any suggestions for secret ways to recover any more of my missing data would be greatly appreciated. Russell
  13. Hi Amy, I'm using the trial version of Retrospect 7.0 (version 7.0.3.101) on Windows XP Pro. No, not using a selector within a selector (didn't know you could do that actually). It appears to be just this one selector list -- it has about 30 or so lines in it, but even if I delete almost all of them, it still crashes the program when I try to export it. I tried copying it to another selector name, but it crashed too. I tried copying "C:\Documents and Settings\All Users\Application Data\Retrospect\config70.dat" to another machine, and the selector came up fine when I viewed it on that machine, but it still crashed Retrospect when I tried to export it. I called tech support, and they'd never heard of the problem. I emailed them my config70.dat and the crash report that's generated each time it crashes, and even told them the exact filename and line of code it crashed on (it's noted in the crash file), but the tech I talked to didn't sound overly concerned with it -- just said it was probably an isolated incident and that I should just recreate the selector :-( I did recreate the list, and it did solve the problem -- we'll see as to whether or not the info I submitted to them gets converted into a program fix. Isolated or not, programs should never crash while dealing with data (especially data they created themselves), programmers should always fix crash bugs (especially when a user reports the exact line of code it crashed on), and phone agents should be a bit more energetic about passing on crash report info from customers to programmers. Thanks, Russell
  14. I'm new to this program also, but you might try this... Start Retrospect. Click Restore. Click Next. Click Recreate. Select Disk (if that's the type of backup you did -- probably) and click OK. Click "All Disks". Select the directory that contains the .rdb files and click OK. Hopefully it'll recreate the catalog and let you restore that way -- I haven't actually tried it. Good luck, Russell
  15. Ah, I think I just found the answer to my own question: http://list.dantz.com/pipermail/retro-talk/2003-December/005552.html It appears to happen if you have IIS installed (which I do) but it's disabled (which it is). I'm assuming I can ignore the error -- please let me know if this isn't the case. Russell
×
×
  • Create New...