Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About devolution

  • Rank

Profile Information

  • Gender
  • Location
    Portland, OR
  1. I have two Dell PowerVault tape drives, a 124T (Quantum Ultrium LTO-3) and a 122T (IBM Ultrium LTO-2), both of which have autoloaders. I have them attached to a Windows Server 2008 R2 box via a Ultra160 SCSI card. normally i only have the 124 attached but i'm trying to get it to work with both attached, each on a separate bus on the card. I've encountered this issue off and on, but i'm pretty sure the initial cause of it was removing Retrospect and installing Data Protection Manager 2010. after uninstalling that, when i reinstalled Retrospect, it could not see the Ultrium drives, though it could see the autoloaders fine. this happened with both drives (which were not installed concurrently). the only fix i ever found for this was to completely reinstall Windows Server 2008 R2, after which everything worked fine. this is something i am trying to avoid doing again as there are some other things installed on this server that are a significant hassle to restore on a new system. i did a few rounds with DPM 2010, testing it out before finally giving up on it. as far as i can tell, it does not install its own driver, but rather uses the ones that are automatically installed by Windows Server, so there's no "DPM driver" to remove that might be causing the problem. here's where it gets odd: if i tell Windows to install the (built-in) drivers for the 124T, Retrospect can't see that drive anymore (but it can see the autoloader). if I uninstall the drive in Device Manager, it shows up under "Other devices" as an "Ultrium 3" drive (instead of "Unknown device") but without a Windows driver installed. Retrospect sees the drive and works great with this setup. the same applies for the 122T, except that if i uninstall it, it doesn't show up at all in Device Manager until i reboot or "scan for hardware changes", when Windows automatically installs the driver for it ("tape.inf"), and it shows up under "Tape Drives" in Device Manager. once this happens, Retrospect cannot see the drive (but it can see the autoloader) until i uninstall it from Device Manager, after which it reappears in Retrospect's device list. this never happened until i installed and then removed DPM 2010. To recap: Retrospect ONLY sees the tape drives if they don't have Windows drivers installed for them, but it can see the autoloaders regardless (autoloaders show up as separate devices in Device Manager). needless to say, this is really not logical and it's REALLY annoying to deal with. i have not had this problem with any software but Retrospect, which i am not willing to get rid of. if anyone can offer some insight into what it causing this and how Retrospect is accessing these drives, i'd really appreciate it. it just doesn't make any sense that the built-in Windows tape driver would cause this much interference.
  2. ok, i think i just realized what the problem might be... i forgot that this backup was from way back when we were still on Exchange 2003 (the DB backup is 2 1/2 years old), and i've been trying to restore to Exchange 2007. i suspect that won't work.
  3. i don't have individual mailbox backups, only a full DB backup. if i try to use the Restore>Mailbox function, there are no snapshots and i can't create any because the backup set "does not contain any mailbox data".
  4. one thing that seemed to be the silver bullet for me on this issue was uninstalling both Visual C++ 2005 redistributables (x86 & x64) and then ONLY installing the x64 one back. someone else on the old forums found this to be the solution and, following his advice, i did the same on mine and it fixed the issue. this is assuming you also have right-clicked on your Exchange Server volume in the "volumes" dialog and set your "login as..." settings to a valid RBU, also. CCR shouldn't have any effect on authentication, but yes, you do have to use the active node.
  5. devolution

    How Do I Remove Snapshots?

    to remove a snapshot from a backup set, choose "Backup Sets" from the main screen, right-click on the one you want to work with, select "Properties", select "Snapshots" tab. highlight the one(s) you want to remove and select "Forget..." button. after confirmation it will remove them. as for removing the files, not sure if you can do that, since they are wrapped into the backup files. maybe grooming backup sets? i've never tried to do this so i'm not sure.
  6. i'm trying to restore a mailbox database backed up from a server that has been retired. i've set up a temporary mailbox server (Server 2008 R2) running as an Exchange 2007 mailbox server for this purpose. there is only "First Storage Group", with no mailbox database in it, on the server. the server has the same name as the old server. retrospect (7.7.503 or whatever the current version is) has no MAPI errors or anything like that. whenever i run the restore, it fails almost immediately and i get the following error, which does not appear anywhere in forum posts (old or new) or documentation or knowledgebase: - 7/26/2011 1:37:20 PM: Restoring from WM Exchange Daily Restore type: Full Trouble writing files, error -3653 ( Destination name returned by server is invalid) 7/26/2011 1:37:52 PM: Execution incomplete Remaining: 3 files, 98.2 GB Completed: 0 files, zero KB Performance: 0.0 MB/minute Duration: 00:00:31 (00:00:25 idle/loading/preparing) one thing i notice right away: the original EDB file was named "Mailbox Database.edb", while the one Retrospect is trying to restore is named "Mailbox Database (XCHG-SRV-09).edb" (it's appending the name of the server to the EDB name). don't know if this is what's causing the error or not. if i have a database already in the FSG named "Mailbox Database.edb" and try to do this restore, it creates a second database, with the different name, in the storage group. in general i've just been leaving the SG empty to minimize conflicts. i REALLY need some mailboxes from this database. i have found restoring DBs from Retrospect to be a complete nightmare, but i have done so successfully one time (on another server with a different backup). i could really use some help here.
  7. i'm trying to recover a public folder database backup, on a server set up specifically for the doing the recovery. Exchange 2007 on Windows Server 2008 R2 - both 32-bit (Retrospect 32-bit seems to be more stable than 64-bit). i have everything set up, server is configured as a mailbox server with two storage groups - one for mailbox, one for PF - and Retrospect 7.7.533 installed. basically, i can't get the storage groups to appear under "volumes" no matter what i try. i've tried every authentication trick i could find on the forums (the old ones). i've had trouble getting mailboxes to show up before because of authentication issues, but never had storage groups not appear. both "exchange server" and "exchange mailboxes" are greyed out. any suggestions or solutions would be appreciated.
  8. devolution

    Exchange - Restoring A Database/storage Group - Public Folder

    my understanding is that you have to restore the entire storage group to the "original location". the best way to do this is set up another exchange mailbox server and do the restore to that one, overwriting the blank PF DB. i think the setup has to be identical -- the stores have to be on the same drive letter and in the same folder paths, and the storage groups and databases have to use identical names. i'm not certain of this but from what i've been able to gather, that's the only approach you can take with restoring Exchange databases with Retrospect (unless you back up the .EDB files directly, which is not recommended afaik). i'm trying to do the same thing you are, but i'm getting hung up on an authentication issue, so i can't verify that this actually works. if you back up both stores in the same backup set, when you choose the source and destination for the restore it should give you the option to select either storage group.
  9. don't have match case on. that's a good idea about going around to the clients and doing exclusions. i just wish it would work from the server, as that's the whole point of having a centralized control center, and it's going to take a good bit of time to go around to each client and set those exclusions.:angry2: thanks for the suggestion though, i think that's what i'm going to have to do so i can get this going. HEAR THAT, ROXIO? you need to make this functionality work correctly from the server software, not just the clients. if i had 200 clients to deal with i would be seriously looking at moving to different software.
  10. i've tried both "match" and "contains" for most of the exclusions and neither really seemed to be better than the other. i know i had "[color:blue]contains 'program files'[/color]" and it still kept pulling stuff out of various directories in the "program files" folder. i think i tried "[color:blue]contains 'recycle'[/color]" also because on a Windows 7 client i got stuff from a folder that was called something like '$recycle_bin', so i figured that using that "contains" selection would eliminate that folder as well as "RECYCLER", but it didn't change anything. thanks for the suggestion though.
  11. i am creating a custom selector for use in backup up our Windows workstations. i'm only choosing to back up "documents", "pictures", "desktop", the Firefox folder in "\Application Data\Mozilla\" and a few other selected items like PST files. for some odd reason, Retrospect keeps including random files from other folders, including "Program Files" and the "RECYCLER" folder, even though i have specifically excluded for those. ([color:blue]folder name starts with "C:\Program Files"[/color] and [color:blue]folder name exactly matches 'RECYCLER'[/color].) the files in RECYCLER from one of the test clients are JPG files, which i haven't included specifically but perhaps are implicit with the "Windows folder is 'Pictures'" selector. most of the random files are insignificant in size, enough that they can be ignored because they add hardly any extra size to the backups, but the pictures in the RECYCLER folder are huge and will take up a lot of space if this happens across many workstations. my question is, how can i ensure that only the specific folders i've listed above are backed up, and everything else is ignored? i've added a bunch of stuff to the exclusion list, most of which works, but obviously some of them are overridden, though it's not clear how.
  12. this worked great! thanks. my setup is Server 2008 x64, so i'm pretty sure the problem is the 32-bit VC++ 2005 redistributable components. and yes, you can do this on a production server. it doesn't affect Exchange mail function at all unless you need to restart the services (you shouldn't have to restart Exchange services, just the Retrolauncher service). Exchange itself doesn't use VC2005 redist (it's installed with Retrospect) and doesn't require MAPI/CDO or it would install it in the first place.
  13. if you are using Exchange 2007 on 64-bit Windows (assuming it's production server) then the solution i found, thanks to another poster on these forums (see this thread: Exchange 2007 Mailbox not visible, my solution), to get your Exchange Mailboxes to appear is as follows: * uninstall both Visual C++ 2005 redistributables, 32-bit & 64-bit. *uninstall Exchange MAPI & CDO if you have it installed (if not, you will need to have it installed for Retrospect for Exchange to work correctly on EX 2007) * install VC++ 2005 redist 64-bit ONLY * install Exchange MAPI & CDO you may have to restart your server, or at least restart exchange services. this has fixed my problem with not being able to see mailboxes two times on two Exchange 2007 servers, so i would definitely recommend giving it a shot.
  14. i'm having this same problem as well. it's on Server 2008 x64 with Exchange 2007, using Retrospect 7.7. unfortunately going to a 32-bit machine (or 7.6) isn't an option for me as i am doing backups to tape and i don't have the option to move the tape drive to another machine. i can do storage group backups but not mailboxes. as yatcher said, if you try to do a lot of mailboxes in one script, the UI will disappear, but in my case it will still be running in the background until i force quit the process(es). in any case the backups don't complete and the logs don't register that anything happened. sometimes i get an assertion failure that's the same as the one the OP listed. this is lame.