Only problem with this approach is that the files are now in an
Netabckup image format that the end user cannot directly access.

On 12/7/05, Dave Markham <dave.markham AT fjserv DOT net> wrote:
> Just a suggestion it may not work in practice but what about doing
> something i suggested but create a storage unit in netbackup as a disk
> device and tell your policy to use that.
>
> Then when invoking bparchive it would write things to a different set of
> disks/array which the customers could still have access to for archived
> data. It would also still have the added benefit of removing it from
> live data storage area thus saving space.
>
> An idea maybe?
>
> Dave
>
>
> Simon Weaver wrote:
>
> > Dave
> >I don't really want to go down this route - maybe an Archiving software
> >solution, where the data is stored on another array (maybe getting
> >backed up once a month) and still accessible to customers!
> >
> >
> >Simon
> >
> >-----Original Message-----
> >From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> >[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Dave
> >Markham
> >Sent: 06 December 2005 17:01
> >To: Simon.Weaver
> >Cc: Veritas-bu AT mailman.eng.auburn DOT edu
> >Subject: Re: [Veritas-bu] ARchiving Old Data
> >
> >I have read the threads here and no-one has mentioned the simple
> >scripting technique.
> >
> >I use bparchive quite a bit to archive logs and other things older than
> >x days on various servers. If its any use this is how i do things using
> >netbackup and solaris.
> >
> >Netbackup :-
> >
> >Standard policy with a volume pool of log_archive
> >
> >A schedule of type User_Archive with a long retention period and using
> >log_archive tape pool
> >
> >Have a backup window of 2200 -> 1200am
> >
> >No backup selections and all clients added i want to be able to archive
> >data
> >
> >
> >Clients :-
> >
> >On each client i have a simple shell script called from cron each night
> >around 11pm.
> >This simply finds files older than x amount of time and puts them in a
> >list to be archived.
> >Then if the list is > 0 bytes it invokes bparchive with the file list.
> >This then backs files up to tape and removes them from the server
> >automatically.
> >Its a fully automated system and reports through netbackup as a separate
> >job. I find it very useful for archiving of data to tape and removing
> >from server in the same go.
> >
> >Example of the dead simple shell script to use :-
> >
> >
> >
> >#!/bin/sh
> >WR=/usr/openv/netbackup/bin
> >hostname=`hostname`
> >
> >#########################################################
> >#
> ># Make sure to check when directing find command to file.
> ># >> /tmp/cout is to be DELETED
> ># >> /tmp/fout is to be ARCHIVED TO TAPE #
> >#########################################################
> >
> >
> > > /tmp/fout
> > > /tmp/cout
> >
> >#archive files
> >find /opt/HTTPD/logs/access_log* -type f -mtime +30 >> /tmp/fout
> >2>/dev/null find /opt/HTTPD/logs/error_log* -type f -mtime +30 >>
> >/tmp/fout 2>/dev/null find /opt/HTTPD/logs/error-ssl_log* -type f -mtime
> >+30 >> /tmp/fout
> >2>/dev/null
> >find /var/audit/*$hostname -type f -mtime +14 |grep -v not >> /tmp/fout
> >2>/dev/null
> >
> ># Delete files older than 30 days in tmp find /tmp/ -mtime +30 -type f
> >
> >
> >>>/tmp/cout
> >>>
> >>>
> >
> >
> >if [ -s /tmp/cout ];then
> >        cat /tmp/cout | xargs rm
> >fi
> >
> >if [ -s /tmp/fout ];then
> >        $WR/bparchive -L /var/log/arch.log -f /tmp/fout f
> >
> >_______________________________________________
> >Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> >http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >
> >
> >
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>