mfeider Posted July 9, 2003 Report Share Posted July 9, 2003 I've got a daily backup script that takes care of all the servers in my office, including our Exchange 2000 server. Last night when it ran it came back with an error message stating that Retrospect couldn't back up drive M on that server because "volume structure corrupt". Anyone familiar with Exchange knows that backing up the M drive is a Bad Thing (we use the Exchange Backup Agent for backing up this data), and the selector for that backup script shows drive M in the exclusion range. Does anyone know why this script would ignore an exclusion like this, and hopefully how to make it not ignore it anymore? We've seen some odd behavior on our Exchange server lately, and I'm wondering if this might be the cause of it. Link to comment Share on other sites More sharing options...
Mayoff Posted July 9, 2003 Report Share Posted July 9, 2003 If the M drive is in your backup script, you should remove it. You should not backup the M drive. From page 274 of the User's Guide. WARNING: Backing up the Exchange M: drive will not back up your Exchange Server and its data. Restoring to the Exchange M: drive will not restore your Exchange Server and its data. In Retrospect, the Exchange M: drive appears under the computer container (My Computer or a client computer), but Retrospect does not include the Exchange M: drive when you use its parent container in an operation. For example, selecting a client container as a backup source causes its C: drive hard disk to be backed up, but not its M: virtual drive. Retrospect ignores the Exchange M: drive because it contains no data you can back up and restore. Instead use the Exchange Server and Exchange Mailboxes containers as instructed under “Backing Up” on page 275 and “Restoring” on page 277. Link to comment Share on other sites More sharing options...
mfeider Posted July 9, 2003 Author Report Share Posted July 9, 2003 That's my problem. It's only in the script to be excluded, not backed up, and is being attempted to be backed up anyway. The script is written to back up everything except certain excluded drives and directories, including the M drive and certain other "untouchables". What would cause it to ignore those exclusions? Link to comment Share on other sites More sharing options...
Mayoff Posted July 9, 2003 Report Share Posted July 9, 2003 Rather then use a selector to exclude the disk, it may be better to add only desired volumes to the script. Basically you would not use a "container" but would select individual disks or databases to be backed up. Link to comment Share on other sites More sharing options...
mfeider Posted July 9, 2003 Author Report Share Posted July 9, 2003 I might try that. This is one of those things that one day suddenly became my responsibility, so I'm not sure why things were done the way they are. I'm still concerned that an exclusion could be overlooked like this. If it can miss an exclusion how do I know it will follow a new set of rules and only backup those drives that I specifically tell it to? At this point it's the unexplained behavior that worries me more than anything else. Link to comment Share on other sites More sharing options...
Mayoff Posted July 9, 2003 Report Share Posted July 9, 2003 A selector still looks for the disk and will still try to scan the disk. A selector is not designed to totally bypass a disk. The selector has to check the disk, because you may want to backup 1 file from it, copy the registry or NTFS permissions If you want to exclude a disk, then it should not be included as a source. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.