Hi TSM-ers!
One of our SQL Server 2005 (running DP for SQL Server 5.3.3.0) the full
backup fails every time.
In the tdpsql.log we see the following messages:
11/23/2007 02:26:44 ACO5436E A failure occurred on stripe number (0), rc
= 428
11/23/2007 02:26:44 ACO5407E The SQL server aborted the opera
Google-ing for "rc=428" return a lot
more results, including one from
Del Hoober that might be interesting.
Alexander
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]
> On Behalf Of Loon, E.J. van - SPLXM
> Sent: Tuesday, November 27, 2007 10:22 AM
> To: ADS
Hi Eric,
You didn't give any details about the BUFFERS, BUFFERSIZE,
SQLBUFFERS, SQLBUFFERSIZE, or STRIPES that you are using.
I would start by setting
BUFFERS 3
BUFFERSIZE 1024
SQLBUFFERS 0
SQLBUFFERSIZE 1024
STRIPES 1
to see if that helps at all.
If not, I suggest that you place a
Is any one working on Hitachi Storage and performing In-system replication
(Shadowimage)?
( o )
---
I,I ' ' I,I
"(("
))
With Best Regards,
Sandeep Jain
** Legal Disclaimer
*
"This email may contain confidential and
Hi Del!
Thank you very much for your reply!!!
I assume these paramaters all have to be specified in the TDP option
file?
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Del Hoobler
Sent: dinsd
Hello,
we would like to get a list of nodes where the option "PASSEXP" is unequal 0.
We used the following SQL statement:
tsm: SA023ADD>select node_name, passexp from nodes where passexp<>0
ANR2034E SELECT: No match found using this criteria.
ANS8001I Rückkehrcode 11.
But we definitely have
These commands will do the trick:
tdpsqlc set BUFFERS=3
tdpsqlc set BUFFERSIZE=1024
tdpsqlc set SQLBUFFERS=0
tdpsqlc set SQLBUFFERSIZE=1024
tdpsqlc set STRIPES=1
You can also set them through the DP/SQL GUI "Edit-->Configuration".
Del
-
try this -->
select node_name, passexp from nodes where PASSEXP!=0
On Nov 27, 2007 4:06 PM, Herrmann, Boris <[EMAIL PROTECTED]> wrote:
> Hello,
>
> we would like to get a list of nodes where the option "PASSEXP" is unequal 0.
> We used the following SQL statement:
>
> tsm: SA023ADD>select node_n
I suspect the value of passexp can be NULL, so it should be
select node_name,passexp from nodes where not (passexp is null)
Rainer
On Tue, 27 Nov 2007, goc wrote:
> try this -->
>
> select node_name, passexp from no
When I select the column with
select * from syscat.columns where tabname='NODES' and colname='PASSEXP'
TABSCHEMA: ADSM
TABNAME: NODES
COLNAME: PASSEXP
COLNO: 30
INDEX_KEYSEQ:
INDEX_ORDER:
TYPENAME: INTEGER
LENGTH: 0
SCALE: 0
NULLS: FALSE
REMARK
Hi All,
Thanks for your help!!
I have TSm 5.3.5 on AIX 5.3.5 using an IBM 3584 w/16 LTO drives. I have
run out of slots in the library and can't seem to get enough scratch
volumes in to get any decent move data commands flowing based on
pct_reclaim values. Does anyone have any "ideas" on how I
Thanks for your answer, but it's the same result:
tsm: SA023ADD>select node_name, passexp from nodes where PASSEXP!=0
ANR2034E SELECT: No match found using this criteria.
ANS8001I Rückkehrcode 11.
-Ursprüngliche Nachricht-
Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag
Hi Thomas,
your select statement "select node_name, passexp from nodes where PASSEXP IS
NULL" is the one we've searched for.
Thanks,
Boris
-Ursprüngliche Nachricht-
Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Thomas
Rupp
Gesendet: Dienstag, 27. November 200
Look for filling volumes. Sometimes I find a pool has more filling
volumes than I think it should have.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Nicholas Rodolfich
Sent: Tuesday, November 27, 2007 9:13 AM
To: ADSM-L@VM.MARIST.ED
One way is to use " query media" and "move media".
If you have more than one onsite tape pool, most likely at least
one is not used as often. Q medai can show list of tapes in a pool
not accessed in more than x number of days.
Then Move Media moves those tapes out of library. That's
what these
Hi ladies and gentlemen,
I *really* appreciate the feedback including one by private
e-mail! It's helped a lot in resolving our DBAs' concerns.
Yesterday, we configured RMAN/TDPO (our first TDPO setup) and I
must say the performance flies with use of multiple parallelized
streams!
Hello:
I have some Windows NT (SP 4) servers I need to setup for backups. I am
wanting to find out what versions of the TSM client support this OS
platform? I have already gone out to the IBM website and it lists all
the OS platforms supported in TSM 5.5, 5.4 and 5.3... but it mentions
nothing
The fastest scratch provisioning in a situation like that is to
delete any Pending volumes.
Where you are constrained for tape space to reclaim volumes within
the library, consider performing a Move Data to the upper disk
storage pool in the hierarchy. (You can always temporarily add a
spare dis
According to Richard Sims TSM QuickFacts:
Windows NT client Supported through TSM 5.1.7.3 only.
Not supported in TSM 5.2 or beyond.
HTH
Thomas Rupp
-Ursprüngliche Nachricht-
Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Welton,
Charl
TSM 5.2 was the last version of TSM to support Windows NT 4.0 (support was
at the 5.1 code level, but shipped as part of 5.2). 5.2 is out of
mainstream support as of this past April. See
http://www.ibm.com/support/docview.wss?uid=swg21251347 for additional
information about the TSM 5.2 EOS.
Regard
This will give you a list of tapes under twenty percent utilized from all pools
select volume_name, stgpool_name,pct_utilized, status from volumes -
where pct_utilized < 20 and status='FILLING' -
order by pct_utilized, stgpool_name, volume_name
After that, do a MOVE DATA VOLUMENAME to help it a
Hot Diggety! Jim Young was rumored to have written:
> This will give you a list of tapes under twenty percent utilized from
> all pools
>
> select volume_name, stgpool_name,pct_utilized, status from volumes -
> where pct_utilized < 20 and status='FILLING' - order by pct_utilized,
> stgpool_name, vo
On Nov 27, 2007, at 12:24 PM, Jim Young wrote:
Does anyone know whay TSM has this issue with keeping lots of
'filling' volumes?
This is an old chestnut issue.
See "Tape leak" in http://people.bu.edu/rbs/ADSM.QuickFacts
for general info on it.
Richard Sims
If you happen to have a copy of 5.2.00 or 5.1.5, slap it on there. Just don't
have any client issues, because you won't get any help. :)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Welton, Charles
Sent: Tuesday, November 27, 2007 10:14 AM
To: AD
Are you running backups, directly to tape, in the same storage pool
where you are seeing the "filled" volumes?
I have an issue, with my SQL DB backups, that results in the same
situation. Because of their size, they go directly to tape. Due to the
available backup window, I am forced to back t
We have been having an intermittant problem with ANR8833E errors, which
are addressed in apar: IC54107: TSM ANR8833E DURING CHECKIN LIBVOL FOR
SOME VOLUMES.
However, the apar says: projected to be fixed in level 5.3.6.1, 5.3.7, and
5.4.3.
Since I haven't seen anything higher than 5.4.1.2 and 5.5
Hello list.
Environment .
TSM 5.3.4.1 running on AIX.
I have a question about the mig stg command versus the hi/lo parameter
on a Disk Storage pool for migration purposes.
I was recently in a TSM class and the instructor informed me that the
mig stg command runs single threaded as compared t
I used the "overflow location" once with success when I was in this same
situation. Just long enough to put in some scratch tapes and move data.
I wouldn't recommend it for normal occasions though.
Johnny Lea CNE
Data Center Manager
Division of Information Systems
University of MS Medical Cente
"ADSM: Dist Stor Manager" wrote on 11/27/2007
01:43:41 PM:
> We have been having an intermittant problem with ANR8833E errors, which
> are addressed in apar: IC54107: TSM ANR8833E DURING CHECKIN LIBVOL FOR
> SOME VOLUMES.
>
> However, the apar says: projected to be fixed in level 5.3.6.1, 5.3.7
Hi All,
I am trying to configure TSM on windows 2003 64 bit client with SP1 but
having some serious issues. Where ever the disks are failed over, I am
not able to start even the base tsm client (command line or GUI). When I
reboot the box, all the disks are failed over to the other server and
tsm
30 matches
Mail list logo
