Windows archive and per-user permissions?

2009-03-13 Thread Jim Zajkowski
It seems that the TSM client for Windows is not honoring a user's rights when handling archives that came from a netware server. The backstory: we have a NetWare server that we'd like to let our users archive their data off of and onto TSM-managed tape. We currently do this just fine for our Lin

Re: slow restore

2009-03-13 Thread Andrew Raibeck
Hi Rainer, The problem was introduced by the fix for IC56846 in client versions 5.4.2 and 5.5.1. Thus your interpretation of the flash is correct. The problem affects only those versions of the client that are mentioned in the flash. Best regards, Andy Andy Raibeck IBM Software Group Tivoli Sto

Re: TSM 6.1 - can I do a X server platform database restore?

2009-03-13 Thread Paul Zarnowski
At 02:21 PM 3/12/2009, Richard Rhodes wrote: My point was, which I obvously failed to make,, was that it's a programming issue that is doable, given the will to do it. Oh, I absolutely agree - it's just code, but code that doesn't yet exist. I would like to see TSM support a better process for

TSM server buffer overflow...

2009-03-13 Thread Allen S. Rout
There's an overflow being reported for versions under 5.4.4.1... http://www-01.ibm.com/support/docview.wss?uid=swg21377388 - Allen S. Rout

Re: Cross restore between diff. tsm server clients

2009-03-13 Thread Baker, Jane
>From node y, point the dsm.sys to CROTSM01 and change the port... and from dsmadmc use 'dsmadmc -virtualn=nodex' This will mean you're connected through to server CROTSM01 and it thinks you are node x. It will therefore allow you to restore node x data to node y, via CROTSM01. Is that what

Re: Cross restore between diff. tsm server clients

2009-03-13 Thread ashish sharma
Hello, How will that help?Let me explain my scenario in more detail: There are two TSM servers CROTSM01 and CROTSM03. Node x is client of CROTSM01 and Node y is client of CROTSNM03.Now i have to restore data of x at y.Now please suggest. On Fri, Mar 13, 2009 at 8:33 PM, Huebschman, George J. < g

Re: Cross restore between diff. tsm server clients

2009-03-13 Thread Huebschman, George J.
You can create a second server definition in your dsm.sys file; Define ServerName1 and ServerName2 Use your dsm.opt file to select which servername is in use. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of ashish sharma Sent: Friday, March 13,

Re: Cross restore between diff. tsm server clients

2009-03-13 Thread ashish sharma
Hello, This doesnt seems to me a gud approach as in this case everytime need arises , i will have to edit dsm.sys file.Also there will not be any information about data of this node on new server. On Fri, Mar 13, 2009 at 8:24 PM, Baker, Jane wrote: > > If it's at client file level, change the d

Re: Cross restore between diff. tsm server clients

2009-03-13 Thread Baker, Jane
If it's at client file level, change the dsm.sys to point to the other TSM server and connect via baclient using 'dsmc -virtualn=nodename you are pretending to be'... This will then connect to TSM server y as the client you're pretending to be. HTH. -Original Message- From: ADSM: Dis

Cross restore between diff. tsm server clients

2009-03-13 Thread ashish sharma
Hello, Can anybody please tell me how to do if i have to do restore data from client of one tsm server,suppose x, to client of other tsm server ,suppose y.I know if both clients belongs to same tsm server i can do it using proxynode agent but i dont know how to do this if tsm servers are different

Re: slow restore

2009-03-13 Thread Rainer Wolf
thanks - one question I have on that flash: We have several win2000 Clients stil running with 5.3.6.4 and some WinNT Systems running possibly 5.1.8.2. Reading this flash I interpret those clients not affected by that problem -- aren't they ? If not -- those win2000 and NT Klients are affected but

Re: slow restore

2009-03-13 Thread Andrew Raibeck
> okay - you could change the COMPRESSALWAYS to 'NO', the default is at 'YES' > Otherwise already compressed files normally grow with the tsm compression > and so 'COMPRESSALWAYS NO' can disable compression for those files. Using EXCLUDE.COMPRESSION is better performance-wise for known file specif

Re: slow restore

2009-03-13 Thread Rainer Wolf
okay - you could change the COMPRESSALWAYS to 'NO', the default is at 'YES' Otherwise already compressed files normally grow with the tsm compression and so 'COMPRESSALWAYS NO' can disable compression for those files. regards Rainer Richard Rhodes schrieb: Thanks . . . Grrr . . . I fig

Re: slow restore

2009-03-13 Thread Dwight Cook
OH... Yea, toss in an Exclude.compress /.../*.Z (and remember to bounce the scheduler) -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Rhodes Sent: Friday, March 13, 2009 7:50 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] slow resto

Re: slow restore

2009-03-13 Thread Richard Rhodes
Thanks . . . Grrr . . . I figured out what is happening. The files that are backed up are unix compressed (foo.Z). The dsm.sys file is set with "compression yes". Of course the cpu is spinning, it's uncompressing the file which is already compressed Rick Rainer Wolf

Re: slow restore

2009-03-13 Thread Dwight Cook
How many inactive versions exist??? (what are your retention characteristics and how frequently do the files change) Also, what is the total number of files stored for that file system??? If you have 7 million files in that file system, that can have ugly results... Also, do you have any looping li

Re: slow restore

2009-03-13 Thread Rainer Wolf
Hi, you may try instead dsmc restore "/oracle/backup/fedwp1/bkup.hpdw1p.200903081920.fedwp1.hot/?*" /oracle/backup/paul/ -inactive -subdir=yes -replace=no This would deactivate the nqr -feature and we use it often when restoreing quite small number of files out of bigger file-spaces. regards R

slow restore

2009-03-13 Thread Richard Rhodes
We are performing a restore that is running real slow. client: hpux 11.11, tsm v5.5.0 tsm server: v5.4.1 The restore operation is about 1000 files totaling about 600gb. The tsm server is sitting with the session on SendW.When dsmc is first started it runs the restore at about 10-15mb/s. Af