• Tsm Update Volume
• Tsm Update Stgpool

Hi, Sorry if this has been covered before (I did search but only one thread came up as a result of my criteria and this particular thread didn't help We have two TSM servers which deal with more than one drive. They are both reporting a drive offline but i'm confused by the results given in a DSS command Heres the outputs, does this mean the drives are offline or online? The drives showing as offline (online = no) are not online according to TSM.

TSM will not try to use those drives. As far as it's concerned they are unavailable. How a drive gets into that state can vary.

As soon as TSM uses the drive the state will. 0,0,1,7 Drive State: UNKNOWN. 77 Last Update. A couple of days ago, we had a bad tape in one of our drives. TSM reported the problem and took the drive 'off-line' I removed the tape and brought the drive back 'on.

You can set it that way with an define/update drive command or TSM itself and automatically set it to that state if it senses drive read/write or communications problems. It can be a bit missleading as it doesn't truly mean the drive is online, just whether TSM will try to use it or not. You'll notice if you power off a drive, TSM will still report it to be 'online yes' - at least until you try to use it and it fails to communicate with it. I have also seen improperly configured TSM servers where TSM reports it as online yes and yet when you try to run a command that will use the drive, it'll report insufficient mount points. You'll also see you have enough mount points configured. That can be pretty confusing:).

But thats not what you're describing and it sounds like your environment is already configured properly and running. RE: TSM Drive status (TechnicalUser). Good luck:) If the drive is offline and thats not expected (you may think TSM took it offline automatically), you can query the TSM activity log for specific drive errors.

Usually somewhere in there it'll show why TSM chose to take it offline. Searching for certain error codes or words like 'scsi' or 'offline' often is a good approach if you're not too familiar with TSM error codes. I also find usually if TSM had a problem communicating with a drive or reading/writing to one, you'll find a corresponding error in the OS's error log. For AIX running 'errpt' is a quick and dirty way to look for drive related problems that might've occured. If all else fails you can try to recreate the scenario. Bring it back online (update drive command) and then try doing a DB backup to that drive (might have to take the other drives offline) and see if it behaves. RE: TSM Drive status (TechnicalUser).

Tsm Update Volume

In this case, the drive Device Type is set to UNKNOWN because the drive path was defined using a source name that did not match the name of the Tivoli Storage Manager server. To correct this problem, follow these steps:. Delete the drive and its path using the DELETE PATH and DELETE DRIVE commands. Run the QUERY STATUS command to verify the server name.

For example: tsm: MYSERVER1q status Server Name: MYSERVER1 In this case, the name of the server is MYSERVER1. Run the DEFINE DRIVE command to define the drive to the library.

Tsm Update Stgpool

Run the DEFINE PATH command and define a path to the drive using the same 'Server Name' in the Source Name parameter. For example: define path MYSERVER1 DRIVE1 srctype=server destt=drive library=LIB1 device=xxx. Run the QUERY DRIVE command to verify the device type of the drive. For example: tsm: MYSERVER1q drive f=d Library Name: LIB1 Drive Name: DRIVE1 Device Type: LTO.