dear Bertaut,
many thanks.
with best regards
stefan savoric
Allen,
My only thought - given that you are restoring lots of small files -
is that you may be thrashing the target disk. Have you looked at that ?
Ian Smith
Oxford
England
On Monday 03 Aug 2009 5:07 pm, Allen S. Rout wrote:
Howdy, all.
I've done a decent amount of small-scale online
On Tue, 4 Aug 2009 10:29:05 +0100, Ian Smith ian.sm...@oucs.ox.ac.uk said:
My only thought - given that you are restoring lots of small files -
is that you may be thrashing the target disk. Have you looked at that ?
Thanks, Ian; I did, and nope. I'm getting 2.3-2.5 MB/s on this; I'm
having
You will have to move the NAS clients over to the new TSM server,
and wait for the old backups to expire before you retire the old backup
server.
That's what I figured, but I'm not keeping that thing around for 7 years.
I guess we'll have to stick with Windows :(
Regards,
Shawn
I believe there is a tool called Backup Migrator that can do automated,
hands off migrations of legacy data. There is an initial policy setup
stage then the appliance moves the data between the environments.
Meaning the old environment can be decommissioned.
Ian Smith
-Original
I know performance benchmarking is an art. And asking questions like
how can I test this new storage may bring a smile on face of some of
you. But still...
The time has come and I need to replace the disk storage underlying
the DB/DISKCLASS/FILECLASS files. I'm going to test two storages from
What I did recently was to load a production DB on the test server and run my
series of tests. Then reloaded the DB, changed stuff and run again. It sounds
like you are setup to do that.
For comparison, I noted the run time for expiration on the production and test
systems to estimate an
You could store a DB tape with the NAS tapes.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Shawn
Drew
Sent: Tuesday, August 04, 2009 9:46 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Change TSM Platform
You will have to
You are exactly correct: modeling what will be rather than what is can be
tricky. The problem really boils down to not having enough data to really play
with it adequately.
I can tell you from experience on probably 200 TSM servers (Windows 2003 based,
which is just fine all of you AIX
What is the concern with keeping a Windows TSM platform (I sat in the weeds on
this as long as I could)?
Kelly Lipp
CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777 x7105
www.storserver.com
-Original Message-
From: ADSM: Dist Stor Manager
Do I understand you to say you have to keep your NDMP backups around for
7 years? The tape media isn't even meant to last for 7 years. Do you
have customers that actually think they will need 7 year old copies of you
NAS data? That's a tough requirement.
I thought I'd change this to a new
Just a standard.
All of our TSM servers are based on AIX in our main data centers. We
recently took control of a branch location who has been running on
Windows. We are spending a disproportionate amount of time to get our
automation, and everything else, to work with Windows just for this
In here, we use something like this:
Exclude *
Exclude *:\...\*
Include C:\test\...\*
Exclude.dir C:\[a-s]*
Exclude.dir C:\[u-z]*
Tha way, we exclude from processing the other unwanted directories of the
drive C:
On Fri, Jul 24, 2009 at 9:58 AM, lindsay morris lind...@tsmworks.comwrote:
Wanda
Perfectly rational! That one I can get behind...
Kelly Lipp
CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777 x7105
www.storserver.com
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Shawn
Drew
Sent: Tuesday,
Only 7 years? We're in Healthcare. Seven is usually the minimum.
If you're talking Minors, then it is 18+7= 25 years. Digital Mammography
Research-related electronic medical records are FOREVER. There are lots of
numbers on time-retention floating around out there - it just depends on the
Questions flood into my head along the lines of 'what's the difference
between a backup and an archive' (obviously not in a TSM sense) and if/
how should they be treated differently practically with TSM (e.g. a
seperate TSM Server instance for archival purposes, as some places do
etc).
/David Mc
On 4 aug 2009, at 19:56, David McClelland wrote:
Questions flood into my head along the lines of 'what's the difference
between a backup and an archive' (obviously not in a TSM sense) and
if/
how should they be treated differently practically with TSM (e.g. a
seperate TSM Server instance for
There is a huge difference between backup and archive, especially with TSM.
One can actually make them different in TSM.
The keys to effective archiving are three fold:
1. Only archive that which you are legally (or for business purposes) required
to archive and then for only the time
Specifically TSM-related Archive vs Backup - We found this out the hard way
also...
A 350GB database for TSM 5.1 on a Windows 2000 Server (w/ LTO2) that did ARCH
BACK was painful.
We do have a dedicated TSM-Archive server, now, on AIX LTO4 with only a few
nodes, but the database is still
Anything wrong with running these scripts etc. on an AIX server and just
point your dsmadmc's to the windows TSM server?
Steven Langdale
Global Information Services
EAME SAN/Storage Planning and Implementation
( Phone : +44 (0)1733 584175
( Mob: +44 (0)7876 216782
ΓΌ Conference: +44 (0)208 609
Shawn,
You've probably already looked at this, but if you want to stick
with shell programs without having to rewrite, we have had good success
with Cygwin, a free Windows package that includes pdksh (public-domain
korn shell), and all the goodies that a Unix guy likes; grep, tail, cut,
mail,
Thanks! You made me a bit more confident and feel more assured about
my plan. And thanks for reminding about DB audit, it's a good
measuring stick indeed!
--
Warm regards,
Michael Green
On Tue, Aug 4, 2009 at 7:35 PM, Huebner,Andy,FORT
WORTH,ITandy.hueb...@alconlabs.com wrote:
What I did
Here is a suggestion for proper auditability of ISC-AC based TSM
administration:
1) create an ISC ID for each TSM administrator
2) create a TSM admin ID for each TSM administrator and grant auth ...
cl=sys
3) have each TSM administrator add their server connection on the ISC
(under Manage Servers
Great information Jeorg, thanks
One issue that I found with older versions of ISC was that there seemed
to be no easy way to preserve/copy/update the ISC security information.
It was its own island and I also found it for the most part
incomprehensible. That may just be because I did not take
24 matches
Mail list logo
