When Does Data Backup Become a Full Time Job?

nasteric asks: "Myself and 5 co-workers assume a number of responsibilities at my current job, including monitoring our tape backup jobs that run nightly. We do a good job of keeping non work related items (mp3's, wav files, etc.) off our servers, but our users keep eating up disk space very quickly. File storage, along with the fact that we have numerous projects 'going live' that each require one or more servers means more investment in our backup solutions. Fortunately, we have the capital to expand our backup solution (media, drives, autoloaders, software, etc.) but my boss cringes when I suggest hiring a full-time person to handle the backups. Ensuring the integrity of our nightly backups is critical, but my teammates are being spread thin due to the rapid expansion of our company. We really feel the best solution would be dedicated backup person. We currently backup approximately 3.5 terabytes of data and our enterprise expands to over 4 states. Does anybody have any suggestions as to when data backup becomes a full-time position? Are there any resources that specify when a full-time person dedicated to data backup should be hired? It would be nice to have some resources to refer to when proving my point to my boss."

Comments

Obvious?

[Perdo]

When the cost of losing data exeeds the salery that would be paid to a dedicated IT guy

-or-

Backup will be taken seriously right after you loose a good chunk of data.

Then your boss will hire two people. One to do backups and one to replace the guy that cheesed the last one.

With all due respect...

[aaarrrgggh]

Is there a business need for the level of backup that is being provided? Specifically, is the backup strategy in-line with the value of the data? No timeframe is given for your 3.5TB, so it is difficult to discern your exact needs.

Maybe the easier battle to fight is to reduce the level of data backup, and show how it can save the company money. Chart the growth in number of tapes in your backup journal, and see if it is getting out of hand.

Of course, if you ever DO have a problem, you will be fired, but... what are the odds? ;)

automated solutions?

[Tumbleweed]

Have you looked into ways of only backing up data that really _needs_ to be backed up? Perhaps a backup solution that is configurable enough to block out mp3's and suchlike? Make the users do some of the work, or at least configure their machines so that the software they use saves files in places that get backed up automatically? (yet is still subject to the non-mp3,etc filters)

There's no way that this kind of thing *can't* be automated with enough work. The amount of billable time spent to get such a system going has to be much less than hiring a full-time backer-upper.

A place I used to work at had some shared drives on the servers - if you wanted your data backed up, you fricking saved it to those shared drives (dedicated folders for each employee & project), or else you didn't get your data backed up. And if something happened to your data that wasn't backed up, it's your problem (and thus, your ass).

Just a few thoughts.

Just a thought.

Re:automated solutions?

[madajb]

Interesting, but it doesn't work like that in The Real World(tm).

In The Real World(tm), users bitch and moan to their boss, who bitches and moans to his boss, who will then bitch and moan to your boss, who will bitch and moan to you.

When this happens, you _will_ drop what you are doing and restore said file.

My solution to this problem in the past has been simple. Start writing a log, simple spreadsheet, whatever, of how many hours per week you spend working on the backups (changing tapes/checking the logs/restoring). Do the same for your coworkers. If you and each of your coworkers spend 6 or so hours a day, that's about 40 hours, or one full time person. If it ends up being only a few hours a day, it might not be worth hiring a full timer.
Of course, this doesn't take into account intangibles, like how productive you are if you keep getting interrupted every hour to restore something. Or how much you know/don't know about optimizing backup solutions.

Another, perhaps more palatable option, is the rotating shift. Just like a rotating on call schedule, one person is responsible for all backup related issues during a given week. Presuming you have an automated system, this should really be limited to changing tapes, the occasional backup, and checking the logs to make sure things didn't break in the night.

===
-ajb

Cost analysis

[TheSHAD0W]

Is the total time spent by people in your department on backup operations approaching 40 hours per week? If your department needs more manpower anyway, and the bosses are considering hiring another person, then yes, you might as well dedicate this guy to backup solutions. Specialization is more cost effective than interrupting other jobs to do the work.

Create a part-time postition

[dt23507]

Just a thought: Would your boss would be more willing to hire someone *part-time* to handle the backups?

Oh, oh!

[Associate]

Hire me! Please! I can do mind numbing tasks for hours on end. As long as I can read /. between tapes. I work cheap too. I think $45k sounds good.