how to delete dataretention license?

2011-03-30 Thread TSM
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 of license?
(the holded files are now released)

its only a tsm test system, version 5.5.5.


with best regards
Stefan Savoric


Re: how to delete dataretention license?

2011-03-30 Thread Grigori Solonovitch
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: [ADSM-L] how to delete dataretention license?

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 of license?
(the holded files are now released)

its only a tsm test system, version 5.5.5.


with best regards
Stefan Savoric


Please consider the environment before printing this Email.

CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail 
message and any attachments hereto may be legally privileged and confidential. 
The information is intended only for the recipient(s) named in this message. If 
you are not the intended recipient you are notified that any use, disclosure, 
copying or distribution is prohibited. If you have received this in error 
please contact the sender and delete this message and any attachments from your 
computer system. We do not guarantee that this message or any attachment to it 
is secure or free from errors, computer viruses or other conditions that may 
damage or interfere with data, hardware or software.


Portable restore from TDP for Databases (SQL) ?

2011-03-30 Thread Rick Adamson
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 before moving forward. I have had this situation come up
before and scoured over the TDP documentation and found no clear
definition of how to complete the task. 

 

Is there a way to perform what I will call a portable "flat file"
restore of SQL databases from TSM without it affecting the production
copy that is live on the SQL server?

How do you handle these requests?

 

All feedback appreciatedTIA

 

Rick Adamson

Jacksonville, FL


Re: Portable restore from TDP for Databases (SQL) ?

2011-03-30 Thread Del Hoobler
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
stream of bytes at restore time.

Now.. having said that, you can solve your problem by
redirecting the restore of the backup into
a "temporary" database name and relocate the files.
After the restore is complete, you will have the
temporary database with all the database files
(.MDF, .LDF, .etc.) under your temporary directory.
Use the "Restore Into" and "Relocate" abilities of
Data Protection for SQL to accomplish this.
This technote might help:
   http://www-01.ibm.com/support/docview.wss?uid=swg21253263

Thanks,

Del



"ADSM: Dist Stor Manager"  wrote on 03/30/2011
08:41:24 AM:

>> From: Rick Adamson 
>> To: ADSM-L@vm.marist.edu
>> Date: 03/30/2011 08:43 AM
>> Subject: Portable restore from TDP for Databases (SQL) ?
>> Sent by: "ADSM: Dist Stor Manager" 
>>
>> 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 before moving forward. I have had this situation come up
>> before and scoured over the TDP documentation and found no clear
>> definition of how to complete the task.
>>
>>
>>
>> Is there a way to perform what I will call a portable "flat file"
>> restore of SQL databases from TSM without it affecting the production
>> copy that is live on the SQL server?
>>
>> How do you handle these requests?
>>
>>
>>
>> All feedback appreciatedTIA
>>
>>
>>
>> Rick Adamson
>>
>> Jacksonville, FL


Re: how to delete dataretention license?

2011-03-30 Thread chris rees
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 (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: [ADSM-L] how to delete dataretention license?
> 
> 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 of license?
> (the holded files are now released)
> 
> its only a tsm test system, version 5.5.5.
> 
> 
> with best regards
> Stefan Savoric
> 
> 
> Please consider the environment before printing this Email.
> 
> CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail 
> message and any attachments hereto may be legally privileged and 
> confidential. The information is intended only for the recipient(s) named in 
> this message. If you are not the intended recipient you are notified that any 
> use, disclosure, copying or distribution is prohibited. If you have received 
> this in error please contact the sender and delete this message and any 
> attachments from your computer system. We do not guarantee that this message 
> or any attachment to it is secure or free from errors, computer viruses or 
> other conditions that may damage or interfere with data, hardware or software.
  

Re: how to delete dataretention license?

2011-03-30 Thread PAC Brion Arnaud
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 Retention 
Protection:". If "ON" then the license is required !
Note that such a setup will make archived objects deletion impossible ...

Cheers.

Arnaud


**
Corporate IT Systems & Datacenter Responsible
Panalpina Management Ltd., Basle, Switzerland,
CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: arnaud.br...@panalpina.com
**


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of TSM
Sent: mercredi 30 mars 2011 14:09
To: ADSM-L@VM.MARIST.EDU
Subject: how to delete dataretention license?

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 of license?
(the holded files are now released)

its only a tsm test system, version 5.5.5.


with best regards
Stefan Savoric


Antwort: Re: how to delete dataretention license?

2011-03-30 Thread TSM
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


Re: Portable restore from TDP for Databases (SQL) ?

2011-03-30 Thread Shawn Drew
>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 one-off requests.

Regards,
Shawn

Shawn Drew





Internet
rickadam...@winn-dixie.com

Sent by: ADSM-L@VM.MARIST.EDU
03/30/2011 08:41 AM
Please respond to
ADSM-L@VM.MARIST.EDU


To
ADSM-L
cc

Subject
[ADSM-L] Portable restore from TDP for Databases (SQL) ?






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 before moving forward. I have had this situation come up
before and scoured over the TDP documentation and found no clear
definition of how to complete the task.



Is there a way to perform what I will call a portable "flat file"
restore of SQL databases from TSM without it affecting the production
copy that is live on the SQL server?

How do you handle these requests?



All feedback appreciatedTIA



Rick Adamson

Jacksonville, FL



This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.


Re: Linux & SAN Device Interruptions

2011-03-30 Thread Robert Clark
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 found is that the default setting for the in-kernel
(or would that be in-distro?)  Emulex driver defaults to running multiple
discovery threads when scanning for devices at boot time. (16 threads,
IIRC.) This pretty much guarantees that devices won't ever be discovered
in the same order. According to the Emulex doc, this can be changed with a
boot time setting to the old behaviour of one discovery thread. (Would
take longer.)

The second item is that CDL/EDL emulating 3584 doesn't look much like a
3584 at the WWNN level. On a 3584, each drive has a unique WWNN that
incorporates both the library serial number and information about where
the drive is in the library. (Control path drives have a second LUN for
communicating with the library.)  On CDL/EDL all virtual tape drives in a
given VTL show up as different LUN numbers on the virtual library's one
WWNN. (Not optimal for the default udev rules on RHEL?)

The third item is that RHEL ships with a udev rule already poplulated that
could be used to make the CDL/EDL tape drives persistent, by using
something other than boot-time-enumerated mt#/rmt# for the naming
convention. (Name the drive after some part of the WWNN & LUN number?)
Personally I like this approach better than the
try-to-update-it-after-the-fact-on-the-library-manager scripts we use now.

When IBM allowed copy-on-write to go into Linux, I wish they'd also have
donated cfgmgr. I don't think any distro would take ODM though, so a
ported cfgmgr would likely be useless.

[RC]



From:   Nick Laflamme 
To: ADSM-L@VM.MARIST.EDU
Date:   03/29/2011 04:28 PM
Subject:[ADSM-L] Linux & SAN Device Interruptions
Sent by:"ADSM: Dist Stor Manager" 



How are those of you who run TSM servers or storage agents on Linux on
Intel doing with disruptions with SAN-attached tape devices or the SAN
fabric itself?

In my current shop, we run TSM servers on AIX (and MVS, but that's another
story), but we have storage agents on AIX, Windows, and Red Hat Linux on
Intel. The Linux storage agents are relatively new; they were first
deployed about two years ago. AIX and Windows storage agents have been
there a bit longer, although I can't say how much longer; I, too, have
been there less than two years.

One problem that we've never been able to overcome with our Linux storage
agents has been that if a virtual tape library is rebooted or if the SAN
fabric gets massively unzoned (it happened about a month ago to us, sigh),
the Linux storage agents don't notice the return of the SAN-attached tape
devices until we reboot the Linux server. (We never had the Linux servers
zoned to real 3584s and real LTO tape devices; they've only ever been
zoned up to EMC Clariian Disk Libraries and then DataDomains with VTL
cards in them.) This has persisted across updates to LINtape, CDL code
levels, Data Domain code levels, and TSM storage agent levels. Needless to
say, the application teams are rather steamed with us about this.

We have at times had cases open simultaneously with EMC, Red Hat, and IBM,
to no avail.

If you have Linux TSM servers or storage agents that gracefully recover
from disruptions on your tape SAN, can you share with me (and the rest of
the list, if you want) RHEL level, device driver levels, HBA
configuration, and whatever else you think might be relevant?

Thanks,
Nick

U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


Re: Portable restore from TDP for Databases (SQL) ?

2011-03-30 Thread Rick Adamson
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 until now has
fallen on deaf ears.
Thanks Shawn.

~Rick


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Shawn Drew
Sent: Wednesday, March 30, 2011 10:42 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Portable restore from TDP for Databases (SQL) ?

>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 one-off requests.

Regards,
Shawn

Shawn Drew





Internet
rickadam...@winn-dixie.com

Sent by: ADSM-L@VM.MARIST.EDU
03/30/2011 08:41 AM
Please respond to
ADSM-L@VM.MARIST.EDU


To
ADSM-L
cc

Subject
[ADSM-L] Portable restore from TDP for Databases (SQL) ?






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 before moving forward. I have had this situation come up
before and scoured over the TDP documentation and found no clear
definition of how to complete the task.



Is there a way to perform what I will call a portable "flat file"
restore of SQL databases from TSM without it affecting the production
copy that is live on the SQL server?

How do you handle these requests?



All feedback appreciatedTIA



Rick Adamson

Jacksonville, FL



This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in
error,
please delete it and immediately notify the sender. Any use not in
accord
with its purpose, any dissemination or disclosure, either whole or
partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall
(will)
not therefore be liable for the message if modified. Please note that
certain
functions and services for BNP Paribas may be performed by BNP Paribas
RCC, Inc.


Re: Portable restore from TDP for Databases (SQL) ?

2011-03-30 Thread ADSM-L
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 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 one-off requests.
> 
> Regards,
> Shawn
> 
> Shawn Drew
> 
> 
> 
> 
> 
> Internet
> rickadam...@winn-dixie.com
> 
> Sent by: ADSM-L@VM.MARIST.EDU
> 03/30/2011 08:41 AM
> Please respond to
> ADSM-L@VM.MARIST.EDU
> 
> 
> To
> ADSM-L
> cc
> 
> Subject
> [ADSM-L] Portable restore from TDP for Databases (SQL) ?
> 
> 
> 
> 
> 
> 
> 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 before moving forward. I have had this situation come up
> before and scoured over the TDP documentation and found no clear
> definition of how to complete the task.
> 
> 
> 
> Is there a way to perform what I will call a portable "flat file"
> restore of SQL databases from TSM without it affecting the production
> copy that is live on the SQL server?
> 
> How do you handle these requests?
> 
> 
> 
> All feedback appreciatedTIA
> 
> 
> 
> Rick Adamson
> 
> Jacksonville, FL
> 
> 
> 
> This message and any attachments (the "message") is intended solely for
> the addressees and is confidential. If you receive this message in error,
> please delete it and immediately notify the sender. Any use not in accord
> with its purpose, any dissemination or disclosure, either whole or partial,
> is prohibited except formal approval. The internet can not guarantee the
> integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
> not therefore be liable for the message if modified. Please note that certain
> functions and services for BNP Paribas may be performed by BNP Paribas RCC, 
> Inc.