hello,
after playing with the client command "set event -type=hold" the tsm server
license in not valid anymore.
dataret.lic is now necessary to be in a valid license.
i am wondering, that a client command can get the tsm server out of
license.
which is the best way to get back in a valid state
I can find this file in /usr/tivoli/tsm/server/bin/dataret.lic (TSM 5.5.4.1
under AIX 5.3).
Grigori G. Solonovitch
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of TSM
Sent: Wednesday, March 30, 2011 3:09 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [A
We have a remote vendor who sends updates to a SQL db that lives on one
of our SQL servers. From time-to-time the updates are determined
undesirable and before performing a restore in production we want to be
able to send them a portable copy so they can determine the root cause
of the problem bef
Rick,
One thing to understand about SQL Server legacy (VDI) backups:
The backups are a "stream of bytes". Data Protection for SQL
does not read and write files. The SQL Server gives
Data Protection for SQL a stream of bytes at backup time,
and Data Protection for SQL gives the SQL Server those
str
i had the same issue
tryaudit license audithold=yes
cheers
> Date: Wed, 30 Mar 2011 15:21:08 +0300
> From: grigori.solonovi...@ahliunited.com
> Subject: Re: how to delete dataretention license?
> To: ADSM-L@VM.MARIST.EDU
>
> I can find this file in /usr/tivoli/tsm/server/bin/dataret.lic (TS
Stephan,
To my mind it is not the "set event" command that changed licensing scheme on
your machine, but very probably a "SET ARCHIVERETENTIONPROTECTION" command,
which basically transforms TSM server into SSAM (archiving system).
This can verified with "q status" searching for "Archive Retentio
hello Chris, hello Arnaud,
audit license audithold=yes that works, the license is not needed
anymore. thanks
Arnaud: on my test tsm server, there are also backup data, so i cannot
activate this license with the set archiveretentionprotection on.
thanks very much
stefan savoric
>From what I understand, you want to send a copy of your DB over to a
vendor before performing a modification.
Instead of using TSM, why not use the internal DB processes for doing
this? (BAK files for MS SQL)
Continue using TDP for your internal backups but use the disk-based BAK
files for these
Hi Nick,
I don't claim to have slayed that particular dragon yet, but I have
uncovered some background info on the subject:
In our case we're running a mix of RHEL (RHES?) 4 & 5 (on Intel x86_64) on
the TSM servers and a few storage agents (and moving to SLES at some
point).
The first item I've
Now there's a concept, test before change :). This vendor is obviously
more reactive than proactive.
In this situation they usually determine they have hosed the db, then
need the active backup for their tests and later for recovery. I have
suggested that we question their practices but at least up
Be sure to perform any MS SQL (i.e., non-TDP) backups with the COPY_ONLY
directive so as not to invalidate your ongoing TDP backups (i.e., not
interrupting the log sequence number).
David Mc
London, UK
On 30 Mar 2011, at 15:41, Shawn Drew wrote:
> From what I understand, you want to send a co
11 matches
Mail list logo
