# Network Backup

**URL:** <https://boards.straightdope.com/t/network-backup/635432>\
**Category:** Factual Questions\
**Created:** [September 21, 2012, 9:05pm UTC](https://boards.straightdope.com/t/network-backup/635432 "2012-09-21T21:05:16Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![howye](https://avatars.discourse-cdn.com/v4/letter/h/a9adbd/32.png) [@howye](https://boards.straightdope.com/u/howye)\
**Post date:** [September 24, 2012, 2:06pm UTC](https://boards.straightdope.com/t/network-backup/635432/21 "2012-09-24T14:06:59Z")

</div>

> [@yoyodyne](#):
>
> Upgrading infrastructure costs money that isn’t generated by the IT department. I don’t know any IT admin that wouldn’t be able to put more money to good use. The problem is going to the non-IT person that controls the budget with a proposal for a good backup system that costs $X plus $Y per user plus $Z per year maintenance and convincing them it’s better to spend the money than “just tell people to log off”.

Except telling people to log off is a loser proposition. It will never work and makes the IT dept. look amateurish. There are cost-effective ways around the problem as described. Indeed, if PSTs are the issue, you stop using PSTs. I understand they are not the nightmare they used to be, but OSTs and storing data on the server are a better option (even hard caps on email storage - although I don’t like those). Even being up to date on OS and email software will help to work around this.

I am out of IT now, and I never log out during the week. End of day, I three finger salute and lock the machine. My email is server stored and offloaded to archive files for retention policy purposes, all in the background.

[Previous page](https://boards.straightdope.com/t/network-backup/635432.md?page=1)