Hi Allen,

Thanks for your reply !!

Using virtual mount points do we know if TSM takes care of the Journalling of 
the files that he is going to do backup ¿?
If it takes care, the backup window will be more small because it knows which 
files have changed...¿? less processing time...
What do you think about that ¿?

Thanks in advance,

Regards,

Ibán Bernaldo de Quirós Márquez 
Technical Specialist 
cell: + 34 659 01 91 12 
Sun Microsystems Iberia



-----Mensaje original-----
De: ADSM: Dist Stor Manager en nombre de Allen S. Rout
Enviado el: vie 20/10/2006 19:08
Para: ADSM-L AT VM.MARIST DOT EDU
Asunto: Re: [ADSM-L] Backing up very large Filesystems...
 
>> On Fri, 20 Oct 2006 10:50:09 +0100, "Bernaldo de Quiros, Iban 1" 
>> <iban.bernaldodequiros AT SUN DOT COM> said:


> I am planning to backup very large Filesystems (GPFS filesystems),
> about 37 TB and more , does exists a White Paper or best practices
> to do that

Consider virtualmountpoints; these let you separate all kinds of
processing.  Independant storage volumes, independant incremental
processing, etc.

With separate filespaces, you can also make the reclamation
independant; this can be very useful if your file sizes on that huge
tract of land are normal.  You'll be talking many many millions; it
could take days of expiration to cover it.

If it's one big filespace, expiration has to finish the whole
filespace before it goes on.  That could be sticky in your case.

If your filespace is full of big (multi-GB) files, this might not be a
big deal.


- Allen S. Rout