Hi Ashish,

Our archive data sizes are about 100TB+, with issues of partial restore, we
want to avoid it.

Any inputs for the backupsets? Restore permissions ?

Thanks
Amit


On Fri, Aug 24, 2012 at 11:47 PM, ashish sharma <ashishsharma44 AT gmail DOT 
com>wrote:

> Hi,
>
> Why dont you first make a tar file of your data and then archive it? This
> will keep the TSM DB size very small as for one archive you will have just
> one entry in TSM database. Of course partial retrieval is not possible in
> this case.
>
> On Sat, Aug 25, 2012 at 8:48 AM, amit jain <amit12.jain AT gmail DOT com> 
> wrote:
>
> > Hi,
> >
> > We are planning to change our archive strategy. Planning to do one time
> > full backup and then create two backup sets, latter delete the backups.
> > With this strategy we can have  single tsm instance to cover most of our
> > archive needs,  as this will not fill up the TSM DB size. Also we can
> have
> > the archive without having to bother about the archive getting terminated
> > in between and triggering the archive again.
> >
> > Any one knows the downside of backups set apart from the fact that
> partial
> > restores take longer. Any other issues or suggestions ? What about file
> > permissions ? Somebody told me that on linux the restore may not have
> same
> > permissions ?  We will be using it for archiving big filesets.
> >
> > With version 6.2 TSM DB size has reached about 1TB with 2 archives. So DB
> > size is big driver for us to move to backupsets. Any one using
> backupssets
> > ? How is the permissions while restore for LINUX filesystems  ?
> >
> > Any inputs will be of help.
> >
> >
> > Thanks
> > Amit
> >
>
>
>
> --
> Best Regards
> Ashish Sharma
> ST Microelectronics Ltd.
> 919717003853
>