ADSM-L

[no subject]

2015-10-04 17:41:28


---------------------- Weitergeleitet von Reinhold Wagner/A/DE/ZEUNA on 23.07.99
09:29 ---------------------------
09:29 ---------------------------


"Eric LEWIS" <eric.lewis AT ccmail.adp.wisc DOT edu> on 22.07.99 21:28:29

An:   Reinhold Wagner/A/DE/ZEUNA@ZS
Kopie:
Thema:    Re: Can users perform their own restores on UNIX?



     Hi: I sent this out this AM but I don't think the listserver accepts
     stuff from me anymore.  did you see it earlier?  If not would you post
     it for me? tks. erl


______________________________ Forward Header __________________________________
Subject: Re: Can users perform their own restores on UNIX?
Author:  Eric LEWIS at DoIT-MAIL1
Date:    7/22/99 10:15 AM


     Hi:  I have the same requirement and did get some assistance from IBM
     with this.  We concluded that the way to do this was to establish
     multiple nodes on the machine.  Use includes/excludes to limit each
     node to an individual user's files/directories.  Also, because Archive
     ignores includes/excludes, the nodes would not have any archive
     storage pool - no archive capability.  The nodes would be able to
     "see" the other user's file entries in directory tree displays for
     backup but would not be able backup the files - thus preventing
     restores to a directory with permissions for the node/user.  The dsm
     and inclexcl files would be isolated from user update.

     Following is a set of dsm.opt, dsm.sys, and inclexcl files that would
     permit a single installation of the backup clients to be used to
     launch multiple nodes:

     ? DSM.OPT (Client user options file for the dsmc client)
     **  SErvername      The server name is specified by the dsmc scheduler
     initialization
     command.
     DATEformat 3
     LANGuage AMENG
     DOMain ALL-LOCAL
     BOOKS "browser_path http://axle.doit.wisc.edu/docs/adsm/adsm.htm";
     * replace browser_path with the path to your web browser application
     * END DSM.OPT

     ? Node1-DSM.OPT (Client user options file for the dsmcad client)
     SErvername node1-stanza
     DATEformat 3
     LANGuage AMENG
     DOMain ALL-LOCAL
     BOOKS "browser_path http://axle.doit.wisc.edu/docs/adsm/adsm.htm";
     * replace browser_path with the path to your web browser application
     * END DSM.OPT

     ? Node2-DSM.OPT (Client user options file for the dsmcad client)
     SErvername node2-stanza
     DATEformat 3
     LANGuage AMENG
     DOMain ALL-LOCAL
     BOOKS "browser_path http://axle.doit.wisc.edu/docs/adsm/adsm.htm";
     * replace browser_path with the path to your web browser application
     * END DSM.OPT

     ? * DSM.SYS (Client system option file)
     SErvername node1-stanza
     NODename node1
     HTTPport 1582
     COMMmethod TCP
     TCPPort 1500
     TCPServeraddress buckybackup2.doit.wisc.edu
     TCPBuffsize 32
     TCPWindowsize 24
     USERs root
     COMPRESSIon Yes
     CHAngingretries 1
     PASSWORDAccess generate
     MAILprog /usr/sbin/sendmail root
     SCHEDMODe PRompted
     SCHEDLOGRetention 10,D
     ERRORLOGRetention 10,D
     SCHEDLOGName /usr/lpp/adsm/bin/node1-dsmsched.log
     ERRORLOGname /usr/lpp/adsm/bin/node1-dsmerror.log
     * /usr/lpp/adsm/bin is the AIX path, other UNIX clients may use
     different paths
     TXNBytelimit 4000
     INCLExcl /usr/lpp/adsm/bin/node1-inclexcl
     *  End of node1-stanza

     SErvername node2-stanza
     NODename node2
     HTTPport 1583
     COMMmethod TCP
     TCPPort 1500
     TCPServeraddress buckybackup2.doit.wisc.edu
     TCPBuffsize 32
     TCPWindowsize 24
     USERs root
     COMPRESSIon Yes
     CHAngingretries 1
     PASSWORDAccess generate
     MAILprog /usr/sbin/sendmail root
     SCHEDMODe PRompted
     SCHEDLOGRetention 10,D
     ERRORLOGRetention 10,D
     SCHEDLOGName /usr/lpp/adsm/bin/node2-dsmsched.log
     ERRORLOGname /usr/lpp/adsm/bin/node2-dsmerror.log
     * /usr/lpp/adsm/bin is the AIX path, other UNIX clients may use
     different paths
     TXNBytelimit 4000
     INCLExcl /usr/lpp/adsm/bin/node1-inclexcl
     *  End of node2-stanza
     * END DSM.SYS

     ? * INCLEXCL (Include-exclude options file named node1-inclexcl)
     EXCLUDE /./*                       Excludes all other files not
     explicitly included below
     INCLUDE {specify all the directories that are to be backed up for
     Node1 here}
     INCLUDE /usr/lpp/adsm/bin/node1-dsm*.log DYNAMIC
     * END INCLEXCL for node1

     ? * INCLEXCL (Include-exclude options file named node2-inclexcl)
     EXCLUDE /./*                       Excludes all other files not
     explicitly included below
     INCLUDE {specify all the directories that are to be backed up for
     Node2 here}
     INCLUDE /usr/lpp/adsm/bin/node1-dsm*.log DYNAMIC
     * END INCLEXCL for node2

     The scheduler clients would be started using the following command
     lines:
     dsmc sched -Servername=node1-stanza > /dev/null 2>&1 # ADSM Scheduler
     Node1
     dsmc sched -Servername=node2-stanza > /dev/null 2>&1 # ADSM Scheduler
     Node2

     The web backup clients would be started using the following command
     lines:
     Dsmcad -optfile=Node1-DSM.OPT
     Dsmcad -optfile=Node2-DSM.OPT


     Eric Lewis UW-Madison



______________________________ Reply Separator _________________________________
Subject: Can users perform their own restores on UNIX?
Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>  at IPNET
Date:    7/22/99 4:09 PM


Folks,

our scenario is:

ADSM server 3.1 on AIX
Solaris 7 fileserver (NFS, ADSM client)
AIX CAD workstations (load/store CAD files from/to Solaris fileserver)

What would be the best method to allow the CAD users to perform
their own restores?

It must be guaranteed that the user can only restore his own files. How
is this be done in practice?

TIA

Reinhold Wagner, Zeuna Staerker GmbH & Co. KG





<Prev in Thread] Current Thread [Next in Thread>
  • [no subject], Unknown <=