<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>Re: [TLUG]: 'Best practices' question for a backup</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>You're right, however I guess that some people have anm expectation of what they do is private and not their employers business, hence having them sign an acknowledgement of such policies makes it clear what the expectations are. Not being a lawyer, I can't tell you who's correct, but at least by signing such an acknowledgement, the employer asserts his rights.<BR>
This could be a whole other discussion. Any lawyers here care to chime in?<BR>
D<BR>
Dave Bour<BR>
Desktop Solution Center<BR>
905.381.0077<BR>
dcbour@desktopsolutioncenter.ca<BR>
<BR>
For those who just want it to work...<BR>
Giving you complete IT peace of mind.<BR>
<BR>
(Sent via Blackberry)<BR>
PIN 30073084 (as of May 9,2005)<BR>
<BR>
-----Original Message-----<BR>
From: owner-tlug@ss.org <owner-tlug@ss.org><BR>
To: tlug@ss.org <tlug@ss.org><BR>
Sent: Thu Sep 22 15:41:56 2005<BR>
Subject: Re: [TLUG]: 'Best practices' question for a backup<BR>
<BR>
On Thu, Sep 22, 2005 at 02:32:54PM -0400, Dave Bour wrote:<BR>
> Madison, I currently run a backup service and this issue has come up<BR>
> before. My stance has been this.<BR>
><BR>
> The owner of the computer (usually the company president) has to sign<BR>
> off if a backup is requested by an individual. In my case, all files<BR>
> in the specified folders are backed up, regardless of permissions. As<BR>
> pointed out, there is an exposure of privledges during that period and<BR>
> my users have accepted that (or at least acknowledged that). <BR>
><BR>
> Conversely, in some cases, multiple users are using the same machine<BR>
> and all are concerned their data remain private. Again, the owner of<BR>
> the computer has the authority to acknowledge that the backup occurs<BR>
> regardless of the individual's desires, and everyone is advised<BR>
> accordlingly.<BR>
><BR>
> This "heavy handed" approach has cost me one client over the past 5<BR>
> years. The balance have accepted it and some companies have even<BR>
> changed their corporate policies such that the "company" has the<BR>
> rights on the computer, rather than individual. If the individual<BR>
> doesn't like the policies, they are welcome to find other jobs, etc.<BR>
<BR>
Dave, I'm curious. Why would such policy change be even necessary?<BR>
Company pays for premise, utility, computers, software, and salary.<BR>
<BR>
><BR>
> As long as it's documented and the users have acknowledged it, you<BR>
> should be clear.<BR>
><BR>
> In my case, this was the easiest approach rather than trying to do it<BR>
> a half dozen configurations to please each individual. <BR>
<BR>
--<BR>
William Park <opengeometry@yahoo.ca>, Toronto, Canada<BR>
ThinFlash: Linux thin-client on USB key (flash) drive<BR>
<A HREF="http://home.eol.ca/~parkw/thinflash.html">http://home.eol.ca/~parkw/thinflash.html</A><BR>
BashDiff: Super Bash shell<BR>
<A HREF="http://freshmeat.net/projects/bashdiff/">http://freshmeat.net/projects/bashdiff/</A><BR>
--<BR>
The Toronto Linux Users Group. Meetings: <A HREF="http://tlug.ss.org">http://tlug.ss.org</A><BR>
TLUG requests: Linux topics, No HTML, wrap text below 80 columns<BR>
How to UNSUBSCRIBE: <A HREF="http://tlug.ss.org/subscribe.shtml">http://tlug.ss.org/subscribe.shtml</A><BR>
</FONT>
</P>
</BODY>
</HTML>