This is just one folder I'm talking about here. This folder simply has files
that are recordings of every single phone call and cust service rep's computer
screen while that phone call was happening. Were talking about 100gigs per day
and these people want to be able to go back a year!
So what we are doing is setting up a script to copy certain files (the ones
that are over 24 hours old) and move them into this folder which will then be
archived by netbackup. Problem we have is if the folder is NOT archived (i.e.
the script fails or doesn't run for whatever reason and we are not notified
about it) and we don't catch it right away that drive will fill up quickly.
This is really my only option as no one wants to throw any more money into this
project. Luckily I have a ton of tapes.
My main question was that I wasn't sure if there was an alternative to USER
Archive Backups. It seems like a logical option to be able to have server
directed archived backups in NB, I just figured I couldn't find where to do it.
Our big concern is that if the scheduled task doesn't run (which has happened
and a server went without backups for 2 months) we would never know about it
unless everyday we checked for a successful backup of the client initiated
backups.
-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu [mailto:veritas-bu-bounces
at mailman.eng.auburn.edu] On Behalf Of David Rock
Sent: Wednesday, May 16, 2007 10:49 AM
To: veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Starting an Archive backup from a policy
* Schneider, Matthew J. <Matthew.Schneider at mybrighthouse.com> [2007-05-16
09:19]:
> Hello,
>
> I'm trying to setup a policy to start an Archived backup from the
> media server instead of from the client. In other words I would
> rather not use a script to start an archived backup from the client in
> the case the scheduled task or script fails, I would not find out
> about in the Activity Monitor.
no, no, NO. User Archive backups can be run only from the client system
for a reason. You want the USER to be the one to shoot themselves in
the foot, not you. User Archives are bad news, ESPECIALLY scripted
ones. All it takes is one filelist entry to be wrong and your whole
client system is GONE (backed up, but gone regardless).
So, unless you are the admin of that client system, do not go near it.
A better option is to understand what you are trying to accomplish and
see if there is a better (safer) way to do it. Archive jobs are not
really intended to be used as a space-saving technique, they should be
used to Archive data (Take static data that is logically related and
store it off the system). That is not the same thing.
Having said all that, of course there are ways to do it (bpstart_notify
on the client for one) but you should really re-evaluate your needs.
--
David Rock
david at graniteweb.com
_______________________________________________
Veritas-bu maillist - Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
CONFIDENTIALITY NOTICE: This e-mail may contain information that is privileged,
confidential or otherwise protected from disclosure. If you are not the
intended recipient of this e-mail, please notify the sender immediately by
return e-mail, purge it and do not disseminate or copy it.
|
