e not gotten that error
message since it was applied (about 6/18).
Bob Levad
system becomes unavailable for whatever
reason. Perhaps in some future version of TSM, a flag could be added for
each domain statement to fail the backup and keep the previously stored data
unless something explicit was entered to confirm the intent to expire.
Thanks for listening...Any thoughts?
ou never see.
[RC]
On Sep 21, 2007, at 2:22 PM, Bob Levad wrote:
> Greetings,
>
> I know this is "working as designed", but I was hoping someone might
> have a work-a-round.
>
> Several times over the last 10 or so years, we have had file systems
> on servers cause
I've scheduled this script to run every day to keep an eye on our volumes.
I don't look at all of it every day, but if there is a problem, I can
usually find the cause in the output. NOTE: YMMV and PLEASE test the
sections in your environment to see how much cpu and time the queries may
take.
Bob
NOTES:
These may run for a while. Watch for wrapped lines to fix.
In the first query, watch for Number of Groups greater than 1 when the
storage pool is supposed to be collocated by group.
In the second query, you will see a line item for each group on each tape.
All of our nodes belong to a
select DISTINCT (100.0*(Select count(*) from events where scheduled_start
>current_timestamp - 1 day)/(Select count(*) from events where status not
like '%Completed%' and scheduled_start >current_timestamp - 1 day)) AS
"Percent" FROM events
-Original Message-
From: ADSM: Dist Stor Manager
Use caution when restoring the DB!!
Any other changes since the DB Backup will be lost if you restore the
database.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Anderson Douglas da Silva
Sent: Wednesday, May 27, 2009 3:58 PM
To: ADSM-L@VM.MAR
Wanda,
We actually tried 2 TS3100s in a test recovery. It didn't go very well.
If you attempt it.
The Gresham product should be able to present 1 library image to TSM. I
don't know at what cost.
Without Gresham:
Make sure your incremental DB backups are directed to disk or someplace
other
Zoltan,
In playing with various DR scenarios and working through occasional hardware
problems, I found it difficult to get all the right commands entered
correctly and in the correct sequence and with the library/drives in the
correct states so I created scripts that delete and re-define everythin
ly 13, 2009 9:13 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Replacing tape drives (or "there has to be a better
way")
So, are you saying that I always need to delete and redefine all connections
to the drive being replaced?
I have just tried this and will see if it works.
From:
I think you'll need a separate query for each utilization range.
At least, I haven't thought of a good way to iterate.
select stgpool_name, count(*) as "60% < utilized < 70%" -
from volumes -
where devclass_name='LTOCLASS4' -
and pct_utilized>=60 -
and pct_utilized<70 -
group by stgpool_na
Mario,
Based on your server level (5.5) you may be experiencing the following:
IC57855: TSM SERVER DELAYS TRANSACTIONS BY 1 SECOND WHEN RECOVERY LOG
UTILIZATION EXCEEDS 80% RESULTING IN PERFORMANCE DEGRADATION
Please check your recovery log utilization to see if this may be the issue.
With only
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
dri
TSM Version 5.5.2 on Windows
I have set up two active data pools (one physical-LTO4 and one virtual-LTO2)
for a group of nodes. When a restore is requested by the client, the active
data on the physical tape is usually mounted. Since I have set up
collocation of the virtual tape by node and I ha
yahoo.com>
<1c63ffb4e7581f4e9cb6476a096367f788b0848...@a2xmxs1v1.a2x.lan.at>
<2266722b-923f-40bb-a65e-ac6be2747...@bu.edu>
X-ASG-Orig-Subj: RE: [ADSM-L] AW: [ADSM-L] AW: [ADSM-L] Deleting EXPORT tape
Subject: RE: [ADSM-L] AW: [ADSM-L] AW: [ADSM-L] Deleting EXPORT tape
Date: Thu, 7 Jan
Hi George,
When you get behind with reclamation, you end up with many volumes with low
util/high reclaim values. TSM trys to minimize tape mounts by reclaiming
offsite data from your onsite tapes without too many remounts, which can
pull data related to several/(or many) offsite volumes. You can
We do multiple queries, activity for today, today-1, today-2, etc.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
yoda woya
Sent: Tuesday, March 16, 2010 2:41 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] issue with sql syntax in TSM databas
You could look into a virtual library manager. Gresham
(www.greshamstorage.com) I believe has a product that will present multiple
libraries to your system as if they were one.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Christian Svensson
S
DELETE VOLHISTORY type=backupset volume=xx force=yes
todate=today
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Mario Behring
Sent: Friday, April 16, 2010 10:03 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Backupset removal from Vo
This would possibly be a good thing to do for an offsite recovery server
with access to replicated TSM data.
One problem with using TSM for this is files that have been deleted from the
original server. You'd need to determine which files have been deleted from
the source server so you could do th
All good advice. I would add a couple of points:
When checking performance on a VTL (especially deduped) be sure to check
both write and read speeds. Some VTLs will ingest very well, but when you
are running reclamation or large restores (especially multiples), you may be
limited by the re-hydra
Here is a how-to on restoring a complete system. Good luck!
Modified Instructions for Complete Restores of Windows Systems with the TSM
Client:
Bare Metal Restore (BMR), System State Restore, Windows System Object Restore
https://www-304.ibm.com/support/docview.wss?uid=swg21164812&wv=1
-O
There is no reason a single library can't have multiple device classes.
If I thought I would ever need to run multiple libraries, I'd be tempted to
create multiple device classes, one per tape storage pool.
Then if it ever became necessary to move a pool to another library, it would be
a simple
Do a Q DRMSTATUS to ensure the correct pools are listed for primary and copy
pool.
Update if it is not correct:
SET DRMPRIMSTGPOOL
And
SET DRMCOPYSTGPOOL
Bob.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Moyer,
Joni M
Sent: Tuesday, Au
Greetings,
I am looking for a recommendation and/or information on using a TSM 6.2.3
deduped file pool as storage for Content Manager for Multiplatforms.
We stored 12GB of PDF data from our old CM server into the new CM server which
uses TSM for storage. Once the data hit my file pool, dedupe o
I've not tested the product, but Gresham Storage (www.gresham-storage.com)
sells something called Clareti Backup Virtualization which is supposed to
offer the look and feel of single large virtual library with multiple
smaller physical libraries on the backend.
I've also considered (but not implem
HI-MB.w i le!
<[EMAIL PROTECTED]><[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>A<[EMAIL PROTECTED]><[EMAIL
PROTECTED]> <[EMAIL PROTECTED]>
X-ASG-Orig-Subj: RE: [ADSM-L] Question about group collocation
Subject: RE: [ADSM-L] Question about g
Our biggest restore failure was for a small windows domain controller. It
was not replicated and we were slightly backleveled on the client. When the
vmware disk became corrupted, we had to rebuild the client list as we were
not able to correctly restore the active directory. The moral is to kee
tory?
Even though it backed it up OK?
And was this a known problem with the TSM client?
--
Lindsay Morris
Principal
www.tsmworks.com
919-403-8260
lind...@tsmworks.com
On Dec 15, 2008, at Dec 15, 10:49 AM, Bob Levad wrote:
> Our biggest restore failure was for a small windows domain control
Larry,
Your query works fine if you switch the double quotes to single quotes.
This query will tell you where every node resides.
select distinct vu.stgpool_name, -
vu.node_name, -
vu.volume_name, -
v.pct_utilized -
from volumeusage vu, -
volumes v -
where
Drop the "not" and it will work fine. You might want to order by node_name.
Bob
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Larry Clark
Sent: Wednesday, January 07, 2009 5:57 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Request for som
Kiran,
This worked for me for a backupset. I don't know if it will work for your
particular case. The volume was a FILE type volume that no longer existed.
DELETE VOLHISTORY type=backupset volume=D:\88894302.OST force=yes
todate=today
Bob
-Original Message-
From: ADSM: Dist Stor Manag
If you are only occasionally moving old volumes, you could just run a script
that builds the command and manually paste it to the command line.
select volume_name, date(last_write_date) as "Oldest Volume" from volumes
where last_write_date=(select min(last_write_date) from volumes)
select 'MOV
Don't forget collocation by group.
All of our nodes belong to one group or another and we can then be pretty
sure that collocation will do what we need. Mostly, our tape pools are
collocated by group. Some nodes are in a group all by themselves and some
(e.g. workstations) have many nodes in their
I am not sure which parms are absolutely required, but this is the command I
used to get rid of an old entry.
DELETE VOLHISTORY type=backupset volume=D:\88894302.OST force=yes
todate=today
Bob.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
KI
Adrian,
We mostly use collocation by group for this issue, but we have upon occasion
done as you suggest and have run a selective to consolidate a particular
client's data. We have also renamed filespaces which forces a "full"
incremental. When we do this, we include the date (as in
\\mynode\c$_
If you change the "period units" to "onetime", the start date will have been
passed and the schedule will not start until you change it back to a recurring
unit. The Period will also change to 0 when onetime is selected, so the
reversal will have to set both back to their original values.
Bob.
James,
set summaryretention xx
Merry Christmas
Bob.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lepre,
James
Sent: Thursday, December 22, 2011 10:05 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Select Statement
Does anyone know how
Check out this deduperequiresbackup information
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=%2Fcom.ibm.itsm.srv.ref.doc%2Fr_opt_server_deduprequiresbackup.html
I think you'll have to run backups of your devt_file before you can reclaim.
Backup stgpool devt_file lto_copy
Greetings!
I'm looking at building a very small TSM environment to support a remote site.
Since there are only a couple of terabytes of data and the change rate should
be only a few hundred gig per day, what I'm thinking of is a TSM server with
about 5TB of internal storage for onsite deduped f
server as a last resort.
Steven
On 22 March 2012 16:29, Bob Levad wrote:
> Greetings!
>
> I'm looking at building a very small TSM environment to support a remote
> site.
>
> Since there are only a couple of terabytes of data and the change rate
> should be only
Yes, but it isn't necessarily a straight forward process.
The tool we use is DELETE VOLUME (volume_name) DISCARDDATA=YES, BUT, and that
can be a big obstacle, we only want to delete data that belongs to the
pertinent node on the volumes.
To accomplish this, we have set up our copy pools and nod
This works for copy pools, but requires that you bring the tapes onsite...not
always an option if you need your DR media offsite.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of George
Huebschman
Sent: Wednesday, March 28, 2012 2:09 PM
To: ADSM
George,
I'm still at 5.5, but I don't believe the requirement that the copypool volumes
needed for a move nodedata job be mountable has changed in newer releases.
If you run it without the volumes onsite, you will get a message for each
needed volume:
"MOVE NODEDATA FROMSTGPOOL=
04/02/2012 0
Another option that may quickly give you some rough information is query
filespace.
A spreadsheet with filespace size times percentage full for the pertinent
filespaces will give you an estimate of the data involved.
This depends also on backup excludes that may be involved.
Bob.
-Origin
If you really want to isolate it, change the IP address to one in an
unused/isolated subnet/vlan and don't give it a route statement. Make sure
DHCP is not enabled on any of your other NICs.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Z
The most obvious reasons would be a tape operator running a check-in script
instead of a label script or checking in with a status=private instead of
status=scratch.
TSM will not initialized a tape with data it knows about, so checking them out
and labeling or checking back in as scratch (which
Greetings!
We are running remote volumes as backups for our TSM backstore of Tivoli
Enterprise Content Manager. We had a damaged volume on the backup system and
audited the volume, which deleted the remote volume containing eCM info from
the tape. I don't see any evidence that the eCM backst
Check your spelling "Sytem State"
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim
Brown
Sent: Monday, November 26, 2012 12:14 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] rename nodes fi for systemstate
I can rename a servers systemstate F
Jerome,
If your cleaning tapes are known to TSM, you'll need to check them back in also
with the number of cleanings remaining.
Q libv CL* f=d should show number of cleanings remaining before you drop
the library.
checkin libv search=y stat=clean checkl=bar clean=<# remaining> will
check in
Gary,
Since you're using backup for archiving, you can route these backups to your
disk/tape archive pools, then you'll avoid having to move the data around much
once it's been saved.
Bob.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Ron
Tim,
I haven't found a direct check, but I kludged this together to accomplish it.
select licensecompliance from status where time(current_time)<'02:00:00.'
if (rc_ok) goto action
Bob.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim
B
Something like this? I haven't tested it, but it should be close.
select current_time from status where time(current_time)>'23:00:00.'
if (rc_ok) goto today
yesterday:
query actlog search= " ane ***" begind=today-1 endd=today begint=18:00
endt=now
goto exit
today:
query actlog search= "
Jeannie,
Current_date, Current_timestamp, and Current_time are not part of any table,
they are SQL variables that can be derived as needed by referencing them in an
SQL statement. The STATUS table in TSM is useful as it only contains 1 record,
other tables will work, but may return many lines
Tim,
The info given by the library should match what q libvol shows. You maybe
should run an audit library to see it clears things up.
Bob.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim
Brown
Sent: Monday, January 14, 2013 11:20 AM
To:
You might try this query:
select cast(vu.stgpool_name as char(9)) as "Pool", -
(select access from volumes where volume_name=vu.volume_name) as "Access", -
cast(vu.volume_name as char(9)) as "Volume", -
cast(count(distinct nd.collocgroup_name) as decimal(4,0)) as "Groups", -
cast(count(distinct vu
We attach the date (as in \\nodename\c$\_20080523) to our old filespaces and
set a tickler for deleting them.
We will also occasionally rename a filespace to force a full backup if a
filespace is becoming too scattered on the offsite media.
We set the tickler a little past when the last inactive fi
A note of caution.
Windows has a way of disconnecting your mapped drives when they haven't been
accessed for a bit. Most programs will force a reconnect, but I've seen on
some systems where the TSM backup expired all the files in an entire
filesystem it couldn't access. You may want to run an au
Analyse collocation status of onsite and offsite media in anticipation of
their need. If you have nodes with data scattered on too many offsite
tapes, it will greatly impact your ability to recover your environment in a
timely manner.
Review, test, and document your recovery plan.
Bob
-Orig
It's a big hammer, but this is the only thing I've found for this type of
thing. It could be made into a separate macro and a series of calls could
be made for each percentage level to test.
/* Display message for DB utilization */
90:
select pct_utilized from db where pct_utilized > 90
if (rc_n
checkout libv ltolib2 100562 checklabel=no remove=bulk
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Timothy Hughes
Sent: Thursday, September 04, 2008 7:37 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Incorrect volume being mounted for reclama
James,
This may not address your specific need, but here is how we handle reclaims.
We are running reclamations about 12 to 20 hours a day.
We check every 15 minutes to see if a any other job is accessing a each
storage pool, then check if an admin schedule called "STOP_PROCESSING"
(which does
I've always liked running with an odd number of tape drives to make it "more
difficult" to busy them all at once. Plus you have a spare for when one is
ACTUALLY down.
Bob.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
lindsay morris
Sent: Tuesday
ther have IBM keep a spare at the depot, instead of paying ongoing
maintenance on one more drive. YMMV.
[RC]
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bob
Levad (641-585-6770)
Sent: Tuesday, November 04, 2008 10:28 AM
To: ADSM-L@VM.MARIST.EDU
HI-MB.w i le!
<[EMAIL PROTECTED]><[EMAIL PROTECTED]>
X-ASG-Orig-Subj: RE: [ADSM-L] Collocation question
Subject: RE: [ADSM-L] Collocation question
Date: Fri, 21 Nov 2008 08:33:30 -0600
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plai
65 matches
Mail list logo
