Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


bcarter27 last won the day on November 11 2012

bcarter27 had the most liked content!

Community Reputation

2 Neutral

About bcarter27

  • Rank
    Occasional Forum Poster

Profile Information

  • Gender
    Not Telling
  1. It would be nice to choose multiple volumes or subvolumes in the Duplicate script (file copy or file move) Source window.
  2. bcarter27

    Instant Scan and long-time bugs

    Does anyone have a command I can push out to the Macs via Apple Remote Desktop to disable and stop this service?
  3. bcarter27

    Instant Scan and long-time bugs

    To disable the service remotely- sc \\remotecomputer config "RetroInstantScanService" start= disabled sc \\remotecomputer stop "RetroInstantScanService" or with psexec on a whole domain- psexec \\* cmd /c (sc config "RetroInstantScanService" start= disabled ^& sc stop "RetroInstantScanService")
  4. bcarter27

    Instant Scan and long-time bugs

    +1 This introduces another point of failure, the time-savings is minimal according to my logs, and this FAQ doesn't inspire confidence- --Question: If I think the scan file is corrupted, can rebuild the scan file? Answer: Yes, you will need to first stop the RetroISA process and then you can delete the RetroISAScans directory. I want to backup what is on the disk, not what this catalog thinks is on the disk. There should be an option on the server-side to not use Instant Scan when talking to a client. Or there should be an option to disable it client-side in the new client prefs. Logging into each client to disable this service will be time-consuming.
  5. Retrospect won't do a full restore to different hardware. Here are the steps I take to solve this- Setup your new hardware. If your crashed system had XP SP2, you must restore over the top of the same service pack version. So, clean install XP SP2 on the new system. Give the clean install a new, temporary computer name. Install the NIC drivers, if necessary. Restart. Install the Retrospect client and log it in at the server. Begin your full volume restore. After your restore finishes, but before you restart the new client machine, edit the Boot.ini file to make sure it is pointing to the correct partition. (Check the KB for more info on this. Many OEM systems have multiple partitions due to utility partitions, etc. It is good to have a UBCD4Win boot CD to edit your Boot.ini file offline.) Restart. The client PC won't boot. Boot from your XP SP2 disc and run a Repair install. This will put in the necessary HAL and storage drivers. After restart, reinstall the latest drivers for your new hardware from the manufacturer's website. Restart again and run all of the hotfixes at MS Update. At the Retrospect server, forget the temporary client you logged in earlier. Confirm that the old client name will communicate. The key here is the Repair install after the failed restore. Hopefully, EMC will write a boot CD for Vista that will boot a system, talk to the Retrospect server and act as a client, then merge the necessary drivers and registry keys to accomodate the new hardware. AFAIK, this functionality is built in to Vista's new backup app.
  6. We desparately need the ability to restore to different hardware during a disaster recovery. ntbackup can do this by NOT restoring certain files and merging certain hardware related reg keys. Retrospect needs this feature as the hardware turnover at small businesses is getting shorter and shorter. Also, most competing products are implementing this. It takes forever to reload apps & settings following a clean install of XP. HELP!
  7. Then you would need Retrospect running at the other location. I would settle for something a lot less complex- On the fly compression and encryption to an offsite sftp server (at a hosting provider) using the Transfer Snapshots option would enable my clients to have a a disk to disk to offsite solution. It would be great to integrate sftp, rsync, and/or webdav clients right into the Retrospect app. Virtual Drive utilities for these protocols don't virtualize at a low enough level for Retrospect to "see" the drive.
  8. Can we get an offsite option that will do a Transfer Snapshot script to an offsite data center via rsync or something similar?
  9. bcarter27

    True background backup

    I have a client with a small branch office and no server on that site. Retrospect runs on a workstation that sees only part time use. I get around having Retrospect show in the console by setting it to run at system startup through an item in the Windows Task Scheduler. Set your task to run as Administrator and it will not show up in the user's session.
  10. I have a product feature request- I have most of my customers backing up to hard drive in two sets. Set A runs for 4 weeks then goes idle. Set B runs for the next 30 days and then goes idle. Set A recycles and runs for 4 weeks, and so on. The only wrinkle is that the laptops being backed up through Proactive will sometimes backup to the "idle" Set instead of the active one, because it is available (because the media is HDs). There needs to be a Schedule section on the Proactive scripts that resembles the Schedule section of a regular backup script. The Proactive script section that deals with active times of the day should be renamed to something like Polling Window or Backup Window or Blackout Timetable, etc.
  11. Just an idea, but I don't think your backup user will have local logon rights on the machine if it is a DC. You may have to specify this in Group Policy or Local Security Settings (I am sorry but I don't remember exactly where.)
  12. Just wanted to post that my client experiencing this issue has not had a problem since downgrading all of their Retrospect Clients to 6.0. Additionally, we upgraded the machine running Retrospect 6.5 Single Server to Win XP Pro from Win 2000 Pro.
  13. Quote: When you installed the clients were you logged in as the domain administrator or the administrator of the local machine? Do the users have admin rights on each local machine? Clients were installed as Domain admin. Users are Domain users with restricted permissions and no admin rights. I wasn't able to reproduce it right away either. I think it is intermittent. The clients describe that they leave their desk with Outlook 2003 (Cached Exchange) open, it locks with the screen saver, Proactive backup kicks in, they come back later and their computer is hung. They restart and either the App Data or My Docs folder are newly created on the root level of C.
  14. OK,after a long time, I have more information on this issue. I apparently missed a few laptops. So, I did not disable the screensaver password lockout option for them. Sure enough, when I saw them recently, the Application Data folder, and in a few cases the My Documents folder, had been re-created on the root level of C:. This pretty much confirms the issue is due to the backup running while the machine is in a Locked state. To re-iterate, this has been happening since Win v6.0, I am currently running all of the latest Retro versions. The clients are set to Read-Only. The scripts have had the Force Outlook to quit option disabled long ago. These setups are not using Open File Backup Option. Nothing has helped until I started disabling the screensaver password lockout in the Display Control Panel. In a typical network environment, user privacy is crucial and it is very difficult to teach users to Log Off their machines every time they go to lunch, the bathroom, a meeting, etc. I have found an easier way to fix the corruption than to rely on System Restore (which doesn't always fix it) or doing a System State Restore From Retrospect (which sometimes entails removing the machine from the domain while offline, going online, and re-joining to the domain). If you login as the corrupted account, go into regedit, to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders You can see the offending folder paths have been changed. Change them back to point at the correct folders in the Documents & Settings\UserName path. Log Off and back in as Administrator, remove the incorrect folders that were placed in the root level. Move any important docs or files in them back to the correct folders in the Documents & Settings\UserName path. Log back in as the user to test- open & close Outlook and My Documents. Check out the root level of C to make sure the folders were not re-created. Then look at the key above on regedit to make sure that everything is still set properly. Make sure that the Screensaver password is disabled (or do this via Domain Group Policy). Run a System Restore checkpoint. Make a full backup in Retrospect. I hope this helps someone. My clients were about to kill me. I hope Retrospect can fix this so I can give my users back their privacy lockout.
  15. I finally had time to run these tests. The server at one client has since been updated to 6.5.350 and the clients to 6.5.136. I had a machine enter a locked state during a Proactive backup and it did not cause a problem. I will repeat the trial again this week, as sheduling allows, as it seems to be intermittent.