I would recommend creating a second copygroup and a private storage pool
for that node.  You'd probably want to give it a DB snapshot of its own
also.

If you NEED backupsets, then you definitely need the source pool to be
collocated.  If you have to, it could be by group with all of your other
nodes in one group and this one in its own.  That would at least save
media mount times on recreates.

Your other option is EXPORT NODE using FROMDATE and FSID.  You can't
restore it directly from the client, but it can still be imported to a
stranger tsm server.  Also, trying to do incrementals this way would not
clear out files which had been deleted between exports, so in a recovery,
you'd be left with stray files.

-Josh



On 06.03.10 at 10:34 Timothy.Hughes AT OIT.STATE.NJ DOT US wrote:

Date: Fri, 10 Mar 2006 10:34:39 -0500
From: Timothy Hughes <Timothy.Hughes AT OIT.STATE.NJ DOT US>
Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Weekly/Monthly -Backupsets running long

Mark,

Thanks, These Backupsets are for a Novell Client they are still
currently using ArcServe for there full weekly backup of a POI
Volume on a Novell OS server until we get ours working
correctly.  I believe they do this because this Volume is very
important and holds many many GroupWise user files and they
the Backup Sets for Archival/Restores.

So I assume this means there is no way to shorten these? They
causing tape problems with Oracle clients on the weekend.

Thanks again!

Mark Stapleton wrote:

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 03/10/2006
09:05:13 AM:

I have Backup Sets that run extremely long these Backup Sets
backup only 1 file space. It seems the Backup Sets are backing
up the same Data plus the new Data it's like doing a Full backup
every week. Is there a command or setting that I can implement
to ensure that the Backup Set only backs up ONLY the NEW
Data? Or is there another way lessen the time on these
Backup Sets.

By definition, a backupset creates a copy of the most recent version of
*every* active file in a given server (or a filespace within that server).

Sorry.

As a matter of curiosity, why do you create regular backupsets? Do you
ever use them?

--
Mark Stapleton (mark.stapleton AT usbank DOT com)
MR Backup and Recovery Management
262.790.3190

------------------------------------------------------------------------------
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.
==============================================================================