Jump to content

ngallman

Members
  • Content count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ngallman

  • Rank
    Newbie
  1. I'm also running 7.7.208 multi-server edition and have noticed this polling issue. To reiterate... server A belongs to backup set A-B and is currently executing. Server B belongs to backup set A-B and gets a retry status because backup set A-B is in use by Server A. Rather than polling Server C which belongs to backup set C-D (which is available for execution), polling starts over at the top of the list; Starting with Server A which is executing, so drops to Server B, getting a retry and starting over at the top of the list again. Server C of backup set C-D could be running as well as Server E of backup set E-F. But instead, only Server A is backing up because the polling issue.
  2. I'm running Retrospect 7.7 Multi-server edition. Since 7.0, I still find the reporting features to be a little lacking. What I'd REALLY like to print (for audit purposes) is the backup History TAB Contents located in the Activity Monitor Window and the detailed log associated with each history tab entry. This data is straight to the point and more informative (IMO) than the Backup Report and Operations Log Report found in the Reporting Menu. Besides, the history tab has a longer backup history than the reports in the reporting feature!? So, is there a way in the program to print the history tab contents? Or do I have to resort to taking screen shots?? Thanks, Nick
  3. ngallman

    Retrospect 7.7.208 released

    Mayoff. Since upgrading from 7.0 to 7.7, our exchange server backup routine now automatically backs up individual mailboxes as well. I don't care to backup individual mailboxes, just the directory and information store databases. How do I exclude the mailboxes? I opened the exchange server client and deselected the highlighted mailboxes under the volumes tab, but they backup anyway.
  4. ngallman

    Retrospect 7.7.208 released

    I just changed my logging preferences to 6 on trees and volumes. After tonight's backup routines' date=' I'll post the log results. [/quote'] Wouldn't you know it? No locked range conflict errors last night :confused2: Only disk inactivity threshold not met on the volume that had the conflict errors the night before. I lowered the threshold value to see what happens tonight.
  5. ngallman

    Retrospect 7.7.208 released

    I just changed my logging preferences to 6 on trees and volumes. After tonight's backup routines, I'll post the log results.
  6. ngallman

    Retrospect 7.7.208 released

    This release has resolved my issues (memory handling). The system runs much faster now that the memory usage no longer creeps to 500mb. I have a new issue now, however, that I never had with Retrospect 7.0 Multiserver edition. I'm now receiving the following errors on PST files only: can't read, error -1111 ( locked range conflict) Any suggestions? My RetroClient is running as local service/interact with desktop as it always has. I have the open file backup option, but suddenly I get the error that open file backup cannot be used on the drive in which the -1111 errors also appear.
  7. This release has resolved my issues (memory handling). The system runs much faster now that the memory usage no longer creeps to 500mb. I have a new issue now, however, that I never had with Retrospect 7.0 Multiserver edition. I'm now receiving the following errors on PST files only: can't read, error -1111 ( locked range conflict) Any suggestions? My RetroClient is running as local service/interact with desktop as it always has. I have the open file backup option, but suddenly I get the error that open file backup cannot be used on the drive in which the -1111 errors also appear. --nick
  8. Yeah. I noticed that AFTER the purchase and installation (having gone by the advertisement page for 7.7). Anyway, it seems that only the new disaster recovery feature doesn't work for restoring Windows 2000 servers/workstations. I've just completed a successful restore of a Windows 2000 server by first loading win2k on the machine, installing the retroclient, and then restoring to the new client with the replace corresponding files option. All is well. So I really don't understand how Retrospect backup running on a 2003 and up OS will resolve restoring a Win2k box using the new disaster recovery winPE tool. Oh, well... just so that my restores work
  9. I recently upgraded from Retrospect 7.0 MultiServer edition to 7.7 MultiServer edition which runs on a Windows Server 2000 SP3 machine. All existing backup routines are running without issue. Today I decided to try the new disaster recovery cd that comes with 7.7. I booted the disc, partitioned the drive of the test machine, and started the client restore session. From the Retrospect server, I added the awaiting client, then proceeded to restore it from a Windows 2000 workstation backup. The restore fails with no specific error other than 'incomplete'. I tried restoring one of our Windows 2000 Server snapshots; it failed in the same way. Then I decide to restore a Windows XP workstation snapshot... it ran without issue! Please don't tell me that Retrospect 7.7 MultiServer Edition does not reliably backup Windows 2000 Servers! I'd rather that just the new Disaster Recovery CD doesn't support Windows 2000 restores and that I can still AT LEAST install windows 2000 on a machine, install the retrospect client, and then proceed to perform a restore of 'corresponding files only'. Someone please clarify this for me. I decided to upgrade BECAUSE of the Vista/Win7/Server08 support; expecting Windows 2000 to still be supported. Especially since this is what I read on the website before purchasing: ***Retrospect for Windows Editions Retrospect Multi Server 7.7 for Windows Retrospect Multi Server Edition runs on Windows 7 and other Windows operating systems, and provides licenses to protect an unlimited number of networked servers. In addition, Multi Server protects unlimited Windows, Macintosh, Linux, and Solaris desktops and notebooks, and now provides complete bare metal disaster recovery in the event of a catastrophic loss of data. Add-ons enable backup and restore of open files, SQL servers, and Exchange Servers.*** Notice the 'and other Windows operating systems' statement. Help!
  10. Decided to add a backup routine for Mailboxes as well, however I get an error stating "Exchange Mailboxes was Empty". This has me baffled because I'm using an account that: a. Has an active exchange account b. Has logon as service rights c. Is a member of User, Domain Admins, Administrators, backup Operators, Enterprise Users d. Has 'Services account' permissions AND 'Admin Permissions' permission in Exchange 5.5 administrator c. Can logon to ANY mailbox via OWA d. Can browse all mailboxes from the Volumes Database window in the Retrospect. Any ideas?? Thanks, Nick
  11. OK. Thanks for your help. I already have a parallel Exchange Server that I run in a VMWare environment. I'll use this server to run full-system-state restores to. Thanks again, Nicholas
  12. This is what I was afraid of. Are there ANY utilities that can read the Retrospect RDB files directly in order to perform this extraction? Or is through Retrospect the ONLY way? I'd like to remove the burden from myself and simply hand our tape libraries (14 members per tape backup set) over to our lawyers. Is this pointless, or could they have any success getting the Exchange data directly from tape? Or... am I stuck having to restore the entire server one instance at a time? Does DANTZ by chance sell a tool that I/our lawyers could use to read the RDB files directly? Thanks, Nicholas
  13. We have a forensics situation where I really need to simply EXTRACT the PRIV.EDB files from our Exchange Server 5.5 backup sessions! Is there ANY way; through the use of Retrospect OR a 3rd party utility? Here's more info: Retrospect 7.0 Multi-Server Edition w/Exchange opt Exchange Server 5.5 No individual mailbox backups (hind-site is 20/20) I can browse the sessions in the backup set, choose the "Information Store", see the 15.5Gb Information Store file, but the "retrieve" button in the backup-set properties box remains greyed out; unlike performing the same steps above when choosing a document simply backed up on a particular volume. I can't bring down our mail server, restoring it's entire state for each day in question, for the sake of obtaining the contents of ONE mailbox for a range of days. Help! How can I simply extract the Exchange 5.5 EDB files from the exchange backups and place them in another folder in order to read the EDB files using my Ontrack Tools?? Thanks, Nicholas
×