| Title: | Archive/Backup |
| Moderator: | COOKIE::MHUA IG |
| Created: | Wed Sep 08 1993 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 479 |
| Total number of notes: | 2283 |
There was a request in the past to write down the steps to configure
VMS clients (which is not trivial). I sent this doc to our tech. docs
person to get it published in the next round of documentation update.
This did not go into V2.1 ABS which is already in SSB. It will go into
the next version.
In the meanwhile, here is your reference.....
(Comments appreciated)
Masami
--------------------------------------------------------------
Here are the steps of configuring VMS server/clients on ABS.
1. On both server and client nodes, DECscheduler has to be installed
before ABS installation.
1. Install ABS on server (nodesv). When the installation asks the
following question, enter node name nodesv.
* cluster or node list for ABS policy engine [nodesv::] : nodesv
This will cause ABS server to be installed on nodesv. Nodesv is
sometimes referred as CSD (central security domain) node in our
documentation.
2. Install ABS on client (nodecl). When the above question is
asked, enter the name of the server that this client node is served by.
* cluster or node list for ABS policy engine [nodecl::] : nodesv
This will cause only VMS client portion of the ABS to be installed on
nodecl.
3. After the installation of the client node, setup a proxy account for
server node ABS account to access. (See installation guide chapter 3)
On node nodecl, enter a set of DCL commands :
$ set default sys$system
$ run authorize
UAF> add/proxy nodesv::abs abs/default
UAF> exit
ABS uses DECschdeuler remote job mechanism to submit DECscheduler job
from the server node to the client node
From this point, the steps are different depending on which types of
backups are performed, system backups or user backups.
Another thing to note is that storage class and execution environment objects
can only be create on server (CSD) nodes.
***** If you want to create system backups, here are the steps :
1. On nodesv, Create a storage class (for example, nodecl_sys_storage)
(or modify an exisitng storage_class).
The archive file system information in the storage class should point to
the resources (tape drives, or disks) available for on the nodecl where
the requests are executed. It is possible for nodecl to utilize RDF
devices to store the backup data on a remote node (for example, on
nodesv).
The execution node of the storage class should be nodesv, which is the
default.
You need ABS_CREATE_STROAGE_CLASS access right granted to your account
to do this step.
2. On nodesv, Create an execution environment (for example, nodecl_sys_env)
(or modify an exising execution environment).
The user profile information (See chapter 8 of Guide to Operations)
should be specified as :
user name : ABS
node name : *
cluster name : *
With this unser profile, save and restore requests
will be executed in the context of ABS (system backups).
You need ABS_CREATE_EXECUTION_ENV access right granted to your account
to do this step.
3a. If you want to create/submit save/restore requests from the server
(CSD) node, do the following:
On nodesv, Create a save request which uses nodecl_sys_storage storage
class and nodecl_sys_env execution environment. DECscheduler will
submit a save request job on nodecl. The source_node of the save/restore
request should be specified as nodecl (where the data resides).
To be able to create a request executing on a client node, your account
on nodesv must have ABS_CREATE_REMOTE_JOBS access rights granted.
3b. If you want to create/submit save/restore requests from the client
node, do the following:
On nodecl, Create a save request which uses nodecl_sys_storage storage
class and nodecl_sys_env execution environment. DECscheduler will
submit a save request job on nodecl. The source_node of the save/restore
request should be specified as nodecl (where the data resides).
***** If you want to create user backups, here are the steps :
In this example, assume that nodecl::smith is the account where the
user backup will be getting the context from.
1. On nodesv, Create a storage class (for example, nodecl_user_storage)
which allows access of nodecl::smith account.
The access control entry should look like:
Access Right - NODECL::SMITH
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL,EXECUTE
The archive file system information in the storage class should point to
the resources (tape drives, or disks) available for on the nodecl where
the requests are executed. It is possible for nodecl to utilize RDF
devices to store the backup data on a remote node (for example, on
nodesv).
The execution node of the storage class should be nodesv, which is the
default.
You need ABS_CREATE_STROAGE_CLASS access right granted to your account
to do this step.
2. On nodesv, Create an execution environment (for example,
nodecl_user_env)
which allows access of nodecl::SMITH
account. The access control entry should look like:
Access Right NODECL::SMITH
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL,EXECUTE
The user profile information should speicfy :
user name : smith
node name : nodecl
cluster name : *
(If nodecl is a part of a cluster, you can specify the cluster alias
instaed of *)
You need ABS_CREATE_EXECUTION_ENV access right granted to your account
to do this step.
3a. If you want to create/submit save/restore requests from the server
(CSD) node, do the following:
On nodesv, Create a save request which uses nodecl_user_storage storage
class and nodecl_user_env execution environment. DECscheduler will
submit a save request job on nodecl. The source_node of the save/restore
request should be specified as nodecl (where the data resides).
To be able to create a request executing on a client node, your account
on nodesv must have ABS_CREATE_REMOTE_JOBS access rights granted.
3b. If you want to create/submit save/restore requests from the client
node, do the following:
On nodecl, Create a save request which uses nodecl_user_storage storage
class and nodecl_user_env execution environment. DECscheduler will
submit a save request job on nodecl. The source_node of the save/restore
request should be specified as nodecl (where the data resides).
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 367.1 | CX3PST::BSS::SAUL | Wed Jan 29 1997 11:16 | 4 | ||
This is good stuff. Mind if we format it up and get into STARS for customers? Ted | |||||
| 367.2 | COOKIE::MHUA | Wed Jan 29 1997 13:26 | 9 | ||
Okay,
You may want to wait until Deb is done editing the text though, before
publishing it in the article. I'll let you know when Deb think it's
ready for publication.
Thanks,
Masami
| |||||
| 367.3 | edited version of the text | COOKIE::MHUA | Wed Feb 05 1997 08:45 | 556 | |
1 Configuring the ABS OpenVMS Client/Server Software
When installing the ABS software, notice that ABS does not
provide two separate software kits. Instead, installation
of the ABS OpenVMS server or client software is determined
by the OpenVMS Cluster alias name or node name that you
enter during the installation procedure.
To use the ABS software for system and user backup
operations, you must:
o Install and configure both the ABS OpenVMS server and
client software (see Table 1).
o Create (or modify) storage classes and execution
environments that meet those needs (see Sections 1.1
and 1.3).
o Create system and user backup operations using the
correct storage classes and execution environments (see
Sections 1.2 and 1.4).
Requirement:
Before installing the ABS software, first install
POLYCENTER Scheduler on both the ABS OpenVMS server and
client systems.
1
Table 1 Installing and Configuring the ABS Client/Server
________Software___________________________________________
Step_Action________________________________________________
1. Install ABS on the OpenVMS node that will be the ABS
OpenVMS server.
When the installation procedure prompts for the node
name of the ABS policy engine, enter the OpenVMS
Cluster alias name or the node name that you want
to become the ABS server:
* cluster or node list for the ABS policy engine [SVNODE::] : SVNODE
Result:
ABS installs the server software on the node named
SVNODE. The ABS OpenVMS server node is commonly
referred to as the central security domain (CSD) node.
2. Install the ABS software on the OpenVMS client node.
When the installation procedure prompts for the
node name where the ABS policy engine resides (the
ABS OpenVMS server node), enter the OpenVMS Cluster
alias or OpenVMS node name that you entered when you
installed the ABS OpenVMS server software:
* cluster or node list for ABS policy engine [CLNODE::] : SVNODE
Result:
ABS installs only the client portion of the ABS
software on the node named CLNODE.
(continued on next page)
2
Table 1 (Cont.) Installing and Configuring the ABS Client
________________/Server_Software___________________________
Step_Action________________________________________________
3. After installing the ABS software on the OpenVMS
server and client node, create a proxy account for
the ABS OpenVMS server node on the ABS OpenVMS client
node.
On the ABS OpenVMS client node (CLNODE::), enter the
following set of DCL commands:
$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
UAF> ADD/PROXY SVNODE::ABS ABS/DEFAULT
UAF> EXIT
Because ABS uses POLYCENTER Scheduler as its mechanism
to submit save and restore requests, POLYCENTER
Scheduler requires a proxy account to submit to the
remote node.
More_information:
Chapter 3 of the Archive/Backup System for OpenVMS
Installation Guide also describes how to create a
_____proxy_account.________________________________________
1.1 Creating System Backup Policy Objects
To create system save and restore requests from the ABS
OpenVMS server for the ABS OpenVMS client system, or to
create system save and restore requests on the ABS OpenVMS
client system, you must first create (or modify) storage
classes and execution environments that meet those needs.
In Table 2, the examples show you how to create ABS storage
classes and execution environments that enable system
backup operations.
3
Table 2 Creating Storage Classes and Execution Environments
________for_System_Backup_Operations_______________________
Step_Action________________________________________________
1. Create (or modify) a storage class that allows access
to the ABS OpenVMS client node. For example, create a
storage class named CL_SYSTEM_BACKUPS:
ABS> CREATE STORAGE_CLASS CL_SYSTEM_BACKUPS -
_ABS>/ACCESS=(USER_ID=*::ABS, -
_ABS> ACCESS="READ+WRITE+SET+SHOW+CONTROL+DELETE+EXECUTE")
Restrictions:
o You can only create (or modify) a storage class on
the ABS server node (central security domain).
o The execution node of the storage class must be the
ABS OpenVMS server node (SVNODE::). By default, ABS
obtains the node on which you create the storage
class. Because you can only create a storage class
on the ABS server node, the current node (server
node) becomes the execution node.
o The creating account must have the ABS_CREATE_
STORAGE_CLASS access rights identifier granted. See
Chapter 3 in the Archive/Backup System for OpenVMS
Installation Guide for instructions about granting
access rights identifiers.
The storage class must point to the archive file
system resources (MDMS or FILES-11 resources) that
are available to the ABS OpenVMS client node. It is
possible for the ABS OpenVMS client node to utilize
MDMS to store backup data on a remote device (such
as on the ABS server node). See the Media and Device
Management Services for OpenVMS Guide to Operations
for information about configuring remote tape devices.
(continued on next page)
4
Table 2 (Cont.) Creating Storage Classes and Execution
________________Environments_for_System_Backup_Operations__
Step_Action________________________________________________
2. Create (or modify) a corresponding execution
environment that also allows access to the ABS OpenVMS
client node:
ABS> CREATE ENVIRONMENT CL_SYSTEM_BACKUPS_ENV -
_ABS>/ACCESS=(USER_ID=*::ABS, -
_ABS> ACCESS="READ+WRITE+SET+SHOW+CONTROL+DELETE+EXECUTE") -
_ABS>/USER_NAME=ABS/NODE=*/CLUSTER=*
Restrictions:
o You can only create (or modify) an execution
environment on the ABS server node (central
security domain).
o The creating account must have the ABS_CREATE_
EXECUTION_ENV access rights identifier granted. See
Chapter 3 in the Archive/Backup System for OpenVMS
Installation Guide for instructions about granting
access rights identifiers.
Because the execution environment CL_SYSTEM_BACKUPS_
ENV specifies a user profile with the user name ABS,
only system backup operations in the context of ABS
are allowed. For detailed user profile information,
see Chapter 8 of Archive/Backup System for OpenVMS
_____Guide_to_Operations.__________________________________
1.2 Creating System Backup Operations
You can create system requests from either the ABS OpenVMS
server node or from the ABS OpenVMS client node. Table 3
describes how to do both.
5
Table_3_Creating_System_Backup_Save_Requests_______________
Step_Action________________________________________________
1. From_the_ABS_Server_Node:
To create a save or restore request from the ABS
server node (SVNODE::), from the server node create
a request that uses the storage class named CL_
SYSTEM_BACKUPS and the execution environment named
CL_SYSTEM_BACKUPS_ENV. Specify the source node as the
ABS OpenVMS client node (where the data resides):
ABS> SAVE/STORAGE=CL_SYSTEM_BACKUPS/FULL DISK$USER1:/SOURCE_NODE=CLNODE::
Result:
ABS submits the job on the ABS OpenVMS client node
(CLNODE::).
Requirement:
To create a save or restore request that executes
on the OpenVMS client node, the creating account on
the ABS server node must have ABS_CREATE_REMOTE_JOBS
access rights granted.
2. From_the_OpenVMS_Client_Node:
To create or submit a save or restore request from the
ABS OpenVMS client node, on the client node create a
request that uses the storage class named CL_SYSTEM_
BACKUPS and the execution environment named CL_SYSTEM_
BACKUPS_ENV. Specify the source node of the save or
restore request should as the OpenVMS client node
(where the data resides):
ABS> SAVE/STORAGE=CL_SYSTEM_BACKUPS/FULL DISK$USER1:/SOURCE_NODE=CLNODE::
Result:
POLYCENTER Scheduler submits the job on the ABS
_____OpenVMS_client_node.__________________________________
1.3 Creating User Backup Policy Objects
To create user save and restore requests from the ABS
OpenVMS server for the ABS OpenVMS client system, or to
create user save and restore requests on the ABS OpenVMS
client system, you must first create (or modify) storage
classes and execution environments that meet those needs.
6
In Table 4, the examples show you how to create ABS storage
classes and execution environments that enable user backup
operations.
Table_4_Creating_User_Backup_Policy_Objects________________
Step_Action________________________________________________
1. Create (or modify) a storage class for user backup
operations. For example, you could name the storage
class CL_USER_BACKUPS. This storage class allows
access to user SMITH from the node named CLNODE. In
this example, user SMITH would be allowed to create
save and restore requests using the following storage
class:
ABS> CREATE STORAGE_CLASS CL_USER_BACKUPS -
_ABS>/ACCESS=(USER_ID=CLNODE::SMITH, -
_ABS> ACCESS="READ+WRITE+SET+SHOW+DELETE+CONTROL+EXECUTE")
Restrictions:
o You can only create (or modify) a storage class on
the ABS server node (central security domain).
o The execution node of the storage class must be the
ABS OpenVMS server node (SVNODE::). By default, ABS
obtains the node on which you create the storage
class. Because you can only create a storage class
on the ABS server node, the current node (server
node) becomes the execution node.
o The creating account must have the ABS_CREATE_
STORAGE_CLASS access rights identifier granted. See
Chapter 3 in the Archive/Backup System for OpenVMS
Installation Guide for instructions about granting
access rights identifiers.
(continued on next page)
7
Table_4_(Cont.)_Creating_User_Backup_Policy_Objects________
Step_Action________________________________________________
Performing a show operation of CL_USER_BACKUPS shows
the following access attributes:
Access Right -- CLNODE::SMITH
Access Granted --
READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
The storage class must point to the archive file
system resources (MDMS or FILES-11 resources) that
are available to the ABS OpenVMS client node. It is
possible for the ABS OpenVMS client node to utilize
MDMS to store backup data on a remote device (such
as on the ABS server node). See the Media and Device
Management Services for OpenVMS Guide to Operations
for information about configuring remote tape devices.
(continued on next page)
8
Table_4_(Cont.)_Creating_User_Backup_Policy_Objects________
Step_Action________________________________________________
2. Create a corresponding execution environment that also
allows access to the user SMITH:
ABS> CREATE ENVIRONMENT CL_USER_BACKUPS_ENV
_ABS>/ACCESS=(USER_ID=CLNODE::SMITH, -
_ABS> ACCESS="READ+WRITE+SET+SHOW+CONTROL+DELETE+EXECUTE") -
_ABS>/USER_NAME=SMITH/NODE=CLNODE::/CLUSTER=*
Note:
If the node CLNODE:: is a part of an OpenVMS Cluster,
you can specify the OpenVMS Cluster alias name instead
of an asterisk (*).
Restrictions:
o You can only create (or modify) an execution
environment on the ABS server node (central
security domain).
o The creating account must have the ABS_CREATE_
EXECUTION_ENV access rights identifier granted. See
Chapter 3 in the Archive/Backup System for OpenVMS
Installation Guide for instructions about granting
access rights identifiers.
Because the execution environment CL_USER_BACKUPS_
ENV specifies a user profile with the user name SMITH
and the node name CLNODE::, ABS performs user backup
operations in the context of the user SMITH on node
CLNODE::. For detailed user profile information, see
Chapter 8 of Archive/Backup System for OpenVMS Guide
_____to_Operations.________________________________________
1.4 Creating User Backup Operations
You can create user requests from either the ABS OpenVMS
server node or from the ABS OpenVMS client node. Table 5
describes how to do both.
9
Table_5_Creating_User_Save_and_Restore_Requests____________
Step_Action________________________________________________
1. From_the_ABS_Server_Node:
On node OpenVMS server node (SVNODE::), create a save
request that uses the storage class named CL_USER_
BACKUPS and the execution environment named CL_USER_
BACKUPS_ENV. Specify the source node for the save
request as the ABS OpenVMS client node (CLNODE::) (the
node where the data resides).
ABS> SAVE/STORAGE=CL_USER_BACKUPS DISK$USER1:[SMITH]*.*/SOURCE_NODE=CLNODE::
Restriction:
To create a save or restore request that executes on
a client node, the creating account on the OpenVMS
server node must have ABS_CREATE_REMOTE_JOBS access
rights granted.
Result:
POLYCENTER Scheduler submits the job on the OpenVMS
client node.
2. From_the_ABS_Client_Node:
Create a save request on the OpenVMS client node
(CLNODE::) that uses the storage class named CL_USER_
BACKUPS and the execution environment named CL_USER_
BACKUPS_ENV. Specify the source node for the save or
restore request as the OpenVMS client node (node where
the data resides).
ABS> SAVE/STORAGE=CL_USER_BACKUPS DISK$USER1:[SMITH]*.*/SOURCE_NODE=CLNODE::
Result:
POLYCENTER Scheduler submits the job on the OpenVMS
_____client_node.__________________________________________
10
| |||||
| 367.4 | COOKIE::MHUA | Wed Feb 05 1997 08:47 | 8 | ||
Ted,
I posted the .txt version of the edited text. It should be go enough
to be submitted as an article. Deb Copeland was the technical editor.
Take it away!
Masami
| |||||
| 367.5 | I Got it... | CX3PST::BSS::SAUL | Wed Feb 05 1997 13:56 | 0 | |