ADSM-L

Re: [ADSM-L] Taking Permanent Offsite Copy before deletion

2008-12-02 09:13:07
Subject: Re: [ADSM-L] Taking Permanent Offsite Copy before deletion
From: Curtis Preston <cpreston AT GLASSHOUSE DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 2 Dec 2008 09:11:00 -0500
Doesn't the backup set contain only the active files, where the export node 
will contain active and inactive files?  Wouldn't that make a backup set much 
faster?

Richard, why don't you want to go the backup set route?



Curtis Preston  |  VP Data Protection  
GlassHouse Technologies, Inc.
 
T: +1 760 710 2004 |  C: +1 760 419 5838 |  F: +1 760 710 2009  
cpreston AT glasshouse DOT com |  www.glasshouse.com
Infrastructure :: Optimized
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Roger Deschner
Sent: Monday, December 01, 2008 9:31 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Taking Permanent Offsite Copy before deletion

.
Consider GENERATE BACKUPSET for this, instead of EXPORT NODE. There are
both pluses and minuses.

ADVANTAGE: You can restore from it without the server, or even without a
network. All you need is a client that is more or less the same level as
when it was generated, and the physical media. If the physical media is
tape, you can check it out of your tape library, freeing valuable slots.

DISADVANTAGE: You can restore from it without the server, so the server
no longer keeps track of it for you in its database. Physical media can
get lost, become obsolete, or be incompatible with client system
hardware. (That is, if your server writes on LTO4 tape, does your CLIENT
have an LTO4 tape drive?)

The time it takes to produce a backupset should be about the same as for
an export. That is, same number of tape mounts, etc.

There's a lot of information about backupsets in the TSM Administrator's
Guide.

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu


On Mon, 1 Dec 2008, Mark Stapleton wrote:

>
>       help export node
>
>at the TSM server command line, particularly the version that exports to
>a tape device class.
>
>
>--
>Mark Stapleton (mark.stapleton AT cdw DOT com)
>CDW Berbee
>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:ADSM-L AT VM.MARIST DOT EDU] On Behalf
>> Of Cheung, Richard
>> Sent: Monday, December 01, 2008 7:02 PM
>> To: ADSM-L AT VM.MARIST DOT EDU
>> Subject: [ADSM-L] Taking Permanent Offsite Copy before deletion
>>
>> Hi all
>>
>> I have a few nodes which have been decommissioned as production
>systems
>> in my environment and therefore no longer exists.   I want to delete
>> them from within TSM as well as delete any filespaces associated with
>> them - so the data is no longer consuming space in the production tape
>> storage library etc.
>>
>> However I don't want to 'loose' these data - as we have a business
>> requirement that we require the ability to restore from these data for
>> a
>> period of time.
>>
>> So, logic and mechanics aside in terms of retention of hardware for
>> such
>> restores.....   the query I have is, what is the procedure for me to
>do
>> a kind of 'export' or 'copy' of these filespace data for these old
>> nodes
>> to be taken offsite?  Would i need to create some kind of new
>mediapool
>> - eg call it archival - set a never expire on the data etc, and just
>> copy it??
>>
>> <html>
>> <body>
>> <font face="arial" color=#808080 size="-2"><img
>> alt="Santos Logo" src="http://www.santos.com/library/logo.gif";>
>> <br>Santos Ltd A.B.N. 80 007 550 923<br>
>> Disclaimer: The information contained in this email is intended only
>> for the use of the person(s) to whom it is addressed and may be
>> confidential or contain privileged information.
>> If you are not the intended recipient you are hereby notified that any
>> perusal, use, distribution, copying or disclosure is strictly
>> prohibited.
>> If you have received this email in error please immediately advise us
>> by return email and delete the email without making a copy.</font>
>> <font face="arial" color=#008000 size="-2">Please consider the
>> environment before printing this email</font>
>> </body>
>> </html>
>





This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail.

<Prev in Thread] Current Thread [Next in Thread>