Mehdi,
Does defining logical tape drives helps eliminating this single point of
failure such that if during client backup the fiber connection of drive
fails, another tape drive in the library takes over the operation?
Okay, the quote from the Redbook below may have misled you in this case: a
Hi,
Which version of SANergy is compatible with TSM 6.1? I could not find enough
information about SANergy except the old practical guide (June 2001)!
Thanks
Hi All,
I'm currently looking into the snapdiff feature of the TSM 6.1 client.
My customer is still running TSM server version 5.4, so I was looking
into the requirements for using the 6.1 client and the snapdiff
feature. Does anyone know if there is any dependancy on a specific
server version
Have you tried to search in Internet?
For example:
http://www-01.ibm.com/support/docview.wss?rs=663context=SSGSG7uid=swg21392122loc=en_UScs=UTF-8lang=en
Grigori G. Solonovitch
Senior Technical Architect
Information Technology Bank of Kuwait and Middle East http://www.bkme.com
On 12 okt 2009, at 12:36, Grigori Solonovitch wrote:
Have you tried to search in Internet?
For example:
http://www-01.ibm.com/support/docview.wss?rs=663context=SSGSG7uid=swg21392122loc=en_UScs=UTF-8lang=en
Where does this document list TSM server level requirements? I've
searched the TSM
Hello,
I am currently analyzing a TSM server which uses 100% CPU on 4 cores
when doing client backups. Almost all of it is privileged times, but
there are very few IO's and low disk queues for both stgpools, db and log.
Are there any trace flags similar to the client testflag instrument:detail
I once saw this when we had set BUFPOOLSIZE way too high.Giving the TSM
server lots of memory starved the OS for memory; things slowed down horribly
until we set BUFPOOLSIZE back to the Performance-tuning-guide
recommendations ( I forget - 1/4 of available memory?)
On Mon, Oct 12, 2009 at 7:58
The Migrating from earlier versions section near the beginning of the
client manual discusses the topic of which servers are supported with the
5.5 client (5.5 or 6.1). Alternatively see
http://www.ibm.com/support/docview.wss?uid=swg21053218
In theory the SnapDiff functionality should work with a
You should not add things to your options files which are not defined
as valid for your software.
DATEformat, NUMberformat, and TIMEformat have been obsolete
specifications since TSM 3.7, when such controls were transferred to
locale settings.
The Options table may evidence the options, though
Go to the link in my sig and do a search on:
performance tuning information
Best regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Hartford/i...@ibmus
Internet e-mail: stor...@us.ibm.com
Andy,
thanks. I'm aware of the official support issue, I'll urge the
customer to upgrade the servers to 5.5.
On 12 okt 2009, at 14:38, Andrew Raibeck wrote:
The Migrating from earlier versions section near the beginning of
the
client manual discusses the topic of which servers are supported
Our TSM Server was upgraded from previous versions many times, so maybe it is
coming from there.
According to dsmserv.opt.smp in TSM 6.1.2 DATEFORMAT, TIMEFORMAT and
NUMBERFORMAT are still used for z/OS.
Grigori G. Solonovitch
Senior Technical Architect
Information Technology Bank of
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Remco Post
Sent: Monday, October 12, 2009 8:45 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] snapdiff
Andy,
A teammate successfully implemented snapdiff in our storage environment.
He used the
Yeah, I'm leaning towards memory or maybe network right now.
I'm seeing some of these during client backups:
ANR0132E smnode.c(27085): Memory allocation failed: object sessP-qryBuf, size
1048576. (SESSION: 5518)
This is on a win32 system so 2GB mem is max. I'll try reducing the
bufpool to give
Thank you. I had forgotten that instrumentation was implemented as its own
command.
On 12/10, Andrew Raibeck wrote:
Go to the link in my sig and do a search on:
performance tuning information
Best regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product
Hello all,
I have to configure TSM backup for Microsoft exchange server.The problem is
that TSM BAC client is unable to backup open files and the mail admin
requires these files to be backed up anyway.According to him, all log files
, whcih are always open are needed for recovery.So , my question
HEllo,
you can't backup database files or other files that change during
processing with the normal client. For that you need an application
specific client, called a TDP in the TSM world, that can backup the
application via it's supported backup API.
For Exchange, please see:
Ashish,
Changing the serialization parameter in your backup copygroup definition
from shrstatic or static to shrdynamic or dynamic will force TSM to
backup open files; HOWEVER, there is no guarantee that you will be able
to make use of the backed up open files in the case of restore.
You should
Compromise: Go to TSM 5.5 and use the 5.4 client on older machines.
TSM 6.1 from what I'm hearing, isn't exactly an environment I'd want to
go to at the moment. And, you can, as Wanda has said, use the 6.1
clients where it makes sense to.
See Ya'
Howard
-Original Message-
From:
Hi all,
for information, I've implemented snapdiff but in a TSM v6.1 only
environment (client and server) and we're going on production. There are a
couple of limitations and requirements (for ex. the ntfs support only, the
UTF8 page code, the permissions on the filer ...etc.) that you should be
All,
We have a TSM server that's running out of steam, and nearing the end
of its expected reliable life. We have Version 5, Release 3, Level 4.6
installed, with various levels of clients installed on our servers.
The server has 1gb RAM, roughly 2tb of disk storage, but it's old/slow
PATA, and
Are you looking purely at a lift and shift hardware change here, or at a clean
installation of TSM Server (at 5.5.3 for example) and migrating clients into
the new instance?
Cheers,
/David Mc
London, UK
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On
On 12 okt 2009, at 19:13, Olivier Levan wrote:
Hi all,
for information, I've implemented snapdiff but in a TSM v6.1 only
environment (client and server) and we're going on production. There
are a
couple of limitations and requirements (for ex. the ntfs support
only, the
UTF8 page code, the
Hello everyone, I am trying to track down a client backup error.
TSM Server 5.5.1, AIX 5.3.0.0
TSM ba Client 5.5.1.0, Win2K3 R2 SP2 - The server is part of an HP
Polyserver cluster. We have excluded the Polyserve related mountpoints.
We have not edited the registry.
I am trying to
I'd prefer to be able to migrate server data as much as possible,
including the diskpool, but if it it would be an incredibly difficult
maneuver (or take inordinate amounts of time, say on the order of more
than a 4-day weekend) and/or the downside of losing the diskpool is
relatively minor, I
Start from scratch. Install TSM at the level you would like, move and
configure the library. Point the clients at the new server and go. That first
backup will necessarily be a full. Will take longer than usual, but easy.
This method allows you go clean up your database.
Keep the old server
Hello,
I encountered the same problem a while ago. Searching for security.config.cch
backup with Google shows that this is a common problem.
I suspect that these files are locked or have even been deleted while locked/in
use by another process.
As per Microsoft Knowledge Base,
The files that
So, what happens to all the tapes I have offsite at Iron Mountain, and
the archives I have stored in my basement vault, etc.
I'll be perusing the archives as you suggest, but this isn't exactly
crystalline to me just yet.
A complicating factor that I hadn't realized until I did a bit of
digging
Okay, another fun question for you Kurt, investigating some alternative lines
of simply migrating your current TSM server instance to new hardware: is the
disk upon which your current TSM database/recovery log/storage pool live
internal to your old server, or is it instead hosted upon external
When we migrated to a new server and LTO4 from LTO1, we installed all of the
new stuff and tested the hardware with the TSM version we were running.
When that was working well, we drained all of the disk pools, backed up the
database from the existing server, shut it down, attached the old tape
Disk for the current TSM server is IDE/PATA in a RAID5 array internal
to the machine - though the OS is on a (eep!) single IDE/PATA drive
connected to the motherboard.
Kurt
On Mon, Oct 12, 2009 at 13:19, David McClelland t...@networkc.co.uk wrote:
Okay, another fun question for you Kurt,
For my last migration to new hardware I built a new system and used
export/import server to server.
Worked very well. Doesn’t work if you have only one library though.
However, you are looking for an alternate method.
I'd recommend upgrading to TSM 5.5 first. Especially if you run into problems
Yeah, as I dig into this it becomes more complicated.
We have a number of pools:
Disk Pools:
diskpool
Sequential Access Storage Pools:
ltopool
8mmpool1 (which needs to die)
archivepool
ltoarchive
reclaimpool
Copy Storage
I'll have to work through a fair amount to understand what you've
outlined, but it seems doable. I think pruning volhist and devconfig
first might be a good idea, if for no other reason than to cut down on
the confusion.
Thanks for the input. I'll most likely be back for more information.
Kurt
34 matches
Mail list logo
