Jump to content

pentium4forever

Members
  • Content count

    21
  • Joined

  • Last visited

Everything posted by pentium4forever

  1. Hello, For quite some time, I've been getting the error below. I've substituted the backup set name for privacy purposes. How in the world do I get it fixed? The server in question, the First Storage Group, Second Storage Group, all related to Exchange. I've noticed the 1004 error has caused Retrospect to crash occasionally. The errors are below. I found some articles but they all seem to speak of SQL. We use another product for compressing and backing up SQL, we do write SQL data to tape via retrospect. Check out the errors below. + Normal backup using Test1 Exchange at 10/19/2009 6:39 AM (Execution unit 2) To Backup Set Test1... - 10/19/2009 6:39:48 AM: Copying First Storage Group on testad02 Backup type: Full T-8: >>>HrESEBackupSetup(050d) -- T-8: MapError: unknown Windows error 1,293 Trouble reading files, error -1004 (Database Backup/Restore error) 10/19/2009 6:40:29 AM: Execution incomplete Remaining: 2 files, 23.7 GB Completed: 0 files, zero KB, with 0% compression Performance: 0.0 MB/minute Duration: 00:00:41 (00:00:12 idle/loading/preparing) + Normal backup using Test1 Exchange at 10/19/2009 5:47 AM (Execution unit 2) To Backup Set Test1... - 10/19/2009 5:47:25 AM: Copying First Storage Group on testad02 Backup type: Full T-8: >>>HrESEBackupSetup(050d) -- T-8: MapError: unknown Windows error 1,293 Trouble reading files, error -1004 (Database Backup/Restore error) 10/19/2009 5:48:19 AM: Execution incomplete Remaining: 2 files, 23.7 GB Completed: 0 files, zero KB, with 0% compression Performance: 0.0 MB/minute Duration: 00:00:54 (00:00:20 idle/loading/preparing) + Normal backup using Test1 Exchange at 10/19/2009 5:08 AM (Execution unit 2) To Backup Set Test1... - 10/19/2009 5:08:34 AM: Copying First Storage Group on testad02 Backup type: Full T-8: >>>HrESEBackupSetup(050d) -- T-8: MapError: unknown Windows error 1,293 Trouble reading files, error -1004 (Database Backup/Restore error) 10/19/2009 5:09:23 AM: Execution incomplete Remaining: 2 files, 23.7 GB Completed: 0 files, zero KB, with 0% compression Performance: 0.0 MB/minute Duration: 00:00:49 (00:00:18 idle/loading/preparing) Thanks, Nick
  2. pentium4forever

    Exchange backup/restore error 1004

    The first storage group always generates the 1004 error, the Second storage group DOES NOT. Also, individual mailboxes back up fine, mainly just the first storage database that is an issue. Looking on the exchange server event logs, I do see some errors in it's application logs saying a process already started with first storage group. There a conflict or something I wonder? One of the links that someone provided earlier, should I dismount the mailbox database on the exchange server and remount it? Or reboot the exchange server?
  3. pentium4forever

    Exchange backup/restore error 1004

    Mayoff, Thanks for the response. The server that runs Retrospect server and services the clients, it is on a Windows 2003 Enterprise 64-bit platform, and not joined to any domain. On the server which we nicknamed Terastorus that acts as the retrospect server, it connects via domain authentication to the client, in this instance the client is an Exchange server. When I go into volumes, the login info: it's set to domain authentication and username is xbackupsvc and there's a password configured. for domain it has xdomainnet.com (hiding the identity for privacy purposes) This xbackupsvc account is a domain account in Active Directory on the Exchange server. What groups is the account a member of? Backup Operators, Domain Admins, Domain Users, Enterprise Admins, & Exchange Organizational Administrators. Cheers, Nick
  4. pentium4forever

    Exchange backup/restore error 1004

    I just looked, Exchange Backup Add-on is the last one listed in the whole box. 1 used 0 available for status of exchange database/mailboxes backup. Cheers, Nick
  5. pentium4forever

    Exchange backup/restore error 1004

    How can I tell if I have it? Under volumes I see "Exchange mailboxes and the first and second storage unit groups. Looking in licensing manager, we have the "Exchange Backup Add-on being used or installed. Only one I see, this is listed right under Exchange Database/Mailbox backup. (we use Exchange 2007) Cheers, Nick
  6. pentium4forever

    Exchange backup/restore error 1004

    Russ, Sorry, I'm glad I at least got someone's attention. The server Retrospect runs on is Server 2003 64-bit. Retrospect Multi-Server is the flavor. Retrospect 7.6.123. The exchange server is running server 2003, and the latest retrospect client software.
  7. pentium4forever

    Exchange backup/restore error 1004

    .......Anybody?
  8. pentium4forever

    Recycling glitch?

    Let me add I've canceled jobs before and ran them later and not seen this much of a drop of data transferred.
  9. pentium4forever

    Recycling glitch?

    I use Retrospect Multiserver 7.6.x and just noticed something very odd. We have different backup sets that run and are written to tape and after written to tape, they recycle. One particular job set, let's call it "Test" for privacy concerns. It occupied about 1.48TB of space. Another, smaller job ran before Test ran cause a proactive backup of Test was running When manually running "Test" later on, I noticed it only wrote about 260GB and then recycled. I noticed this as usually several tapes, tape 8 is next when the job is done. Still on tape 6 though. I should mention that YESTERDAY in the morning Retrospect crashed but these two particular tape set jobs were not even scheduled at that time. The other tape set, "Test 2" was approximately 500GB, I had purposely canceled this one to let Test run first. After, I ran Test 2 and the log shows 8.9GB written to tape and successfully recycled?! Test2 did run before Test early yesterday but just briefly, probably for like 10 minutes because I canceled it. Is this a recycling glitch? This is not good! I hope my writing of "Test" and "Test 2" aren't too confusing, I'm just trying to provide privacy. Thanks, Nick
  10. At my work, we use Retrospect Multi-server 7.6.123 and last week and this week I've noticed something odd and I can't believe they are both bad tapes or going bad. Each week we run file backups, 8 tapes used for that, then sql backups which are in the right magazine. In the left magazine, library slots 1-8, the tape in slot 2 last week when jobs were writing to tape I noticed it wanted to select new media, it had the tape in drive 2 read as "unknown" or something similar. This week, when putting week 1 tapes in, when everything initalized, all tapes were shown, including the drive in slot 2, Tape 2- and it's label there too. I've noticed as of right now, the tape in slot 2 is showing unknown. It did write to it this week, I was never prompted to insert a new media or anything. I've taken a screenshot for proof. http://nkeklund.googlepages.com/retrospecttapedrivelist.jpg Go to the link below. What should I do? I find it hard to believe that 2 tapes are going bad, all the tapes have labels on them, tapes are all LT03 tapes. We use 400GB tapes with compression can be up to 800GB per tape. Thanks, Nick
  11. Let me add that I just moved the tape from slot 2 to slot 13 in the right magazine where sql tapes usually are, and it stills says unknown. I moved it back to slot 2, unknown again. Then moved from slot 2 to the drive and it sees it as Tape Week 2!??????????
  12. Hello, I've recently seen the error below when backing up the Second Storage Group. I've replaced the server name and backup set with "X" for privacy reasons. The below if from the backup log. + Normal backup using X Exchange at 2/16/2009 5:02 AM (Execution unit 5) To Backup Set X... - 2/16/2009 5:02:25 AM: Copying Second Storage Group on X Backup type: Full T-8: >>>HrESEBackupSetup(050d) -- T-8: MapError: unknown Windows error 1,293 Trouble reading files, error -1004 (Database Backup/Restore error) 2/16/2009 5:03:15 AM: Execution incomplete Remaining: 2 files, 503.2 MB Completed: 0 files, zero KB, with 0% compression Performance: 0.0 MB/minute Duration: 00:00:50 (00:00:21 idle/loading/preparing) Now, I looked it up in knowledgebase and found the link below although it pertains to Retrospect 6.5. http://kb.dantz.com/display/2n/kb/article.asp?aid=5304&n=10&s= Any ideas would be greatly appreciated. Thanks, Nick
  13. pentium4forever

    Error 1004 with Retrospect 7.6

    I don't think there's a fix yet, reason being they point to link on how to set up things. I've been informed to check my settings on how I have things set up, funny thing is it was working fine for quite some time, I hadn't changed anything. I hope they come up with a solution eventually.
  14. pentium4forever

    Error 1004 with Retrospect 7.6

    I haven't yet gotten a response. Sorry to be a nag Mayoff. I have updated to version 7.6.107 (a month ago or so) and still receiving the error. Script: X Client: X Date: 4/17/2009 Trouble reading files, error -1004 (Database Backup/Restore error) >From Retrospect: Script "X" failed during automatic execution, error -1004 (Database Backup/Restore error). Please launch Retrospect and check the log for details. Script: X Date: 4/17/2009 Script "X" incomplete
  15. pentium4forever

    Error 1004 with Retrospect 7.6

    Mayoff, What are your suggestions to fix or troubleshoot this problem further? The machine it has a problem with is a Windows Server 2003 OS that does run Active Directory. Just looking now, the client software on this AD server was running 7.6.116 or whatever the version is exactly. Just updated it to 7.6.107. Will see what happens. Thanks, Nick
  16. pentium4forever

    Error 1004 with Retrospect 7.6

    Multi-server 7.6.123
  17. pentium4forever

    Matching takes forever

    Hello, This has been a problem for some time, although rather minor. At my work, we write several jobs to tapes, or backup sets I should say. There's one particular backup set that always seems to take forever to finish. Current size of it that is being written to tape for this week is 826GB. It's saying "matching" quite a bit, I realize there must be a lot of files. It does change to "copying" but it seems to do the matching stage for a long time.
  18. We do backups with Retrospect and use LT03 tapes, compression with the tapes should be 800GB. I realize there is data that can't be compressed as high or at all. Not talking about SQL, just file backups, tell me if any of these tape sizes that were written to last week don't look right. One from week 3, the last time--only filled up the 3rd tape at 72GB! Obviously, we're on week 3 in the backups. week 2: tape 1 - 616GB tape 2 - 510GB tape 3 - 448GB tape 4 - 730GB tape 5 - 498GB tape 6 - 618GB What size would you consider too small or in determining compression might not be working to it's maximum? For SQL backups, they seem to use about 400GB each week. I don't know SQL very well, we back it up with a program called Redgate SQL Backup and then write the data to the tapes via Retrospect. Thanks, Nick
  19. Hello, At my work, we run Retrospect SMB for Windows, 7.5.x. We added a "client" that uses Red Hat Linux and is installed on 5 servers for them I believe. I have jobs written to tape once a week. The jobs always successfully write to tape but I always notice errors relating to different modify/date time. Is their a way to get rid of this or is it a matter of those files being modified while the job is running? Some of the examples of the error I copied and pasted below. File "/opt/local/logs/iostat_logs/bsgsql02.noc.iscgnet.com.iostat.080702": different modify date/time (set: 7/2/2008 6:37:14 PM, vol: 7/2/2008 6:37:44 PM) File "/opt/local/logs/mpstat/bsgsql02.noc.iscgnet.com.mpstat.data.080702": different modify date/time (set: 7/2/2008 6:37:19 PM, vol: 7/2/2008 6:37:49 PM) File "/opt/local/logs/vmstat_logs/bsgsql02.noc.iscgnet.com.vmstat.data.080702": different modify date/time (set: 7/2/2008 6:37:21 PM, vol: 7/2/2008 6:37:51 PM) File "/opt/local/mysql/data/ib_logfile0": different modify date/time (set: 7/2/2008 6:37:26 PM, vol: 7/2/2008 6:37:55 PM) File "/opt/local/mysql/data/ib_logfile1": different modify date/time (set: 7/2/2008 6:37:16 PM, vol: 7/2/2008 6:37:52 PM) File "/opt/local/mysql/data/ibdata1": different modify date/time (set: 7/2/2008 6:37:26 PM, vol: 7/2/2008 6:37:55 PM) File "/opt/local/mysql/data/master.info": different modify date/time (set: 7/2/2008 6:37:45 PM, vol: 7/2/2008 6:37:52 PM) File "/opt/local/mysql/data/relay-log.info": different modify date/time (set: 7/2/2008 6:37:45 PM, vol: 7/2/2008 6:37:52 PM) 7/2/2008 6:38:01 PM: 8 execution errors This isn't that big of a deal since all the data is being written to the tape. Thanks, Nick
  20. pentium4forever

    MD5 digest error

    Hello, At my company we do backups to tape, we have a list of clients and servers underneath them which we back up various contents. We have separate jobs that run or are written to tape. One particular job gives the error below and according to the log, 67GB remaining that wasn't able to be written to tape for that job. The error is below. Generated MD5 digest for file "C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0002\comp0000\file0000" does not match stored MD5 digest. There's 2 of the above errors. How can this be fixed. There's also errors which I've seen previously but I recall that data to tape was able to be written to still. It relates to TMemory::createMapFile: Could not create the paging file, error 80. I searched somewhere on dantz a little bit ago and some people said they updated Retrospect. and that stopped. This page file error 80 is only happening for this one specific job. I installed an update to Retrospect this past Monday I believe, as it stands the version information: Retrospect Multiserver version: 7.5.508 Driver Update & Hot fix version: 7.5.13.100 Machine that runs Retrospect base program is OS running Windows Server 2003 I'm more concerned about the digest error. I don't really want to recreate the whole config if it is just one client that is having this error. Thanks, Nick
  21. pentium4forever

    MD5 digest error

    Quote: You can delete the contents of the RtrExec.dir after closing Retrospect. Then try the backup again. Something about those files is corrupted. How much free space do you have on the C drive of that computer? Thanks for the response. Well there's one server that runs Retrospect backups, the rest run the Retrospect client obviously. The big box that runs Retrospect and backs up this one backup client is the only one failing. When you say C drive of that computer, I assume you mean the one where Retrospect is running and writing to tape, etc? That computer's C drive has 32GB of free space right now. The backup client which generated the MD5 digest error has several servers under it, when I say client in this case I mean I guess the company. There's several other backup clients that run fine, it's just this one. I'm cautious on deleting the RtrExec.dir directory, will I lose the config and everything?
×