Jump to content

willfurby

Members
  • Content count

    95
  • Joined

  • Last visited

  • Days Won

    2

willfurby last won the day on August 23 2017

willfurby had the most liked content!

Community Reputation

3 Neutral

About willfurby

  • Rank
    Occasional Forum Poster

Profile Information

  • Gender
    Not Telling
  1. Retrospect Multi Server ver 11.5.0.190 running on Microsoft Windows 7 SP1 I am backing up an SBS 2011 server and I am receiving the following error when backing up the Exchange database. However, the individual mailboxes are getting backed up without issue. Any troubleshooting steps would be greatly appreciated. Thanks. - 11/13/2017 7:30:22 PM: Copying Mailbox Database on ANC (SBS2011) 11/13/2017 7:30:39 PM: Found: 1 files, 2 folders, 252.8 GB 11/13/2017 7:30:40 PM: Finished matching 11/13/2017 7:30:41 PM: Copying: 2 files (252.8 GB) and 0 hard links Backup type: Differential [*] T-10: MapError: unknown Windows error -3,050 Trouble reading files, error -1004 (Database Backup/Restore error) 11/13/2017 7:37:54 PM: Execution incomplete Remaining: 2 files, zero KB Completed: 0 files, zero KB, with 0% compression Performance: 0.0 MB/minute Duration: 00:07:31 (00:00:17 idle/loading/preparing)
  2. Multi Server V 11.5.0.190 Exchange 2010 running on SBS 2011 Retrospect computer running on workgroup workstation I am using a Retrospect Backup User (RBU) user account as recommended by Retrospect to log into the Exchange databases. Retrospect is not running in that users security context becasue I get and "invalid" error when entering those credentials into the preferences. That said, when backing up the Exchange databases I get the following error: 8/22/2017 11:26:28 AM: Found: 1 files, 2 folders, 241.7 GB 8/22/2017 11:26:28 AM: Finished matching 8/22/2017 11:26:30 AM: Copying: 2 files (241.7 GB) and 0 hard links Backup type: Differential [*] T-10: MapError: unknown Windows error 271,114 Trouble reading files, error -1004 (Database Backup/Restore error) 8/22/2017 11:26:38 AM: Execution incomplete Remaining: 2 files, zero KB Completed: 0 files, zero KB, with 0% compression Performance: 0.0 MB/minute Duration: 00:00:28 (00:00:22 idle/loading/preparing) However, it can backup the mailboxes successfully. I'm a little confused by that... If anyone has some insight or guidance they can give me, I would be most appreciative. Thanks.
  3. Retrospect 8.5 crashed hard, and corrupted the configXX.dat file over the weekend. I tried restoring this, but was unsuccesful. I had to obtain the product license keys and basically start over with everything. There are only 2 backup sets (servers, and servers2) backup set "servers" was recycled before the crash, and only backed up for about 2 hours (meaning it only has 2 hours worth of backup data altogether) backup set "servers2" seems to still be intact and as it was (meaning all of the .rdb files are still in their original location) I succesfully recataloged "servers" with no issues. However when I perform the same steps on "servers2" I get the error message: "The Backup Set data file name is invalid, cannot recatalog the set using these files" Any input or suggestions would be greatly appreciated. Thanks
  4. Can't List Volumes Error -3408

    Sorry for the late reply. I did find the issue. IPv6 is disabled on the Exchange server NIC; but, there was an IPv6 loopback entry in the Hosts file. I REM'd it out and Retrospect could list the mailboxes.
  5. glyphco.cpp Assertion Failure

    Backing up with only one execution running seems to work. Must be too much for the computer to run multiple executions.
  6. Retrospect Multi Server v9.0.0 (189) Windows Server 2003 R2 Enterprise SP2 Exchange 2007 SP1 Windows Server 2008 Enterprise SP2 When attempting to run a backup of our Exchange Mailboxes we received the following error: Sorry, can't list volumes on Exchange Mailboxes on [servername] error -3408 (unknown) Any assistance with an "unknown error" would be appreciated.
  7. glyphco.cpp Assertion Failure

    The Retrospect computer is a Windows 7 Pro workstation with 8GB RAM. The backup set is on a NAS, so is not attached to the workstation at all. The client is going to run a recycle backup of his servers. I asked him to pause the schedule on any other scripts, so that we only have one operation running. We'll see how that goes and I will post an update.
  8. glyphco.cpp Assertion Failure

    I'll have to look into that. I will talk with the client and get back to you.
  9. glyphco.cpp Assertion Failure

    It was matching.
  10. Windows 7 Pro SP1 x64 with 8GB RAM Retrospect Multi Server v9.0.1 (110) I have a client who is experiencing quite a number of assertion errors. He has already renamed the programdata\retrospect folder and recreated scripts, and recataloged backup sets. This morning he received Assertion failure at "glyphco.cpp-2862" I am attaching the assert_log.utx file. Any assistance would be appreciated. assert_log.utx
  11. VADP Failure

    Thanks. A co-worker opened a Retrospect Support Case on this.
  12. VADP Failure

    Windows Server 2008 R2 Standard SP1 Retrospect Multi Server 8.5.0 (136) VMware ESXi 5.0.0 When backing up the clients, the backup completes without error. However, when backing up a Virtual Machine we get the following: VMwareVolumeTracker::VMwareTrackCreateSnapshot: Failed to create snapshot for Virtual Machine "BSI remote" (error -3521 ( VADP failure)) VMwarePro::VMwareMountVirtualMachineVolumes: Failed to create snapshot for Virtual Machine "BSI remote" (error -3521 ( VADP failure)) VMwareVolumeMountHelper::Setup: Failed to mount Virtual Machine "BSI remote" (error -3521 ( VADP failure)) VMwareVolumeTracker::VProAccess: Can not create volume, error error -3521 ( VADP failure) Can't access volume C: on BSI remote, error -3521 ( VADP failure) I have already verified that there are no Independent disks configured. Any assistance would be greatly appreciated.
  13. Retrospect Server: Microsoft Windows Server 2003 R2 Enterprise SP2 Retrospect Multi Server 8.2.0 (177) Exchange Server: Microsoft Windows Server 2008 Enterprise SP2 Microsoft Exchange 2007 SP1 .NET 4 Extended and Client Profile installed MAPI and Collaboration Data Objects 1.2.1 installed Visual C++ 2005, 2005 (x64), 2008 -x86, and 2010 x64 all installed Retrospect Client 8.2 IPv6 disabled on NIC Domain Controller: Microsoft Windows Server 2003 R2 Enterprise SP2 We are getting the following error when attempting to backup our Exchange server: * Resolved container Exchange Server on [servername] to 2 volumes: First Storage Group on [servername] Second Storage Group on [servername] T-2: Create MAPI session failed: If the domain controller and Exchange server are installed on different Windows 2008 servers, this may be an issue of IPv6. The databases get backed up; but, not the mailboxes. We do not have a Windows 2008 Domain Controller, and IPv6 is disabled on the Exchange server. Does anyone have any insight on how to solve this. Thanks in advance.
  14. I am running Retrospect 7.6.2.101 on a SBS 2011 box I am unable to add a client machine which is running windows 7 64bit SP1 I have tried using the client installer version 7.6.107 and 7.6.106 During the installation on the client machine an error appears "RegCreateKey(HKEY_LOCAL_MACHINE, "SOFTWARE\Dantz\RetrospectClient\5.0\Install", ...) returned 5" The installation appears to complete and the registry appears to have entries in the path mentioned in the error message above. I have tried uninstalling/ reinstalling the software as well as running the installation as both a local administrator / a domain admin with no differences in results. The retrospect client management area seems to function properly reporting no first access. The sbs environment can test ping through the add client wizard both via IP address and Hostname. But when actually adding the client retrospect reports "Couldn't add backup client, error -560" Any help would be appreciated, if additional information is needed just let me know. Thank you! ,Sean
  15. Client Deferred

    Thank you very much. That worked. Retrospect Phone Support states that it is a bug in 7.6; apparently it is fixed in 7.7.
×