Jump to content

BillIrwin

Members
  • Content count

    74
  • Joined

  • Last visited

Community Reputation

0 Neutral

About BillIrwin

  • Rank
    Frequent Poster
  1. The disk check comes up clean, as does the surface scan and bad block check. I'm going to test it in another enclosure. Thanks for the quick response.
  2. For several weeks now, every time Backup Set 2 is rotated into service the log gets over 100 entries for error -1129 MD5 digest mismatch. When set 1 or 3 are used this doesn't happen. Each set is an external USB disk drive that is connected to the server using the same USB and power cables. Only one disk is connected at a time and each gets drive F: assigned. Last night I reformatted disk 2 with NTFS, removed Backup Set 2 and created a new set 2 using disk 2. The catalogue was replaced for the set. During the full backup of the Exchange server First Storage Group the verification phase had 128 of these MD5 errors. Does this indicate that disk 2 is faulty, since it is the only thing changing from one backup set to another? If so, is it more likely to be the USB disk enclosure, or the drive itself? The server is 2003 R2 and Retrospect 7.6.111.
  3. I'm running 7.0.326 on a W2K Domain Controller and I'm getting every day. Were you getting this before you upgraded? If so, did it go away after? I'm trying to get the money approved for an upgrade because I'm not sure that System State restore would work using this vintage of Retrospect.
  4. I suspected as much, but I needed some official endorsement of my stand on this, as another tech is wanting it to be done to ensure we can recover in the event of another server failure where I was not able to recover when the Active Directory became corrupt. Upgrading to the latest version and leaving the AD logs in the default location is the best thing to do, I believe. Thanks Robin.
  5. I'm wondering is it's possible to test the Disaster Recovery routine to a test computer, rather than the server that it was made on. The test computer would not have the exact same hardware configuration. Is this possible to test without taking a production server out of service? The server is a Primary Domain Controller (and the only server) on W2K3 R2.
  6. Check the date that the excluded folder was backed up. You say you did a Normal backup, so I'm wondering if the folder was backed up prior to the time you excluded it in the Selector. Make a new test Backup Set and see if it gets included. Or do a Recycle on an existing backup set.
  7. I'm getting an error about FSRM in the C: Volume backup: Is this part of the System State in Windows 2003 R2 for a Primary Domain Controller? It doesn't say which file or directory it's looking for, which couldn't be found. I'm using 7.0.249, running on the PDC.
  8. After trying a couple of times to restore the System State only I did a C: restore and got the same problem of AD not starting due to corruption. I went back to the first backup after promoting the server to a PDC, but the results were the same. The tech support I spoke to said that even the current version (mine is 7.0) hasn't been tested to restore when the AD logs are not in the default location. So in this life as a PDC the logs have been left at default. Thanks for the help.
  9. I don't know what using a Microsoft API is supposed to mean to me. Are you saying that if Retrospect isn't backing up the system state in a way that can be used to recover, that the fault lies in a Microsoft utility that Retrospect uses? The Properties clearly list NTDS (ntds) in the list, yet when I browse that Snapshot all I see is the folder C:\Windows\NTDS and NTDS\Drop, but no files. At the time this Snapshot was taken the log files were on D: but the database was there. During the same backup the Snapshot of D: shows the D:\System\Windows\ADlogs, and ADlogs\Drop, folders but again, no files. Now that I've rebuilt this server and left the AD logs in their default location, the Snapshot still only shows the NTDS folders, but no files. Why are the database and log files not being archived? How can a Domain Controller be restored without this critical component of the system state? As far as I can see, I'm still at risk of not being able to restore this PDC if its AD becomes unrepairable again.
  10. This is an old thread but there doesn't seem to be an answer. I have just gone through two weeks of pure hell because my Retrospect safety net turned out to have a huge hole in it, which I fell through. The Active Directory became corrupt on the Windows 2003 R2 Standard PDC (which is the only DC) because the log files that were located in the D: partition (since the promotion to DC advised that the logs be on a different partition than the database ... for better recovery) became victim to some file system corruption that occurred. The server would not boot and restoring the System State to a few days prior did nothing to recover from this. These AD logs were not contained in any Snapshot of C:, which supposedly contained the System State, or D:, which was backing up all except cache files. The question yet to be answered by EMC is if the System State in version 7 includes the AD logs when they are not located in the default location of C:\Windows\NTDS. It should, so that they are contained in the C: Snapshot, even though they reside on D:, so that they are archived at the same time as the database that they are supposed to stay in sync with. But even failing that, they should have been included in the D: backup, but weren't. I have been getting this FSRM error since reloading Windows on this server, which is also the Retrospect server. I suspect that it has something to do with the System State backup. The scary part is that now that basic functionality has been restored, which the AD logs left in the default location, a browse of the C: Snapshot shows the NTDS and NTDS\Drop folders, but no log files and no AD database. So I am still vulnerable to another unrecoverable system failure. My Retrospect safety net still has the huge hole in it! Is this a bug that was fixed in version 7.5?
  11. BillIrwin

    Report for users prior to Archive job

    Hi nate: I'm not trying to get a report of files that would be archived, although that would be convenient. I want a report of what was backed up. I just want to be able to generate a list of files without having to manually expand every folder and adjust column widths so that paths don't get truncated. Is there a way to do this? Have you had any reports of Retrospect not being able to print to an Acrobat driver? Having the same thing happen (complete system freeze) on two different computers tells me that there's an issue with these two software products. Bill
  12. I would like to start running Archive jobs to move old large files into an archive, rather than waiting for users to clean up their areas. I'd like to run a job first that uses the same selector, but doesn't delete the files. Then I'd like to be able to send to each user (hopefully by e-mail) a list of their files that have been selected for archiving in the near future. This will give the users a chance to review their old large files and delete the ones they don't need and resave (to update the modify date) the ones they want to keep available. It would be nice to be able to select by access date so that files that are used regularly, but not modified, are not deemed old. The only report I've been able to find is from the session browser, but it doesn't expand all the folders so that the file names are visible. I can't find a way to do this other than manually expanding each folder. Also, the report mimicks the column widths that are in the browser, which causes truncation and makes some file names unavailable. Is there not some way of generating a report of all the files that are contained in a session without having to produce a custom version for each user? I tried to select an Acrobat printer so that the report would be made a PDF and e-mailed, but on two different computers this caused a complete freeze that required a power-cycle to restart the servers. It seems that Retrospect 7.0.326 does not like an Acrobat print driver. I can live with paper reports if there's no other way to do it, but I'd sure like to find an easier way to display all the file names. Selecting a parent folder in the browser and a right click to select a print option that would expand all subfolders and wrap long paths so that no data is truncated, would be very convenient ... but likely not currently available. Has anyone found a good way to do this? Bill
  13. BillIrwin

    Restoring an Exchange Public Folder

    Thanks Nate. Does this mean that I have to be informed whenever a Public Folder is added or removed so I can add or remove it from the Volume list? Is there no way to make this self-maintaining?
  14. The Restore operation states that there are no mailbox Snapshots in the Backup Set, yet when I look at a Content Report I can see an All Public Folders item in the list, along with all the mailboxes. In Backup Set Properties > Snapshot I don't see anything about Mailboxes or Public Folders, just the Directory Service and Information Store. However, in the Sessions tab I see several Public Folders objects. In the backup script the selector has "Exchange Mailboxes" and "Exchange Server". The Exchange Server Volume contains Directory Service and Information Store. The Mailboxes Volume contains all the mailboxes and an "All Public Folders" object. Is it possible that my problem is that I haven't added any Public Folders subvolumes to the All Public Folders Volume, the way I added mailboxes to the Exchange Mailboxes Volume? I need to restore one Public Folder completely and, although the data has been archived, I can't restore it. Bill
  15. Bex: No System Restore (it's 2003 server) or swap files. Two USB drives of 200 GB each. Each partitioned into two, with first disk holding Disk 1 and Disk 3 partitoions, and 2nd disk with Disk 2 and Disk 4 partitions. The idea being that one disk gets taken offsite each week. I know ... without a 3rd disk we have both of them onsite on switch day which, given Murphey's Law (what number is it?), will be the day the fire hits or the bomb goes off. Bill
×