Re: Backing up a large file system for a TSM newbie
Paul further info Tapes are 3590's - two of them! Disks are 18G internal SCSI Versions of TSM are 4.2.1.0 (server and client) n/w between client and server is 100BaseT Direct fibre connections between server and each tape device Other info which may help FTP'ed large (2G!) files between cleint and /dev/null on server.9000Kbytes/sec setting on server viewed thru GUI Maximum files in a client transaction = 256 (from TSM Server gui) Maximum files moved in a transaction = 500 (TSM server gui) Maximum megabytes moved in a transaction = 256 (gui again) Details of files below. TIA Peter dsm.sys on client is as follows... === SErvername tsmserv SCHEDMODE POLLING QUERYSCHEDPERIOD 1 COMMmethod TCPip TCPPort1500 TCPServeraddress tsmserv tcpnodelay no tcpwindowsize 1024 largecommbuffers yes txnbytelimit 2097152 nodename oradev1 errorlogretention 10,D passwordaccess generate schedlogname dsmsched.log schedlogretention 10,D compression no Nothing in dsm.opt == no dsmserv.sys (at least that I can find == Dsmserv.optas follows..non comment lines only included.I have never looked at the dsmserv filesthey are as was left by the 'consultants' who installed and ran away! COMMmethod TCPIP COMMmethod SHAREDMEM COMMmethod HTTP LANGuage en_US ENABLE3590LIBRARY YES HTTPPORT 1580 SHMPORT 1510 TCPBUFSIZE 32 TCPNODELAY YES TCPPORT 1500 COMMTIMEOUT 60 DISABLESCHEDS YES IDLETIMEOUT 15 MAXSESSIONS 40 USELARGEBUFFERS YES BUFPOOLSIZE 32768 SELFTUNEBUFPOOLSIZE YES LOGPOOLSIZE 2048 MIRRORREAD DB NORMAL MIRRORREAD LOG NORMAL MIRRORWRITE DB SEQUENTIAL MIRRORWRITE LOG SEQUENTIAL MOVEBATCHSIZE 500 MOVESIZETHRESH 256 TXNGROUPMAX 256 EVENTSERVER YES DEVCONFIG /usr/tivoli/tsmlog/devconfig DEVCONFIG /usr/tivoli/tsmlogmir/devconfig2 EXPINTERVAL 0 VOLUMEHISTORY /usr/tivoli/tsmlog/volumehistory VOLUMEHISTORY /usr/tivoli/tsmlogmir/volumehistory -Original Message- From: Seay, Paul [mailto:[EMAIL PROTECTED]] Sent: 22 March 2002 01:18 To: [EMAIL PROTECTED] Subject: Re: Backing up a large file system for a TSM newbie I have file systems with 1.5TB and 9 million files. They do take a while to backup. We can save a 1 TB SAP database in about 2.5 hours. So, I think we need some more information. What kind of tape? What kind of disk? TSM server on AIX? What kind of Network interface? What does your dsmserv.sys and opt and dsm.sys and dsm.opt look like? -Original Message- From: Schaub Joachim Paul ABX-PROD-ZH [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 21, 2002 2:40 PM To: [EMAIL PROTECTED] Subject: AW: Backing up a large file system for a TSM newbie try with the adaptive sub-file differencing incl. in the 4.2 Client If you have enough capacity in the network components the ressourceutil param in the dsm.opt or dsm.sys may also help regards joachim -Ursprüngliche Nachricht- Von: Peter McMahon [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 21. März 2002 19:33 An: [EMAIL PROTECTED] Betreff: Backing up a large file system for a TSM newbie Hi, sorry if this is a repost! firstly let me state that I am very new to TSM and have only picked up bits and pieces from reviewing the list and some FAQ type docosso pls excuse if this is a basic question... We have several AIX boxes which have 'large' file systems...by large I mean 30Gig which contain multiple installs of Oracle sever s/w so thousands of files/directories. (NB Not the database files them selves) A selective backup of these is taking a 'significant' amount of time - approx 4 hr to do a filesystem of about 35G...I have tried going directly to tape - think it was even slower so what I am looking for is some advice on the best settings for these types of file systems TIA Peter ** The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action or reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer. **
Re: Backing up a large file system for a TSM newbie
Hi Upgrading at least the client to a newer level such as 4.2.1.20 or 4.2.1.30 would be a good idea. The 4.2.1.0 client has had a lot of performance problems. Another thing to use is the journal-based backup, which probably will save you a lot of time. Best Regards Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Bergkällavägen 31D 192 79 SOLLENTUNA Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Peter McMahon [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 2002-03-22 12:10 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Backing up a large file system for a TSM newbie Paul further info Tapes are 3590's - two of them! Disks are 18G internal SCSI Versions of TSM are 4.2.1.0 (server and client) n/w between client and server is 100BaseT Direct fibre connections between server and each tape device Other info which may help FTP'ed large (2G!) files between cleint and /dev/null on server.9000Kbytes/sec setting on server viewed thru GUI Maximum files in a client transaction = 256 (from TSM Server gui) Maximum files moved in a transaction = 500 (TSM server gui) Maximum megabytes moved in a transaction = 256 (gui again) Details of files below. TIA Peter dsm.sys on client is as follows... === SErvername tsmserv SCHEDMODE POLLING QUERYSCHEDPERIOD 1 COMMmethod TCPip TCPPort1500 TCPServeraddress tsmserv tcpnodelay no tcpwindowsize 1024 largecommbuffers yes txnbytelimit 2097152 nodename oradev1 errorlogretention 10,D passwordaccess generate schedlogname dsmsched.log schedlogretention 10,D compression no Nothing in dsm.opt == no dsmserv.sys (at least that I can find == Dsmserv.optas follows..non comment lines only included.I have never looked at the dsmserv filesthey are as was left by the 'consultants' who installed and ran away! COMMmethod TCPIP COMMmethod SHAREDMEM COMMmethod HTTP LANGuage en_US ENABLE3590LIBRARY YES HTTPPORT 1580 SHMPORT 1510 TCPBUFSIZE 32 TCPNODELAY YES TCPPORT 1500 COMMTIMEOUT 60 DISABLESCHEDS YES IDLETIMEOUT 15 MAXSESSIONS 40 USELARGEBUFFERS YES BUFPOOLSIZE 32768 SELFTUNEBUFPOOLSIZE YES LOGPOOLSIZE 2048 MIRRORREAD DB NORMAL MIRRORREAD LOG NORMAL MIRRORWRITE DB SEQUENTIAL MIRRORWRITE LOG SEQUENTIAL MOVEBATCHSIZE 500 MOVESIZETHRESH 256 TXNGROUPMAX 256 EVENTSERVER YES DEVCONFIG /usr/tivoli/tsmlog/devconfig DEVCONFIG /usr/tivoli/tsmlogmir/devconfig2 EXPINTERVAL 0 VOLUMEHISTORY /usr/tivoli/tsmlog/volumehistory VOLUMEHISTORY /usr/tivoli/tsmlogmir/volumehistory -Original Message- From: Seay, Paul [mailto:[EMAIL PROTECTED]] Sent: 22 March 2002 01:18 To: [EMAIL PROTECTED] Subject: Re: Backing up a large file system for a TSM newbie I have file systems with 1.5TB and 9 million files. They do take a while to backup. We can save a 1 TB SAP database in about 2.5 hours. So, I think we need some more information. What kind of tape? What kind of disk? TSM server on AIX? What kind of Network interface? What does your dsmserv.sys and opt and dsm.sys and dsm.opt look like? -Original Message- From: Schaub Joachim Paul ABX-PROD-ZH [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 21, 2002 2:40 PM To: [EMAIL PROTECTED] Subject: AW: Backing up a large file system for a TSM newbie try with the adaptive sub-file differencing incl. in the 4.2 Client If you have enough capacity in the network components the ressourceutil param in the dsm.opt or dsm.sys may also help regards joachim -Ursprüngliche Nachricht- Von: Peter McMahon [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 21. März 2002 19:33 An: [EMAIL PROTECTED] Betreff: Backing up a large file system for a TSM newbie Hi, sorry if this is a repost! firstly let me state that I am very new to TSM and have only picked up bits and pieces from reviewing the list and some FAQ type docosso pls excuse if this is a basic question... We have several AIX boxes which have 'large' file systems...by large I mean 30Gig which contain multiple installs of Oracle sever s/w so thousands of files/directories. (NB Not the database files them selves) A selective backup of these is taking a 'significant' amount of time - approx 4 hr to do a filesystem of about 35G...I have tried going directly to tape - think it was even slower so what I am looking for is some advice on the best settings for these types of file systems TIA Peter ** The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action or reliance upon, this information by persons or entities
Re: Backing up a large file system for a TSM newbie - journal backup
Girl and Guys, lets make it clear - is journal backup feature only available in Windows or I am missing something. If I am not wrong Peter posted in the beginning that is talking about AIX boxes, so journaling TSM feature is not available there. Zlatko Krastev IT Consultant Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject:Re: Backing up a large file system for a TSM newbie Hi Upgrading at least the client to a newer level such as 4.2.1.20 or 4.2.1.30 would be a good idea. The 4.2.1.0 client has had a lot of performance problems. Another thing to use is the journal-based backup, which probably will save you a lot of time. Best Regards Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Bergkällavägen 31D 192 79 SOLLENTUNA Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Peter McMahon [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 2002-03-22 12:10 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Backing up a large file system for a TSM newbie Paul further info Tapes are 3590's - two of them! Disks are 18G internal SCSI Versions of TSM are 4.2.1.0 (server and client) n/w between client and server is 100BaseT Direct fibre connections between server and each tape device Other info which may help FTP'ed large (2G!) files between cleint and /dev/null on server.9000Kbytes/sec setting on server viewed thru GUI Maximum files in a client transaction = 256 (from TSM Server gui) Maximum files moved in a transaction = 500 (TSM server gui) Maximum megabytes moved in a transaction = 256 (gui again) Details of files below. TIA Peter dsm.sys on client is as follows... === SErvername tsmserv SCHEDMODE POLLING QUERYSCHEDPERIOD 1 COMMmethod TCPip TCPPort1500 TCPServeraddress tsmserv tcpnodelay no tcpwindowsize 1024 largecommbuffers yes txnbytelimit 2097152 nodename oradev1 errorlogretention 10,D passwordaccess generate schedlogname dsmsched.log schedlogretention 10,D compression no Nothing in dsm.opt == no dsmserv.sys (at least that I can find == Dsmserv.optas follows..non comment lines only included.I have never looked at the dsmserv filesthey are as was left by the 'consultants' who installed and ran away! COMMmethod TCPIP COMMmethod SHAREDMEM COMMmethod HTTP LANGuage en_US ENABLE3590LIBRARY YES HTTPPORT 1580 SHMPORT 1510 TCPBUFSIZE 32 TCPNODELAY YES TCPPORT 1500 COMMTIMEOUT 60 DISABLESCHEDS YES IDLETIMEOUT 15 MAXSESSIONS 40 USELARGEBUFFERS YES BUFPOOLSIZE 32768 SELFTUNEBUFPOOLSIZE YES LOGPOOLSIZE 2048 MIRRORREAD DB NORMAL MIRRORREAD LOG NORMAL MIRRORWRITE DB SEQUENTIAL MIRRORWRITE LOG SEQUENTIAL MOVEBATCHSIZE 500 MOVESIZETHRESH 256 TXNGROUPMAX 256 EVENTSERVER YES DEVCONFIG /usr/tivoli/tsmlog/devconfig DEVCONFIG /usr/tivoli/tsmlogmir/devconfig2 EXPINTERVAL 0 VOLUMEHISTORY /usr/tivoli/tsmlog/volumehistory VOLUMEHISTORY /usr/tivoli/tsmlogmir/volumehistory -Original Message- From: Seay, Paul [mailto:[EMAIL PROTECTED]] Sent: 22 March 2002 01:18 To: [EMAIL PROTECTED] Subject: Re: Backing up a large file system for a TSM newbie I have file systems with 1.5TB and 9 million files. They do take a while to backup. We can save a 1 TB SAP database in about 2.5 hours. So, I think we need some more information. What kind of tape? What kind of disk? TSM server on AIX? What kind of Network interface? What does your dsmserv.sys and opt and dsm.sys and dsm.opt look like? -Original Message- From: Schaub Joachim Paul ABX-PROD-ZH [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 21, 2002 2:40 PM To: [EMAIL PROTECTED] Subject: AW: Backing up a large file system for a TSM newbie try with the adaptive sub-file differencing incl. in the 4.2 Client If you have enough capacity in the network components the ressourceutil param in the dsm.opt or dsm.sys may also help regards joachim -Ursprüngliche Nachricht- Von: Peter McMahon [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 21. März 2002 19:33 An: [EMAIL PROTECTED] Betreff: Backing up a large file system for a TSM newbie Hi, sorry if this is a repost! firstly let me state that I am very new to TSM and have only picked up bits and pieces from reviewing the list and some FAQ type docosso pls excuse if this is a basic question... We have several AIX boxes which have 'large' file systems...by large I mean 30Gig which contain multiple installs of Oracle sever s/w so thousands of files/directories. (NB Not the database files them selves) A selective backup of these is taking a 'significant' amount of time - approx 4 hr to do a filesystem of about 35G...I have tried going directly to tape
Re: Backing up a large file system for a TSM newbie
Hello Run a q db f=d What is yor cachehit%? If it is under 99 try to increase the bufpoolsize Also use resource utilization on the client: In dsm.sys add Resour=10 Journal based backup is only for Windows Regards Niklas Lundström -Original Message- From: Peter McMahon [mailto:[EMAIL PROTECTED]] Sent: den 22 mars 2002 12:10 To: [EMAIL PROTECTED] Subject: Re: Backing up a large file system for a TSM newbie Paul further info Tapes are 3590's - two of them! Disks are 18G internal SCSI Versions of TSM are 4.2.1.0 (server and client) n/w between client and server is 100BaseT Direct fibre connections between server and each tape device Other info which may help FTP'ed large (2G!) files between cleint and /dev/null on server.9000Kbytes/sec setting on server viewed thru GUI Maximum files in a client transaction = 256 (from TSM Server gui) Maximum files moved in a transaction = 500 (TSM server gui) Maximum megabytes moved in a transaction = 256 (gui again) Details of files below. TIA Peter dsm.sys on client is as follows... === SErvername tsmserv SCHEDMODE POLLING QUERYSCHEDPERIOD 1 COMMmethod TCPip TCPPort1500 TCPServeraddress tsmserv tcpnodelay no tcpwindowsize 1024 largecommbuffers yes txnbytelimit 2097152 nodename oradev1 errorlogretention 10,D passwordaccess generate schedlogname dsmsched.log schedlogretention 10,D compression no Nothing in dsm.opt == no dsmserv.sys (at least that I can find == Dsmserv.optas follows..non comment lines only included.I have never looked at the dsmserv filesthey are as was left by the 'consultants' who installed and ran away! COMMmethod TCPIP COMMmethod SHAREDMEM COMMmethod HTTP LANGuage en_US ENABLE3590LIBRARY YES HTTPPORT 1580 SHMPORT 1510 TCPBUFSIZE 32 TCPNODELAY YES TCPPORT 1500 COMMTIMEOUT 60 DISABLESCHEDS YES IDLETIMEOUT 15 MAXSESSIONS 40 USELARGEBUFFERS YES BUFPOOLSIZE 32768 SELFTUNEBUFPOOLSIZE YES LOGPOOLSIZE 2048 MIRRORREAD DB NORMAL MIRRORREAD LOG NORMAL MIRRORWRITE DB SEQUENTIAL MIRRORWRITE LOG SEQUENTIAL MOVEBATCHSIZE 500 MOVESIZETHRESH 256 TXNGROUPMAX 256 EVENTSERVER YES DEVCONFIG /usr/tivoli/tsmlog/devconfig DEVCONFIG /usr/tivoli/tsmlogmir/devconfig2 EXPINTERVAL 0 VOLUMEHISTORY /usr/tivoli/tsmlog/volumehistory VOLUMEHISTORY /usr/tivoli/tsmlogmir/volumehistory -Original Message- From: Seay, Paul [mailto:[EMAIL PROTECTED]] Sent: 22 March 2002 01:18 To: [EMAIL PROTECTED] Subject: Re: Backing up a large file system for a TSM newbie I have file systems with 1.5TB and 9 million files. They do take a while to backup. We can save a 1 TB SAP database in about 2.5 hours. So, I think we need some more information. What kind of tape? What kind of disk? TSM server on AIX? What kind of Network interface? What does your dsmserv.sys and opt and dsm.sys and dsm.opt look like? -Original Message- From: Schaub Joachim Paul ABX-PROD-ZH [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 21, 2002 2:40 PM To: [EMAIL PROTECTED] Subject: AW: Backing up a large file system for a TSM newbie try with the adaptive sub-file differencing incl. in the 4.2 Client If you have enough capacity in the network components the ressourceutil param in the dsm.opt or dsm.sys may also help regards joachim -Ursprüngliche Nachricht- Von: Peter McMahon [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 21. März 2002 19:33 An: [EMAIL PROTECTED] Betreff: Backing up a large file system for a TSM newbie Hi, sorry if this is a repost! firstly let me state that I am very new to TSM and have only picked up bits and pieces from reviewing the list and some FAQ type docosso pls excuse if this is a basic question... We have several AIX boxes which have 'large' file systems...by large I mean 30Gig which contain multiple installs of Oracle sever s/w so thousands of files/directories. (NB Not the database files them selves) A selective backup of these is taking a 'significant' amount of time - approx 4 hr to do a filesystem of about 35G...I have tried going directly to tape - think it was even slower so what I am looking for is some advice on the best settings for these types of file systems TIA Peter ** The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action or reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer. **
Backing up a large file system for a TSM newbie
Hi, sorry if this is a repost! firstly let me state that I am very new to TSM and have only picked up bits and pieces from reviewing the list and some FAQ type docosso pls excuse if this is a basic question... We have several AIX boxes which have 'large' file systems...by large I mean 30Gig which contain multiple installs of Oracle sever s/w so thousands of files/directories. (NB Not the database files them selves) A selective backup of these is taking a 'significant' amount of time - approx 4 hr to do a filesystem of about 35G...I have tried going directly to tape - think it was even slower so what I am looking for is some advice on the best settings for these types of file systems TIA Peter ** The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action or reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer. **
AW: Backing up a large file system for a TSM newbie
try with the adaptive sub-file differencing incl. in the 4.2 Client If you have enough capacity in the network components the ressourceutil param in the dsm.opt or dsm.sys may also help regards joachim -Ursprüngliche Nachricht- Von: Peter McMahon [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 21. März 2002 19:33 An: [EMAIL PROTECTED] Betreff: Backing up a large file system for a TSM newbie Hi, sorry if this is a repost! firstly let me state that I am very new to TSM and have only picked up bits and pieces from reviewing the list and some FAQ type docosso pls excuse if this is a basic question... We have several AIX boxes which have 'large' file systems...by large I mean 30Gig which contain multiple installs of Oracle sever s/w so thousands of files/directories. (NB Not the database files them selves) A selective backup of these is taking a 'significant' amount of time - approx 4 hr to do a filesystem of about 35G...I have tried going directly to tape - think it was even slower so what I am looking for is some advice on the best settings for these types of file systems TIA Peter ** The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action or reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer. **
Re: Backing up a large file system for a TSM newbie
I have file systems with 1.5TB and 9 million files. They do take a while to backup. We can save a 1 TB SAP database in about 2.5 hours. So, I think we need some more information. What kind of tape? What kind of disk? TSM server on AIX? What kind of Network interface? What does your dsmserv.sys and opt and dsm.sys and dsm.opt look like? -Original Message- From: Schaub Joachim Paul ABX-PROD-ZH [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 21, 2002 2:40 PM To: [EMAIL PROTECTED] Subject: AW: Backing up a large file system for a TSM newbie try with the adaptive sub-file differencing incl. in the 4.2 Client If you have enough capacity in the network components the ressourceutil param in the dsm.opt or dsm.sys may also help regards joachim -Ursprüngliche Nachricht- Von: Peter McMahon [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 21. März 2002 19:33 An: [EMAIL PROTECTED] Betreff: Backing up a large file system for a TSM newbie Hi, sorry if this is a repost! firstly let me state that I am very new to TSM and have only picked up bits and pieces from reviewing the list and some FAQ type docosso pls excuse if this is a basic question... We have several AIX boxes which have 'large' file systems...by large I mean 30Gig which contain multiple installs of Oracle sever s/w so thousands of files/directories. (NB Not the database files them selves) A selective backup of these is taking a 'significant' amount of time - approx 4 hr to do a filesystem of about 35G...I have tried going directly to tape - think it was even slower so what I am looking for is some advice on the best settings for these types of file systems TIA Peter ** The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action or reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer. **
