Andy, Thanks for responding. I was just coming to the same conclusion. Talking to the end-user, I discovered that they had not disabled backups after the disk-array failure. They had also initiated a restore and restored 94 GB (out of about 700G) before cancelling it. Then, when they attempted to start another restore, that's when they could not see the D: drive backups any longer.
I've got a PMR open so will continue pursuing this with support. ..Paul At 12:43 PM 3/17/2008, Andrew Raibeck wrote:
It sounds like the disk format type might have changed after the failure, and TSM picked up on this and updated the file space accordingly. I recommend opening a PMR with IBM support. This needs to go right to Level 2, and they should be able to help get the file space type corrected. It would also be useful to figure out when the disk array failure occurred, what happened during subsequent client backups, with the idea being to try to figure out the sequence of events that led up to the file space type change. If there is some error condition being ignored by the client that should have avoided the file space type change, we need to pursue that. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <[email protected]> wrote on 2008-03-17 09:18:16: > Len, > Thanks for responding. No, after talking to the user, I've determined this > further information. The D: drive was on an old Compaq RAID-5 disk array, > which failed. The client system is a W2K3 server, and was running TSM > 5.1.5.15, which I suspect never supported W2K3. However, the user claims > that they were able to see the backups in TSM for D: in the past, even > though they cannot see them now. We tried upgrading the client to 5.4.1.4, > but that did not help. > > Was there a new filesystem type introduced with W2K3? I'm trying to > figure out why this one filesystem shows up as filesystem_type=raw. > > ..Paul > > At 11:31 AM 3/17/2008, Len Boyle wrote: > >Hello Paul > > > >I am taking a few guesses here. > > > >A recovery partition. > >A dual boot machine and it is an alt os partition > > > >len > > > >-----Original Message----- > >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > >Paul Zarnowski > >Sent: Monday, March 17, 2008 11:05 AM > >To: [email protected] > >Subject: [ADSM-L] filespace_type=raw on windows > > > >We have a few windows nodes here that have a filespace_type=raw > >filesystem. I've never noticed this before and am wondering what that > >indicates on a Windows system. Any ideas out there? > > > > > -- > Paul Zarnowski Ph: 607-255-4757 > Manager, Storage Services Fx: 607-255-8521 > 719 Rhodes Hall, Ithaca, NY 14853-3801 Em: [EMAIL PROTECTED]
-- Paul Zarnowski Ph: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801 Em: [EMAIL PROTECTED]
