Thanks David! I have not been backing up developers PCs and my boss is trying to
get them to pin down very specific file paths to be backed up. He is afraid we
will be getting into a black hole and would need to expand our hardware
capabilities if we leave the door open. Your suggestion is well taken. I have
been backing up only servers in the past... User data has been protected by
backing up user home directories on network drives...
George
David Longo <David.Longo AT HEALTH-FIRST DOT ORG> on 02/15/2001 03:14:19 PM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: George Lesho/Partners/AFC)
Fax to:
Subject: Re: inclexcl
For a short answer I would take the path of least resistance. If you are only
backing up a few files/directories it would be simplest (easiest to figure out
the incl/excl statements and their effects) to do one of the following:
1. Include the directories/files you want backed up and then exclude the world.
2. Have your schedule do a SEL instead of INC and put the directory you want
backed in the Objects parameter.
This is just a very brief overview - depends on how many things you want or want
to exclude.
David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH 321.434.5536
Pager 321.634.8230
Fax: 321.434.5525
david.longo AT health-first DOT org
>>> glesho AT AFCE DOT COM 02/15/01 03:16PM >>>
I am looking at putting on a bunch of client PCs in the future where there will
only be a limited number of paths and/or files that will need to be backed up.
Is there anything written, relative to windows, on the syntax and methodology or
either excluding or including specific files? The TSM documentation on this is
kind of thin. Would also like to look at the same type of material for Novell
clients. Thanks-
George Lesho
Storage/System Admin
AFC Enterprises
"MMS <health-first.org>" made the following
annotations on 02/15/01 16:19:18
------------------------------------------------------------------------------
This message is for the named person's use only. It may contain confidential,
This message is for the named person's use only. It may contain confidential,
proprietary, or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it, and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are
not the intended recipient. Health First reserves the right to monitor all
e-mail communications through its networks. Any views or opinions expressed in
this message are solely those of the individual sender, except (1) where the
message states such views or opinions are on behalf of a particular entity; and
(2) the sender is authorized by the entity to give such views or opinions.
=======================================
|
