Zoltan, thanks for the Windows 2012 info.
About the 5.5 EOS thing. On this page
http://www-01.ibm.com/support/docview.wss?uid=swg21053218
I saw this
* = TSM 5.5 clients will be supported with TSM 6.3 servers and storage agents
during the upgrade of TSM 5.5 servers to TSM 6.3, through Septembe
Hello everyone,
what I am trying to do is a rather simple task - I thought.
I just want to backup a whole Linux-system with TSM.
So I want to exclude all system-specific dirs and the TSM logs (because
otherwise there will be an error because TSM writes to the files while
backing them up) from
Source: TSM 5.5.6 for AIX 5.3-12-06
Target: TSM 6.3.3.100 for AIX 7.1-01-06
It looks "export node" is very slow when I am trying to move all data for
Windows 2008 R2 64 bit (speed is less than 1MB/s).
It is almost unbelievable, but I have moved a few Windows 2003 servers with
speed 10-20MB/s, but
Hi,
I suggest you make the following changes:
PASSWORDACCESS GENERATE
SCHEDLOGNAME/var/log/tsm/schedule.log
Schedlogretention 30 d
ERRORLOGNAME/var/log/tsm/error.log
Errorlogretention 30 d
DOMAIN ALL-LOCAL
EXCLUDE.DIR /proc
EXCLUDE.DIR /sys
EXCLUDE.D
Hi,
We have two servers in a cluster that looks like this:
DataCenter A
WinServer-A (Windows 2008)(ba client v6.4.2)(VCS Global)
TSMserver-A (v5.5.6 on AIX)
DataCenter B
WinServer-B (Windows 2008)(ba client v6.4.2)(VCS Global)
TSMserver-B (v5.5.6 on AIX)
The two Win servers are a cluste
Hi fello TSM'ers,
I need the advice of my fellow Backup admins :)
With TSM 5.5 nearing EOL support and my customer going the Exchange 2010 the
hand has finally been forced to go with TSM 6.x
My current setup;
Server: w2k3
TSM version 5.5.6 - I have about 60 servers being backed all windows base
This is how we did our v5->v6 migration, with the exception that we
actually did fresh backups for some of our larger clients due to the
amount of time required to run EXPORT NODE. Basically our procedure was:
1. Stand up a new TSM server as a library client to the old one (with
all the requisite
Hi Jerome,
What is the current size of the TSM database ? If it's moderate, it's far
simpler and faster to do an upgrade following one of the methods presented in
the upgrade guide.
I'll really advise you to do this.
Regards,
Erwann
"Swartz, Jerome" a écrit :
>Hi fello TSM'ers,
>
>I need t
Thanks Erwann,
Currently just over 200GB. I know it's big and was planning doing a reorg but
the new DB2 will take care of that.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Erwann
Simon
Sent: 27 March 2013 09:20 PM
To: ADSM-L@VM.MARIST.ED
Hi Grigori,
Know that system state contains many more files in Win2k8 than in Win2k3 (10
times).
How are the data organised on medias within the storage pools ?
Which TSM version are you using for those Win2k8 clients ? 6.2 that allows for
incremental backup of system state ?
Regards,
Erwan
Thanks Skylar,
What was the average time for your node exports? I will need to factor that in
as well.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Skylar
Thompson
Sent: 27 March 2013 09:13 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L]
One of the worrying things about the upgrade process is that it's not
really possible to know how long it will take to convert the v5 DB to
DB2. This is why we setup new TSM servers, so that we could control the
size of the outage better (that and the old TSM server hardware was
ready to be ret
It was strongly dependent on the number of files in each node filespace.
Anything with more than 3 million or so files we did using a fresh
incremental backup rather than an export, because those tended to take
more than a day to perform.
On 03/27/2013 12:30 PM, Swartz, Jerome wrote:
Thanks Skyl
The life cycle page that Zoltan cited represents our official EOS
statements, and is the authoritative place for that info. If no EOS date is
listed on the life cycle, then it hasn't been announced yet.
The statement you are referring to:
> TSM 5.5 clients will be supported with TSM 6.3 servers a
I guess my biggest filespace of 31 million is a no-go then. I have a about 10
in the region of 1-10 million. The rest I am sure the export will go smoothly.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Skylar
Thompson
Sent: 27 March 2013 0
I should add the old v5.5 TSM server had some poorly-spec'd DB disks, so
the DB was definitely a bottleneck. If you have decent DB disks, then
you might be OK. The nice thing with the exports is that you can cancel
them and then run an incremental if you need to.
On 03/27/2013 01:04 PM, Swartz, J
I have backup data for all Windows servers on FILE primary storage pool - so
there is no problem reading files for the both 2003 and 2008 servers.
I know about big number of files in SYSTEM STATE for 2008, but it I definitely
not a reason of bad performance. For example, 2003 server has total 72
Hi, Jerome. I've found IBM's quote of 5GB/hr is pretty accurate across
a variety of hardware architectures, OSs, and disk arrays. Figure your
200GB database would take 40-ish hours to upgrade, possibly less if you
feel a reorg would shrink your database significantly. That means you'd
probabl
One other thing to consider during the upgrade is how you rollback in
the case that you run into some serious bug w/ v6. With the in-place
upgrade you need to restore the TSM database before you're back in
business (I've done this before - it works, but is a little harrowing).
If you bring up a ne
Having just done an upgrade of a 120 GB TSM 5.5 server to 6.2, IBM's
time estimates were surprisingly accurate. The process was long and
labor intensive, but in the end it worked. You can see my notes in the
archives of this list from the end of December.
We're even considering altering our strate
20 matches
Mail list logo
