Nas 8000 Security Level Guidelines; Installation Of Oracle Software; Installation Of Oracle On Nas 8000 - HP StorageWorks 8000 - NAS User Manual

below for more details. For the NAS 8000 system that has a VA 7400, multiple volume groups on
separate redundancy groups can be used to increase the fault tolerance level. The operating system of the
NAS 8000 will always use the most efficient data pathway to access the VA 7xxx array. If the backup or
usage plan calls for the use of NAS 8000 snapshots, space must be reserved in the volume group for the
snapshots.
After creating volume groups, the next step is to create file volumes. A file volume is somewhat equivalent
to a file system. There are many possibilities at this level, and each choice should be weighed carefully
before committing to an overall storage design. One or more file volumes are entirely contained in a single
volume group. A file volume cannot be a member of more than one volume group. Placing an entire
database into one single file volume may facilitate easier backup through the snapshot features of the NAS
8000. Snapshots can be utilized for backing up the database even if the database data files exist in
multiple file volumes and multiple volume groups.
Finally, once the file volumes have been created, the DBA/NAS 8000 administrator can create the desired
directory structure and CIFS/SMB shares. A directory structure can be created from the Command View
NAS GUI and then individual directories can be shared. Another method is to share the root directory of
the storage file volume(s) for read/write access by the DBA. The DBA can then create directories under the
file volume as desired and set the permissions. The CIFS/SMB shares must be defined through the
Command View NAS GUI. Once the shares have been defined, the Oracle server(s) may connect to the
shares, and the database may be moved, started or created. Please read carefully the section in the
"problems, challenges and constraint" section below about defining new CIFS/SMB shares while Oracle is
active.

NAS 8000 security level guidelines

The NAS 8000 has two different security setting options for Windows (CIFS/SMB) shares. The security
level of the NAS 8000 only applies to CIFS/SMB shares, not to nfs exports. When the NAS 8000 is in
Share level security, all security is handled by the NAS 8000 through the use of passwords on each share.
A share can have a "read" password, a "read/write" password, or no passwords assigned on it. In order
to gain access to a share with a password on it, NAS 8000 clients (e.g. the database servers) must provide
the appropriate password. Every share can have a different set of passwords associated with it. When
the NAS 8000 is in User/Domain level security, the NAS 8000 joins the domain and the Public Domain
Controller for the domain handles all security. In order to gain access to the shares, every NAS 8000 client
must be a valid member of the domain or of a trusted domain, or must be able to access the storage as
though it were a valid member of the domain. All CIFS/SMB shares defined on the NAS 8000 will be in
either Share level security or Domain level security. The CIFS/SMB security level should be set before any
CIFS/SMB shares are defined. Although it is possible to change security levels once CIFS/SMB shares
have been defined, if there are data files in those shares, the changing of security attributes may have
undesirable results. Because of this, it is crucial that the NAS 8000 administrator and the DBA plan out the
security model that best fits the planned use. The NAS 8000 can serve Oracle database data files in either
Windows security setting; however, the setting does affect the database creation process, as well as the
database services that run on the Oracle server. The sections under 'Creating a Database' will describe
these issues in detail.

installation of Oracle software

installation of Oracle on NAS 8000

The Oracle ORDBMS (Object Relational DataBase Management System) may be installed to the NAS
8000. That is to say, the NAS 8000 may be used to store the Oracle binaries and support files that are
accessed and executed by the Oracle server. The NAS 8000 does not execute any of the Oracle binaries.
The ability to place one set of Oracle executables on the NAS 8000 and then allow access by several
Oracle servers, does not alleviate the customer from securing the appropriate licenses from Oracle.
Additionally, since the NAS 8000 supports a heterogeneous environment, it is possible that several different
Oracle versions/installations could be placed on the NAS 8000. In this scenario, care must be taken to
assure that each Oracle server accesses the appropriate Oracle executables.
6