5 replies
by cavedweller
Ususlly some kind of cost/benefit analysis should work. Get some application notes from Vetitas (Backup Exec) or CA (ArcServe) and show how a faster, centralized backup could save them money. By the way, I think that BE can read NT-Backup tapes. It can also do virus scanning before backup which can help keep you from restoring a virus. I used ArcServe briefly but didn't like it's scheduling options.
Do you have someone tending the tape drive 24 hrs or is the data transfer rate so slow that it just takes that long? They sound too cheap to have bought an autoloader.
In any case, a new tape drive isn't that expensive. What is the business value of the data. Can you wait 24 Hrs to restore lost files? What if your only tape drive breaks?
I'm sure other TR members have some good ideas too.
by bdhageman
by lo
Hi - 1st answer on right track.
Even if do valid cost/benefit analysis, may not be able to convince mgt to spend $. Unfortunately, 4 mind set, it will take crash/recovery/rebuild to convince them time and $ in backup is justified.
As you willbe held responsible should do a cost just. Benefits may be long sht (if x happens & we have ... then). Mgt doesn't like spend $ because think it will not happen to them.
Like car ins. Murphy wrks 24x7. If u operate sys 2-5 years, can expect 1dsk fail, 1 pwr fail, 1 ... In justifcation est. time to rebuild/restore/reconfigure fire, vandalizm, hdw failure, etc., with & w/out good bu 4 what needs rebuilt. Be honest & objective in est. (if you need to rebuild from scratch, you do it, takes 50 hors, you can't get up in 2 days, can't stay up that long & be effective, est.e wrk 16-18/day (get sleep when bu restores, inst runs, etc.).
Besides recvry 4 disasster, there is 3 mth after last file access, access again & find out that it isdel, corrupt, etc. While doesn't happen too often, occurs enough that hav file resolves/ Nice when asked ... for the last 6 months ..., log file hist, mail memos (HR problem), etc.
Wwe keep 45 day all disks + prod db, 18 wk (daily), 18 mth (daily). Keep 3 mth prod db tran log & various other bu. Keep 1 on 1 off site (purchased storage). Lot of $, but if/when we expect we will be able to rebuild in a reasonable time. For my company, I think they estimate down time at 1k/min. Down for 1day (24 hr) while you rebuild vs down for 8-10 hr for restore, it's not too hard to justify a good bu policy.
Those that think it won't happen, will have to be creative to convince.
Good luck. Not situation 1 likes to be. Best u can do is try (every mth (wk?) or so). If/when, you can say "Remember when I gave you all of those cost/benefit ..."
by bdhageman
by bdhageman
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending