Hi Tom, I'm not familiar with Diskextender Is there a difference in the names of the filespaces that are being backed up in TSM ?
A q filespace "nodename" on the TSM server. If the "bad" backups are listed as a different filespace you can just delete the filespace. Do the stubs have a different extension ? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Melton, Tom Sent: Monday, July 19, 2010 8:50 AM To: ADSM-L@VM.MARIST.EDU Subject: I have an issue I need to find a solution for. We use EMC's Diskxtender on two Windows servers. At some point in the past a Diskxtender option was changed that had detrimental effect on backups..TSM started backing up Diskxtender stub files instead of the actual files. That option has been corrected, but I need to find out what files exist on TSM that are stubs. I cannot simply re-backup all the data as it would all have to be "recalled" from Diskxtender and we are talking about many terabytes of data. I tried doing queries from the client (QUERY BACKUP) and then comparing the dates backed up versus the create/mod date, but that does not help because Robocopy has been used to populate some of the filesystems and the create/mod dates were copied and not updated. Thus my TSM backup date is nowhere near either of those dates as it would normally be. The actual issue is that if one of the stub files is restored from TSM - the length is zero and due to the fact that TSM does not backup/restore the Diskxtender metadata that is stored either in an alternate data stream or some non-standard file metadata - the file is basically garbage. I have tried looking from the server side with SQL queries but cannot find anything that will help in this quest. Anyone have any thoughts? Thanks in advance.. -Tom This e-mail message (including any attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message (including any attachments) is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail message and destroy all copies of the original message (including attachments).