On Oct 9, 2008, at 4:52 PM, Clark, Robert A wrote:
We're working on changing some backups from command schedules to
incrementals with pre/post commands.
Between now and when we complete the work, is there any way to enable
verbose time/date stamps per line in the interactive backup output?
Ro
Has anyone seen the following. I have a few servers that report this
every couple of nights, it is not always the same mount point that
fails, but always a TCP/IP connection failure:
10/08/08 20:10:44 Retry # 1 Normal File-->
12,288 /etc/objrepos/CuAt Changed
10/08/08 20:10:47 ANS1228E Send
Eric -
File size (actually, Aggregate size) is in the Contents table - which
is the worst of all TSM database tables to have to trawl. If you
must, do so with as fully qualified search as possible, to minimize
sequential traversals. An alternative would be to inspect tapes
recently used by the
Hi Richard!
Thanks you very much for your help!
Indeed it's the worst of all. I just did a select * from contents where
volume_name='just on of my volumes' on my very small test environment.
Output is returned quite fast, but as soon as you hit c to cancel the
output, you loose the cursor for sever
On Oct 10, 2008, at 9:51 AM, Loon, EJ van - SPLXM wrote:
The output of the Query CONtent command is useless for me, because the
file size is not listed. Bummer.
When using TSM commands, always be mindful of the availability of
Format=Detailed with many commands, to provide more extensive info
I see no failure. What I see is that your client is taking quite long
to find a changed file, so it needs to reconnect the data session
(usually a different session from the 'control session that is used to
download the list of active files from the server). You could increase
the idletimeout sett
Hi *SM-ers!
We are using a EMC Disk Library (virtualizing a LTO tape library) for
quite some time now.
Since tape mount and data seek times are about two seconds on such a
device, we have collocation tuned off for the storage pools.
Every now and then customers call me because they started a restor
Hi Richard!
Oeps... Missed that option... Thanks!!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: vrijdag 10 oktober 2008 16:00
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Find
Zoltan -
This, of course, is the historic "Many small files" challenge.
Recommendations on it are summarized in ADSM QuickFacts, based upon
our communal pursuit of it in our shops.
You've provided no information about the client system itself, where
memory and swap space contribute to the issue,
Hi Eric,
we use the following steps to identify large files in last nights
backup:
Step 1 - Query the volumes used in last nights backup
select volume_name as Volume, stgpool_name as Stgpool,
date(last_write_date) as "Date", -
time(last_write_date) as "Time" from volumes where -
last_write_dat
If you know that a suspect file is being moved (reclaim, not backup
stgpool), use this command with the volser of the source tape:
query content VOLSER count=1 f=d
That will show you the node, file name, size, and a few other details on
the first file on the volume, which is the one being moved.
I am setting up NDMP backup of a Celerra and I am having trouble getting the
Celerra to see the tape drives. Has anyone made this work with the equipment
listed?
Celerra - NS80
Tape Library - IBM3494
Tape Drive - 3592
TSM - 5.4.2.0
Andy Huebner
This e-mail (including any attachments) is con
On Oct 10, 2008, at 22:02 , Huebner,Andy,FORT WORTH,IT wrote:
I am setting up NDMP backup of a Celerra and I am having trouble
getting the Celerra to see the tape drives. Has anyone made this
work with the equipment listed?
I've had some experience with a nsx and T10K drives, just plugging t
13 matches
Mail list logo
