Jump to content

chadh

Members
  • Content count

    25
  • Joined

  • Last visited

Community Reputation

0 Neutral

About chadh

  • Rank
    Occasional Forum Poster
  1. The email alert I get from the server says: From Retrospect: Script "Server" failed during automatic execution, error -3405 (unknown). Please launch Retrospect and check the log for details. In th log that number appears under an exchange mailbox that was supposedly deleted some time ago. The text also says scanning error. I don't know why it it's trying to backup a mailbox that was removed. Chad
  2. I'm still having an error that might not be related, but it says "-3450" I cannot find any information about it. Chad
  3. I looked through the logs more closely and found errors for BU B related to grooming. Even though B was not connected it was still trying to groom it and possibly hanging the system. Since BU B is offsite right now, I removed it from the list of backup sets by forgetting it. I then started the proactive backups which completed and then ran the server script which also completed. So, it looks like a grooming error on and un related backup set was hanging the application. Is there a better way to setup rotating USB backup sets so this doesn't happen? Chad
  4. I just tried starting a manual backup to Backup A using the server's script. I click the execute button and now it is just hanging with an hourglass cursor.
  5. The open file option is NOT enabled. Any other ideas? Chad
  6. For the past week I've been struggling to get Retrospect to backup correctly. I have one Small Business server that runs retrospect backing up itself and four WinXP workstation on the LAN. 2 of the XP systems are on a normal backup script running every night. The other 2 are are on proactive backups. All backup to one of 2 USB hard disks (Backup A and . The drives are rotated every 2 weeks. The scripts (Server and 2 Workstations) run twice/day once to backup A and once to B, if A is not connected, it times-out and then the B script runs, or vice versa. Last week when I switched Backup A back in, none of my backups would complete. I rebuilt the catalog for backup A, verified the media, deleted and recreated the Retrospect configuration, but things still hang on the Preparing to Execute step. The only way to get Retrospect to do anything is to End its process with the Task Manager. Please help, this similar problem has been happening every 5-6 months since I installed Retrospect and began using it. Usually, rebuilding the catalog works, although it takes about 12 hours. Nothing seems to work this time. Chad
  7. chadh

    Backup Set problem

    I closed the application, Rebooted the server and deleted the Retrospect configuration files. Re-opened the application and went through the initial setup. I added the one Backup Set A, created a proactive backup containing only one client and Backup Set A. The backup completed successfully. I am currently running a scheduled backup of the server to Backup Set A.
  8. chadh

    Backup Set problem

    After 10 hours it still says closing. What is going on?
  9. chadh

    Backup Set problem

    I finally had to give up waiting and ended the Retrospect Tasks in task manager. After re-launching the application, I stopped all waiting scripts and started only the Proactive backup. I have Backup Set A installed. The Proactive Script is set to backup to Backup Set A and Backup Set B. I rotate these backups on a weekly basis. The proactive backup started and began backing up the source called 'Dell" which has two drives. Below is an outline of the backup process: Started 8:24pm 1of2 8:25 Scanning 8:47 Preparing to execute 8:49 Matching 8:55 Preparing to Execute 8:56 Copying 9:08 Updating Catalog file 9:10 Building Snapshot 9:20 Comparing 9:26 Closing 2 of 2 9:33 Scanning 9:35 Preparing to Execute 9:36 Copying 9:50 Updating Catalog file 9:0 Building Snapshot 9:51 Colsing 9:51 Comparing 9:55 Closing 10:15 closing The backup is hanging on the closing step. There are no errors in the retrospect log or Windows logs. The system is also sending me email alerts that it is waiting for Backup Set B and that grooming failed for Backup Set B. Chad
  10. chadh

    Backup Set problem

    24 Hours and no change.
  11. chadh

    Backup Set problem

    The backup still says "Preparing to Execute" Has been running for 8 hours. Now Retrospect has become unresonsive. The cursor has become an hourglass anywhere in the application. Chad
  12. chadh

    Backup Set problem

    After 15 hours the recatalog completed successfully. I restarted me backup scripts (after re-adding the backup set as a destination and then adding to the schedule. The backup started. There are two source computers on the script. The first was powered off and reported as an error. The second one is online. It has been saying "Preparing to execute" for 2 hours now. There are no errors in Windows or Retrospect, aside for the one computer that could not be found. This backup job is scripted, and is holing up a proactive job, as they both use the same backup set. Chad
  13. chadh

    Backup Set problem

    No VSS errors. I'm currently recreating the catalog for the backup disk set. There is only one disk, but as it has about 600gb of data, the recatalog will take several more hours. I will post if/when it completes. Chad
  14. chadh

    Backup Set problem

    What started as a problem with one backup set has now grown to all my sets. When a scripted or proactive backup now runs it hangs on the Preparing to Execute step after scanning the source and matching it with the backup set. Retrospect appears to have crashed. The rest of Windows is functioning. There are no errors messages in the Retrospect log. There are no errors in the Windows logs. I am running the latest version of Retrospect 7.6 (7.6.2.101) And Windows SBS 2003 with the latest patches. What could be the problem here and how do I fix it? Chad
  15. Since yesterday, my backups are failing. They ask for the disk that the backup is on. But that disk is already connected and can be browsed in Windows Explorer. I've tried verify media, and it just asks for the disk to be be inserted even though it already is. When I try to repair the catalog-->Update existing Catalog File it completes successfully but it still will not verify. If I try repair catalog --> Repair file Backup Set, it asks for the catalog file which I select and get the error "Can't use a valid non-file Backup Set to Recreate. So, I try repair catalog--> recreate from disks. I choose all disks. Then it asks me to choose the disk and it tells me The Selected disk does not contain any Backup Set Data files. But it does. What is wrong and how do I fix it? Chad
×