ADSM-L

Re: [ADSM-L] Netware backup include/exclude/domain issues

2007-06-06 13:04:23
Subject: Re: [ADSM-L] Netware backup include/exclude/domain issues
From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 6 Jun 2007 13:03:18 -0400
I tried the "DOMAIN VOLUMENAME: -NDS"  but it wasn't happy.

Not sure why you would need to install TSM multiple times.  We do have
individual opt files and are using -optfile= options and that works. If
there is a collision issue then we will look at doing your way.

Can you send me one of your dsm.opt files ?
----------------------------------------------------
Zoltan Forray
Virginia Commonwealth University
Office of Technology Services
University Computing Center
e-mail: zforray AT vcu DOT edu
voice: 804-828-4807



"Ball, Tim" <Ball.Tim AT PRINCIPAL DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
06/06/2007 12:51 PM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: [ADSM-L] Netware backup include/exclude/domain issues






We installed TSM to each volume, set up an opt for the specific volume
with the domain statement pointing only to that volume.  Even renamed
the dsmc.nlm to a more volume specific name such as dsmcshare.nlm.  This
allowed us to load/unload as needed without effecting the other volumes.
We also renamed dsmcad.nlm in the same fashion.

Tim Ball
IT System Associate - Lead
Principal Financial Group
Mason City, IA  50402
641.421.4973

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Wednesday, June 06, 2007 11:41 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Netware backup include/exclude/domain issues

We have this big-honkin Netware server we are creating, to consolidate
multiple smaller servers.

Each department will have their own volume.  Therefore, we need to
create
multiple opt files and nodes to keep each volumes backup separate from
the
others.  We created separate Netware id's that have specific rights to
their volumes, only.

Try as I might, I can't seem to get an incremental backup from scanning
all the volumes and generating errors.

If I negate the volumes via the DOMAIN statement, this works.  But, as
we
add volumes, we would have to go around and update dozens of opt
files.....not a good idea since we are already at 20-volumes.

I tried the approach of EXCLUDE *\*:*   and then an INCLUDE
server\volume:/.../   but it still scans everything.   Even tried
exclude.dir *

It also keeps erroring on trying to backup "System specific information"
eventhough I have DOMAIN -SYS: -NDS.  How do you exclude this attempt to
backup the "system specific information" on a Netware system ?

What am I doing wrong ?  Anyone else have this kind of configuration.
----------------------------------------------------
Zoltan Forray
Virginia Commonwealth University
Office of Technology Services
University Computing Center
e-mail: zforray AT vcu DOT edu
voice: 804-828-4807


-----Message Disclaimer-----

This e-mail message is intended only for the use of the individual or
entity to which it is addressed, and may contain information that is
privileged, confidential and exempt from disclosure under applicable law.
If you are not the intended recipient, any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by
reply email to Connect AT principal DOT com and delete or destroy all copies of
the original message and attachments thereto. Email sent to or from the
Principal Financial Group or any of its member companies may be retained
as required by law or regulation.

Nothing in this message is intended to constitute an Electronic signature
for purposes of the Uniform Electronic Transactions Act (UETA) or the
Electronic Signatures in Global and National Commerce Act ("E-Sign")
unless a specific statement to the contrary is included in this message.

While this communication may be used to promote or market a transaction
or an idea that is discussed in the publication, it is intended to provide
general information about the subject matter covered and is provided with
the understanding that The Principal is not rendering legal, accounting,
or tax advice. It is not a marketed opinion and may not be used to avoid
penalties under the Internal Revenue Code. You should consult with
appropriate counsel or other advisors on all matters pertaining to legal,
tax, or accounting obligations and requirements.