Re: Physically shred tape after one use? [ email retention ]

2008-02-08 Thread Richard Rhodes
- Allen S. Rout wrote
I've got some sentiment on the UF campus that anything which could be
retrieved by a data-recovery house should be deemed not deleted.  This
is making me wince at the thought of turning 3592 volumes into
single-use disposables.

So how do you-all do it, and how did you decide?


W wrote
Are you talking about discoverable meaning the legal term discovery,
or
as in snoopable, meaning somebody gets access to your media because it
falls off a truck or they walk out the door with it?


I read the question as asking (probably incorrectly) as whether a scratch
tape
be recovered, or a  currently in use tape have it's unused portion
recovered.

We have had this conversation with our email folks here.  I have explained
that, YES,
the previous data is sitting there past the defined deletion period.  YES,
it
is possible to access it on a very expensive fishing expedition.  So far,
that has
been acceptable.  If this changes, I suppose I'll be reading up on TSM
and/or
3592 encryption (something I know nothing about).

Rick









-
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.


Re: TSM Novell client 5.5 upgrade

2008-02-08 Thread Kinder, Kevin P
Tim,

We have had major, and I do mean major, problems with our upgrade, but
ours involved going to TSM server 5.5.0.0. IBM itself has been unable to
determine whether our problems are due to upgrading the server,
upgrading the clients, a combination of both, or the phase of the moon
when doing the upgrade.  

I have detailed this problem in recent posts, but will be glad to share
more info with you offline. IBM's respose to my multiple PMRs on the
upgrade issues has ranged from average to pathetic, so I would strongly
urge you to do this on just one NetWare client, and one that you can
afford to lose, as you move into the 5.5 world.


Kevin Kinder
State of West Virginia



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Timothy Hughes
Sent: Friday, February 08, 2008 10:31 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM Novell client 5.5 upgrade

Hello All,

I am planning to start upgrading our TSM Novell clients next week from
5.3.4 to 5.5.0 and would like to know if anyone has upgraded to the
Novell 5.5.0 yet? if so has there been any or problems?

two more questions

1) During previous upgrades uninstalling the client was not necessary
and there were no issues but someone informed me that I should uninstall
the 5.3.4 client. I have not read this on any documents or manuals. Has
anyone read this anywhere?

2) The last time we upgraded we had a issue with extracting the files to
the right directorie(s) I remember  install not finding the files anyone
ever experience this before?

The configurations are below

TSM SERVER 5.3.4
AIX 5.3
Novell Servers are at Netware 6.5 SP6
1 Novell Netware Server is at SP7

Thanks for Any Help, suggestions or comments in Advance!


How to selectively delete export tapes from volhist

2008-02-08 Thread Roger Deschner
I've got an older export tape I want to keep. But I've got several newer
ones that are no longer needed, and I'm tight on scratch tapes so I want
them back. All the options I can think of on the DELETE VOLHIST command
would delete all of them. Is there any other way? (AIX TSM 5.5)

Roger Deschner  University of Illinois at Chicago [EMAIL PROTECTED]
   Academic Computing  Communications Center


TSM Novell client 5.5 upgrade

2008-02-08 Thread Timothy Hughes

Hello All,

I am planning to start upgrading our TSM Novell clients next week from
5.3.4 to 5.5.0 and would like to know if anyone has upgraded to the
Novell 5.5.0 yet? if so has there been any or problems?

two more questions

1) During previous upgrades uninstalling the client was not necessary
and there were no issues but someone informed me that I should uninstall
the 5.3.4 client. I have not read this on any documents or manuals. Has
anyone read this anywhere?

2) The last time we upgraded we had a issue with extracting the files to
the right directorie(s) I remember  install not finding the files anyone
ever experience this before?

The configurations are below

TSM SERVER 5.3.4
AIX 5.3
Novell Servers are at Netware 6.5 SP6
1 Novell Netware Server is at SP7

Thanks for Any Help, suggestions or comments in Advance!


Re: Physically shred tape after one use? [ email retention ]

2008-02-08 Thread Allen S. Rout
 On Fri, 8 Feb 2008 07:49:11 -0500, Richard Rhodes [EMAIL PROTECTED] said:


 Are you talking about discoverable meaning the legal term
 discovery, or as in snoopable, meaning somebody gets access to
 your media because it falls off a truck or they walk out the door
 with it?

The former. :P

 We have had this conversation with our email folks here.  I have
 explained that, YES, the previous data is sitting there past the
 defined deletion period.  YES, it is possible to access it on a very
 expensive fishing expedition.

I think the problem here is that many people, coming to this question
fresh, try to set policy without understanding what we (backup admins)
mean when we say things like This is expensive, vs. This is
difficult vs. This is extremely difficult, and what-not.

When I talk about special equipment and gobs of staff time (I don't
think a stock 3592 will seek beyond logical EOT, will it?)  I seem to
get feedback that tastes of Oh, so it's possible, right?.

Yeah, if you want to pay mumblety-thousand dollars to a recovery unit,
you can get your bitstream back off the end of the tape (singular).
Put another mumblety-thousand dollars in staff time in, and you can
probably pick out email-looking stuff.  Is this part of our policy
response to discovery?  Probably not.

But when someone says to me This data must not be recoverable, even
through extraordinary measures, I shudder, and prepare to repel
boarding by the NSA.


- Allen S. Rout
- Why bother, they already know.


Re: TSM Novell client 5.5 upgrade

2008-02-08 Thread Timothy Hughes

KevinThanks for your response!

Were your recent posts on this (ADSM) site? Also, Is there a link were I
could take
a look at your PMRs? I do have a ID for the IBM site already. I have
noticed that there is
a Novell Client 5.5.0.1. I will probably be installing that one first on
one server then waiting
a couple days before installing the client on any more servers to see if
there are any issues.
I would like to also find out what the fixes are in 5.5.0.1.

Tim

Kinder, Kevin P wrote:


Tim,

We have had major, and I do mean major, problems with our upgrade, but
ours involved going to TSM server 5.5.0.0. IBM itself has been unable to
determine whether our problems are due to upgrading the server,
upgrading the clients, a combination of both, or the phase of the moon
when doing the upgrade.

I have detailed this problem in recent posts, but will be glad to share
more info with you offline. IBM's respose to my multiple PMRs on the
upgrade issues has ranged from average to pathetic, so I would strongly
urge you to do this on just one NetWare client, and one that you can
afford to lose, as you move into the 5.5 world.


Kevin Kinder
State of West Virginia



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Timothy Hughes
Sent: Friday, February 08, 2008 10:31 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM Novell client 5.5 upgrade

Hello All,

I am planning to start upgrading our TSM Novell clients next week from
5.3.4 to 5.5.0 and would like to know if anyone has upgraded to the
Novell 5.5.0 yet? if so has there been any or problems?

two more questions

1) During previous upgrades uninstalling the client was not necessary
and there were no issues but someone informed me that I should uninstall
the 5.3.4 client. I have not read this on any documents or manuals. Has
anyone read this anywhere?

2) The last time we upgraded we had a issue with extracting the files to
the right directorie(s) I remember  install not finding the files anyone
ever experience this before?

The configurations are below

TSM SERVER 5.3.4
AIX 5.3
Novell Servers are at Netware 6.5 SP6
1 Novell Netware Server is at SP7

Thanks for Any Help, suggestions or comments in Advance!




Re: Physically shred tape after one use? [ email retention ]

2008-02-08 Thread Allen S. Rout
 On Fri, 8 Feb 2008 14:11:47 -0500, Wanda Prather [EMAIL PROTECTED] said:

 For the onsite stuff, tell the people who want the stuff physically
 erased that they have to buy you enough SATA disk to store all their
 email backups, and set up a TSM file pool with Disk Shredding
 (that's what it's for).

You know, that's a fine fine idea.

Heck, I could do that both locally and remotely.  It's cheaper than
buying a chipper.

- Allen S. Rout


Re: Physically shred tape after one use? [ email retention ]

2008-02-08 Thread Allen S. Rout
 On Thu, 7 Feb 2008 17:25:10 -0500, Richard Sims [EMAIL PROTECTED] said:

 Applicable state and federal laws largely determine the disposability
 of media, as previously explored in threads such as
 http://www.mail-archive.com/adsm-l@vm.marist.edu/msg74957.html

 If media is kept in a secured facility, then the issue is moot, as no
 unauthorized persons will gain access to the media.  Under such
 circumstances there is no issue as to rewriting or data
 recoverability at any point.


My apologies for the imprecision.  The exposure threat against which
this measure is contemplated is that of legal discovery.

It is thought that, once the tape is reclaimed and comes out of
pending state, if it is re-used for some host which writes relatively
slowly, then data beyond the new end-of-tape marker might be subject
to discovery.

I am hoping to discourage this interpretation, emphatically.


- Allen S. Rout


Re: Physically shred tape after one use? [ email retention ]

2008-02-08 Thread Gee, Norman
 
Take a look at the FATS/FATAR product from www.fdr.com. It has the
capability of reading pass EOF on 3592 tapes.


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Allen S. Rout
Sent: Friday, February 08, 2008 10:25 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Physically shred tape after one use? [ email retention ]

 On Fri, 8 Feb 2008 07:49:11 -0500, Richard Rhodes
[EMAIL PROTECTED] said:


 Are you talking about discoverable meaning the legal term
 discovery, or as in snoopable, meaning somebody gets access to
 your media because it falls off a truck or they walk out the door
 with it?

The former. :P

 We have had this conversation with our email folks here.  I have
 explained that, YES, the previous data is sitting there past the
 defined deletion period.  YES, it is possible to access it on a very
 expensive fishing expedition.

I think the problem here is that many people, coming to this question
fresh, try to set policy without understanding what we (backup admins)
mean when we say things like This is expensive, vs. This is
difficult vs. This is extremely difficult, and what-not.

When I talk about special equipment and gobs of staff time (I don't
think a stock 3592 will seek beyond logical EOT, will it?)  I seem to
get feedback that tastes of Oh, so it's possible, right?.

Yeah, if you want to pay mumblety-thousand dollars to a recovery unit,
you can get your bitstream back off the end of the tape (singular).
Put another mumblety-thousand dollars in staff time in, and you can
probably pick out email-looking stuff.  Is this part of our policy
response to discovery?  Probably not.

But when someone says to me This data must not be recoverable, even
through extraordinary measures, I shudder, and prepare to repel
boarding by the NSA.


- Allen S. Rout
- Why bother, they already know.


Re: migrateing .9TB of data

2008-02-08 Thread Richard Rhodes
What kind of data is it?

If mostly static files, we like to use rdist (robocopy on windows).  Run it
every so often, then a final run at cutover. You can multiple parallel cmds
if need be.

If a database you can use a backup/restore with rollinig logs (at least for
oracle).  We have moved Multi TB Oracle databases this way with only a few
min of downtime at cutover.

In general, a TSm backup/restore is about the last thing we look at to
migrate servers.  It's usually too big of an outage.


Rick





 Larry Clark
 [EMAIL PROTECTED]
 R.COM To
 Sent by: ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager
 [EMAIL PROTECTED] Subject
 .EDU migrateing .9TB of data


 02/07/2008 06:13
 PM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






Currently I am migrating servers for a customer. In all instances but one I
am using a combination of mksysb and sysback on uservgs to do this.

One node has .9TB of data, however and would take too long using sysback.

Someone has suggested using TSM. Can the client node be exported to tape
and
imported on a TSM server at the target site?


-
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.


Re: Physically shred tape after one use? [ email retention ]

2008-02-08 Thread Wanda Prather
Should either

1) solve the problem or
2) make them go away, which will
3) solve the problem!


On 2/8/08, Allen S. Rout [EMAIL PROTECTED] wrote:

  On Fri, 8 Feb 2008 14:11:47 -0500, Wanda Prather [EMAIL PROTECTED]
 said:

  For the onsite stuff, tell the people who want the stuff physically
  erased that they have to buy you enough SATA disk to store all their
  email backups, and set up a TSM file pool with Disk Shredding
  (that's what it's for).

 You know, that's a fine fine idea.

 Heck, I could do that both locally and remotely.  It's cheaper than
 buying a chipper.

 - Allen S. Rout



Re: How to selectively delete export tapes from volhist

2008-02-08 Thread Stapleton, Mark
Roundabout way: create a second TSM instance, share your library out to
the new instance, run EXPORT NODE TOSERVER=new_instance, delete the
export volume history entries you want, then run EXPORT NODE
TOSERVER=original_instance.
 
--
Mark Stapleton
Berbee (a CDW company)
System engineer
7145 Boone Avenue North, Suite 140
Brooklyn Park MN 55428-1511
763-592-5963
www.berbee.com
 

 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
Of
 Roger Deschner
 Sent: Friday, February 08, 2008 11:20 AM
 To: ADSM-L@VM.MARIST.EDU
 Subject: [ADSM-L] How to selectively delete export tapes from volhist
 
 I've got an older export tape I want to keep. But I've got several
newer
 ones that are no longer needed, and I'm tight on scratch tapes so I
want
 them back. All the options I can think of on the DELETE VOLHIST
command
 would delete all of them. Is there any other way? (AIX TSM 5.5)
 
 Roger Deschner  University of Illinois at Chicago
[EMAIL PROTECTED]
Academic Computing  Communications Center


Re: Physically shred tape after one use? [ email retention ]

2008-02-08 Thread Wanda Prather
Ack.  I feel your pain.
(Those are the same people who will argue with you that AES256 encryption
just isn't secure enough.)

But the L word (litigation) trumps everything, as far as I've been able to
determine.

Isn't there an ERASE command that works on the 359x hardware?
You can't access it via TSM, but perhaps you could invoke it from AIX,
creating a very tedious task for operators to use when tapes come back from
the vault.  (But that will only work if you PROMISE not to mention to them
that the dead stuff still exists on tapes in between good stuff that hasn't
expired, and you can retrieve that if you restore your TSM DB back 3 or 4
months whenever they need it)

For the onsite stuff, tell the people who want the stuff physically erased
that they have to buy you enough SATA disk to store all their email backups,
and set up a TSM file pool with Disk Shredding (that's what it's for).

W






On 2/8/08, Allen S. Rout [EMAIL PROTECTED] wrote:

  On Fri, 8 Feb 2008 07:49:11 -0500, Richard Rhodes 
 [EMAIL PROTECTED] said:


  Are you talking about discoverable meaning the legal term
  discovery, or as in snoopable, meaning somebody gets access to
  your media because it falls off a truck or they walk out the door
  with it?

 The former. :P

  We have had this conversation with our email folks here.  I have
  explained that, YES, the previous data is sitting there past the
  defined deletion period.  YES, it is possible to access it on a very
  expensive fishing expedition.

 I think the problem here is that many people, coming to this question
 fresh, try to set policy without understanding what we (backup admins)
 mean when we say things like This is expensive, vs. This is
 difficult vs. This is extremely difficult, and what-not.

 When I talk about special equipment and gobs of staff time (I don't
 think a stock 3592 will seek beyond logical EOT, will it?)  I seem to
 get feedback that tastes of Oh, so it's possible, right?.

 Yeah, if you want to pay mumblety-thousand dollars to a recovery unit,
 you can get your bitstream back off the end of the tape (singular).
 Put another mumblety-thousand dollars in staff time in, and you can
 probably pick out email-looking stuff.  Is this part of our policy
 response to discovery?  Probably not.

 But when someone says to me This data must not be recoverable, even
 through extraordinary measures, I shudder, and prepare to repel
 boarding by the NSA.


 - Allen S. Rout
 - Why bother, they already know.



Re: migrateing .9TB of data

2008-02-08 Thread Larry Clark

db2

- Original Message -
From: Richard Rhodes [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Friday, February 08, 2008 7:21 AM
Subject: Re: [ADSM-L] migrateing .9TB of data



What kind of data is it?

If mostly static files, we like to use rdist (robocopy on windows).  Run
it
every so often, then a final run at cutover. You can multiple parallel
cmds
if need be.

If a database you can use a backup/restore with rollinig logs (at least
for
oracle).  We have moved Multi TB Oracle databases this way with only a few
min of downtime at cutover.

In general, a TSm backup/restore is about the last thing we look at to
migrate servers.  It's usually too big of an outage.


Rick





Larry Clark
[EMAIL PROTECTED]
R.COM To
Sent by: ADSM:   ADSM-L@VM.MARIST.EDU
Dist Stor  cc
Manager
[EMAIL PROTECTED] Subject
.EDU migrateing .9TB of data


02/07/2008 06:13
PM


Please respond to
ADSM: Dist Stor
Manager
[EMAIL PROTECTED]
  .EDU






Currently I am migrating servers for a customer. In all instances but one
I
am using a combination of mksysb and sysback on uservgs to do this.

One node has .9TB of data, however and would take too long using sysback.

Someone has suggested using TSM. Can the client node be exported to tape
and
imported on a TSM server at the target site?


-
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.