Hi,
I have the next error every night...
ANE4993E (Session: 217053, Node: GBCWBLEIPSF3-SQL) TDP
MSSQL ACO3002 Data Protection for SQL: log backup of
database Pirate_Audit from server GBCWBLEIPSF3 failed, rc
= 1914. (SESSION: 217053)
1) What does it mean?
2) What corrective
Also you can add to administrative schedule:
RECLaim STGpool pool_name THreshold=number DUration=minutes Wait=No(Yes)
OFFSITERECLAIMLimit=number_of_volumes
and set REClaim=100 (DEFINE or UPDATE STGPOOL for prevent unexpected
reclamation process)
REClaim must be greater than 50 (default
Go to the Achive of adsm-L (http://www.mail-archive.com/[EMAIL
PROTECTED]q=1914)
and you'll find a lot of answers.
HTH
Thomas Rupp
-Ursprüngliche Nachricht-
Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von
Gopinathan, Srinath
Gesendet: Freitag, 29. September 2006
Hi,
Can you help me in getting a doc containing a list of return codes and their
explanations.
Regards,
Srinath G
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Rupp
Sent: 29 September 2006 07:13
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L]
I'm just implementing TSM 5.3. Is it possible to limit what goes into the BA
client log file (dsmsched.log)? I really don't need to know every single
file that is processed successfully. Exceptions or folders only would be
fine. A typical client log is over 100MB a day so I either have to rollover
With the 5.3 baclient, a new parameter was introduced to limit the size
of the logs
schedlogmax
errorlogmax
Also, previous parameters pruned the size of the logs in terms of days
schedlogretention
errorlogretention
The juicy nuggets are generally in the dsmerror.log.
Using a pattern searching
Srinath,
RC=1914 means the SQL Server reported some type of error
to Data Protection for SQL. Examine the the TDPSQL.LOG file
(or appropriate file if you specified a different name)
for details on what the error was.
Thanks,
Del
ADSM: Dist
Ah well. I'll probably just stick to the error log then.
Thanks
-Original Message-
From: Leigh Reed [mailto:[EMAIL PROTECTED]
Sent: 29 September 2006 11:16
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Is it possible to limit what goes into the
schedule log?
With the 5.3 baclient, a
Know thy toolkit...
There is a client option called QUIET which eliminates detail, which
of course discards information which may be useful in security and
problem analysis. Auditors may object to such loss of record-keeping.
Richard Sims
Apologies.I stand corrected.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: 29 September 2006 12:16
To: ADSM-L@VM.MARIST.EDU
Subject: [SPAM: 4.000] Re: [ADSM-L] Is it possible to limit what goes
into the schedule log?
On Sep 29, 2006, at 12:31 AM, Gopinathan, Srinath wrote:
Hello,
Can anyone help me on how to schedule with a sample example in a TSM?
The Admin Guide manual contains examples, and best guidance, such as
under Scheduling a Client Operation. Look for define schedule in
the PDF.
And there is
Amen to that.
What looks like noise today is valuable forensic data tomorrow, when you
need to diagnose problems like, Why does TSM not have any backup versions
of my file?
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew
On Fri, 29 Sep 2006 09:59:17 +0100, Angus Macdonald [EMAIL PROTECTED] said:
I'm just implementing TSM 5.3. Is it possible to limit what goes
into the BA client log file (dsmsched.log)? I really don't need to
know every single file that is processed successfully. Exceptions or
folders only
which is the procedure to copy a volume and send the copy to an external
site?
Regards
Miguel Sáez Sáez
IBM Certified Deployment Professional
IT Specialist
IBM de Chile S.A.C.
mail: [EMAIL PROTECTED]
Phone: 562-2006638
I imagine you are looking into providing a DR copy of a volume at an external
site.
TSM provides a mechanism for managing this called DRM although there are manual
ways of achieving it.
In general, look at taking a backup of the storage pool the original volume
resides in to a copy storage
Hi list,
What could be wrong for a schedule not start?...I mean not start at all.
All nodes are associated with the schedule, policy and management class are
defined correctly.
When running a dsmc backup command at the client, the backup starts and
completes successfully.
The environment
Scheduler disabled in dsmserv.opt after a TSM upgrade?
Damaged DB causing the scheduler to croak? What does show pend say?
[RC]
On Sep 29, 2006, at 9:30 AM, Mario Behring wrote:
Hi list,
What could be wrong for a schedule not start?...I mean not
start at all. All nodes are associated
On Sep 29, 2006, at 12:30 PM, Mario Behring wrote:
Hi list,
What could be wrong for a schedule not start?...I mean not
start at all. All nodes are associated with the schedule, policy
and management class are defined correctly.
When running a dsmc backup command at the client, the backup
Hi Richard,
Please, in the case of Linux clients, just the dsmcad daemon will do the trick?
Or is there anything else needed?
Thanks
Mario
- Original Message
From: Richard Sims [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Friday, September 29, 2006 1:35:31 PM
Subject: Re:
On Sep 29, 2006, at 12:56 PM, Mario Behring wrote:
Hi Richard,
Please, in the case of Linux clients, just the dsmcad daemon will
do the trick? Or is there anything else needed?
Hi, Mario -
See the Unix client manual for a full description, where CAD launches
dsmc schedule and operates as
What are folks using to do TSM trending? I need to answer questions like
these:
- How long will our current supply of scratch tapes last, assuming
constant usage?
- If I add insert a number TSM clients similar to an existing client,
how will it affect my tape usage?
- What's our peak drive usage
Take a look at ServerGraph.
At 02:15 PM 9/29/2006 -0400, you wrote:
What are folks using to do TSM trending? I need to answer questions like
these:
- How long will our current supply of scratch tapes last, assuming
constant usage?
- If I add insert a number TSM clients similar to an existing
I have a client that is requesting the following, and I am not sure how to
resolve.
Below is what they want...
Report 1: Daily Backup Report for Trinity
Date
Frequency
Site
Number of Server Backups Scheduled
Number of Server Backups Completed
Number of Jobs Scheduled
Number of
On Fri, 29 Sep 2006 14:15:49 -0400, Anker Lerret [EMAIL PROTECTED] said:
What are folks using to do TSM trending?
I use R.
http://open-systems.ufl.edu/reports/tsm/graphs/ALL.html
It's clickable!
[...]
I've found that TSM's own tools (the TSM web GUI and that ghastly
thing that's
The how many restores were done is easily answered from the TSM
accounting files.
SET ACCOUNTING ON to create the dsmaccnt.log file.
Look in the admin guide for a description of the fields.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Allen S.
All,
I am sketching out my plan for running an archive session, I want to move
the data to off-site tape and not keep any of the data in a primary storage
pool. My hope is to conserve space on my tape library for regular backup
data.
Here is my game-plan and my problem:
1. Data goes to the
If you delete the files in a primary storage pool from the TSM DB, the
copy pool version is deleted as well.
Simple solution:
Let the data migrate from your archive disk pool to an archive tape pool
(primary), and send those tapes offsite.
DRM doesn't support vault management of primary tape
27 matches
Mail list logo
