Search results for query: *

You can also open it, take all the tapes out, then run audit libvol XXXX checklabel=barcode. It shouldn't taken more than 5min.

What is the Reclaim Threshold set to in the stg pool: tsm: DPSTSM2>q stg Collocatetape f=d Storage Pool Name: COLLOCATETAPE Storage Pool Type: Primary Device Class Name: LTO2 Estimated Capacity: 3,124,148 G Space Trigger...

also try "q vol access=unav" if you want to change the status after that "upd vol XXXXXX access=readw/reado

Play around with the Max utilization parameter, it might be one word.

Not sure how much this will help you, but you can monitor the system through a command window dsmadmc -id=id -pass=pass -mountmode This will show all the tape mounts, request, and if any drives go offline. It will not produce an alarm, but you can glance at it every so often.

You're using Linux like I was thinking about AD. It's central place for everyone to store file and yet is still segregated. Have you thought about granting the new user proxy over the old user?

I don't know how your organization is setup so this solution may not work. What you need is Active Directory, as much as I hate AD, or a network file share. Then when a user quits you can move the data, reassign the permissions, let the new user archive the data, and then delete the “old”...

Did one of the nodes fail the pre-check? Sometimes SQL server will detect that a node needs to be rebooted or something else. I've only tried to install it in a cluster when I saw that message. If this is a standalone install be sure you aren't checking the cluster install option.

THROUGH PUT FOR SESSIONS select session_id as "Session", client_name as "Client", state as "State", current_timestamp-start_time as "Elapsed Time", (cast(bytes_sent as decimal(18,0)) / cast((current_timestamp-start_time)seconds as decimal(18,0))) as "Bytes sent/second", (cast(bytes_received as...

I had contacted IBM over this same issue this is the response: Hello, you will need a combination of commands. The first part is to identify the "object id" of the file you want to restore. You can obtain this...

Try adding a drive letter q backup -su=yes \\epodbms\data\0001\d$\w*\* Where d corresponds to what ever drive the data resides on.

That's huge, you should start a second server instance after about 110 GB database, and documentation actually says 40 GB. I could see 8 hours.

The library doesn't have a front panel that allows for eject operations? What does TSM think is in the vault slots occupied by the DR media? I'd run an audit after I got the tapes out.

No, but are you aware off all the ramifications of that?

I added an option to my dsm.opt file that appears to make the GIU as fast as the command line. TESTFLAG DISABLENQR I'm not sure what this flag does. Does anyone have an explanation?

Yeah, I'm practicing restoring a server. So I've got a base install of W2K3 and I'm laying down the rest of the C:, which is about 20,000 objects and 2gigs. The server and client are at 5.3.2. Opt file: NODENAME TAP01 PASSWORDACCESS GENERATE TCPSERVERADDRESS 10.7.3.166 MANAGEDSERVICES...

I can get the expected speed. It will back-up between 5,000 and 6,000 kb/sec. On the restore with the command line I got a restore rate of 5,200 kb/sec. When I used the GUI I got a restore speed of 72 kb/sec.

No, but as mentioned this was comming from a disk pool. Also it's only with the GUI, I get great speed through the command line restore.

What is it that a node can backup at 6,000 kb/sec and only restore at 80 kb/sec. It's not tape reads either, I did this with a node that backs-up to a storage pool before migration occurred. Server and Client version 5.3.2

Does anyone have any ideas: DSMERROR.LOG: 10/24/2005 19:10:17 Mutex lock failed: 6. 10/24/2005 19:10:17 Acquire Mutex failed: invalid mutex. Last Portion of DSMSCHED.LOG: 10/24/2005 19:10:15 Directory--> 0 \\dpsms01\c$\WINDOWS\Temp\hsperfdata_SYSTEM [Sent] 10/24/2005...