One of my clients does about that, every night. Call or write.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Paul Zarnowski
Sent: Thursday, April 05, 2001 2:37 PM
To: [EMAIL PROTECTED]
Subject: Re: Amount of Data Backed Up Each Night
At 01:39 P
You can run vmstat periodically (oops - are you UNIX?) and see how badly
your CPU is doing, and whther you're paging or not.
Which leads me to another question --
I have a client with an overloaded server. vmstat shows a lot of paging
activity whenever migration from disk to tape happens. Is t
If you use TSM on AIX, you might look at www.servergraph.com. It has a piece
that tracks the activity log's "client X backed up 4.56 MB" messages and
writes a daily total. Costs money, but there's a free trial.
or you could go through the activity log manually and parse out these
messages...it's
Here's an easy answer that'll work some of the time:
If your organization already has in place a job that archives the necessary
things to microfiche or local tape, etc, just modify that job to write the
archive to TSM instead.
I mean, somebody at some point in your organization did some thinking
The formula, while correct, isn't very useful because nobody really knows
(until they HAVE TSM!) what percent of files get changed. (Or what
retention policies they'll be using...)
I have a similar client whose database is about 10GB.
You can just format space for a smaller one (say 2 GB), then
Are you running reclamation?
Try "upd stgp xxx recl=95". (long-term, use 60, not 95, but for now, that
will tell TSM to copy-and-reclaim only tapes 5% used or less - much faster
than
copying a tape that's 40% used.)
You should see a reclamation process kick off within a minute - it'll want
two
TSM development recommedns using JFS, not raw - but Jack's right, it sure is
quiker using raw.
Anybody have a summary of the pros and cons?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Palmadesso Jack
Sent: Monday, April 16, 2001 4:36 PM
To: [EMA
try putting spaces around it. ie, in dsmadmc, "q this >that" fails; "q this
> that" works.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Gill, Geoffrey L.
Sent: Friday, April 20, 2001 9:59 AM
To: [EMAIL PROTECTED]
Subject: redirecting output
He
You know, you can also say":
q drmedia ... CMDFILE=/tmp/checkout.txt CMD=&VOL&NL
which makes a nice one-volume-per-line files suitable for input to other
scripts.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Gill, Geoffrey L.
Sent: Friday, Apri
Ftp a large file (twice, to ignore disk-to-mem buffering the first time)
between the two suspect systems.
That gives you a network performance reading, while tkaing TSM completely
out of the picture.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
P
I have to agree.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Mark Stapleton
Sent: Thursday, April 26, 2001 12:19 AM
To: [EMAIL PROTECTED]
Subject: Re: Reducing/compressing the database
"Thomas A. La Porte" wrote:
> Is anybody else a little bi
You diskpool may have MAXSIZE set, which means files larger than that "jump
over" the disk pool and go to its NEXT pool.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Sam Schrage
Sent: Thursday, April 26, 2001 10:20 AM
To: [EMAIL PROTECTED]
Subjec
I have used it several times. It usually starts - but it takes a while,
maybe 2-5 minutes.
(Has to be prompted mode, of course. Are you using polling? )
I turned on tracing once to try and see why it would not start immediately.
I found that there was a 30-second timing loop in the server - but
I don't think there's a way. I did a competitive evaluation of ADSM vs
Harbor, a mainframe-based storage manager.
Harbor did have the nice feature that it could make a copy tape on the fly.
But I looked hard for a way to do that in ADSM, and at the time, there was
none. (Though using a disk stora
What command causes this error? I mean, can you do the archive manually? If
so, I guess it's a problem with a schedule parameter, right?
Just need a little more context...
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
MORGAN TONY
Sent: Wednesday,
Hi, Jim. Did you ever get a chance to look at Servergraph? What did you
think?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Jim Taylor
Sent: Friday, April 20, 2001 11:08 AM
To: [EMAIL PROTECTED]
Subject: Presentations
Hello fellow *SMers
I h
ll do know that it's coming, right?!? Future plans include added
replication (e.g., similar to what BackInt already allows SAP dba to do, but
in a LAN-free way for copies beyond the first).
-Original Message-
From: Lindsay Morris [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 01, 20
Hi, Curtis.
Did you ever get a chance to look at Servergraph/TSM?
I'd be very interested in your take on what SAMS has that Servergraph lacks.
The slideshow only takes 10-15 minutes, if you just want the 5,000-foot
view.
Hope to hear from you. Thanks.
-Original Message-
From: ADSM: Dis
Hi, Paul.
Did you ever get a chance to look at Servergraph/TSM, after I sent you the
press reelease last week?
The slideshow only takes 10-15 minutes, if you just want the 5,000-foot
view.
Hope to hear from you. Thanks.
-
Mr. Lindsay Morris
Principal
Applied
Hi, Steve.
Did you ever get a chance to look at Servergraph/TSM, after I sent you the
press release the other day?
The slideshow only takes 10-15 minutes, if you just want the 5,000-foot
view.
Hope to hear from you. Thanks.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMA
Hi, Stephen.
Did you ever get a chance to look at Servergraph/TSM?
I'd be very interested in your take on what TDS has that Servergraph lacks.
The slideshow only takes 10-15 minutes, if you just want the 5,000-foot
view.
I know TDS is free with 4.1, but you still have to buy the supporting
pack
Sorry,all, about the accidental commercial postings about Servergraph. I
clicked reply, and oh,well. Honest mistake.
-
Mr. Lindsay Morris
Principal
Applied System Design
[EMAIL PROTECTED]
Office: 859-253-8000
Fax: 425-988-8478
Performance that bad suggests (shooting in the dark here) that your NIC
might be set to autonegotiate rather than 100mbps.
You might try to ftp a file from your TSM server to its client (i.e., take
TSM out of the picture) and see what kind of numbers you get.
I don't think it's a crappy product.
You activity log probably has some revealing messages.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Jon Milliren
Sent: Friday, May 04, 2001 1:01 PM
To: [EMAIL PROTECTED]
Subject: reclaim spoy stgpool volumes
Hi all,
I have a copy stora
EMAIL PROTECTED]
Subject: Re: reclaim spoy stgpool volumes
Lindsay Morris wrote:
>
> You activity log probably has some revealing messages.
Hi,
Well, the reason I know reclaim didn't kick off was because I
performed
a "q actlog begind=-1". I didn't see anything in
The quote Jack offered is relevant to PRIMARY pools, but not to COPY pools,
I think.
TSM reclaims COPY (off-site) storage pools by using the drives and tapes
available to the PRIMARY (on-site) storage pool.
It can do this because its massive database knows where in the PRIMARY pool
to find a cop
Yes, we are. What do you need to know?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Jeff Bach
Sent: Monday, May 07, 2001 12:04 PM
To: [EMAIL PROTECTED]
Subject:
I need to convert from using Tivoli as an event receiver to using an
in-house produ
explain why it turned off.
Then send us "q stg copypool f=d".
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Jon Milliren
Sent: Tuesday, May 08, 2001 10:21 AM
To: [EMAIL PROTECTED]
Subject: Re: reclaim spoy stgpool volumes
Lindsay Morri
TSM can collocate (i.e, keep on the same tape) all files for one node, or
not. If you tell it NOT to, then a FULL restore can be slow - but full
restores are the exception rather than the rule. A single-file restore will
still be fast.
Not collocating files is good because it lets several nodes
I asked the same wuestion a couple of years ago.
Under older versions of TSM, you didn't want the database to get too large.
On mainframes, it was so you could use multiple virtual machines - something
maybe to do with the TCP/IP bottleneck under older MVS.
Nowadays I don't see why.
-Origin
Well, you're right. Server consolidation is a good thing.
But I usually (for simplicity) try to have one machine with one TSM server
doing all the work. Why do you need several different instances of TSM on
the same box? Why not just have one instance?
-Original Message-
From: ADSM:
r [mailto:[EMAIL PROTECTED]]On Behalf Of
Jon Milliren
Sent: Wednesday, May 09, 2001 9:17 AM
To: [EMAIL PROTECTED]
Subject: Re: reclaim spoy stgpool volumes
Hi all,
Lindsay Morris wrote:
>
> does "q vol stg=copypool" show you any volumes with a "pct util" less than
> 60%?
Sounds clever.
Always lookingfor a better solution, though, I have to ask: if you're rich
enough to have a spare DR box just sitting there, maybe clustering would be
the way to go?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Denis L'Huillier
Se
No offense, Tim, but perhaps you're missing the point of the
incremental-forever scheme.
A good reference is the Tivoli "Storage Vision" whitepaper :
http://www.tivoli.com/products/documents/whitepapers/storage_vision.html
And the section you should read is 3.3.1.1.2 - about three pages worth.
B
This one comes up frequently - but has a request made its way to adsm-r?
"export node allactive preview=yes" comes very close - but it doesn't list
volume names.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Denis L'Huillier
Sent: Thursday, May 1
That's a good reason ( IMHO ).
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Jim Sporer
Sent: Thursday, May 10, 2001 2:28 PM
To: [EMAIL PROTECTED]
Subject: Re: Multiple TSM* Servers On Same Machine
I do it to run a test TSM server on the same ma
I could kind of understand it it the SQLBT backup was causing Sybase to use
more paging space.
It's hard to see how the filesystem's incremental backup could.
Might it be the former instead of the latter?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf
Hi, Ted. Rebook SG24-4632 has what you want. www.redbooks.ibm.com, search
for the number.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Ted Byrne
Sent: Monday, May 14, 2001 9:02 AM
To: [EMAIL PROTECTED]
Subject: 3494 Convenience I/O category
I'm
TSM is liable to report a client "command"-type schedule (as opposed to an
incremental-backup) as completed, when in fact the command failed dismally,
and even returned an error status into the client's dsmsched.log.
The logic is (I guess) that dsmc succesfully issued the command, so the
client s
Notes? Are you using the TDP backup agent, or just the regular filesystem
client(dsmc)?
I assume dsmc.
So, backups happened...
then migration from DPOOL to TPOOL...
And now you're doing a "COPY STGPOOL TPOOL COPYPOOL" and seeing small files.
Well, MAXSIZE=5G means that during BACKUP, files over
ANR8392 includes sense codes (ASC=, ASCQ=xxx), which your hardware
vendor should be able to interpret.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Derek Smith
Sent: Monday, May 14, 2001 2:08 PM
To: [EMAIL PROTECTED]
Subject: ANR error
All,
2001 2:51 PM
To: [EMAIL PROTECTED]
Subject: Re: maxsize threshold for disk storage pools
>-Original Message-----
>From: Lindsay Morris [mailto:[EMAIL PROTECTED]]
>Sent: Monday, May 14, 2001 11:21 AM
>To: [EMAIL PROTECTED]
>Subject: Re: maxsize threshold for disk storage pools
>
Mind posting Phillip's info?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Tab Trepagnier
Sent: Friday, May 18, 2001 1:40 PM
To: [EMAIL PROTECTED]
Subject: Re: Script logic
Phillip,
Thanks so much for the info!
I will try to follow your exampl
= part 1 =
We all have to tell TSM how to do its daily housekeeping.
In 3.1 we used admin schedules;
in 3.7 maybe we supplemented that with server scripts;
in 4.1 the scripts became a little more programmable;
But they're not great. The problems I see:
1. A second admin schedule w
Gee, are you sure?
TSM admin guide says "For the client-polling scheduling mode, you can
specify ... randomize..."
and when I've tried with schedmode prompted, no randomization seems to take
place - all the client sessions start at the same time.
> -Original Message-
> From: ADSM: Dist St
Wow!
You don't really have a million clients, do you?
Were some of those admin sessions?
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Cook, Dwight E
> Sent: Wednesday, May 30, 2001 1:25 PM
> To: [EMAIL PROTECTED]
> Subject: Re: ADSM/TSM mem
Bounce the client. It will then contact the server, and the server will then
know how to contact the client.
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Phillip Guan
> Sent: Wednesday, May 30, 2001 2:48 PM
> To: [EMAIL PROTECTED]
> Subject
1. try "q actlog begind=-2 s=recla" (or maybe s=100 or some other search
string) to see when the reclamation threshold got reset. If you find that
it happened at 15:00, then say "q actlog begind=-2 begint=14:55" to see who
issued what command. That ought to shed some light.
2. I suggest you not
1'21'924'28'88 * K4-117
> email [EMAIL PROTECTED]
> Visit our site: http://www.nestle.com
>
> This message is intended only for the use of the addressee and
> may contain information that is privileged and confidential.
>
>
>
> > -Origin
I've looked at some other TSM forums. Don't bother.
People who have or need knowledge about TSM should go to ONE central place,
right?
Patronizing other forums just fragments the collection of wisdom.
So here we are.
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PR
It's a very common question, though in the US culture direct discussion of
salaries is frowned upon.
(And where did this ethic come from? Management?)
Anyway, search adsm.org for "salary survey" - someone collected statistics
on ADSM admin salaries last year and posted them to a website. I see
maybe EXCLUDE /archive/.../*
maybe "q filespace", and put the filespace in {} (is /archive a filespace?)
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Jeannine Walter
> Sent: Tuesday, June 05, 2001 11:42 AM
> To: [EMAIL PROTECTED]
> Subject
It's bit Rube-Goldbergish:
You have a Domino client node, with a script that will back it up sitting on
the client.
What happens is:
-you make sure dsmc sched is running on that (ie the normal file-system
client)
-you make a TSM server schedule with action=command, object=that clie
And another thing - even without publising dsmsched.log files on a web site,
each client's user can say "dsmc query backup ..." and see if file x has
been backed up, and when; or see all files that have been backedup; or see
how many versions have been backed up, etc.
And Richard is right. But m
I cleaned up just such a posting, and here it is. It's old, though.
From: Doffie Benjamin <[EMAIL PROTECTED]>
Subject: Re: Tivoli TMS (ADSM) vs Veritas Netbackup
To: [EMAIL PROTECTED]
ADSM
Best meets these requirements with an extensive range of features which
provide:
Da
It would be nice to have ONE central repository of wisdom - if we have five,
then it gets fragmented - you have to look on all five for your ansers.
Yuck.
So, what's the BEST AIX listserv? Anybody have enough experience to say?
> -Original Message-
> From: ADSM: Dist Stor Manager [mailt
dsm.sys is only read when the client starts up.
Look at using cloptsets - they are read every time a backup happens, even if
the client SW has been running all week and you changed the cloptset
yesterday.
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Be
TDSfSMA is bundled with TSM 4.1 for free -- but ---
it requires Tivoli Decision Support, which retails at $21,000 or so.
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Pitur Ey~srsson
> Sent: Thursday, June 14, 2001 11:43 AM
> To: [EMAIL PROT
Try the command line: help update schedule.
GUI sometimes has problems.
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Patrick Sheehan
> Sent: Thursday, June 14, 2001 12:05 PM
> To: [EMAIL PROTECTED]
> Subject:
>
>
> Hello TSMer's
>
> I'm try
EMAIL PROTECTED]
> Subject: Re: Tivoli Decision Support
>
>
> Can you elaborate as to what the difference is...
> Are you able to do anything with the free TDSfSMA? or MUST you buy the
> TDS?
> Thanks!
> Marc
>
>
>
> Lindsay Morris
>
Restore DOES take priority, but it may also take an hour to decide to
relinquish a tape drive.
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Dearman, Richard
> Sent: Monday, June 18, 2001 2:03 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Reclai
IMHO --
Archives and backups serve two different purposes.
Backups let you restore a damaged file or a damaged machine.
Archives let you get some data off the machine and put in on a shelf for a
long time.
Archives are useful for meeting legal requirements for retention, or for
getting rid of a m
I think you can halt TSM (ooops - you might have to kill the dsmserv
process)
go to the TSM server bin directory (/usr/tivoli/tsm/server/bin?) and type
./dsmserv
That should get you a bunch of start-up messages; then ENTER should get you
a prompt, at which you can say
register admin me mypassw
Did this thread mention the use of cloptsets? using them, you CAN change
include-exclude options, and the changes ARE picked up dynamically, with no
restart of the client needed.
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Michael Oski
> S
How long does it usually take for the reclamation process to actually stop,
and release the tape drive(s) so the restore can use them? I've typically
seen this be 40 minutes or more, but I'm not sure why, or if something
could be done to speed it up.
> -Original Message-
> From: ADSM: D
Thanks Richard, Eric, all---
I've seen the reclaim-won't-let-go situation a lot, and sometimes tried to
cancel the reclamation process ---
and STILL, more often than not, it takes 40 minutes for cancel process to
take effect!
I didn't have NOPREEMPT set (unless it's a default value -- I think it
I'm with Kelly in thinking that roll-forward is unnecessary in most cases.
The TSM admin guide seems to recommend roll-forward:
"To get the best protection for your TSM data, you should use ...
mirrored copies of your database and recovery log, with the recovery log
mode set to roll-forward"
Do you have enough space / permissions in /adsm/drplans?
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Dixon, Swonda
> Sent: Friday, June 22, 2001 10:50 AM
> To: [EMAIL PROTECTED]
> Subject: File write error message
>
>
> I'm new to the Adsm
Off the top of my head:
Can you create that file /adsm/drplans/DRPLAN.20010627.152129 maually?
Is there enough space in the filesystem? a typical DRplan is maybe 200K.
Can you define a different devclass with FILE devtype pointing to a
different directory and make THAT work?
> -Original Mess
Put a "\" in fron of the quote (") after the SEARCH=.
And you'll have a problem with "server*" also.
The UNIX shell treats these characters specially - remove the special
meaning with \ or by using ' ' arounf the whole expression.
> -Original Message-
> From: ADSM: Dist Stor Manager [mai
I had that happen a few months ago, too. I finally called support, and
somebody there (who said, "Gee, *I'm* not having any trouble getting into
the site...") emailed them to me.
And that's the second time I've seen that...
Your report makes three...
> -Original Message-
> From: ADSM:
It may take prompted actions 5 minutes to kick off.
I don't know why this is.
I wish I did.
Try again and be patient.
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Kleynerman, Arthur
> Sent: Thursday, June 28, 2001 4:20 PM
> To: [EMAIL PROT
Summing up LASTSESS_RECVD will miss some data, though.
If a node had two or more sessions in one day, only the last session will be
counted.
And many nodes do this: nodes using HSM, database nodes where the archive
logs are saved every hour ...
A more accurate way is to sum up the ANE4961 message
If David's answer didn't help you, here's a shell script that you can use as
a model.
(it's an old script - the usual caveats apply...)
The basic trick is to make two sorted lists of tapes, then use "comm" to
compare them.
"comm" is a great unix filter most people don't use - try "man comm" to r
create backupset for the archive...
delete association to stop the scheduled backups in the future...
and you COULD delete filespace - understand that you will NEVER AGAIN
RESTORE anything for MIS_10 if you delete filespace, with the exception of
restoring from the backupset you made earlier.
>
The parallel backup feature (set by resourceutilization) means that ONE
backup session makes SEVERAL accounting log entries / summary table entries.
This is indeed confusing.
Don't you wish there were a product that would take care of this? ;-}
--Lindsay Morris, at servergrap
Use backslashes to hide the quote's special meaning from the unix shell:
dsmadmc -id=xxx -pas=xxx q actl begint=-48 search=\"119 mi nutes\"
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> George Lesho
> Sent: Tuesday, July 03, 2001 11:03 AM
>
I've done a LOT of command-line queries. Some tricks:
1. Use select rather than query. The output of "q stg" etc. may change in
new releases of TSM and break your script, but the output of "select xxx
from stgpools" probably won't.
2. Use -tabd. If not, sometimes a query will come out formatte
Does your accounting log (dsmaccnt.log, in the server/bin directory)
indicate a lot of media wait, comm. wait, or idle wait?
If it's idle wait, turn on client tracing,;
If it's media wait, turn on server tracing;
If it's comm wait, see if you can get ftp to do the same thing, then bug
your network
ject: RE: Solaris 2.6 bad performance with TSM
>
>
> It seems to point to high idle wait times, and I am not sure how
> to turn on
> client tracing. Can you tell me? What should I be looking for if the idle
> wait times are very high?
>
> -Original Message-
> Fr
Great question. Specifically, I'd like to know how much journal based
backups reduce the millions-of-little-files problem, i.e., TSM client spends
all its time walking a huge directory tree, only to discover that there's
little or nothing to back up.
(Of course, this problem can occur with Unix
Look at idlewait (client think time and compression time, comm wait (network
time), and media wait (TSM server time) in the accounting log
(server-dir/dsmaccnt.log - you may need to SET ACCOUNTING ON)
Then you can definitely see where the slowdown is. Compression on a low-end
client will slow th
We get this question often, full vs incremental. We need a paradigm-shift
whitepaper, explaining how TSM never needs a full backup. The best I know
of is the Storage Vision paper,
http://www.tivoli.com/products/documents/whitepapers/storage_vision.html,
section 3.3.1.1.2.
> -Original Messa
Aggregate uses wall-clock time;
Network uses the intervals between when the client says "I'm sending data
now", to when the server actually receives it.
It's perfectly normal to have aggregate be a lot slower than network.
If you really want to speed up your backups, you need to
look at the acco
You have to unmount the filesystem before doing image backups. That makes it
not as great a tool ...
For the millions-of-small-files problem on NT, the new journalled backups
feature in 4.2 should help
(has anybody used it in a MM-small-files situation?)
> -Original Message-
> From: ADSM:
restart the TSM scheduler service on NT. TSM remembers the IP address used
when the client first contacts it.
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
>
> Sent: Thursday, August 02, 2001 11:41 AM
> To: [EMAIL PROTECTED]
> Subject: sav
ck with
> what we have.
>
> -Original Message-
> From: Lindsay Morris [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 22, 2001 9:55 AM
> To: [EMAIL PROTECTED]
> Subject:Re: Recovery Log size / roll forward benefits
>
> I'm with Kelly in thinkin
> this, we have only gotten bitten by a large delete filespace.
>
> BTW, we have an 83GB database and a 5GB log.
>
> ..Paul
>
> At 10:54 AM 6/22/2001 -0400, Lindsay Morris wrote:
> >I'm with Kelly in thinking that roll-forward is unnecessary in
> most cases.
>
You can do the same kind of thing with cloptsets, you know - kind of a
virtual dsm.opt file that lives in the server database rather than on the
client's disk - and cloptsets have the advantage that you can change them,
and the changes take effect WITHOUT you having to restart the scheduler
servic
filesystem client? or Database client?
And if database, are you using TDP-for-whatever, or SQL-backtrack, or ...?
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Jorge Rodrmguez
> Sent: Wednesday, August 08, 2001 3:46 PM
> To: [EMAIL PROTECTED
ugust 08, 2001 4:21 PM
To: [EMAIL PROTECTED]
Subject: Re: Using multiple drives in a backup...
Hi...
I4m using a backup/archive client, no tdp. And the backup goes directly to
the library.
Regards...
Jorge Rodrmguez
Caracas - Venezuela
>From: Lindsay Morris
>Reply
If you create two clients, TSM will treat them like two different machines,
and you'll double the amount of storage used.
Maybe you're OK with that...
What I'd try is setting up a cron job on sunday morning to run a script like
this (untested - off top of head here):
#!/bin/sh
# usage: chginclud
he week-day schedule will back up only the files specified in the
> schedule's OBJECTS setting, and the week-end schedule will process the
> entire system.
>
> Regards,
>
> Andy
>
> Andy Raibeck
> IBM Tivoli Systems
> Tivoli Storage Manager Client Development
> e-ma
OK, OK. Swapping inclexcl files is a bad idea.
We all get one thoughtless post per year, don't we? ;-}
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Richard Sims
> Sent: Tuesday, August 14, 2001 4:42 PM
> To: [EMAIL PROTECTED]
> Subject: R
If you have 20 tape drives, and you're trying to recover many clients,
you'll probably run into this:
Restore of system A has tape volume 0001 mounted;
Restore of System B ALSO needs volume 0001, so it hangs.
If you collocate your copy pool, this shouldn't happen. But collocating
your copy pool
Just guessing - you might change your LANG variable, if it's "C", to "en_US"
or something that's really in /usr/lib/nls/msg.
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Gill, Geoffrey L.
> Sent: Thursday, August 16, 2001 6:04 PM
> To: [EM
Scott -
See the move drm and q drm commands.
For example, as soon as db backup and copy stgpool jobs finish (ie, you have
some DR tapes to send away), run:
q drm wherestate=mountable f=cmd cmdfilename=/tmp/tapes_to_vault
cmd=&VOL&NL (and email that file to your vault service)
move drm * where
SG24-5416-01, Getting Started with Tivoli Storage Manager:
Implementation Guide, suggests (roughly) this as the "wheel of life" for TSM
Nightly incremental node backups
Copy tape storage pools to offsite tapes
Backup database
DR plan creation
Migration of d
maybe your archive sessions are grabbing your tape drives instead of going
to the disk pool, and you finally have enough archives so that ALL your
drives are busied out.
Is MAXSIZE set on your disk pool? That would cause a session to grab a tape
drive.
You're using Servergraph - look and see if
One of the fields in the accounting log is bytes restored.
Look up "dsmaccnt.log" in the index of the admin guide.
- Original Message -
From: "Daniel Swan/TM" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 28, 2000 3:51 PM
Subject: Re: Tracking restores?
> Joshua,
1 - 100 of 326 matches
Mail list logo
