We got creative.
Our dsm.opt for the scheduler has dfsmountpoint backup to yes
but as a post scheduled command we invoke dsmc inc -subdir=yes
-optfile=dsm2.opt /mountpoint/directory (or something like that syntax)
the dsm2.opt has dfsmountpoint set to no and no domain statements.
first we back up the mount point
then run an incremental for the share with a different options file with in the
scheduler as a batch post scheduled command.
its a stop gap until we get ndmp going ...
>>> warbogas AT INDIANA DOT EDU 12/06/06 03:44PM >>>
Richard,
I think I threw the baby out with the bath water. . When you
enlightened me on dsmcdfs I put it and the dfsbackupmntpnt option
together in the trash without too much thinking. But, on re-reading,
I see that dfsbackupmntpnt is indeed meant for backing up Dfs mount
points. But, how do people typically change the the dfsbackupmntpnt
option from 'no' to 'yes' between scheduled backups of the 1) mount
points, and 2) the files and directories? We would like to do both i
one schedule, but that looks improbable. Yes/no?
Thank you,
Keith
On Dec 6, 2006, at 2:35 PM, Richard Sims wrote:
Keith -
The dsmcdfs command was for backing up the open systems DCE
Distributed File System, unrelated to MS Dfs. As of TSM 5.2, DCE's
DFS utilizes XBSA to perform backups to TSM, so the TSM clients were
discontinued.
Richard Sims
On Dec 6, 2006, at 1:41 PM, Keith Arbogast wrote:
> Where do I read about the details of dsmcdfs for Windows? Is it a
> separate client? I have read the entries in Quickfact and looked in
> several of the manuals.
>
> Thank you,
> Keith Arbogast
> Indiana University
-------------------------
We Believe In Catholic Health Care. Stand Up For Our Mission!
Visit http://www.believecatholic.com
CONFIDENTIALITY NOTICE: This message is confidential, intended only for the
named recipient(s) and may contain information that is privileged, or exempt
from disclosure under applicable law. If you are not the intended recipient(s),
you are notified that the dissemination, distribution or copying of this
message is strictly prohibited. If you receive this message in error, or are
not the named recipient(s), please notify the sender by reply e-mail, delete
this e-mail from your computer, and destroy any copies in any form immediately.
Receipt by anyone other than the named recipient(s) is not a waiver of any
attorney-client, work product, or other applicable privilege. This message and
all contents may be reviewed by authorized parties of the Catholic Health
System other than those named in the message header.
The contents of this message do not bind the Catholic Health System to any
contract, position, or course of action unless the sender is specifically
authorized to enter into contracts on behalf of the Catholic Health System. The
contents of this message do not necessarily constitute an official
representation of the Catholic Health System.
|