You need to lower the maxclient setting first and then you can reduce
maxperm.
But as noted if your using jfs2 filesystems it is not a good idea to lower
maxclient.
-Original Message-
From: Wheelock, Michael D [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2003 5:38 PM
To: [EMAIL
Thank for your answer.
Can I ask you some more detail:
a.. PATCH 5.1.7.1 is patch for autoloader IBM 360716X or patch for TSM 5.1.5 or TSM
5.1.7. I install TSM 5.2, Win2K SP3 but nothing change
b.. Where I can download it ?
c.. What does it mean: TSM will stop working with 3607-16x . TSM
You have room for bar-code label on the cartridge. Actually from that
space only part is machibe-readable (the bar-code area) and the rest can
be used for your own purposes.
Thus a solution might be (no warranty and other marketing stuff): print
own bar-code labels. The specification is available
Hi Andy
Comment as follows (marked with #);
Flemming,
The only possibilities I can think of:
- someone ran a selective backup of the file (how have you verified that
this is not the case?)
# This is not the case, the only backup which has been performed on this server is a
incremental
I understood the only options for collocation were on or off
-Original Message-
From: Richard Sims [mailto:[EMAIL PROTECTED]
Sent: 30 July 2003 16:41
To: [EMAIL PROTECTED]
Subject: Re: Collocation from nocollocation
With Collocation on, we had one small problem with the DB2 API.
What
Hello everyone!
I'm still doing this tpoc, but this time it's with lto2. The client is SUN
at 5.2, storage agent is 5.1.6.2 and the server is a sun solaris at
5.1.6.2. I have a detail trace on the client and I am receiving the
following output. As you can see it is giving erroneous data for
Hi,
Reply for the questions :
a) PATCH 5.1.7.1 is the TSM patch which
will have Fix for the 3607-16x autoloader. and if you have already upgraded
to TSM 5.2 you will need to download PATCH TSM 5.2.0.2
b) This will be available at Customer
Download site for regular Patch dowloads.
c) TSM does
Actually there are 3 options:
No None
Yes At the NODE level
Filespace At the FILESPACE level
Bill Boyer
DSS, Inc.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Tudor,Troy,VEVEY,GL-IS/IT
Sent: Monday, August 04, 2003
I could swear I read somewhere that TSM v5 added a feature to client
schedules that allowed for Pre- and Post-schedule commands. I can't
remember where I read that, nor can I find the information about it in the
version we have installed now (just upgraded from 4.2.1.7 to 5.1.7.1).
Does v5 allow
This is a feature that has been in the product for a lot longer than v4 or
v5.
See the PRESCHEDULECMD, PRENSCHEDULECMD, POSTSCHEDULECMD, and
POSTNSCHEDULECMD options in the client manual.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes
Hi,
TSM 5.1.6.5 on windows 2K server. I'm trying to make a command script that
will tell me how many filespaces have a BACKUP_END greater than 1 day.
Then I want it to email those results to me. That way if a client stops
backing up I'll get an email about it and go fix it. The emailing can be
Alex,
For number of file spaces that haven't backed up:
select count(*) from filespaces where backup_endcurrent_timestamp-1 day
For total number of filespaces:
select count(*) from filespaces
For names of filespaces:
select node_name, filespace_name from filespaces where
If you also want to capture file spaces that have no completion date,
consider adding or backup_end is null to the where criterion, i.e.:
... where backup_end current_timestamp - 1 day or backup_end is null
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client
TSM rocks. And so do you guys. Thanks.
Alex
On Mon, 4 Aug 2003, Andrew Raibeck wrote:
If you also want to capture file spaces that have no completion date,
consider adding or backup_end is null to the where criterion, i.e.:
... where backup_end current_timestamp - 1 day or backup_end is
Can anybody help. I getting the following errors in my activity log:
08/04/2003 12:45:13 ANR0102E dsalloc.c(980): Error 1 inserting row
in table DS.Segments.
This errors occurs at the start of a backup of some of my NT servers.
08/02/2003 08:05:56 ANR0102E dsalloc.c(980): Error 1
Let uour D/R requirements drrive this. I have 3 archive copy pools and one
backup pool. This worked out as easier to implement and monitor than a lot
of co-located nodes. One archive pool is TDP; one is SAP/Oracle redo logs;
and the third is all other oracle databases AND the second copy of the
Tivoli just announced the addition of a new Version Release Information
(VRI) page for the TSM community.
If your running Netscape or IE in the field, a word to the wise, load the
new link (in blue below) from your highest
speed connection first (to avoid a lengthy 1st time download), your
Hi all,
I do have problems, backing up one of our W2K-Nodes within the given
timeframe of 10 Hours.
It is a very big node ( 350 GB Filespace, 6 000 000 files, all files under
one mountpoint) and we always make full incremental. I plan to use
journal-based-backup to get it done in time.
Does
18 matches
Mail list logo