What about the TSM server side of things ? Is the data being written to
disk or does it end up writing to tape ?
We experienced what we though was a network issue a couple of years back
it turned out two of our Exchange servers were using all the available
diskpool space and everything else had to write to tape.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Gary Osullivan
Sent: Friday, December 30, 2005 11:08 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Novell backups
hi
The battle continues with the slow running tsm backups for netware.
-tsa is set at...20, no caching (any higher causes the backup to fail).
-The SAN is at raid 5 (7 disk, 1P) -San disks are each 72Gb -FC disks
-1gb FC connections -Host bus adapter was the 1st thing we updated -Our
backup window is tight, We have several large tsm backup running at the
same time. (the best that we can do is stagger the starting times).
Still looking for a way to shorten the backup time.
Thanks, Gary
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Troy Frank
Sent: Thursday, December 29, 2005 4:47 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Novell backups
In addition to what duane wanted to know, I would look at a couple other
things. In the sys:\etc\sms\tsa.cfg file, check these settings...
Enable Caching - should be no. tsm client already does read-ahead
caching, the tsa caching is redundant.
Cache Memory Threshold - should be set to as high as you can get away
with. 25% is the max. If backups give you errors with it set this
high, I usually move down in increments of 5% until errors stop
happening.
To make the above changes take affect, you'd have to unload dsmcad, run
smsstop, then reload everything. To continue on with Duane's line of
thinking, make sure that the hba's in your server are at the latest
firmware/driver versions. There's also a post sp5 NSS patch available
(nw6nss5c). Also, since it's san-attached, how many other servers are
attached to this san, and could some of them also be running backups (or
other things) at the same time?
>>> Duane.Ochs AT QG DOT COM 12/29/2005 3:13:33 PM >>>
The data only took 6.6 hours to transfer. To me it would look like the
process of scanning the filesystem is taking the majority of the time.
How are your san disks set up ? Raid 5 ? How many physical disks to make
up a volume ? FC disk or sata ? 2gb FC connections ?
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Gary Osullivan
Sent: Thursday, December 29, 2005 2:59 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Novell backups
hi
here are a few details to add to Richard's original query.
This tsm backup of netware data is now taking us 19 hours to complete !
Any ideas ?
-netware version 6 sp5
-tsafs (version 6.51 JUNE 18 2005)
-client server proliant DL380\G2
-Pentium 3 /1.33GHZ dual processor 512cache
-client server internal disk 17361mb
-clent server memory (2359296kb)
-NIc 6136 gigabit
-client data is SAN attached (2 data volumes, 650Gb of data on each vol
/ 2.1 million object on each vol. -number of objects scanned 4.2 million
- objects backed up: 1,527,474
- processing time: 19:20:45
-bytes transferred: 221.36 GB
-Data transfer time: 23,651.11 sec
-Network data transfer rate: 9,814.20 KB/sec
dsp.opt file
************************************************************************
* Tivoli Storage Manager
*
* Sample client options file for scxxxxx (ver 5.1.6.0)
************************************************************************
* Communications settings
* Setting Options for the TCP/IP Communication Method
* -------------------------------------------------------
*
COMMMETHOD TCPip
TCPSERVERADDRESS tsmgiga.slac.ca
TCPPORT 1600
* Recommended for automated backup schedules
* -------------------------------------------------------
Passwordaccess generate
* Setting Nodename
* -------------------------------------------------------
NODENAME scxxxxx
*
* Recommended exclude list for NetWare
* -------------------------------------------------------
*
* NetWare 3.12, 3.20 specific - use the INCR BINDERY or SEL BINDERY
* command to backup the bindery; exclude the real bindery
* files:
* -------------------------------------------------------
* EXCLUDE sys:\system\net$obj.sys
* EXCLUDE sys:\system\net$prop.sys
* EXCLUDE sys:\system\net$val.sys
*
* NetWare 4.11, 4.20 & 5.00 specific - NDS leaf objects can be included/
* excluded; container objects are not affected. This example
* shows how to include only objects in container
* .OU=Development.O=TIVOLI
* ---------------------------------------------------------
* EXCLUDE directory:/.O=TIVOLI/.../*
* INCLUDE directory:/.O=TIVOLI/.OU=Development.O=TIVOLI/.../*
*
* NetWare general excludes
* ---------------------------------------------------------
INCLUDE scxxxxx\SYS:.../* mgm_nov
INCLUDE scxxxxx\SHARE1:.../* mgm_nov
INCLUDE scxxxxx\USER3:.../* mgm_nov
EXCLUDE scxxxxx\SYS:/SYSTEM/CSLIB/LOGS/SMLOGS/*
EXCLUDE scxxxxx\SYS:/_SWAP_.MEM
EXCLUDE scxxxxx\SYS:/LTAUDIT/.../*
EXCLUDE scxxxxx\SYS:/TIVOLI/TSM/CLIENT/BA/*.log
EXCLUDE scxxxxx\SHARE1:/graphics/.../*
EXCLUDE scxxxxx\SHARE1:/Internet branding shared/.../*
EXCLUDE scxxxxx\USER1:.../* mgm_nov
EXCLUDE scxxxxx\VOL1:.../* mgm_nov
EXCLUDE scxxxxx\SHARE2:.../* mgm_nov
EXCLUDE scxxxxx\SHARE3:.../* mgm_nov
EXCLUDE scxxxxx\SHARE4:.../* mgm_nov
EXCLUDE scxxxxx\NDPS:.../* mgm_nov
EXCLUDE scxxxxx\FTP:.../* mgm_nov
EXCLUDE scxxxxx\USER2:.../* mgm_nov
EXCLUDE scxxxxx\SOFTWARE:.../* mgm_nov
EXCLUDE "scxxxxx\VOL2:/.../Windows NT 5.1 Workstation
Profile/Recent/*.lnk" EXCLUDE "scxxxxx\VOL2:/.../Windows NT 5.1
Workstation Profile/Application Data/Microsoft/Office/Recent/*.lnk"
EXCLUDE "scxxxxx\SHARE1:/GS&R Client Install\GS&R - ICIS/*"
* NetWare Memory management option
* ---------------------------------------------------------------
* The following option uses a memory conserving algorithm for
* processing incremental backups as each directory is backed up.
* This option may increase the duration of time required for
* backups and increase CPU utilization on the TSM Server.
* But will decrease the required NetWare memory needed for backups.
*
* MEMORYEFFICIENTBACKUP YES
* --------------------------------------------------------------
* NetWare Screen option
* ---------------------------------------------------------------
* The following option instructs the NetWare client to destroy
* the TSM screen when quitting the dsmc program.
*
NWWAIT NO
* --------------------------------------------------------------
* NetWare user ID and password option
* --------------------------------------------------------------
* The following option specifies a user ID and password to connect
* to a local or remote NetWare resource (server or NDS tree). The
* user ID must have NetWare supervisory equivalence. Use this
* option for each resource which will be managed by TSM.
*
* If this option is not specified in the client options file, TSM
* will check for a user ID and password in an encrypted file (if
* NWPWFILE is set to YES). If a correct user ID and password
* is not found in a file (or NWPWFILE is set to NO), TSM will prompt
* for a user ID and password when a backup or archive operation
* is initiated.
* NWUSER server_1_name\user:password
* NWUSER server_2_name\user:password
* NWUSER nds_tree_name\user:password
* --------------------------------------------------------------
* NetWare user ID and password file
* --------------------------------------------------------------
* The following option specifies that the user ID and password used
* to connect to a NetWare resource (server or NDS tree) will be stored
* in an encrypted file in the installation directory after the intiial
* prompt. An encrypted file will be created for each resource with the
* extension .PWD
* NWPWFILE YES
* -----------------------------------------------------------------
* Silencing screen output
* -----------------------------------------------------------------
* Use the QUIET option to keep messages from being displayed on the
* NetWare console and the schedule log file. This option will enhance
* the performance during scheduled backups. Default is VERBOSE. QUIET
* -----------------------------------------------------------------
* COMMON OPTIONS SETTINGS
* -----------------------------------------------------------------
SUBDIR YES
resourceutilization 6
tcpwindowsize 64
queryschedperiod 2
retryp 5
changingretries 1
schedlogretention 1 S
schedmode prompted
managedservice webclient schedule
dirmc mgm_nov
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Troy Frank
Sent: Thursday, December 29, 2005 1:40 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Novell backups
There is a way to do what you want, but I would question the
necessecity. We have a handful of file servers with over 1 million files
each, and on average they take about 45min to backup (~2.5GB/day). If
you only have a # of files in the thousands, and it's taking a long
time, then I suspect something is wrong. Would it be possible to collect
some information about the situation?
Netware version? -
TSA's version? -
Server hardware (cpu/disk/memory/nic)? -
Total # of files being scanned? -
Backup sesssion stats (total time taken/network rate/aggregate rate)?
-
Paste in the contents of dsm.opt? -
>>> Richard.Mochnaczewski AT STANDARDLIFE DOT CA 12/29/2005 11:37:50 AM >>>
Hi Everybody,
Is there a way to schedule multiple Novell backups to run simultaneously
for one node ? We are having trouble with our backups completing in a
timely manner as we have thousand of files which are being scanned for
backup. What we would like to do is have the volume on the node split
out and backed up through multiple sessions simultaneously. Is this
possible ?
Rich
Confidentiality Notice follows:
The information in this message (and the documents attached to it, if
any) is confidential and may be legally privileged. It is intended
solely for the addressee. Access to this message by anyone else is
unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken, or omitted to be taken in
reliance on it is prohibited and may be unlawful. If you have received
this message in error, please delete all electronic copies of this
message (and the documents attached to it, if any), destroy any hard
copies you may have created and notify me immediately by replying to
this email. Thank you.
Confidentiality Notice follows:
The information in this message (and the documents attached to it, if
any) is confidential and may be legally privileged. It is intended
solely for the addressee. Access to this message by anyone else is
unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken, or omitted to be taken in
reliance on it is prohibited and may be unlawful. If you have received
this message in error, please delete all electronic copies of this
message (and the documents attached to it, if any), destroy any hard
copies you may have created and notify me immediately by replying to
this email. Thank you.
|
