Jump to content

curioffl

Members
  • Content count

    54
  • Joined

  • Last visited

Community Reputation

1 Neutral

About curioffl

  • Rank
    Newbie
  1. Retrospect 8, Exchange 2007. Since migrating to Retrospect 8, when I make a backup of "Exchange Mailboxes", I get this error on the same 5 (of 40 or so) mailboxes (an they appear not to back up very much of their content): - 2/4/2014 11:39:40 PM: Copying Ron E James on Rainbow Trouble reading files, error -1010 ( API request bad) 2/4/2014 11:45:26 PM: Execution incomplete Remaining: 21677 files, 697.4 MB Completed: 98 files, 3,394 KB Performance: 16.5 MB/minute Duration: 00:05:45 (00:05:33 idle/loading/preparing) I had no such problem on Retrospect 7.6 (or, at least it did not email me nightly to alert me of it). What do I do? Ron E. James D.O.
  2. curioffl

    Windows 2012 Foundation?

    I called support for the answer, in case anyone else ever asks this: Retrospect 7.6 will not support a 64 bit OS server-side, so anything newer than Windows 2008 R1 is out. Retrospect's support is recommending Windows 2012 Standard for a multi-server install. (At this time there is a problem with running it as a specific user on Essentials which you need for the Exchange and SQL clients and perhaps some other issues with Windows 2012 Essentials.)
  3. Will Retrospect 7.6 multi-server work on Windows 2012 Foundation? (Or do I need Retrospect 8 for 2012 (server-side I mean)? Or do I need at least Windows 2012 Essentials?) Our Retrospect 7.6 multi-server on Windows 2003 has bitten the dust. We have the new blank server and are debating the OS. Thanks.
  4. No, but it stopped. The last backup to end with the error finished at 3:14pm yesterday. I did one thing right after that time and one thing right before then which may have had an effect (though I can't think how). Though many backups ended with this error, they appeared otherwise completed and functional, with the exception of two: One is a very large backup to a remote hard drive on a Windows computer. That Windows computer has compression turned on for the folder that Retrospect writes to. The hard drive itself is 1TB (889GB usable) and has some other backups writing to it. The particular backup set took about 500GB compressed, but was over 9XXGB from Retrospect's perspective. Setting the allowed size to 100% would only give 1TB (not sure if that's Retrospect internal or because of the drive) but any backup immediately asked for media, and logged the error. I decided to copy a few snapshots elsewhere and recycle the set... but even a restore would result in Retrospect asking for more media (after restoring a few megs) and recording the error. (That's a heart-dropping thing... when Retrospect appears intent on not restoring.) Since the backup seemed useless, and since this large backup represents only two weeks of files, I took a chance and recycled it (at 2:44pm) and ran a new backup (I'll know if that was the right choice in 13 days). The other thing was that a Linux client was a failing to run at all and was sending the error in its warning mail. (None of the others were, they were only recorded in the operations log, and I would not have known about the error at all if it weren't for this Linux client.) I went to look at its backup set (after noticing the lack-of-restore on the big one) and Retrospect gave me the "Where's the catalog?" behavior. Rather than try a repair, I copied the catalog file to a -orig, and I renamed the backup set's folder to -orig, then I deleted the backup set altogether and made a new one with the old name and assigned it to the scripts, and ran a backup (at 3:25pm) which worked fine. I noticed before I deleted the old set that it had a date on it (in Retrospect) of 4/27 (though it had not sent any error mails) though it should be backed-up to daily and though the mysterious error did not turn up till 5/7 following and overnight stop error on the Retrospect machine. (Looking now, the files in the -orig folder are dated daily including after 4/27 and the operations log shows completed backups to 5/6... but still it said 4/27 for the set's date in Backup Sets window). One of those two actions seems to have resulted in the error no longer recording. Maybe there was some sort of error that resulted in the Linux machine's backup set not updating Retrospect fully (and so the date remained 4/27) but the error was unexpected by the software (which did not record a problem in the operations log initially) and so it had no error mail to send. This new error came along and many scripts were recording it, so when Retrospect reached the same failure on the Linux machine's script it found this other error text to mail? That would make sense except that the log and files indicate completed runs prior to the error... also the behavior after the error was similar to a corrupted catalog error which Retrospect expects. It also doesn't explain why switching sets would make an error disappear that had not appeared for most of the time that the set was ostensibly in error. I don't know... it's weird. I did those two things though and the error that I recorded 100+ times between the morning of 5/7 and the afternoon of 5/9 suddenly stopped. *Shrug* - thanks for the response though. Ron E. James D.O.
  5. Following a crash of my Retrospect (Multi Server 7.6.123) machine I get: tyceInstall: LmRepair failed, code 14 arcDoRead: can't install tyce, error -802 (typed-space is corrupt) on about half of my backups (even after soft reboot). They do not seem to be client related (a client that backs up to multiple sets might only do this on one of them), and upgrading a client, forgetting and readding a client, and recycling a set seems to not have an effect either. The strange thing is, this seems not to have an effect on the backups. I can still backup and I can still restore. Anybody know what this is, and whether I should be concerned? I found only one forum post and the fix was to restore to an old config.bak file... so I did that, one from a week before the crash (and before the first occurrence of this error) and it did not help. Thanks. Ron E. James D.O.
  6. Is there a current (or planned) upgrade path for our (EMC) Retrospect server to the latest (or next) Roxio Retrospect version? Or will we need to buy the product again to upgrade? We are using EMC Retrospect 7.6.123 (hotfix 7.6.2.101). At some point there was a paid-upgrade from EMC but none of the added features had any appeal for us and the initial spate of problems reported to the forum scared us away. As the projected roadmap for the year has been posted, I am wondering what it will take for us to get from where we are now to the version that supports Exchange 2010 when released (particularly as this is a new company who may not view users of the former company's product as 'existing customers')? Thanks. RJ
  7. curioffl

    Retrospect Insights And 2011 Roadmap

    Has there been any thought given to improving the "service" model of Retrospect? As it stands our version can auto-launch on reboot but it assumes the "console" session when it does. As we control the Retrospect box ordinarily using Remote Desktop it is a bit of a hassle to have to separately overtake the console session with the single remote desktop connection and command-line flags (rather than just jumping in with a manager as with other Windows servers). What we would like to see is a setup whereby if we were to launch Retrospect in a separate terminal services session from the one whose desktop it is currently printing to, rather than an empty blue "monitor" box, the program would either overtake the existing other-session or (better) both sessions would launch to their respective desktops and both would have control (in a client/server model more than the current "this IS the program" model). It is not a far cry from that design to have (best) remote control of Retrospect via such a client (either by authentication or key exchange) so that my office machine, my terminal services session, and the console could all have simultaneous control. This is the model that BackupExec uses. And as needlessly complicated, fussy, and silent during failures as that software is, it has been difficult for me to sell clients on a Retrospect solution. We use Retrospect ourselves, but the one time that we have recommended it, our client (who also controls the server via remote desktop) struggles with what happens after a patch-reboot ("I got the blue box again"). Another who has a 2003 Veritas BackupExec install recently found the install CD and managed to do a "client only" install on his desktop and can watch and control that software from afar (in a way that looks exactly like what he sees on any terminal services session on the server itself). I would like to see Retrospect move toward a service/client model regarding its interface. RJ
  8. I have been getting these errors every Exchange mailboxes run: File "Guys Name\Contacts\00000000e3d017b50f46d549a6bffe5893dc94f60700f2c6d908024f6b46adfc7fb63a571183000000103b4b0000f2c6d908024f6b46adfc7fb63a57118300000015ba010000": can't read, error -3420 (unknown) If there's an errant contact is there any way to convert the long-numbers to tell us which one it is (the user has many)? Maybe we could delete it and add it again? If not is there any "Universal" exclude variable that can be set just to skip these three contacts? We are using 7.6.123. Would upgrading help? Thanks.
  9. It doesn't though. I think because you "exclude something and all of its subfolders", not "exclude only its subfolders" (which is what I'm trying to do). (Maybe I mistyped something, etc. But that's what I thought would do it but my backup was 0-files.) C
  10. Okay but I'm not sure on the logic here. If I define I:\data\ as a Volume. And then make a script that backs up that Volume, if I make an "exclude" rule to exclude sub-folders, that exclude rule has to exclude something in and of itself right? So I could only exclude I:\data\ AND its sub-folders or not (which is not what I want because I want the contents of I:\data\). I'm not sure at all on the logic of Include because I think if I point a script at I:\data\ it will include everything anyway. If I point a script at I:\data\ and say "include" I:\data\ but "exclude" I:\data\* and all sub-folders, retrospect backs up nothing. If I define I:\ as the volume I'm in the same problem (I think) of needing to know what all of the sub-folders will be in order to exclude them (they change). I'm sure I'm missing something obvious here and apologize for my ignorance. C
  11. Sorry, this feels like a total noob question but I can't seem to make it work with the available exclude rules. I want to backup a folder and all of its files, but none of its subfolders. Is there a combination that will do this? Defined "Volume" Data is: I:\data\ I want to backup: I:\data\file1.tmp I:\data\file100.txt I:\data\file1000.bmp But not: I:\data\folder1\* I:\data\folder2\* The files and folders in I:\data\ are constantly changing (so I can't just include/exclude specific ones) but I always want all of the files in the folder and I never want any of the subfolders. Thanks. C
  12. A user requested a Contact be restored (accidentally deleted a few days ago). I found the contact in the backups, but when I do a restore to just 'The Guy's Name' it puts the contact right in the root of 'The Guy's Name', and if I try to select and "Define" his "Contacts" folder, the restore says that it will "copy messages and folders to a new folder on Contacts on ServerName". And when I do the restore Retrospect fashions a subfolder tree named the-backup-set-name \ Contacts. Is it wrong for me to think that I should be able to restore mail (etc) to its "Original Location"? I feel that I must be missing some obvious checkbox but I can't find it so far. Thanks. C.
  13. Thanks for the quick reply. I remembered once shutting the retrospect.exe process with taskmanager and being greeted by a license request and no scripts/logs/backups-of-any-kind after and repairing this with the Config75 file... so I gave that a try, restoring a pre-patch-reboot version of that file (notably 98megs where the newer-by-a-couple-of-days version I replaced was 95megs) and it all just worked again. By the way, I control Retrospect with remote desktop/terminal services generally. Some update (a few years ago) changed the behavior of Retrospect. It used to be that when I'd log-in and Retrospect was running in some other session (usually running automatically in an unreachable console session following an unexpected reboot) it would say "Retrospect is running in another session, shall I shut it down for you?" or some such). For some time now this has been replaced by a blue box, that is said to be a monitor but never actually displays anything 'monitory' and offers no options for me to soft-kill the open Retrospect in the other session, or better 'assume' it. Is there some combination of preference check-boxes (update to 7.7 maybe?) that would make the old behavior return (something better than that blue box?) I feel like I'm pulling a slot-machine lever every time I open Retrospect... Will it come up or will I get the 'slam me shut with taskmanager' blue-box of nothingness? Thank you CF
  14. Exchange 2003 Retrospect 7.6.123 (both run on the same server) (backs up to disk) We have been backing up "Exchange Mailboxes" nightly for almost a year. Friday night's run interrupted with a "waiting for media" and the Exchange backups halted. On Monday morning someone Windows patched and rebooted the server (without considering Retrospect or clearing the error dialogue). Immediately following that reboot (and on last night's try and on all by-hand trys) Retrospect fails almost immediately on its Exchange backup sending a mail as: failed during automatic execution, error -1121 (unknown file system) Also, I removed "Exchange Mailboxes" as the script's source and tried to re-add it, but, though I can see the Exchange server, the storage groups, Exchange Mailboxes, and all of the users underneath that from within Retrospect, when I click to highlight "Exchange Mailboxes", the OK grays out. I can, however, select all or some of the users under "Exchange Mailboxes" but with any of these as the source, the backup fails instantly with the same error mail. Making a new script has the same gray-out of the OK for "Exchange Mailboxes". The other (file) backups continue to work without error. I have rebooted again, no change. I have checked and it appears that all of the stuff in: http://kb.dantz.com/display/2n/articleDirect/index.asp?aid=9633&r=0.8902094 remains true (the login is still good, still has that initializing piece of mail I sent last year, etc). I really have no idea where to go from here. Exchange backups just flat stopped working after a reboot. Nothing has purposefully changed regarding Retrospect or the Exchange server. Any help is appreciated. CF
×