Backup
Hi, Can any one suggest best way to setup backup for 20 clients/ nodes having 75GB Data each (i,e Total 1.5TB approx per Day) to Diskpool. Backup to be schedule every 15 mins. from each clients. Later on at the end of the day 1.5TB will get migrated to 3584 Library. Regards Pranav Parikh Branch Manager - Customer Service Ontrack Solutions Pvt. Ltd. Baroda TeleFax: 91-265-2324730/2324731 Visit Us: www.ontrackin.com
Re: - load balance issue
On Mar 15, 2006, at 4:24 PM, Vats.Ashok wrote: We have about 270 windows clients running daily backup @ 18:00 it chokes our server and we miss backup widow. My question is what is better to do - create new schedules and split the 270 clients into small groups - Or just leave one schedule and increase the duration window Any help would be appreciate . TSM server 5.3.0. on aix p5 You don't mention doing schedule randomization, so that's a good place to start. As the TSM Performance Tuning Guide says: "TSM throughput can degrade if all client backups are started simultaneously. It is best to avoid concurrent backups, and it would be better to spread out the number of TSM client over a period of time by using the randomizing feature of scheduling." The "Top 10 Tips for Improving TSM Performance" TSM document likewise recommends randomizing schedules. Having a large number of Backup clients start at one time, all of them suddenly going after their full list of Active files, is horrendous for the server. Grouping, as you suggest, is another good approach, but also with reasonable randomization. As Moe frequently proclaimed, "Spread out." Richard Sims
Re: New TSM Server, DB and STG POOL question
Hi Richard How about this? Backup your disk stgpool to a separate, distinct copypool (just for ease of restore you could use your regular copypool) When you get to the new system, mark your old volumes as destroyed, define your new disk volumes and add them to the stgpool, then run a RESTORE STGPOOL to get your data back. Regards Steve AIX and Newly Certified TSM Administrator > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf Of Richard Rhodes > Sent: Thursday, 16 March 2006 5:17 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] New TSM Server, DB and STG POOL question > > > We will be doing this later this year. > > We have a complicating problem - several disk pools using > migration delay. We do this for several applications that use > TSM to archive data (deleting it from within the > application). We hold this data in a disk pool for fast > restores, migrating it to tape after about a year. We > accomplish this by using a 1 yr migration delay to make the > disk pool into a queue fifo queue. > > Any thoughts on how to migrate this kind of disk pool to a > new system? If we follow the cook book, we delete the > pool but this also deletes the queued data and I know of > no way to repopulate the new disk pool that will retain with > the most recent data sent to TSM from these applications. > > I'm thinking of something like this . . . > > ( . . . . they are on raw volumes right now . . . ) > > 1) migrate these disk pools to disk pool that is on a filesystem. > 2) just copy the files to the new server > > > > Thanks > > Rick > > > > > anton walde > <[EMAIL PROTECTED] > DE> > To > Sent by: "ADSM: ADSM-L@VM.MARIST.EDU > Dist Stor > cc > Manager" > <[EMAIL PROTECTED] > Subject > .EDU> Re: New TSM Server, DB > and STG POOL >question > > 03/15/2006 10:44 > AM > > > Please respond to > "ADSM: Dist Stor > Manager" > <[EMAIL PROTECTED] >.EDU> > > > > > > > Hallo. > > > We changed our Hardware a year ago. We asked support to help > us and got a good hand-out with all the steps to make. > > Here is the 'cook book': > > 1. you must have the samt TSM-Version on the old and new > server. 2. migrate all diskpools to tape 3. backup the > TSM-DB on the old server maybe to a file-devclass > ( better for restore ) > 4. stop the old server > 5. save all the config-files from the old server > ( > dsmserv.opt,dsmserv.dsk,devconfig.out,volhist.out,nodelock ) > 6. connect the libraryies to the new server 7. install the > tsm device driver on the new server > all the following steps are on the new server > 8. copy the config-files from step 5. to the new server, over > the existing! > 9. create log-files and db-files with dsmserv format > 10. check the config-files! for example the devconfig.out > for devclass,devices,pathes,etc. > 11. restore the db from step 3. > 12. change dsm.opt: > nomigrrecl > expinterval = > disablescheds yes > 13. start the tsm-server in foreground ( dsmserv ) > 14. disable sessions > 15. delete all paths, drives and libraries > 16. define all paths, libraries and drives again > you must do step 15. and 16. because of possible changed > scsi-id's 17. checkin libv search=yes > status=scratch checklabel=barcode 18. checkin libv > search=yes status=private checklabel=barcode 19. create the > diskpools. If you have another directory-name for > the volumes, you must delete the old ones and define new > ones. 20. If everything runs fine, stop the server ( halt > server ), remove > the options you defined in step 12 from dsm.opt and start the > tsm-server as a service like you did on the old hardware > > THAT'S IT! > > Hope that helps you. > > > > Kind regards > > Robert Fijan > > > -- > Bis zu 70% Ihrer Onlinekosten sparen: GMX SmartSurfer! > Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer > > > > - > The information contained in this message is intended only > for the personal and confidential use of the recipient(s) > named above. If the reader of this message is not the > intended recipient or an agent responsible for delivering it > to the intended recipient, you are hereby notified that you > have received this document in error and that any review, > dissemination, distribution, or copying of this message is > strictly prohibited. If you have received this communication > in error, please notify us immediately, and delete the > original message. > > >
Re: Move data from a copy storage pool to another copy storage pool
Or you could simply run the command backup stg primarypool newcopypool and then delete the old copy pool after the new copy completes. Unless you need the 3590's back immediately, or there's a downside to this that I'm not aware of... _ Kathleen Hallahan Freddie Mac "Meuleman, Ruud" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 03/15/2006 11:00 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Move data from a copy storage pool to another copy storage pool Hi all, To move data from a primary storage pool to another primary storage pool, you can use the command 'move nodedata'. But how can you move data from a copy storage pool to another copy storage pool? I have to move data from 3590 tapes to 3592 tapes. I know I can delete volumes from the copy storage pool and make a backup of the primary storage pool again. But I prefer a saver way. With regards, Ruud Meuleman
Re: New TSM Server, DB and STG POOL question
>> On Wed, 15 Mar 2006 14:16:43 -0500, Richard Rhodes <[EMAIL PROTECTED]> said: > We have a complicating problem - several disk pools using migration delay. > We do this > for several applications that use TSM to archive data (deleting it from > within the application). We > hold this data in a disk pool for fast restores, migrating it to tape after > about a year. > We accomplish this by using a 1 yr migration delay to make the disk pool > into a queue fifo queue. > Any thoughts on how to migrate this kind of disk pool to a new system? If > we follow the cook book, > we delete the pool but this also deletes the queued data and I know of > no way to repopulate > the new disk pool that will retain with the most recent data sent to TSM > from these applications. > I'm thinking of something like this . . . > ( . . . . they are on raw volumes right now . . . ) > 1) migrate these disk pools to disk pool that is on a filesystem. > 2) just copy the files to the new server Suggestion: Define a new copy pool. copy -only- the disk pool to it. That way you take care of the years' backlog of data at your leisure. On the occasion of your migration: + Disable sessions + backup the stgpool again, to catch any new data since last regular backup. + Migrate as previously planned, blowing away the disk stgpool. + Restore the disk stgpool in the new location. If you make the copystgpool on FILE devclasses, you can even serve requests for the data while the recovery is happening, with not much user-visible delay. - Allen S. Rout
Re: - load balance issue
We have about 270 windows clients running daily backup @ 18:00 it chokes our server and we miss backup widow. My question is what is better to do - create new schedules and split the 270 clients into small groups - Or just leave one schedule and increase the duration window Any help would be appreciate . TSM server 5.3.0. on aix p5
Laptop schedules
I am trying to use the QuickFacts/Wiki information for setting up a backup schedule that will work for laptops. (See http://www.tsmwiki.com/tsmwiki/BackupLaptopComputers? ). It says to set up a schedule with a 24 hour start window, then have the client use polling and assumes the default 20 minute retryperiod. Will this still work within the client RETRYPERIOD if RANDOMIZE is set on the server? My question arises from this line of thought: We have RANDOMIZE set to 30. If the server assigns a laptop a start time of 8:00am, and the client connects at 6:00am and disconnects at 7:00am, the schedule will be missed, right? However, if the client connects anytime after it assigned random start time, the backup should run when TSM connects, which with be within RETRYPERIOD of the network connection becoming active. Am I understanding this right? Nancy Reeves Technical Support, Wichita State University [EMAIL PROTECTED] 316-978-3860
tsm restore to different node using TSM GUI
Hi Everybody, I am running an old client level of tsm (5.1.6) for netware 6 sp5 TSM server aix 5.2.0 tivoli storage manger 5.3.0 When using the TSM gui I direct my restore destination to local attached volumes.(basically I am restoring back to the original location). Question: How can I take advantage of the option to restore to "network" (restoring to a different node using the TSM GUI). Presently this option is greyed out in the TSM gui thanks, Gary
Re: LanFreeBackup question
Hi Garcia Absolutely right. It's working Thanks very much Robert -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Helder Garcia Sent: Wednesday, March 15, 2006 9:23 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: LanFreeBackup question In dsm.opt, your lanfreetcpserveraddress must be the address of storage agent, not TSM server. So, what I can see is that the line on dsm.opt might be: lanfreetcpserveraddress 132.74.1.78 On 3/15/06, Robert Ouzen Ouzen <[EMAIL PROTECTED]> wrote: > Hi to all > > > > I tried to run a LanFreeBackup on a Windows client version 5.3.2.0 > > > >On the Tsm server side: > > > > 1. Define server with lla=1502 (EXCHANGE_SA TCPIP > 132.74.1.78 1502 <1 Yes No No) > > 2. Define path (EXCHANGE_SA > SERVER I2000DRV1 DRIVE Yes ) > > > >On the client side: > > > > 1. Add on the dsm.opt: > > enablelanfreeyes > > lanfreecommmethod tcpip > > lanfreetcpserveraddress 132.74.1.48 > >lanfreetcpport 1502 > > > > 2. On the dsmsta.opt: > > COMMmethod TCPIP > > TCPPort 1502 > >DEVCONFIG devconfig_sa.txt > >SANDISCOVERY ON > >SERVERNAME ADSM > > > > 3. I run the wizard to create the devconfig_sa.txt > > Here the syntax: > > SET STANAME EXCHANGE_SA > > SET STAPASSWORD 21f11864ecc5337c2f08045b1b36e31f50 > > SET STAHLADDRESS 132.74.1.78 > > DEFINE SERVER ADSM HLADDRESS=132.74.1.48 LLADDRESS=1500 > SERVERPA=216893d5d8fde6508e93e186f0498c787f > > > > I check the connection on the Tsm server by running: validate lanfree > exchsrv01_dbexchange_sa > > > > Here the output: > > > > tsm: ADSM>run val_sa exchsrv01_db exchange_sa > > ANR0387I Evaluating node EXCHSRV01_DB using storage agent EXCHANGE_SA for > LAN-free data movement. > > > > Node Name Storage Agent Operation Mgmt Class > Destination LAN-Free Explanation capable? > > - - -- - > - > > EXCHSERV01_DB EXCHANGE_SABACKUP MGWEXCHANGEF I-WINDOWS >Yes > > > > ANR1706I Ping for server 'EXCHANGE_SA' was able to establish a connection. > > ANR0388I Node EXCHSRV01_DB using storage agent EXCHANGE_SA has 1 storage pools > > capable of LAN-free data movement . > > ANR1462I RUN: Command script VAL_SA completed successfully. > > > > I ping from the client the Tsm server too without any problem: > > > >Pinging 132.74.1.48 with 32 bytes of data: > > > > Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 > > Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 > > Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 > > Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 > > > > Ping statistics for 132.74.1.48: > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > > Approximate round trip times in milli-seconds: > > Minimum = 0ms, Maximum = 0ms, Average = 0ms > > > > But when to try a backup (lanFreeBackup) got this error: > > > > 03/15/2006 19:42:48 ANS5216E Could not establish a TCP/IP connection with > address '132.74.1.48:1502'. The TCP/IP error is 'Unknown error' (errno = > 10061). > > 03/15/2006 19:42:48 Error -50 opening session > > 03/15/2006 19:42:48 cuSignOnResp: Error -72 reading SignOn response from > server. > > 03/15/2006 19:42:48 sessOpen: Error -72 receiving IdentifyResp verb from > server > > 03/15/2006 19:42:48 ANS9201W LAN-free path failed. > > 03/15/2006 19:42:52 ANS9201W LAN-free path failed. > > > > My Tsm server version is 5.3.2.4 on Aix > > > > Any idea how to resolve this problem > > > > Regards > > > > Ouzen Robert > > Haifa University > -- Helder Garcia
Re: LanFreeBackup question
In dsm.opt, your lanfreetcpserveraddress must be the address of storage agent, not TSM server. So, what I can see is that the line on dsm.opt might be: lanfreetcpserveraddress 132.74.1.78 On 3/15/06, Robert Ouzen Ouzen <[EMAIL PROTECTED]> wrote: > Hi to all > > > > I tried to run a LanFreeBackup on a Windows client version 5.3.2.0 > > > >On the Tsm server side: > > > > 1. Define server with lla=1502 (EXCHANGE_SA TCPIP > 132.74.1.78 1502 <1 Yes No No) > > 2. Define path (EXCHANGE_SA > SERVER I2000DRV1 DRIVE Yes ) > > > >On the client side: > > > > 1. Add on the dsm.opt: > > enablelanfreeyes > > lanfreecommmethod tcpip > > lanfreetcpserveraddress 132.74.1.48 > >lanfreetcpport 1502 > > > > 2. On the dsmsta.opt: > > COMMmethod TCPIP > > TCPPort 1502 > >DEVCONFIG devconfig_sa.txt > >SANDISCOVERY ON > >SERVERNAME ADSM > > > > 3. I run the wizard to create the devconfig_sa.txt > > Here the syntax: > > SET STANAME EXCHANGE_SA > > SET STAPASSWORD 21f11864ecc5337c2f08045b1b36e31f50 > > SET STAHLADDRESS 132.74.1.78 > > DEFINE SERVER ADSM HLADDRESS=132.74.1.48 LLADDRESS=1500 > SERVERPA=216893d5d8fde6508e93e186f0498c787f > > > > I check the connection on the Tsm server by running: validate lanfree > exchsrv01_dbexchange_sa > > > > Here the output: > > > > tsm: ADSM>run val_sa exchsrv01_db exchange_sa > > ANR0387I Evaluating node EXCHSRV01_DB using storage agent EXCHANGE_SA for > LAN-free data movement. > > > > Node Name Storage Agent Operation Mgmt Class > Destination LAN-Free Explanation capable? > > - - -- - > - > > EXCHSERV01_DB EXCHANGE_SABACKUP MGWEXCHANGEF I-WINDOWS >Yes > > > > ANR1706I Ping for server 'EXCHANGE_SA' was able to establish a connection. > > ANR0388I Node EXCHSRV01_DB using storage agent EXCHANGE_SA has 1 storage pools > > capable of LAN-free data movement . > > ANR1462I RUN: Command script VAL_SA completed successfully. > > > > I ping from the client the Tsm server too without any problem: > > > >Pinging 132.74.1.48 with 32 bytes of data: > > > > Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 > > Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 > > Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 > > Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 > > > > Ping statistics for 132.74.1.48: > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > > Approximate round trip times in milli-seconds: > > Minimum = 0ms, Maximum = 0ms, Average = 0ms > > > > But when to try a backup (lanFreeBackup) got this error: > > > > 03/15/2006 19:42:48 ANS5216E Could not establish a TCP/IP connection with > address '132.74.1.48:1502'. The TCP/IP error is 'Unknown error' (errno = > 10061). > > 03/15/2006 19:42:48 Error -50 opening session > > 03/15/2006 19:42:48 cuSignOnResp: Error -72 reading SignOn response from > server. > > 03/15/2006 19:42:48 sessOpen: Error -72 receiving IdentifyResp verb from > server > > 03/15/2006 19:42:48 ANS9201W LAN-free path failed. > > 03/15/2006 19:42:52 ANS9201W LAN-free path failed. > > > > My Tsm server version is 5.3.2.4 on Aix > > > > Any idea how to resolve this problem > > > > Regards > > > > Ouzen Robert > > Haifa University > -- Helder Garcia
Re: New TSM Server, DB and STG POOL question
We will be doing this later this year. We have a complicating problem - several disk pools using migration delay. We do this for several applications that use TSM to archive data (deleting it from within the application). We hold this data in a disk pool for fast restores, migrating it to tape after about a year. We accomplish this by using a 1 yr migration delay to make the disk pool into a queue fifo queue. Any thoughts on how to migrate this kind of disk pool to a new system? If we follow the cook book, we delete the pool but this also deletes the queued data and I know of no way to repopulate the new disk pool that will retain with the most recent data sent to TSM from these applications. I'm thinking of something like this . . . ( . . . . they are on raw volumes right now . . . ) 1) migrate these disk pools to disk pool that is on a filesystem. 2) just copy the files to the new server Thanks Rick anton walde <[EMAIL PROTECTED] DE>To Sent by: "ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Re: New TSM Server, DB and STG POOL question 03/15/2006 10:44 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> Hallo. We changed our Hardware a year ago. We asked support to help us and got a good hand-out with all the steps to make. Here is the 'cook book': 1. you must have the samt TSM-Version on the old and new server. 2. migrate all diskpools to tape 3. backup the TSM-DB on the old server maybe to a file-devclass ( better for restore ) 4. stop the old server 5. save all the config-files from the old server ( dsmserv.opt,dsmserv.dsk,devconfig.out,volhist.out,nodelock ) 6. connect the libraryies to the new server 7. install the tsm device driver on the new server all the following steps are on the new server 8. copy the config-files from step 5. to the new server, over the existing! 9. create log-files and db-files with dsmserv format 10. check the config-files! for example the devconfig.out for devclass,devices,pathes,etc. 11. restore the db from step 3. 12. change dsm.opt: nomigrrecl expinterval = disablescheds yes 13. start the tsm-server in foreground ( dsmserv ) 14. disable sessions 15. delete all paths, drives and libraries 16. define all paths, libraries and drives again you must do step 15. and 16. because of possible changed scsi-id's 17. checkin libv search=yes status=scratch checklabel=barcode 18. checkin libv search=yes status=private checklabel=barcode 19. create the diskpools. If you have another directory-name for the volumes, you must delete the old ones and define new ones. 20. If everything runs fine, stop the server ( halt server ), remove the options you defined in step 12 from dsm.opt and start the tsm-server as a service like you did on the old hardware THAT'S IT! Hope that helps you. Kind regards Robert Fijan -- Bis zu 70% Ihrer Onlinekosten sparen: GMX SmartSurfer! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
LanFreeBackup question
Hi to all I tried to run a LanFreeBackup on a Windows client version 5.3.2.0 On the Tsm server side: 1. Define server with lla=1502 (EXCHANGE_SA TCPIP 132.74.1.78 1502 <1 Yes No No) 2. Define path (EXCHANGE_SA SERVER I2000DRV1 DRIVE Yes ) On the client side: 1. Add on the dsm.opt: enablelanfreeyes lanfreecommmethod tcpip lanfreetcpserveraddress 132.74.1.48 lanfreetcpport 1502 2. On the dsmsta.opt: COMMmethod TCPIP TCPPort 1502 DEVCONFIG devconfig_sa.txt SANDISCOVERY ON SERVERNAME ADSM 3. I run the wizard to create the devconfig_sa.txt Here the syntax: SET STANAME EXCHANGE_SA SET STAPASSWORD 21f11864ecc5337c2f08045b1b36e31f50 SET STAHLADDRESS 132.74.1.78 DEFINE SERVER ADSM HLADDRESS=132.74.1.48 LLADDRESS=1500 SERVERPA=216893d5d8fde6508e93e186f0498c787f I check the connection on the Tsm server by running: validate lanfree exchsrv01_dbexchange_sa Here the output: tsm: ADSM>run val_sa exchsrv01_db exchange_sa ANR0387I Evaluating node EXCHSRV01_DB using storage agent EXCHANGE_SA for LAN-free data movement. Node Name Storage Agent Operation Mgmt Class Destination LAN-Free Explanation capable? - - -- - - EXCHSERV01_DB EXCHANGE_SABACKUP MGWEXCHANGEF I-WINDOWS Yes ANR1706I Ping for server 'EXCHANGE_SA' was able to establish a connection. ANR0388I Node EXCHSRV01_DB using storage agent EXCHANGE_SA has 1 storage pools capable of LAN-free data movement . ANR1462I RUN: Command script VAL_SA completed successfully. I ping from the client the Tsm server too without any problem: Pinging 132.74.1.48 with 32 bytes of data: Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 Ping statistics for 132.74.1.48: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms But when to try a backup (lanFreeBackup) got this error: 03/15/2006 19:42:48 ANS5216E Could not establish a TCP/IP connection with address '132.74.1.48:1502'. The TCP/IP error is 'Unknown error' (errno = 10061). 03/15/2006 19:42:48 Error -50 opening session 03/15/2006 19:42:48 cuSignOnResp: Error -72 reading SignOn response from server. 03/15/2006 19:42:48 sessOpen: Error -72 receiving IdentifyResp verb from server 03/15/2006 19:42:48 ANS9201W LAN-free path failed. 03/15/2006 19:42:52 ANS9201W LAN-free path failed. My Tsm server version is 5.3.2.4 on Aix Any idea how to resolve this problem Regards Ouzen Robert Haifa University
Re:
Here is high level what we do on the server side not sure what you need on client side. ***LAN FREE CLIENT DEF. for TSM server* define server ff05storagnt serverpassword=password hladdress=client.xx.xx.com lladdress=1500 q drive f=d * gather current tsm server drive wwn values Drive Name: DRIVE1 WWN: 500507630F03A202 Drive Name: DRIVE2 WWN: 500507630F03A201 Drive Name: DRIVE3 WWN: 500507630F03A203 Drive Name: DRIVE4 WWN: 500507630F03A204 Drive Name: DRIVE5 WWN: 500507630F03A205 Drive Name: DRIVE6 WWN: 500507630F03A206 Drive Name: DRIVE7 WWN: 500507630F03A207 Drive Name: DRIVE8 WWN: 500507630F03A208 1.5 Get tsmlist from client * compare last digit of wwn vs wintel tape drive (mtX numbers) define path ff05storagnt drive1 srctype=server desttype=drive library=3584lib device=mt4.0.1.3 define path ff05storagnt drive2 srctype=server desttype=drive library=3584lib device=mt5.0.1.3 define path ff05storagnt drive3 srctype=server desttype=drive library=3584lib device=mt6.0.1.3 define path ff05storagnt drive4 srctype=server desttype=drive library=3584lib device=mt7.0.1.3 define path ff05storagnt drive5 srctype=server desttype=drive library=3584lib device=mt0.0.1.3 define path ff05storagnt drive6 srctype=server desttype=drive library=3584lib device=mt1.0.1.3 define path ff05storagnt drive7 srctype=server desttype=drive library=3584lib device=mt2.0.1.3 define path ff05storagnt drive8 srctype=server desttype=drive library=3584lib device=mt3.0.1.3 thanks, Ashok -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Robert Ouzen Ouzen Sent: Wednesday, March 15, 2006 10:59 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Hi to all I tried to run a LanFreeBackup on a Windows client version 5.3.2.0 On the Tsm server side: 1. Define server with lla=1502 (EXCHANGE_SA TCPIP 132.74.1.78 1502 <1 Yes No No) 2. Define path (EXCHANGE_SA SERVER I2000DRV1 DRIVE Yes ) On the client side: 1. Add on the dsm.opt: enablelanfreeyes lanfreecommmethod tcpip lanfreetcpserveraddress 132.74.1.48 lanfreetcpport 1502 2. On the dsmsta.opt: COMMmethod TCPIP TCPPort 1502 DEVCONFIG devconfig_sa.txt SANDISCOVERY ON SERVERNAME ADSM 3. I run the wizard to create the devconfig_sa.txt Here the syntax: SET STANAME EXCHANGE_SA SET STAPASSWORD 21f11864ecc5337c2f08045b1b36e31f50 SET STAHLADDRESS 132.74.1.78 DEFINE SERVER ADSM HLADDRESS=132.74.1.48 LLADDRESS=1500 SERVERPA=216893d5d8fde6508e93e186f0498c787f I check the connection on the Tsm server by running: validate lanfree exchsrv01_dbexchange_sa Here the output: tsm: ADSM>run val_sa exchsrv01_db exchange_sa ANR0387I Evaluating node EXCHSRV01_DB using storage agent EXCHANGE_SA for LAN-free data movement. Node Name Storage Agent Operation Mgmt Class Destination LAN-Free Explanation capable? - - -- - - EXCHSERV01_DB EXCHANGE_SABACKUP MGWEXCHANGEF I-WINDOWS Yes ANR1706I Ping for server 'EXCHANGE_SA' was able to establish a connection. ANR0388I Node EXCHSRV01_DB using storage agent EXCHANGE_SA has 1 storage pools capable of LAN-free data movement . ANR1462I RUN: Command script VAL_SA completed successfully. I ping from the client the Tsm server too without any problem: Pinging 132.74.1.48 with 32 bytes of data: Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 Ping statistics for 132.74.1.48: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:
[no subject]
Hi to all I tried to run a LanFreeBackup on a Windows client version 5.3.2.0 On the Tsm server side: 1. Define server with lla=1502 (EXCHANGE_SA TCPIP 132.74.1.78 1502 <1 Yes No No) 2. Define path (EXCHANGE_SA SERVER I2000DRV1 DRIVE Yes ) On the client side: 1. Add on the dsm.opt: enablelanfreeyes lanfreecommmethod tcpip lanfreetcpserveraddress 132.74.1.48 lanfreetcpport 1502 2. On the dsmsta.opt: COMMmethod TCPIP TCPPort 1502 DEVCONFIG devconfig_sa.txt SANDISCOVERY ON SERVERNAME ADSM 3. I run the wizard to create the devconfig_sa.txt Here the syntax: SET STANAME EXCHANGE_SA SET STAPASSWORD 21f11864ecc5337c2f08045b1b36e31f50 SET STAHLADDRESS 132.74.1.78 DEFINE SERVER ADSM HLADDRESS=132.74.1.48 LLADDRESS=1500 SERVERPA=216893d5d8fde6508e93e186f0498c787f I check the connection on the Tsm server by running: validate lanfree exchsrv01_dbexchange_sa Here the output: tsm: ADSM>run val_sa exchsrv01_db exchange_sa ANR0387I Evaluating node EXCHSRV01_DB using storage agent EXCHANGE_SA for LAN-free data movement. Node Name Storage Agent Operation Mgmt Class Destination LAN-Free Explanation capable? - - -- - - EXCHSERV01_DB EXCHANGE_SABACKUP MGWEXCHANGEF I-WINDOWS Yes ANR1706I Ping for server 'EXCHANGE_SA' was able to establish a connection. ANR0388I Node EXCHSRV01_DB using storage agent EXCHANGE_SA has 1 storage pools capable of LAN-free data movement . ANR1462I RUN: Command script VAL_SA completed successfully. I ping from the client the Tsm server too without any problem: Pinging 132.74.1.48 with 32 bytes of data: Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 Reply from 132.74.1.48: bytes=32 time<1ms TTL=255 Ping statistics for 132.74.1.48: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms But when to try a backup (lanFreeBackup) got this error: 03/15/2006 19:42:48 ANS5216E Could not establish a TCP/IP connection with address '132.74.1.48:1502'. The TCP/IP error is 'Unknown error' (errno = 10061). 03/15/2006 19:42:48 Error -50 opening session 03/15/2006 19:42:48 cuSignOnResp: Error -72 reading SignOn response from server. 03/15/2006 19:42:48 sessOpen: Error -72 receiving IdentifyResp verb from server 03/15/2006 19:42:48 ANS9201W LAN-free path failed. 03/15/2006 19:42:52 ANS9201W LAN-free path failed. My Tsm server version is 5.3.2.4 on Aix Any idea how to resolve this problem Regards Ouzen Robert Haifa University
Re: Backups of Intel-based Macs
On Mar 15, 2006, at 1:26 PM, Bob Talda wrote: I was interested, Richard, that you chose to use 5.2.4. Was there a reason why? Or was it just happenstance? (It might be a fallback for us to try as well) Bob - I chose that because we're running a late 5.2 TSM server and I generally try to avoid having a client level exceed server level. Because of the inordinate number of problems with TSM 5.3, we're going to stick with 5.2 until IBM can sort out the many problems and deliver a stable, reliable TSM above 5.2. It was thus my expectation that the latest 5.2 level would be a good test basis candidate for the Rosetta test. I don't have time to test it exhaustively, so can't testify to its endurance, except to say that I had no problems as far as I went. Richard
Re: Backups of Intel-based Macs
Just a little more detail on "initial good, then ran into some problems"... We were working with the local team designated to figure out what Cornell services did, and didn't work, on Intel-Macs. The team was composed of experienced Apple developers and users. - One developer was able to install 5.3.2.0, and then 5.3.2.1 without problems, and run a backup manually using the Backup for Administrators application; he was able to configure and start a Client Acceptor Daemon, but was never able to get a scheduled backup to work - Another developer started with 5.2.3.x, but couldn't get that to install properly (lots of permission issues, etc), so he switched to 5.3.2.1, which installed fine, and permitted manual backups; in his case, when he tried to run the Client Acceptor Daemon, it ate up most of his processor. - A user had problems installing the client that we just traced to a permissions issue (it was a complex environment, managed from a central AD server, but, still)...the jury is out on how this will work Attempts to debug the CAD issues via IBM were met by "we don't support that version of the client on that platform". We are continuing on our own, since we have more of these beasties showing up everyday on campus. I was interested, Richard, that you chose to use 5.2.4. Was there a reason why? Or was it just happenstance? (It might be a fallback for us to try as well) At 09:35 AM 3/15/2006, Paul Zarnowski wrote: Our initial attempts at trying 5.3.2.1 on the Intel Macs were good, but we then ran into some problems. As there is no support from IBM, I am nervous about relying on it. At 08:38 PM 3/14/2006, you wrote: On Mar 14, 2006, at 4:44 PM, Paul Zarnowski wrote: Intel Macs are starting to show up on our campus and we are being asked how to back them up. What are other TSM sites doing to backup these new beasties? TSM doesn't support Intel-based Macs yet. Hi, Paul - Good question... I recently got one of the new iMac's as a media storage and feeder for my family room (connecting it to my A/V receiver via optical audio and S-video). Wonderful machine. Reading your posting, and Aaron's response about depending upon Rosetta, I decided to try installing a TSM client (5.2.4). An awkwardness is that the download file is in .hqx format: PowerPC Macs are shipped with Stuffit Expander to handle that stuff, but the new Macs are Intel, so it appears that Apple feels it inappropriate to ship a non-PowerPC binary. I got SE off the net and installed it, and it worked fine to generate the TSM installer, which I then ran to install the TSM client. And the client itself ran fine, as I tried some basic Archive and Backup operations. Apple's Rosetta is excellent, as was promised. I would suggest having one of your "eager adopters" go ahead and give an existing TSM client level a full workout, with a new nodename. Have them report back on general functionality and speed. Richard Sims long time Mac guy (why settle for mediocrity?) -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Systems Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]
Re: OFFSITE TAPES
Hi Jim, It sounds as if there was a problem somewhere in the process. Were there any errors reported during the restore vol process or did it complete successfully? Were there any problems on the client side? Is the restore just for some files that were accidentally deleted, did the client hard drive fail or was there another issue? (If the client drive failed the problem may be related to the client and not the volume restore). If the volume restore was successful, Tivoli automatically updates the information so that the data on the new volume can be accessed. I guess I'm saying that a little more background info is needed to give you a more specific response unless one of my questions above has helped. Jim Neal -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lepre, James Sent: Wednesday, March 15, 2006 7:11 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] OFFSITE TAPES Hello, I restore the volume, and made the volume readw. However, I am not seeing the data that was on the other tape eligible for a restore. Infact in the client gui, I am not seeing anything to restore, it looks like it has been deleted. Is there something I am missing, like telling Tivoli this is a new tape, or committing it to the database. Thank you Jim -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Sent: Tuesday, March 14, 2006 11:46 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] OFFSITE TAPES The restore vol XX command will mark volume XX as destroyed. Upd vol st=reado/readw for the volume(s) brought back will also be needed. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bob Booth - UIUC Sent: dinsdag 14 maart 2006 17:39 To: ADSM-L@VM.MARIST.EDU Subject: Re: OFFSITE TAPES On Tue, Mar 14, 2006 at 11:35:59AM -0500, Lepre, James wrote: > Hello Everyone, > >I need to bring back some offsite tapes for a restore. How do I > check them into the library, and then force Tivoli to use them. I > have a tape that broke and now I need to bring back the offsite copy, > but I am not sure what how to set this up. Should I bring back every > tape for that node that is offsite, any help is much appreciated. Mark the tape that is broken as 'destroyed' Run a restore volume XX preview=yes This will give you the list of tapes to return (it could be a long list) Check them into your library as 'private' volumes Run the restore volume XX That *should* do it. cheers, bob
Re: MSL6030 TSM write failure
Glad I could help! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kurt Beyers Sent: Tuesday, March 14, 2006 9:25 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] MSL6030 TSM write failure Jim, It looks indeed to be a HW problem with the library (which is brand new, so that cancels option 1 and 2). I was just surprised that the tapes could be labelled as data is wrtten to them then too. But apperantly the HW issues only pop-up when you start sending the backup data, which are larger then a label of course. thanks, Kurt Van: ADSM: Dist Stor Manager namens JN Verzonden: di 3/14/2006 18:53 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: Re: [ADSM-L] MSL6030 TSM write failure Hi Kurt, In my experience, the errors that you are seeing are primarily caused by one of three problems: 1) The tape drive is dirty and needs to be cleaned 2) The tape cartridge is bad and needs to be destroyed 3) The Tape drive has a physical problem that needs to be fixed via replacement or maintenance. I hope one of these solutions works for you. Jim -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kurt Beyers Sent: Tuesday, March 14, 2006 1:01 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] MSL6030 TSM write failure Hello, A quick (?) question. My setup is the following: TSM 5.3.2 server with a MSL6030 SCSI attached library (2 HP-Ultrium 3 drives). The library has been defined in TSM and the labelling of the tapes went fine. However a migrate of the diskpool towards the LTOPool fails with the following messages: ANR0984I Process 42 for MIGRATION started in the BACKGROUND at 08:45:30. ANR2110I MIGRATE STGPOOL started as process 42. ANR1000I Migration process 42 started for storage pool DISKPOOL manually, highMig=90, lowMig=0, duration=No. ANR8337I LTO volume HK3722L3 mounted in drive DRIVE1 (mt1.0.0.5). ANR1340I Scratch volume HK3722L3 is now defined in storage pool LTOPOOL. ANR0513I Process 42 opened output volume HK3722L3. ANR8302E I/O error on drive DRIVE1 (mt1.0.0.5) with volume HK3722L3 (OP=WRITE, Error Number=1117, CC=208, KEY=0B, ASC=47, ASCQ=03, SENSE=70.00.0B.00.00.00.00.10.00.00.00.00.47.03.00.00.00.00.00.00.00.00., Description=Command aborted). Refer to Appendix D in the 'Messages' manual for recommended action. ANR1411W Access mode for volume HK3722L3 now set to "read-only" due to write error. ANR0515I Process 42 closed volume HK3722L3. What am I missing here? The library configuration in TSM is as follows: -The TSM device driver is used and the library is detected by the tsmdlst.exe program as follows: Tivoli Storage Manager -- Device List Utility Licensed Materials - Property of IBM 5697-TSM (C) Copyright IBM Corporation 2000, 2005. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Computer Name: TSM-server OS Version: 5.2 OS Build #: 3790 TSM Device Driver: TSMScsi - Running 2 HBAs were detected. ManufacturerModel Driver VersionFirmware Description QLogic Corporation QLA2340ql2300.sys 9.0.2.11 (w32 IP) 3.03.12 QLogic QLA2340 Fibre Channel Adapter QLogic Corporation QLA2340ql2300.sys 9.0.2.11 (w32 IP) 0.00.00 QLogic QLA2340 Fibre Channel Adapter TSM Name ID LUN Bus Port SSN WWN TSM Type Device Identifier lb0.0.0.50005- - LIBRARY HP MSL6000 Series 0507 mt1.0.0.51005- - LTO HP Ultrium 3-SCSI G24W mt2.0.0.52005- - LTO HP Ultrium 3-SCSI G24W Completed in: 0 days, 0 hours, 0 minutes, 1 seconds. -The library is defined in TSM with: tsm: SRV-SPGR-BACKUP_SERVER1>q library f=d Library Name: MSL6030 Library Type: SCSI WWN: 00900D06254B8000 Serial Number: 2U2527002X AutoLabel: No Reset Drives: No Last Update by (administrator): ADMIN tsm: SRV-SPGR-BACKUP_SERVER1>q drive f=d Library Name: MSL6030 Drive Name: DRIVE1 Device Type: LTO On-Line: Yes Read Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM Write Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2 Element: 480 Drive State: EMPTY Volume Name: Allocated to: WWN: 50060B34589E Serial Number: HU105252G0 Library Name: MSL6030 Drive Name: DRIVE2 Device Type: LTO On-Line: Yes Read Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2,ULTRIUMC,ULTRIUM Write Formats: ULTRIUM3C,ULTRIUM3,ULTRIUM2C,ULTRIUM2 Element: 481 Drive State: EMPTY Volume Name: Allocated to: WWN: 50060B34586E Serial Num
Re: Linux client fails after upgrade to v5.3.2.2
David - The symptoms in IC47993 seem much like it. Richard Sims On Mar 15, 2006, at 11:35 AM, David E Ehresman wrote: I'm running Red Hat Enterprise Linux ES release 3 (Taroon Update 6). I upgraded TSM client to 5.3.2.2. When running dsmc command, I get the following error: [EMAIL PROTECTED] root]# dsmc dsmc: dsmem.cpp:1685: void DsmBlockFree(void*): Assertion `((bn)->bh. magic) == 0x3917' failed. Aborted Any ideas?
Linux client fails after upgrade to v5.3.2.2
I'm running Red Hat Enterprise Linux ES release 3 (Taroon Update 6). I upgraded TSM client to 5.3.2.2. When running dsmc command, I get the following error: [EMAIL PROTECTED] root]# dsmc dsmc: dsmem.cpp:1685: void DsmBlockFree(void*): Assertion `((bn)->bh. magic) == 0x3917' failed. Aborted Any ideas?
Re: Move data from a copy storage pool to another copy storage pool
> I have to move >data from 3590 tapes to 3592 tapes. I know I can delete volumes from the >copy storage pool and make a backup of the primary storage pool again. >But I prefer a saver way. > There is not a safer way. Make sure you have the reusedelay parm set appropriately on your copy storage pool before begining.
Anyone Running TSM BA Client on Windows 2003 R2 X64?
We have a new application coming in-house that will be running on Windows 2003 R2 X64. IBM has not certified this yet. Is anyone running a backup archive client on this? How about Windows 2003 SP1 X64? Thank you. DISCLAIMER: This communication, along with any documents, files or attachments, is intended only for the use of the addressee and may contain legally privileged and confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of any information contained in or attached to this communication is strictly prohibited. If you have received this message in error, please notify the sender immediately and destroy the original communication and its attachments without reading, printing or saving in any manner. This communication does not form any contractual obligation on behalf of the sender or, the sender's employer, or the employer's parent company, affiliates or subsidiaries.
Need help with out-of-control Win 2003 client
Client now running v5.3.2.2, recently upgraded from v5.3.0.0. Server running v5.3.1.2. Client machine is actually a document imaging archive server. It contains 3 local drives (C,D,E) and of course the system state/services. On D, there are 39 NTFS mount points (36 archive, 2 journal, 1 database). A majority of the mount points house millions of small files. An incremental is now having to inspect 80 million+ files, and is rapidly growing, now taking 50+ hours. It is out of hand and getting quite ridiculous. The company that designed the horrible setup (talking about the client machine) is not offering help to its customers (others are sharing in my misery in other words), and I have an open ticket with IBM. I am coming here because I know that there are many, many bright folks that patrol the ADSM list. BTW, the ticket open with Tivoli Support is from when I instituted the journaling service on the client, and it would not start. Please help, as this is becoming a major issue. Suggestions, hints, criticism eventually, all is welcome at this point. :-) God bless you!!! Chip Bell Network Engineer I IBM Tivoli Certified Deployment Professional (ITSM 5.2) Baptist Health System Birmingham, AL - Confidentiality Notice: The information contained in this email message is privileged and confidential information and intended only for the use of the individual or entity named in the address. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you received this information in error, please notify the sender and delete this information from your computer and retain no copies of any of this information.
Move data from a copy storage pool to another copy storage pool
Hi all, To move data from a primary storage pool to another primary storage pool, you can use the command 'move nodedata'. But how can you move data from a copy storage pool to another copy storage pool? I have to move data from 3590 tapes to 3592 tapes. I know I can delete volumes from the copy storage pool and make a backup of the primary storage pool again. But I prefer a saver way. With regards, Ruud Meuleman
Re: Linux GUI and client user id
Richard van Denzel schrieb: To my knowledge the Webclient (java) and the Windowsclient first use the admin account to establish a session. Then when executing a command the node account is used. When you use the command-line then always the node-account is used. I had no problems with the Windows clients. But I just found out that the linux java client works, when I set "passwordaccess generate". Without this option or with "passwordaccess prompt" the connection always fails if there isn't an administrator id. -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470
Re: Tape transport question(s)
The specifications should include the G-force and temperature limits specified by the tape manufacturer. In the context of a DR test you might want more stringent temperature limits to avoid waiting for cold tapes to warm up to room temperature. I have seen computer equipment shipped with special labels designed to change color if the shipment was subject to out of specification conditions. You might want similar labels for your tape shipments. Depending on your concerns about confidentiality, you might want tamper-evident seals for tape containers. If you are subject to specific legal requirements for data protection, the contract should include an explicit committment from the vendor to conform to those requirements. For example, my employer is a hospital, and all contracts that involve entrusting clinical or billing information to vendors include provisions stating that the vendor will comply with HIPPA requirements. The carrier should have a bonding contract that would compensate you for lost or damaged tapes. We use an outside vendor to transport and store offsite tapes. Our auditors have been getting very fussy about having an auditable documentation trail for each change of physical custody of tapes.
Re: New TSM Server, DB and STG POOL question
anton walde schrieb: We changed our Hardware a year ago. We asked support to help us and got a good hand-out with all the steps to make. Here is the 'cook book': I followed the technote that Richard mentioned, and everything worked fine. I think you should delete the old disk pool volumes before doing the database backup. And I never had to checkin the libvolumes again, because I used the volhist file from the old server. -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470
Re: Linux GUI and client user id
No, works as designed. To my knowledge the Webclient (java) and the Windowsclient first use the admin account to establish a session. Then when executing a command the node account is used. When you use the command-line then always the node-account is used. Met vriendelijke groet, With kind regards, Richard van Denzel. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Kastens Sent: woensdag 15 maart 2006 16:49 To: ADSM-L@VM.MARIST.EDU Subject: Linux GUI and client user id Hi, when I register a new node on the TSM server (AIX v5.3.2.3), I do not assign owner authority to an admin. There wasn't any problem with that, until I started the java gui on a linux client (v5.3.2.0). The gui presents a login window with a field for the user id (which is the same as the nodename) and for the password. When I enter the password, I always get the error message "ANS1370E The user ID entered does not have the correct level of authority to access the client machine". No work can be done with the client gui. When I create an admin on the server and assign authority for the client node to it, the client gui works. The command line client works without defining an admin. Is there a fix for that behavior? -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470
Linux GUI and client user id
Hi, when I register a new node on the TSM server (AIX v5.3.2.3), I do not assign owner authority to an admin. There wasn't any problem with that, until I started the java gui on a linux client (v5.3.2.0). The gui presents a login window with a field for the user id (which is the same as the nodename) and for the password. When I enter the password, I always get the error message "ANS1370E The user ID entered does not have the correct level of authority to access the client machine". No work can be done with the client gui. When I create an admin on the server and assign authority for the client node to it, the client gui works. The command line client works without defining an admin. Is there a fix for that behavior? -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470
Re: Manual collocation
Hi, If all the data is on the old tapes and you have non-collocated tape pools, you could do it this way, using a script. move node NODE_A from=GENTAPEPOOL to=GENTAPEPOOL recons=yes wait=yes move node NODE_B from=GENTAPEPOOL to=GENTAPEPOOL recons=yes wait=yes move node NODE_C from=GENTAPEPOOL to=GENTAPEPOOL recons=yes wait=yes etc.. . . . . . . Bill "Lee, Gary D." <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 15/03/2006 15:27 Please respond to "ADSM: Dist Stor Manager" To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: [ADSM-L] Manual collocation Simply do a move data for each volume. If the destination stgpool is collocated, tsm takes care of it already. Doing this very thing righ now. Works great. Gary Lee Senior System Programmer Ball State University -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Mochnaczewski Sent: Wednesday, March 15, 2006 10:22 AM To: ADSM-L@VM.MARIST.EDU Subject: Manual collocation Hi Everybody, We have a bunch of old 3590 tapes that we would like to get rid of and replace by higher capacity tapes. Instead of just moving the data off the old tapes to new, I want to do a manual collocation by consolidating data by server on the old tapes to new. Has anyone done this ? How did you accomplish this ? Rich -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.2.3/281 - Release Date: 3/14/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.2.3/281 - Release Date: 3/14/2006 *** Disclaimer *** This email and any files transmitted with it contains privileged and confidential information and is intended for the addressee only. If you are not the intended recipient you must not disseminate, distribute or copy this email. Please notify the sender at once that you have received it by mistake and then delete it from your system. Any views expressed in this email are those of the sender and not necessarily those of ALSTEC or its associated companies. Whereas ALSTEC takes reasonable precautions to ensure this email is virus free, no responsibility will be accepted by it for any loss or damage whether direct or indirect which results from the contents of this email or its attachments. ALSTEC Group Limited - Registered in England No.3939840 - www.alstec.com Registered office: Cambridge Road, Whetstone, Leicester. LE8 6LH. England. Telephone: +44 (0)116 275 0750
Re: New TSM Server, DB and STG POOL question
Hallo. We changed our Hardware a year ago. We asked support to help us and got a good hand-out with all the steps to make. Here is the 'cook book': 1. you must have the samt TSM-Version on the old and new server. 2. migrate all diskpools to tape 3. backup the TSM-DB on the old server maybe to a file-devclass ( better for restore ) 4. stop the old server 5. save all the config-files from the old server ( dsmserv.opt,dsmserv.dsk,devconfig.out,volhist.out,nodelock ) 6. connect the libraryies to the new server 7. install the tsm device driver on the new server all the following steps are on the new server 8. copy the config-files from step 5. to the new server, over the existing! 9. create log-files and db-files with dsmserv format 10. check the config-files! for example the devconfig.out for devclass,devices,pathes,etc. 11. restore the db from step 3. 12. change dsm.opt: nomigrrecl expinterval = disablescheds yes 13. start the tsm-server in foreground ( dsmserv ) 14. disable sessions 15. delete all paths, drives and libraries 16. define all paths, libraries and drives again you must do step 15. and 16. because of possible changed scsi-id's 17. checkin libv search=yes status=scratch checklabel=barcode 18. checkin libv search=yes status=private checklabel=barcode 19. create the diskpools. If you have another directory-name for the volumes, you must delete the old ones and define new ones. 20. If everything runs fine, stop the server ( halt server ), remove the options you defined in step 12 from dsm.opt and start the tsm-server as a service like you did on the old hardware THAT'S IT! Hope that helps you. Kind regards Robert Fijan -- Bis zu 70% Ihrer Onlinekosten sparen: GMX SmartSurfer! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer
Re: Manual collocation
Simply do a move data for each volume. If the destination stgpool is collocated, tsm takes care of it already. Doing this very thing righ now. Works great. Gary Lee Senior System Programmer Ball State University -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Mochnaczewski Sent: Wednesday, March 15, 2006 10:22 AM To: ADSM-L@VM.MARIST.EDU Subject: Manual collocation Hi Everybody, We have a bunch of old 3590 tapes that we would like to get rid of and replace by higher capacity tapes. Instead of just moving the data off the old tapes to new, I want to do a manual collocation by consolidating data by server on the old tapes to new. Has anyone done this ? How did you accomplish this ? Rich -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.2.3/281 - Release Date: 3/14/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.2.3/281 - Release Date: 3/14/2006
Manual collocation
Hi Everybody, We have a bunch of old 3590 tapes that we would like to get rid of and replace by higher capacity tapes. Instead of just moving the data off the old tapes to new, I want to do a manual collocation by consolidating data by server on the old tapes to new. Has anyone done this ? How did you accomplish this ? Rich
How to empty a copystgpool
Hi *SMers, I have the following scenario with some of my 3590-tapes: -I had a primary storage pool "TAPEPOOL_NC" whose data had been copied onto 2 copystgpools by means of: BA stgp TAPEPOOL_NC COPYPOOL_NC BA stgp TAPEPOOL_NC CP_LTO-B_NC -the primary TAPEPOOL_NC had been completely moved lateron by: MOVE DATA stg=3590_NC -the "COPYPOOL_NC" is now left on tapes I need for other purposes Questions: - What is the best way to get rid of the data on the ca. 30 tapes in the COPYPOOL_NC stgpool ? The other copy in CP_LTO-B_NC still exists. - Or is just DEL VOL DISCARDData=yes the right choice ? -- MfG / Ciao - - - - - - - - - - - - - - - - - - - - - - - - - - - - Peter Dümpert Email: [EMAIL PROTECTED] Rechenzentrum der Technischen Universität Fax : ++49/531/391-5549 D 38092 BraunschweigTel : ++49/531/391-5535
Re: OFFSITE TAPES
Hello, I restore the volume, and made the volume readw. However, I am not seeing the data that was on the other tape eligible for a restore. Infact in the client gui, I am not seeing anything to restore, it looks like it has been deleted. Is there something I am missing, like telling Tivoli this is a new tape, or committing it to the database. Thank you Jim -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Sent: Tuesday, March 14, 2006 11:46 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] OFFSITE TAPES The restore vol XX command will mark volume XX as destroyed. Upd vol st=reado/readw for the volume(s) brought back will also be needed. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bob Booth - UIUC Sent: dinsdag 14 maart 2006 17:39 To: ADSM-L@VM.MARIST.EDU Subject: Re: OFFSITE TAPES On Tue, Mar 14, 2006 at 11:35:59AM -0500, Lepre, James wrote: > Hello Everyone, > >I need to bring back some offsite tapes for a restore. How do I > check them into the library, and then force Tivoli to use them. I > have a tape that broke and now I need to bring back the offsite copy, > but I am not sure what how to set this up. Should I bring back every > tape for that node that is offsite, any help is much appreciated. Mark the tape that is broken as 'destroyed' Run a restore volume XX preview=yes This will give you the list of tapes to return (it could be a long list) Check them into your library as 'private' volumes Run the restore volume XX That *should* do it. cheers, bob
Scheduler and montoring
Hi All, We use MOM to monitor the health of the TSM 5.2 schedulers but if MOM is reporting correctly we see Schedulers falling over in the middle of the night, and after checking the Event Log they are all started again automatically no more than 2 minutes later. We don't have any Recovery actions set up so I don't know how, if they are falling over, they are started again. Can anyone else see their own footprints down this path? Many Thanks, Matthew TSM Consultant ADMIN ITI Rabobank International 1 Queenhithe, London EC4V 3RL 0044 207 809 3665 _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _
Re: New TSM Server, DB and STG POOL question
Thanks Dirk Well I set caching to off on the disk pool on the original server and then migrated down to zero before doing the DB backup. So I'm thinking that if I now just format the vols I need on the new server, it should be fine. As it is this is just a test and I'll do the proper upgrade at the weekend, so fingers crossed. Many thanks Farren |-+---| | Dirk Kastens | | | <[EMAIL PROTECTED]| | | CK.DE>| To| | Sent by: "ADSM: Dist Stor | ADSM-L@VM.MARIST.EDU | | Manager" | cc| | | | | |Subject| | 15/03/2006 14:17 | Re: [ADSM-L] New TSM | | | Server, DB and STG| | Please respond to | POOL question | | "ADSM: Dist Stor| | | Manager"| | | | | | | | | | | | | | |-+---| I wrote: > I first deleted all disk storage pools on the old server, CAUTION!!! Of yourse, I only deleted the disk pool volumes, NOT the storage pools themselves. -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470 ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Backups of Intel-based Macs
Our initial attempts at trying 5.3.2.1 on the Intel Macs were good, but we then ran into some problems. As there is no support from IBM, I am nervous about relying on it. At 08:38 PM 3/14/2006, you wrote: On Mar 14, 2006, at 4:44 PM, Paul Zarnowski wrote: Intel Macs are starting to show up on our campus and we are being asked how to back them up. What are other TSM sites doing to backup these new beasties? TSM doesn't support Intel-based Macs yet. Hi, Paul - Good question... I recently got one of the new iMac's as a media storage and feeder for my family room (connecting it to my A/V receiver via optical audio and S-video). Wonderful machine. Reading your posting, and Aaron's response about depending upon Rosetta, I decided to try installing a TSM client (5.2.4). An awkwardness is that the download file is in .hqx format: PowerPC Macs are shipped with Stuffit Expander to handle that stuff, but the new Macs are Intel, so it appears that Apple feels it inappropriate to ship a non-PowerPC binary. I got SE off the net and installed it, and it worked fine to generate the TSM installer, which I then ran to install the TSM client. And the client itself ran fine, as I tried some basic Archive and Backup operations. Apple's Rosetta is excellent, as was promised. I would suggest having one of your "eager adopters" go ahead and give an existing TSM client level a full workout, with a new nodename. Have them report back on general functionality and speed. Richard Sims long time Mac guy (why settle for mediocrity?) -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Systems Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]
Tape transport question(s)
We're starting to look at common carrier transport to get our tapes to our D/R hotsite for testing. Is there anything in perticular we should spec, or things to look out for? We've been hand-carrying the tapes on the corporate jet, but this is starting to loose cost-effectiveness. TIA Tom Kauffman NIBCO, Inc CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
Re: New TSM Server, DB and STG POOL question
On Mar 15, 2006, at 9:12 AM, Dirk Kastens wrote: ... There's a technote on this topic somewhere on the Tivoli support side. 1114874 is at least one on the site. Richard Sims
Re: New TSM Server, DB and STG POOL question
What I do during D/R -- which amounts to your situation, restoring on a 'new' platform -- is create the primary DB volumes and log volume, restore the database, and then create mirror volumes for the database and log. Once the mirrors are in place, delete the old volumes from the storage pools And then define new volumes with the 'formatsize' option, letting TSM format them as part of the definition. What you are seeing is indeed hangover from the previous server -- there is a flatfile, dsmserv.dsk, with path definitions for the database volumes and logs; this is used at startup to find the database. All other definitions are stored in the database. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: Wednesday, March 15, 2006 8:33 AM To: ADSM-L@VM.MARIST.EDU Subject: New TSM Server, DB and STG POOL question Hi All I'm running TSM on Solaris 2.7 and moving to Solaris 2.9 on a new physical server. If moving a TSM server from one machine to another, do you format space for the backup pools first, then do the restore, or do you restore your DB first and then format space for the backup pool and archive pool? I installed TSM and then formatted all the space necessary for the log and db vols, backuppool and archive devices. I then restored the db, but when I start the new TSM server instance I am seeing messages such as the following :- 03/15/06 12:50:53 ANR1315E Vary-on failed for disk volume /usr/tsmdata/back- up01.dsm - invalid label block. Now I'm guessing this is because TSM on the old server (and hence the db) knows nothing about this new device, so do I just create the disk pools after restore? Many thanks Farren Minns ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ## CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
Re: New TSM Server, DB and STG POOL question
I wrote: > I first deleted all disk storage pools on the old server, CAUTION!!! Of yourse, I only deleted the disk pool volumes, NOT the storage pools themselves. -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470
Re: New TSM Server, DB and STG POOL question
Farren, Farren Minns schrieb: If moving a TSM server from one machine to another, do you format space for the backup pools first, then do the restore, or do you restore your DB first and then format space for the backup pool and archive pool? I just moved our AIX TSM-Server from one machine to another. I first deleted all disk storage pools on the old server, made a backup of the database, restored the db on the new server, and finally I recreated the disk pool volumes. There's a technote on this topic somewhere on the Tivoli support side. -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470
New TSM Server, DB and STG POOL question
Hi All I'm running TSM on Solaris 2.7 and moving to Solaris 2.9 on a new physical server. If moving a TSM server from one machine to another, do you format space for the backup pools first, then do the restore, or do you restore your DB first and then format space for the backup pool and archive pool? I installed TSM and then formatted all the space necessary for the log and db vols, backuppool and archive devices. I then restored the db, but when I start the new TSM server instance I am seeing messages such as the following :- 03/15/06 12:50:53 ANR1315E Vary-on failed for disk volume /usr/tsmdata/back- up01.dsm - invalid label block. Now I'm guessing this is because TSM on the old server (and hence the db) knows nothing about this new device, so do I just create the disk pools after restore? Many thanks Farren Minns ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
TSM 5.3 client release for Netware
All, Has anyone an idea when Tivoli are releasing the next patch/maintenance release for the Netware Tivoli client, there are a few major bugs in 5.3.2.2 as it stands and are due to be rectified in the next release of the Netware Tivoli client. Regards, Jim Bollard.
Re: where is dsmcad ?
Hi Goran, Dsmcad is still in TSM Client 5.3 (see below): [dlbnim /home/rdl] # type dsmcad dsmcad is /usr/bin/dsmcad [dlbnim /home/rdl] # ls -l /usr/bin/dsmcad lrwxrwxrwx 1 root system 36 Jul 22 2005 /usr/bin/dsmcad -> /usr/tivoli/tsm/client/ba/bin/dsmcad [dlbnim /home/rdl] # dsmc IBM Tivoli Storage Manager Command Line Backup/Archive Client Interface Client Version 5, Release 3, Level 0.12 Client date/time: 03/15/06 14:11:44 (c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved. Node Name: DLBNIM Session established with server DLB_TSM: AIX-RS/6000 Server Version 5, Release 3, Level 1.6 Server date/time: 03/15/06 14:11:44 Last access: 03/11/06 08:26:02 Met vriendelijke groet, With kind regards, Richard van Denzel. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of goc Sent: woensdag 15 maart 2006 13:56 To: ADSM-L@VM.MARIST.EDU Subject: where is dsmcad ? hi all, i much confused !:-S how come the DSMCAD is in client 5.2 and in client 5.3 is not ? am i missing something here ? talking about AIX here thanks for any clue goran
where is dsmcad ?
hi all, i much confused !:-S how come the DSMCAD is in client 5.2 and in client 5.3 is not ? am i missing something here ? talking about AIX here thanks for any clue goran
Re: TSM-Accounting-File
Chris - That's not documented as supported, and would risk collisions and data loss. I don't see a need for mingling, given how easy it is to report from multiple source logs. It is also the case that the log does not contain a field identifying the server, so mingling would render the log problematic even if it could be achieved. Richard Sims On Mar 15, 2006, at 5:53 AM, Christoph Pilgram wrote: Hi all, Is it possible to use one tsm-accounting-file from two tsm-server- instances
Re: tsm + nfs ??
Dierk - You need to post technical details in such problems. By default, TSM backs up local file systems, given that networked file system backups incur more overhead than is often realistic; and NFS can exhibit timeouts and other irregularities which bungle backups. Review your DOMain statement, in conjunction with the client manual doc for DOMain. Richard Sims On Mar 15, 2006, at 3:59 AM, Dierk Harbort wrote: Hi, all! We are running tsm 5.2.x on Linux; 1 Server; clients with NFS mounted dirs; My question is: Why doesn't tsm see nfs mounted directories? Everything works fine. Only tsm has a problem: No backup for nfs mounted directories?? I'm afraid solution is simple, but sorry I failed... TIA, Dierk
Re: path gone
Dierk - The answer should be in your server Activity Log, if not also your OS error log. The cause is usually hardware problems; in your case, whatever is common to the pathing, as for example a SCSI cable come loose, the library being powered off by an operator, etc. Richard Sims On Mar 15, 2006, at 2:54 AM, Dierk Harbort wrote: Hi all! We are running TSM 5.2.x on Linux, 1 Server; TL3583 with 4x LTO3 drives; My question is: What could cause, during normal business, the tsm server to set all its path' to online=no ? (shown in q path) Has anybody a reason for this? TIA, Dierk
TSM-Accounting-File
Hi all, Is it possible to use one tsm-accounting-file from two tsm-server-instances (TSM V 5.2.4.3 on AIX 5.2 ML6). Thanks Chris
path gone
Hi all! We are running TSM 5.2.x on Linux, 1 Server; TL3583 with 4x LTO3 drives; My question is: What could cause, during normal business, the tsm server to set all its path' to online=no ? (shown in q path) Has anybody a reason for this? TIA, Dierk
tsm + nfs ??
Hi, all! We are running tsm 5.2.x on Linux; 1 Server; clients with NFS mounted dirs; My question is: Why doesn't tsm see nfs mounted directories? Everything works fine. Only tsm has a problem: No backup for nfs mounted directories?? I'm afraid solution is simple, but sorry I failed... TIA, Dierk
