Jump to content


  • Posts

  • Joined

  • Last visited

MRIS's Achievements


Newbie (1/14)



  1. keep going with the fresh start is my advice.
  2. As the proud owner of Windows 7 ULTIMATE, you have the built-in feature named "Create a System Image", which backs up your entire computer to an external hard disk, and which can be restored from by simply booting from the Window 7 DVD and choosing restore. Does "Create a System Image" work on your computer? If it too, hangs, then there might some other kind of problem with your computer. If it gets right through, then there might be a problem with retrospect. I thought I might also mention that if you perform a "Create System Image" of the same computer to the same disk at a later date, both images are stored on the disk and you can select which image is to be restored from, but they only take up the space of a little more than one image, since it keeps a delta between the images.
  3. do you have an MSDE on that computer? (another way of asking this is: "In task manager, on the processes tab, and the option for processes of ALL users are displayed, is there a process named "sqlserver.exe"?")
  4. Until you get this problem sorted out, try running the backups in immediate mode, rather than by using a script. The purpose of this is that immediate mode gives you a PREVIEW of what it's going to be doing, and WHY. So if the preview indicates that its going to backup about 2GB, then the problem isn't happening yet, so let it start and pay attention next time. If the preview indicates it's going to backup 130GB, then you'll be able to click through to the details to INSPECT which files it has selected and why it has done so for each file, then you'll know WHY it has done so. Specifically, look at an old file that doesn't change much, and look at the reason the preview window has selected it. Is it newer now than it was last time? (eg this could point to a filesystem date issue, people see this if they backup from network drives some times) The only other thing I can think of is that someone or something is recycling the backup set when you're not watching! Or the catalog may be corrupt and due for a rebuild.
  5. I've seen this before, and it's basically a case that the volume shadow copy mechanism built into XP isn't working quite right. If you were to do a test backup using NTBACKUP (the one which comes with windows), it will also log error messages that it can't create the volume snapshot needed to backup all the files including normally open ones (such as the registry etc). Thus the problem isn't actually with retrospect itself, rather there's something broken in the internals of the Volume Shadow Copy system. To see if this is the case, do a backup of maybe just the windows folder using ntbackup to a file and take a note of the error log produced. If I'm right you'll see errors related to the vss service being unable to operate properly, and thus you'll see warnings about plenty of open files being skipped. Fixing this is a little more difficult, however from memory involves re-installing all the volume shadow copy modules, and re-registering DLLs etc. I followed some instructions I found via Google last time...
  6. So to re-cap, you're using a Windows XP computer running Retrospect 7.7 to backup a MacOS client computer which has the latest agent installed. My advice would be to create a new, empty backup set, and backup the Mac to it. If you don't have enough space for a full backup, backup some of the mac, such as most of the OS. The purpose is to confirm or disproove my theory that there's something about your current backup set catalog which is corrupt, causing the crash just as the catalog is being updated. I'm hoping that by switching to a new backup set, with its new empty catalog, that the problem will go away. If it does, then that's your answer, simply backup to a new backup set and after a while you'll be able to recycle (wipe) the old one.
  7. Please take another look at the .rdb files in the screenshot above. Notice that NTFS compressions has been enabled some of them. I'd be willing to suggest the following: 1. You're better off using Retrospect's compression, rather than NTFS'. 2. It's possible that the NTFS compression being present on these files is causing the unusual behaviors being observed.
  8. Q. what are you backing up to? Disks or tapes? or D2D2T? I am suspecting user error. Consider this scenario to see if it applies to you: 1. you simply do normal backups to tapes, using a new tape each day. 2. at the end of the week/month you simply erase the oldest tape and then use it again.
  9. try this to see why it is happening: 1. you've just done a few of your backups to the same backup set. 2. now open the immediate backup window, set the source to what you are backing up, set the destination to the same backup set being used, then click the preview button. 3. it will match a whole bunch of files, if you're not mistaken. 4. within the preview window will be the REASON it is choosing to backup those files that probably shouldn't be backed up again since they haven't really changed. What REASON is it giving you?
  10. rather than running retrospect as the logged in user, run it as a specific user with password. alternatively/additionally, define a volume (UNC Path) and make sure to specify the username/password for accessing the UNC path. I'm assuming you're backing up to that UNC path.
  11. Again this is not a bug. I think the actual words are: "Will try to keep 'at least' 10 snapshots active". So this number isn't a maximum, it's a minimum. refer page 94 in the PDF manual. If you want your disk based backup set to consume less total space, change the size of the member of the disk based backup set. Other than that, it's perfectly healthy for a disk based backup set to hover at "near full" status indefinitely. 400GB of a 500GB member size (eg on a 750GB disk) is fine. My tip is to make the member size approx 90% of the actual disk size if that disk is dedicated to this purpose. Do NOT make the member size equal to or greater than the actual disk size.
  12. actually, if you forget a session, and without closing the disk-based-backup-set-properties-panel click the groom action button, that forgotten session will get groomed (deleted). please refer to page 258 in the PDF manual.
  13. Without being able to logon to the PC, it is difficult to determine whether the helper service has done its stuff after the FIRST reboot. - we might be able to remove the drive and mount it into a USB enclosure to review the drive contents (or use BartPE). Is there a log file that gets generated that one can check for? Remember when one logs in as the local administrator, one is immediately logged out again, you don't even get to see the desktop. Curiously, attempting to map a drive to the \\computer\c$ share from elsewhere on the network to that computer, specifying the local administrator account and password during the connection, fails. I recall mention in the release notes of earlier clients (maybe v6) that there were bug fixes made to cater for renamed administrator accounts... What does the helper service do, and might it be possible to use something like BartPE (or USB attaching the drive to a working computer) to manually achieve the same outcome?
  14. I've restored the (hard drive replaced) C: drive of a laptop retrospect client from a full backup (all files) taken just days before. Before starting the restore we installed a vanilla XP OS and patched it to the same SP3 level the laptop was at previously before installing the retrospect client. The restore all processes without error, and the PC reboots OK afterwards (manually), but: 1. the domain account isn't working, so isn't allowing domain users to logon. 2. when you login as the local administrator (whose account has been renamed via Group Policy), one is immediately logged out again. * how can one prevent the auto-logout?
  15. grooming to "10" backups (or more) activates a special feature in retrospect where it doesn't actually groom to that number, instead it "keeps as many as will fit" or something like that. the advice is to use another number, such as 9. my advice is to use the "retrospect defined policy" which works well for all cases.
  • Create New...