This is my last day at ICF, and the first day of my retirement!
I'm moving on to the next non-IT-support chapter in life.
I can't speak highly enough of the people who give of their time and expertise
on this list.
I've learned most of what I know about TSM here.
You all are an amazing
Zoltan,
If you are talking about Windows domains, it's all about permissions.
If you are talking about TSM domains, it's all about retention/backup copy
groups.
Which kind of domain are you referring to?
Wanda
-Original Message-
From: ADSM: Dist Stor Manager
Yep.
From Windows you can use a CIFS share, or from Unix an NFS share.
TSM Windows services have to run under a network account, not a local account,
but that's easily fixed.
Then your DEFINE VOLUME commands (from Windows) just use UNC names instead of
X:\ local drive names, like this:
define
Don't see the purpose of renaming it--
If you just do:
exclude.dir e:\data
That has the same effect.
It excludes them from backup, the existing backups get marked inactive on the
next backup run, and the countdown clock starts for the number of days to keep
the last version.
If it's a lot
Also an interesting contradiction, since in Windows this type of change *does*
trigger a new backup.
Massive ones. Which is then its own problem.
Wanda Prather
TSM Consultant
ICF International Enterprise and Cybersecurity Systems Division
-Original Message-
From: ADSM: Dist Stor
Rick,
It's a problem, everywhere, no matter how you do it.
* The simplistic answer to your question is yes; the external scheduler
is running a list of tasks; after the last task it could call a
perl/ksh/python/yourfavorite script that invokes dsmadmc and does a
delete/define schedule
We had a situation yesterday where 2 VE backups were causing the VM's to go
unresponsive. No response to ping, unable to RDP, etc. As soon as the
backup finished (or was killed in one case), the servers picked back up where
they left off. They never rebooted, but you can actually see in the
class is valid and and when I query the copy
group it is STANDARD. Now, the documentation says that it must be
STANDARD but this doesn't make much sense to me.
Thanks,
Eric
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf
Of Prather, Wanda
McWilliams
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Thursday, March 05, 2015 10:48 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] ANS4174E error
Well, your Q CO shows that you have a management class VMDATA, and it has
There's no mention of pagefile 'awareness' in the documentation, so it's safe
to say that the backup will consist of all changed blocks, regardless of
what's stored on them.
Ditto. We've found that that the backup GB per day for VE can be significantly
higher than it would be if the machines
You are correct.
With TSM/VE, you can only exclude at the hdisk level, or the VM level.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Schaub, Steve
Sent: Thursday, February 26, 2015 10:27 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM
Each backup session backs up some control information, and that information is
restored for use during the next backup. (You can see the restores happening
if you watch the server during the backup, or if you look in the accounting
info.)
I'm just guessing, but I suspect that the data
@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Wednesday, February 25, 2015 12:32 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] ANS4174E error
Each backup session backs up some control information, and that information is
restored for use during the next backup. (You can see the restores happening
Probably just bad luck….
When I set up FILE pools for customers, I usually have to tweak them a couple
of times to get the sizing right, depends on the load, the number of concurrent
sessions, etc. Been there, done that, got the scars.
Assumptions you should change:
• Unlike a disk
Perhaps someone put these into a client option set?
Q NODE nodename F=D
Look for optionset:
If it's non=blank, then you need to investigate the contents of the optionset,
that's where your conflict is coming from.
If that is not revealing, from the client machine:
start the command line
should
have hired you instead!
- - - - - - - - - -
Kevin Kinder
State of WV
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Friday, February 06, 2015 3:30 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Duplicate
to dive into the registry?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Friday, February 06, 2015 2:22 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Duplicate include/exclude option error
Perhaps someone put
TSM 6.3.4 on Win2k8-64
Exchange 2010 on Win2k8 64
This is not a show-stopper, just in the annoying and mysterious category.
Installed Exchange 7.1.1 TDP for a customer today.
The beautiful FCM interface popped in all the pre-reqs, VSS testing ran, I set
the appropriate passwords and proxy
The bug is IT02929; for us it affects Exports as well as restores (so I'm
guessing would affect backupsets as well).
And yes, hits any copypool, LTO or not.
OTOH, it's not necessarily hard to live with, depending on your situation.
More details of that below.
What you get with 7.1.1 that may
FWIW,
I've also been through a lot of problems with dedup, it has been disappointing.
On TSM servers not using dedup I haven't seen many problems at the latest
levels.
Curious to know what you just installed?
On 7.1.1 on Windows, select * from processes works just fine...
Wanda Prather
TSM
Hi Jeanne,
We are in a transition as the OC is getting more function with each release,
but doesn't yet have everything the AC had.
The OC is the new/current admin GUI. The 7.1.1 version has client scheduling
in it now, so it can do more of the admin tasks you need.
In the 7.1.1 version you
Hm. TSM 5.5.
Reinstall Windows
Reinstall TSM
It will create a tiny db and tiny disk pools by default.
Look at the dsmserv.dsk file; it will point to the new DB and log.
I would try doctoring that file to point to the original DB and logs, then
restart TSM and see if it will talk to them.
Oh yeah,
after you reinstall Windows TSM, you'll need to reinstall your tape driver,
whatever that was.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Tuesday, January 27, 2015 1:41 PM
To: ADSM-L@VM.MARIST.EDU
Subject
.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Wednesday, January 21, 2015 5:53 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM on Linux Box
Dunno what version of the client you are installing, or what version of Linux
for linux right now.
But I will find the redhat book for 6.4.1 and see there in instructions for the
auto startup.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Wednesday, January 21, 2015 5:53 PM
To: ADSM-L@VM.MARIST.EDU
That message ended up missing a CR ; should have been:
chkconfig --add dsmcad (that's a space and 2 hyphens)
service dsmcad start
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Thursday, January 22, 2015 10:05 AM
book for 6.4.1 and see there in instructions for the
auto startup.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Wednesday, January 21, 2015 5:53 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM on Linux Box
Dunno
Dunno what version of the client you are installing, or what version of Linux?
But the client manual says how to do it on Linux now if it's relatively recent.
All I do on Redhat is follow these instructions from the book below.
I do the :hkconfig --add dsmcad (those are 2 hyphens), then
TSM 6.3.5 on Windows, LTO6 drives in a TS4500.
Customer had an LTO4 drive go bad and damaged a dozen tapes (maybe more!)
before we figured out which one was doing it and mothballed that drive.
Now trying to MOVE DATA, restore vol, audit, restore stgpool and otherwise fix
the damaged tapes using
Thank you Kurt for that information!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of BEYERS
Kurt
Sent: Monday, January 19, 2015 11:21 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] ANR1890W root-only restriction message
Hello everybody,
Please
My reading of that technote is that the *first* backup will include all
allocated space rather than just the used space; but that subsequent backups
will use CBT and be true incrementals (and the extra allocated space will all
be empty, so it should compress or dedup out).
If you are getting
Oooh, that's evil.
Had a consult with the in-house DBA.
This works for me on V7.1.1:
select count(*) from nodes where node_name not in (select node_name from
filespaces where node_name is not null)
In V6-7 there is 1 filespace with a NULL node name - looks to me like something
created by
level now; so you
still get only 1 stream if only 1 filespace left to be migrated.)
Big help for our environment.
W
-Original Message-
From: Prather, Wanda
Sent: Tuesday, December 16, 2014 3:33 PM
To: 'ADSM: Dist Stor Manager'
Subject: Filespace level migration? was: breaking up tsm
There are 2 GUI's for 7.1.1.
On the system where TSM for VE is installed,
If you do start programs Tivoli Storage Manager TSM for Virtual
Environments,
you will see there is a TSM for VMWare UI, and also the TSM Recovery
Agent 7.1.1
The TSM for VMWare UI doesn't have all the VM-level
Didn't I read that there were supposed to be changes in the 7.1 server to make
migration run at the filespace level? Which would make this a multi-thread
process - anybody with experience? I have a 6.3.5 customer with the same
issue, but don't have a 7.1 customer in production to verify.
And you can do Windows to Unix flavors!.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven
Langdale
Sent: Monday, December 15, 2014 11:22 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Client node replication
No they don't. I have
I've never had a problem defining multiple TSM (logical) libraries on one
device address (but I can't say I've tried it since 6.2, and that was on
Windows).
What you can't do is have one device class pointing to 2 different libraries,
so you'll also have to do some juggling there, create some
Does IBM have some document or website that describes the future of
Administration Center?
Don't know where to find the document, but have been told in presentations:
Will it ever be upgraded to keep in lockstep with the TSM version and
functionality?
No. It is stabilized at 6.3.4, but if you
Hi Thomas,
I agree, don't even think about using dedup at 6.2.5. Too many performance and
data handling bugs.
We're deduping 4.5-5 TB a day (Windows TSM server) and even had issues at 6.3.4.
Have seen no issues at all so far at 6.3.5 (and it should be easy for you to
get there from 6.2.5).
W
We had the same problem on TSM 6.3.4 on Windows, never found out why.
Stopped using archive overflow because of it.
Once the DB backup is done, just delete the extra files.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Roger
Deschner
Sent:
It's awful.
Only saving grace in my case is that the data is mostly images and doesn't
change much.
I assume you've had experience setting up proxy relationships -
use many proxy machines to back up the individual shares on the Isilon, so you
can have them all working at once.
Then back up
a dumb server to act at the backup box for the CIFS shares
like we do with lots of other EMC storage/mounts (we have one right now running
40+ TSM node/clients purely for CIFS backups). As for *NIX users/mounts, no
idea how they want proceed on that.
Z
On Fri, Nov 21, 2014 at 12:59 PM, Prather
it would be other
than a 2nd or 3rd safety-net..
Anybody out there using FastBack BMR?
On Wed, Nov 19, 2014 at 12:49 PM, Prather, Wanda wanda.prat...@icfi.com
wrote:
Fastback is also a separate server, which backs up to disk only.
It uses your regular TSM server to replicate to, but it's
Fastback is also a separate server, which backs up to disk only.
It uses your regular TSM server to replicate to, but it's really reinventing
the wheel if you already have regular TSM clients in place.
Fastback BMR isn't something you add on to your normal TSM clients.
-Original
115 is just a failure to snap.
Log on to Vcenter and see if you can snap it manually from VCenter.
If it won't snap from Vcenter, TSM can't snap it either, and you will have to
treat it as a VMware problem.
If it will snap manually (and I'm assuming this is a Windows guest), then the
problem
Del,
Can you elaborate a little more?
How is the separate invocation as you showed below different from doing
TDPEXCC BACKUP * FULL /MINIMUMBACKUPINTERVAL=720 /PREFERDAGPASSIVE
?
Thanks
Wanda
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Correct.
You can do a VM full backup with the basic client, without TSM/VE.
For incremental forever you need the VE license.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tom
Alverson
Sent: Wednesday, October 22, 2014 6:36 PM
To:
Did you upgrade VE to 7.1.1 first?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tom
Alverson
Sent: Wednesday, October 22, 2014 10:11 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM for VE 7.1.1 upgrade question
I have a number of data
Hi Martha!
Has the storage pool been backed up to a copy pool?
If the DEDUPREQUIRESBACKUP option is set to YES (default), reclaim can't happen
until the BACKUP STGPOOL is done.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Michael Roesch
Don't believe that.
I have seen it before - if you can do a MOVE DATA, it isn't really empty.
I think it has to do with dedup.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Martha
M McConaghy
Sent: Wednesday, October 22, 2014 1:06 PM
To:
I believe it will be the default management class of the domain where the data
lives when expiration runs, not the domain where it originally backed up.
So your first idea will work.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Hanover,
Please join us Weds, Nov 19, 2014 for the next meeting of the
Baltimore-Washington-NoVa TSM User Group
We have a lot to talk about! Tentative agenda:
TSM 7.1.1 Enhancements and Tips - Ken Bury, IBM
TSM Operations Center Update and Demo - Tivoli Development
TSM Cognos Reporting
TSM 6.3.4 on Win2K8 64
Trying to run the upgrade to 7.1.1, the package fails after uninstalling 6.3.4
and DB2 and fails during the DB2 install.
Message:
ANRI1020E The DB2 installation failed. To review errors and correct any issues,
review C:\ProgramData\IBM\Installation
TSM 7.1.1 on AIX
So I have a customer putting in a VTL, which will have 96 virtual drives.
Those virtual drives will be spread across 4 HBA's.
What sort of strategies to people use to keep TSM from starting a BACKUP
stgpool process and picking 4 virtual drives all on the same HBA?
Is it
... drive 5
on hba 1 and so on). I prefer doing this at VTL level using mapping policy (i.e
access groups on Data Domain).
Le 13 octobre 2014 18:28:36 CEST, Prather, Wanda wanda.prat...@icfi.com a
écrit :
TSM 7.1.1 on AIX
So I have a customer putting in a VTL, which will have 96 virtual
drives.
Those
Just pointing out a more common use of maxscratch that I see at smaller
customers, which is in conjunction with collocation.
If you have collocation set to node (or filespace), then TSM is going to try
and put each node (or filespace) on a separate cartridge.
So if you have a smaller library,
There are reports in the TSM/VE plug in that will show you that stuff.
But if you want to create your own reports, simple way is to use the timestamp
on the filespace:
Backup status of all your VM's in TSM/VE, order by name (1) or timestamp(3) as
you want :
select substr(filespace_name,9,18)
No problems with the export/import.
But,
if you are talking about encryption that is done by the TSM client, it is
encrypted before being sent to the server, and when it's transmitted to the new
server it will still be encrypted.
If you are talking about the TSM server managing encryption
The first and last ones are the new ones. If you don't see them, then I suspect
that the upgrade did not complete as expected.
Thank you,
Del
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 09/25/2014
07:12:11 PM:
From: Prather, Wanda
They used to tell us that for the V5 DB.
I think it went away with TSM V6. You would have to ask a DB2 person how to go
into DB2 and look there.
And the problem there, a bunch of the tables are created on the fly, so I don't
have a clue how you would find those.
Anybody got a DB2 DBA in the
Upgraded from TDP for Exchange 6.4 to TDP for Exchange 7.1.1
Exchange 2010, Windows TSM server 6.3.5.
The doc for 7.1.1 says:
The following parameters are available options in the MMC when you select Show
Restore Options from the Recover tab:
- Set the /KEEPRDB parameter option to Yes to retain
The ISC is on the FTP site, under Maintenance\admincenter.
But I don't recommend it.
You should know it has been stabilized at 6.3. There is a 7.1 version on the
site which has been patched to work with a 7.1 server, but it has no 7.1
function and it will never be updated any more.
It also
not been updated with 7.1.1 informations yet.
Le 23/09/2014 19:17, David Ehresman a écrit :
Can the 7.1.1 OpCenter be run with pre-7.1 servers?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf
Of Prather, Wanda
Sent: Tuesday, September 23, 2014 12
Of
Prather, Wanda
Sent: Tuesday, September 23, 2014 3:00 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: tsm administration via web
For all the things they are adding into the TOC (TSM Operations Center), they
had to add new tables and functions in the TSM server itself (Which is why it
has some cool stuff
in the -DBYPASS_TSM_REQ_CHECKS=true flag is required and must be
added on a new line after the -vmargs flag.
../Installation Manager/eclipse/ibmim.ini
Erwann
Le 23/09/2014 21:52, Prather, Wanda a écrit :
For the 7.1 package there is a parm to bypass the min requirements on
install, I'll see if I can find
Been there done that.
BACKUP STGPOOL for a sequential-dedup-pool-which-hasn't-deduped-yet performance
is a nightmare.
Have been fighting this for a year.
We ingest and dedup 4-6 TB of data per day, in a 45TB sequential pool.
We had to back off and land the data on a random pool, backup stgpool
http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=ANsubtype=CAappname=gpateamsupplier=897letternum=ENUS214-340pdf=yes
Wanda Prather | Senior Technical Specialist |
wanda.prat...@icfi.commailto:wanda.prat...@icfi.com |
www.icfi.comhttp://www.icfi.com/ | 410-868-4872 (m)
ICF
=wLQwo6jEM4gBohY6PaUggUKrw4TZKeuDMgOs7FtRQdQ%3D%0As=37a9c6f9d2e7c472c894e68ee88ab04eb74a4c87016a83326c058eb0e36cd30d]
On Behalf Of Prather, Wanda
Sent: Tuesday, 26 August, 2014 12:05 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups
That usually means your activity log is enormous
It's not the schedule.
There are several things that can cause VE to do the whole enchilada, rather
than only the used space.
One I specifically remember is you have to be at Hardware level 7 on the VM;
another is a missing license file for VE.
And there are also some VM's guests where VMware
What version of TSM?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim
Brown
Sent: Tuesday, August 26, 2014 10:21 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] tsm archive log full, causes repeated backups
ANR0299I A full database backup
] tsm archive log full, causes repeated backups
6.3.1
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Tuesday, 26 August, 2014 10:42 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated
Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Tuesday, 26 August, 2014 11:16 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups
You could have a reorg running and pinning the log.
Try: q
Yep.
It's not export to tape, but to sequential media. So anything you set up
as sequential media will work.
You'll need to create a devclass of type FILE that points to the directory, and
use the filename as the volume name to export to.
(I think it's actually easier to just create the
At Edge the target was 3rd quarter.
So worst case, 9/30 23:59? :)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bill
Boyer
Sent: Tuesday, August 19, 2014 11:39 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] ETA on V7.1.1 Server?
I know it
Thanks.
If you would post the APAR # back here when it becomes available, I would
appreciate it.
Wanda
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bent
Christensen
Sent: Tuesday, August 19, 2014 6:28 AM
To: ADSM-L@VM.MARIST.EDU
Subject:
The estimated capacity shown in Q STGPOOL output is pretty much
useless/misleading for sequential pools, as it's based on the MAXSCRATCH value
for the pool, plus other factors.
See the admin ref pages for Q STGPOOL output field descriptions.
W
-Original Message-
From: ADSM: Dist
@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Monday, August 04, 2014 11:04 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Exchange TDP and Export weirdness
- it's a primary volume
- what TOC/metadata would be called for by an EXPORT of 1 Exchange TDP
filespace?
I've done a select
We have about the same number of virtual machines, and use 1 VM as a datamover.
It's on a 10G network, we move about 4 TB of incrementals per night.
The TSM for VE plug in creates the schedule as you show below. But as you
said, that becomes unwieldy when you have a lot of VM's..
You aren't
TSM server 6.3.4 on Win2K8 64
Exchange 2010 in a DAG configuration, 22 DB's
TDP for Exchange 6.4.0
We run fulls on Saturday, incrementals Sun-Fri.
Trying to Export a set of Exchange backups for *one* DB/filespace to sequential
media for legal hold.
Here's the command:
EXPORT NODE x-dag1
@VM.MARIST.EDU] On Behalf Of Grant
Street
Sent: Monday, August 04, 2014 9:24 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Exchange TDP and Export weirdness
On 05/08/14 07:14, Prather, Wanda wrote:
TSM server 6.3.4 on Win2K8 64
Exchange 2010 in a DAG configuration, 22 DB's TDP for Exchange 6.4.0
We
Yup.
I haven't had this problem with Win2K8 yet, but had it all the time on Win2K3.
And we do exactly as Karel said, use a presched .cmd file to dump the system
state to a flat file, then add DOMAIN -systemstate to the dsm.opt file so TSM
won't call VSS to do the system state backup.
Only
39 is actually not a great number; it means you are getting less than 2 for 1
dedup.
Unless you have backups running hard 24 hours a day, those dedup processes
should finish.
When you do Q PROC, if the processes have any work to do, they show as ACTIVE,
if not they show IDLE.
I'd think that
Hi Bill,
The AC only supports IE7 and IE8.
Some parts of it work with IE9, and some don't.
Try this:
Press PF12
That brings up the IE9 debug window
Change both Browser and Document mode to IE8 emulation; if that doesn't' work
try IE7 emulation.
(On some machines I get *faster* response with IE8
DB2 doesn't know whether it's an actual LUN or not.
It only sees the filesystem.
Whether you use dedicated LUNs is a performance question.
On XIV type disk where I/O is striped every which way and everything is
spinning all the time, it's a whole different question than if you put 8
filesystems
Interesting point about NDMP and dedup.
Do you have any experience with it? What kind of dedup ratios did you see?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven
Harris
Sent: Tuesday, July 15, 2014 9:48 PM
To: ADSM-L@VM.MARIST.EDU
Does anybody have the APAR number for the PASSEXP problem so I can track it?
Thanks
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Matthew McGeary
Sent: Monday, June 09, 2014 10:45 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM 7.1
I have been asked to evaluate the possibility to take a backup from AS/400
(Power720 - v6.1) to TSM (I don't know anything about AS/400). I looked on
the info and I understand we need something called Backup Recovery and Media
Services for iSeries, I have a few questions:
Been there done
Hi Eric -
Was it a real write error like:
ANR8302E I/O error on drive DRIVE1 (mt0.0.0.5) with -blah- blah -
ASC=FF, ASCQ= FF, -glub -
Or an unexpected error like an ANRD?
TSM believes that VTL drive is a real tape drive.
And like you, I would expect a legitimate error to result
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hans
Christian Riksheim
Sent: Tuesday, June 10, 2014 8:47 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Restoration Issue in TSM 5.5...
My advice is to not use the GUI. Until IBM eventually
6f296118347a4790852b702466fc6...@vnucitex01.icfi.icfconsulting.com
09256cd9e51ddf4b95f213e986079ca0b476d4a...@dklyexmbx00.cowi.net
5acf24a680df4b4e8bba94b17bf19...@vnucitex01.icfi.icfconsulting.com
Just trying to get a clean email.
Seriously, there is nothing in here that should cause a barracuda to burp.
b017550e05e94becb7d86ca4e5406...@vnucitex01.icfi.icfconsulting.com
56f70b86c212874c8004d9b06992637d13cdb...@dss218.ap.cdc.fr
In-Reply-To: 56f70b86c212874c8004d9b06992637d13cdb...@dss218.ap.cdc.fr
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thanks for the warning; I wasn't aware of this and it's going to save me some
grief!
I just looked in the client install guide, and it says As part of the Windows
client installation process, one or more Microsoft C++
redistributable packages are installed, if they are not already installed on
:32 AM
To: Prather, Wanda
Subject: RE: [ADSM-L] TSM 7.1 and dedup chunking issues
Hi Wanda,
The below is what got through of your response to TSM 7.1 and dedup chunking
issues on the TSM list server :-)
It is really a pain that you don't receive a copy of what you put up on the
list
CAD2=wjk_embayrbrahmefkntw87csy_1qnmyq1g+e7jpyax...@mail.gmail.com
09256cd9e51ddf4b95f213e986079ca0b476d4a...@dklyexmbx00.cowi.net
In-Reply-To: 09256cd9e51ddf4b95f213e986079ca0b476d4a...@dklyexmbx00.cowi.net
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
You are saying there must be FOUR healthy copies (primary + more than 2
replicas) to skip integrity check? - seems like overkill:
http://www.mail-archive.com/adsm-l%40vm.marist.edu/msg90709.html
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
That will work.
But, if they really want *all* non-pst files bound to the new mgmt. class, just
change the copy group/retention settings for the default mgmt. class.
Then all you need is:
include ?:\...\*.pst meager-mc
That would have a slight advantage, in that files that are inactive
I agree.
As long as there are lots of JC tapes on the scratch list, I believe the
default algorithm is to round-robin the scratch list, so the old tapes that
free up will likely be at the bottom of the scratch list and will likely not
get used before you check them out.
And I like the idea of
Install the TSM Operations Center 7.1 when you install the 7.1 server.
(Not available with 6.2)
Very small footprint, free with the server.
Here's a video demo:
https://www.youtube.com/watch?v=5l0wtmCmwkA
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
Rename the systemstate filespace on the server end to something else, I think
will take care of it.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Swartz, Jerome
Sent: Wednesday, June 18, 2014 5:01 AM
To: ADSM-L@VM.MARIST.EDU
Subject:
1 - 100 of 2096 matches
Mail list logo
