Vidit,

This is one way that VSM help reduce the amount of data that NBU needs to
backup.  When a file is migrated even though it might not be purged from the
disk, NBU will see that all of it's copies have been secured within VSM.
Once this is done, NBU only needs to backup the placeholder (inode
information including the extended DMAPI information).  If you lose the
filesystem, simply restore the NBU which will reload all the non-migrated
(active data) and all the placeholders for the in-active data.  Your backups
and restores now will run faster.  After a recovery, simply accessing a
migrated file will cause the data to be cached back into the filesystem.  As
part of your backup tape management, make sure you include taking the second
copy of the HSM data offsite along with your backup tapes.  Another option
would be to make a third copy of the HSM data and take that with the NBU
tapes.

Mark

-----Original Message-----
From: vidit kohli [mailto:vidit_k AT hotmail DOT com]
Sent: Wednesday, February 27, 2002 12:18 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] HSM 3.4.1 issue


hi

i'm using 'ct' HSM method for migration. making dual copies with same 
method.


I used netbackup to backup filesystem of that server, but it did not picked 
up hsm controled files and there data.

what need to be done to get data of particular hsm filesystem using 
netbackup


vidit


_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu