Procedimiento de actualizacion version 7.5.1 a 7.6 Service Pack 3

Page last edited hace 2365 días 4 horas
De Solaris-ES
Jump to navigation Jump to search

BackUp previo a la Actualización[editar]

Romper el mirror[editar]

root@new_backup (nuevo)# metastat -c
d3               m   60GB d13 d23
   d13          s   60GB /dev/dsk/c9t5000C5002C8A1167d0s3
   d23          s   60GB /dev/dsk/c9t5000C5002C8A0AFFd0s3
d1               m   32GB d11 d21
   d11          s   32GB /dev/dsk/c9t5000C5002C8A1167d0s1
   d21          s   32GB /dev/dsk/c9t5000C5002C8A0AFFd0s1
d0               m   44GB d10 d20
   d10          s   44GB /dev/dsk/c9t5000C5002C8A1167d0s0
   d20          s   44GB /dev/dsk/c9t5000C5002C8A0AFFd0s0
root@new_backup (nuevo)# metadb -i
   flags           first blk       block count
a m  p  luo        16              8192            /dev/dsk/c9t5000C5002C8A1167d0s7
a    p  luo        8208            8192            /dev/dsk/c9t5000C5002C8A1167d0s7
a    p  luo        16400           8192            /dev/dsk/c9t5000C5002C8A1167d0s7
a    p  luo        16              8192            /dev/dsk/c9t5000C5002C8A0AFFd0s7
a    p  luo        8208            8192            /dev/dsk/c9t5000C5002C8A0AFFd0s7
a    p  luo        16400           8192            /dev/dsk/c9t5000C5002C8A0AFFd0s7
root@new_backup (nuevo)# metadetach d3 d23 --> /var
root@new_backup (nuevo)# metadetach d1 d21 --> swapfs
root@new_backup (nuevo)# metadetach d0 d20 --> rootfs

Backup en frió de FS Networker[editar]

# BKPFILE="/tmp/`date '+%Y%m%d'`.networker.tgz"
# export BKPFILE
# (cd /;tar cvf - ./etc/rpc ./etc/syslog.conf ./nsr/res/servers ./var/nsr) | gzip -c >$BKPFILE
# mv /tmp/`date '+%Y%m%d'`.networker.tgz [DESTINO]

Backup en frio de DB RMAN[editar]

Realizar un backup en frio de RMAN

Backup en frio de cliente JAVA[editar]


TCP/IP requirements[editar]

All Linux, and UNIX, operating systems require a ::1 entry in the /etc/hosts file for the local host in order to run the 
NetWorker software. The entry must be in the form ::1 localhost aliases.	

The TCP/IP hostname must be identical to the computer name. Do not include an underscore character (_) in the computer name.

The NetWorker server’s TCP/IP hostname and computer name must be the same.

Increase TCP backlog buffer size[editar]

tcp_conn_req_max_q 4096
tcp_conn_req_max_q0 4096


root@new_backup (nuevo)# ndd /dev/tcp tcp_conn_req_max_q

root@new_backup (nuevo)# ndd /dev/tcp tcp_conn_req_max_q0
Note: The TCP backlog parameter defines how many half-open connections can be kept in the backlog queue. If the incoming
      connections exceed this value, packet loss might occur on the NetWorker server. Packet loss can result in the failure, or
      unresponsiveness of the NetWorker server.
Best Practice
Para automatizar la configuracion de estos parametros despues de un reboot, tenemos que crear el archivo llamado
/etc/init.d/network-tuning y crear un link a otro llamado /etc/rc2.d/S99network-tuning
# vi /etc/init.d/network-tuning
ndd -set /dev/tcp tcp_conn_req_max_q0 4096
ndd -set /dev/tcp tcp_conn_req_max_q 4096

# chown root:sys /etc/init.d/network-tuning
# chmod 755 /etc/init.d/network-tuning
# ln -s /etc/init.d/network-tuning /etc/rc2.d/S99network-tuning
The default maximum number of pending TCP connections for a TCP listener waiting to be accepted by accept(3SOCKET)
Default is 128

The default maximum number of incomplete (three-way handshake not yet finished) pending TCP connections for a TCP listener.

Verificación del estado de estas conecciones.
# netstat -sP tcp | grep tcpListenDrop
  tcpListenDrop       =2442553     tcpListenDropQ0     =     0

Nota: To alleviate numerous TCP listen drops, bump up the value for the tunable tcp_conn_req_max_q

Java Runtime Environment[editar]

JRE starting from version 1.5_11 or later. This is required to run the command line reporting feature.


root@new_backup (nuevo)# java -version
java version "1.5.0_26"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_26-b03)
Java HotSpot(TM) Server VM (build 1.5.0_26-b03, mixed mode)
Descargar la ultima version de Java
Download Java
root@new_backup (nuevo)# ls -la /usr
drwxr-xr-x  45 root     sys         1024 Jul  8  2011 .
drwxr-xr-x  41 root     root        1536 Jun 17 12:56 ..
drwxr-xr-x   9 root     bin          512 Feb 15  2011 j2se
drwxr-xr-x   4 root     bin          512 Jul  8  2011 jdk
lrwxrwxrwx   1 root     other         15 Feb 16  2011 java -> jdk/jdk1.5.0_26
# cp jdk-6u32-solaris-sparc.tar.Z /tmp/jdk6u32
# cd sh /tmp/jdk6u32
# uncompress jdk-6u32-solaris-sparc.tar.Z
# tar xvf jdk-6u32-solaris-sparc.tar
# mv [DIR JDK6U32] /usr/jdk1.6.0_32
# mv /usr/java /usr/java_jdk1.5.0_26
# ln -s /usr/jdk1.6.0_32 /usr/java
# java -version

Update from a Previous Release[editar]


The NetWorker software does not support direct upgrade, which means the previous installed version must be removed before the 
new version can be installed. When upgrading the NMC version, make a copy of the current database. This database will be 
required if you downgrade the software.   

Update enablers[editar]

When updating from a 7.5.x release to 7.6 and later, an update enabler is not required and is not generated. If you are 
upgrading to release 7.6 and later from a release prior to 7.5, an update enabler is required. If an update enabler is 
required, the NetWorker software automatically generates and adds the required update enabler code to its configuration. 
The update enabler expires after 45 days. Contact Powerlink Licensing within 45 days to permanently authorize the update 
enabler. More information is available in the NetWorker licensing guide

Update the NetWorker software on UNIX[editar]

Maintain a NetWorker software installation
After NetWorker software is installed, you can run the Setup program to perform the
following maintenance tasks:
- Change the setup language type for the NetWorker installation.
- Change the installation type (for example, from client to server), edit the servers list, add the NetWorker License Manager, 
  add or remove the NetWorker Console software.
- Replace missing or corrupted program files.
- Remove the NetWorker software from the computer
To update the operating system on a NetWorker server, storage node, or client host, first upgrade the operating system, 
then update the NetWorker software.
When updating from a previous release, the NetWorker software is automatically installed in the same location.
The following options are not supported during a NetWorker software update:
- Change the installation type (for example, from client to server)
- Edit the list of NetWorker servers that are allowed to access the computer
- Install NetWorker License Manager
However, details of changes that can be made after the update is available in “Maintain a NetWorker software installation”

Task 1: Prepare to update the NetWorker software to release 7.6 and later[editar]

To update the NetWorker software to release 7.6 and later:

1. Before updating, make notes of the current database location and port numbers used before removing the current installation.

2. Verify that the target computer satisfies the requirements. “UNIX requirements”  on page 16 provides details.

3. Make a copy of the current database and store it in a safe location.

4. Back up all client file indexes and generate a bootstrap for the server. If a current bootstrap does not exist, or a backup 
   of all client file indexes, perform scheduled backups on all clients before updating the software. For example, to save the
   bootstrap information, type this command:
# savegrp -O group

Note: Ensure that all clients are included in the groups to be backed up.

5. Record the latest bootstrap save set ID and its associated volume label. To obtain this information, type this command:
# mminfo -B

6. If the NetWorker software is not currently installed in the default location, record the location of the client file indexes.

Note: A NetWorker storage node release 7.4 or later is not compatible with a NetWorker release
7.3 or earlier server. Update the NetWorker servers to at least version 7.4 before updating a
storage node.

Task 2: Update the software on the NetWorker client, storage node, and server[editar]

To update the software on the NetWorker client, storage node, and server:

1. Keep a copy of the current configuration.

2. Ensure that all NetWorker scheduled backups have been stopped before starting the upgrades.

3. Type the following command to shut down the NetWorker software:
# nsr_shutdown

4. Uninstall the current NetWorker and NetWorker Management Console (NMC) software packages.
   root@new_backup (nuevo)# pkginfo |egrep -i "lgto|ebs"
   application LGTOnmo                          EMC NetWorker Module for Oracle
   application SUNWebsc                         Sun StorageTek(TM) Enterprise Backup Client
   application SUNWebsg                         Sun StorageTek(TM) Enterprise Backup Management Console
   application SUNWebsm                         Sun StorageTek(TM) Enterprise Backup Man Pages
   application SUNWebsn                         Sun StorageTek(TM) Enterprise Backup Storage Node
   application SUNWebss                         Sun StorageTek(TM) Enterprise Backup Server 

5. Verify that no NMC processes (gstd, gsttclsh, dbsrv9) are still running.
   root@new_backup (nuevo)# ps -ef |egrep -i "gstd|gsttclsh|dbsrv9"|grep -v grep

Note: If performing a reinstall of NetWorker release 7.6 and later, the processes are gstd, dbsrv9, and httpd.

6. Install the new release of the NetWorker software.

Note: Do not start the NetWorker daemons. If client computers have a previous release of the NetWorker Client for Linux
      installed, update those clients to the latest NetWorker release to fully exercise all the features in the software. 
      When the installation identifies an existing NetWorker client package for Linux, it prompts for permission to update 
      the client. The update process removes the existing NetWorker client and man pages and installs the new version of the
      NetWorker client software.

7. Apply any required NetWorker software patches.

8. Restart the software by running the NetWorker startup script,
# /etc/init.d/networker start.

9. At the command prompt, type the following command:
# nsrck –L 2

10. License the NetWorker software. More information is available in the NetWorker licensing guide.

Install the NetWorker software[editar]

Task 1: Install the NetWorker software[editar]

By default, the NetWorker software is installed in the /usr directory.
The NetWorker software can be installed in a default or nondefault location.
To avoid shared memory corruption, or possible failures of the NetWorker services
on a NetWorker server, Sun patch142900-03 on Sparc or Sun Patch 142901-03 on x86
or later must be applied:
- Confirm the patch is applied:
# showrev -p | grep 142900
OK: Patch: 142909-17 Obsoletes: 142900-15
Note: This patch has dependencies on other system patches. Ensure that all requirements are met before applying the patch.

Install the NetWorker software to the default location[editar]


1. Keep a copy of the current configuration. The NetWorker software installation script modifies the /etc/rpc and 
   /etc/syslog.conf files during the installation process. 
# cp /etc/rpc /etc/rpc.old
# cp /etc/syslog.conf /etc/syslog.conf.old

2. Type this command:
# pkgadd -d /cdrom/cdrom1/solaris

3. Type the appropriate options to install the following packages. Software packages on the server must be installed in the
   following order:
   a. LGTOclnt (client software package)
   b. LGTOnode (storage node software package)
   c. LGTOserv (server software package)
   d. LGTOman (optional man pages)
   e. LGTOlicm (optional NetWorker License Manager software package)
  The NetWorker License Manager Installation and Administration Guide provides information about the NetWorker License 
  Manager software.
4. Type the number of the option to install a language support package. For example:
  - LGTOfr (French)
  - LGTOja (Japanese)
  - LGTOko (Korean)
  - LGTOzh (Simplified Chinese)

Console server[editar]

1. Ensure that JRE version 1.6.0 or later is installed. This enables the command line reporting feature. If the required JRE
   version is not installed, go to the Java website to download and install the required version.
   a. If the NetWorker software was downloaded from the web, type this command to verify that execute permissions are applied to
      the JRE file. 
   For example:
    # chmod +x /tmpdir/
   The creates an install directory in the working directory where it is run.
   b. Change to the directory where the JRE is to be installed.
   c. Run this script:
    # tmpdir/
   d. Accept the Java licensing agreement.
   Note: Java WebStart is a caching mechanism for web deployed applications such as NMC. If cache is disabled in the Java
   options, WebStart will fail. To verify that 
   Keep temporary files on my computer is enabled (default), in Control Panel > Java > General > Temporary Internet 
   Files > Settings > Keep temporary files on my computer. Click the checkbox to enable temporary internet file caching if it 
   is notchecked.
2. Start the NetWorker software installation:
# pkgadd -d /cdrom/cdrom1/solaris
Note: Do not press Enter for the default response All. Accepting the default installs the server.
3. Type the appropriate option number to install the client package (LGTOclnt), if not already installed.
   The client package temporarily requires 35 MB of free space on the client computer.
4. Type the appropriate option number to install the Console server package, LGTOnmc.
5. (Optional) Type the appropriate option number to install the man pages (LGTOman).
   - LGTOfr (French)
   - LGTOja (Japanese)
   - LGTOko (Korean)
   - LGTOzh (Simplified Chinese)
6. Specify the directory to install the LGTOnmc package (for example, /opt/LGTOnmc).
7. Specify a User/Group with limited privileges that NMC will use to run the web server. This must be a non-root user. 
   For example, Solaris operating systems 
   have a default user/group [nobody/nobody] that can be used.
   Note: If the default group [nobody/nobody] does not exist, and a user/group is not created with limited privileges, follow 
   the Console server requirements specified in the section “Console”.
8. For the web server port number, use the default port number (9000) or use a custom port number. Valid port numbers are between
   1024 and 49151.

9. For the Console server, use the default port number (9001) or use a custom port number. Valid port numbers are between 1024 and
   Note: Do not use port numbers that are already in use. Port 2638 is reserved by the Console server as it uses Tabular Data
         Stream (TDS) protocol to communicate with the database. Port 9002 is the preferred port for the EMC Backup Advisor
10. Specify the directory to use for the LGTOnmc database (for example, /export/home/lgto_gstdb).
    En NEW_BACKUP: /nsr/lgto_gstdb
11. Specify the location of the NetWorker binaries (for example, /usr/sbin).
12. Start the NetWorker Console daemons: /etc/init.d/gst start
    The NetWorker Console daemons include the following:
    - gstd
    - dbsrv9
    - httpd (2 or more processes)
    - gstsnmptrapd (optional daemon) for managing integrated Data Domain backups.
13. If the Console server and the NetWorker server are installed on separate hosts, you must add the Console administrator to the
    administrator lists of the monitored NetWorker server. This enables the Console administrator to administer and monitor the
    target NetWorker server. 
    On the NetWorker server:
    a. Specify the process owner of the Console daemon process depending on which host contains the Console server:
    – If on a Microsoft Windows host, type:
    # nsraddadmin -u "user=SYSTEM, host=console_host"
    – If on a AIX, HP-UX, Linux or Solaris only host, type:
    # nsraddadmin -u "user=root, host=console_host"
    b. Specify the Console administrator user:
    # nsraddadmin -u "user=administrator, host=console_host"
    where console_host is the Console server hostname.

Task 2: Change the NetWorker servers with access to a client[editar]

To limit the servers authorized to access a client, specify a list of trusted NetWorker servers for a client in the
/nsr/res/servers file. After installing the client, storage node, and server software, use the following procedure to 
change theNetWorker servers that are authorized to access a client.
1. Type this command to shut down the NetWorker daemons:
# nsr_shutdown
2. Edit or create the /nsr/res/servers file and add the set of NetWorker servers, one per line, that require access to the 
   client. When adding NetWorker servers, specify both the shortname and FQDN for each NetWorker server. The first entry in 
   this file becomes the default NetWorker server.
   Note: If the /nsr/res/servers file is empty or does not exist, any NetWorker server is authorized to:
   - Access and back up the client.
   - Perform a directed recovery to the client.
3. If necessary, remove the -s option from the nsrexecd command that is invoked by the boot-time startup file. Running nsrexecd
   with the -s option supersedes the /nsr/res/servers file:
   a. Check the NetWorker boot-time startup file to see whether nsrexecd is being run with the -s option. The boot-time startup
      file for the Solaris environment is /etc/init.d/networker.
   b. If the -s option exists in the boot-time startup file, remove all occurrences of this in the startup file: 
      -s server_name

Task 3: Start the NetWorker daemons[editar]

1. Start the NetWorker daemons by using this command:
# /etc/init.d/networker start
2. Verify that the NetWorker daemons are running:
# ps -ef | grep nsr
3. If the output does not list nsrd and nsrexecd as current processes, run the following command to start the NetWorker daemons 
   on the NetWorker server:
# /etc/init.d/networker start
The NetWorker daemon nsrmmd is only present if one or more devices are enabled.

Note: The UTF-8 converters available with the operating system might need to be installed.

NetWorker daemons[editar]

server                    : nsrd, nsrexecd, nsrindexd, nsrmmdbd, nsrmmd, nsrjobd, nsrmmgd, nsrlcpd
client                    : nsrexecd
storage node              : nsrexecd, nsrmmd, nsrlcpd
NetWorker License Manager : lgtolmd

Test de la instalación[editar]

1. Verify that the console processes gstd, dbsrv9 and httpd are running on the NetWorker Management Console server.   
2. Start a web browser session.
Nota: To start the Console server: /etc/init.d/gst start
For users upgrading from a previous release, in the NetWorker Management Console Login dialog box, type the username and password.
Note: If upgrading from a previous release and prompted for a user and password, the default user is administrator and the 
      default password for the administrator is “administrator”. For security purposes, this password should be changed during 
      the first login session.
3. Realizar un backup de un archivo
# save -s new_backup /etc/release
4. Realizar un backup de una DB con RMAN


Procedimiento para la configuración de la Librería[editar]

Paso 9[editar]

# inquire -lc

-l flag found: searching all LUNs, which may take over 10 minutes per adapter for some fibre channel adapters.  
 Please be patient.
scsidev@1.0.0:FUJITSU MAY2073RCSUN72G 0501|Disk, /dev/rdsk/c1t0d0s2
                                           S/N: 000646S07LEN
scsidev@1.1.0:FUJITSU MAY2073RCSUN72G 0501|Disk, /dev/rdsk/c1t1d0s2
                                           S/N: 000646S07L2H
scsidev@1.2.0:FUJITSU MAY2073RCSUN72G 0501|Disk, /dev/rdsk/c1t2d0s2
                                           S/N: 000652S07YK6
scsidev@1.3.0:FUJITSU MAY2073RCSUN72G 0501|Disk, /dev/rdsk/c1t3d0s2
                                           S/N: 000644S071VP
scsidev@2.1.0:HP      Ultrium 4-SCSI  H2BS|Tape, /dev/rmt/0cbn
                                           S/N: HU1802148N
                                           ATNN=HP      Ultrium 4-SCSI  HU1802148N
scsidev@3.0.0:HP      Ultrium 4-SCSI  H2BS|Tape, /dev/rmt/1cbn
                                           S/N: HU1802148L
                                           ATNN=HP      Ultrium 4-SCSI  HU1802148L
scsidev@6.0.0:HP      Ultrium 4-SCSI  H2BS|Tape, /dev/rmt/2cbn
                                           S/N: HU1802148W
                                           ATNN=HP      Ultrium 4-SCSI  HU1802148W
scsidev@6.3.0:HP      Ultrium 4-SCSI  H2BS|Tape, /dev/rmt/4cbn
                                           S/N: HU1802148U
                                           ATNN=HP      Ultrium 4-SCSI  HU1802148U
scsidev@7.0.0:HP      Ultrium 4-SCSI  H2BS|Tape, /dev/rmt/3cbn
                                           S/N: HU175112FJ
                                           ATNN=HP      Ultrium 4-SCSI  HU175112FJ
scsidev@7.3.0:HP      Ultrium 4-SCSI  H2BS|Tape, /dev/rmt/5cbn
                                           S/N: HU1802148K
                                           ATNN=HP      Ultrium 4-SCSI  HU1802148K

Paso 10[editar]

# jbconfig
Jbconfig is running on host new_backup (SunOS 5.10), and is using new_backup as the NetWorker server.

         1) Configure an AlphaStor Library.
         2) Configure an Autodetected SCSI Jukebox.
         3) Configure an Autodetected NDMP SCSI Jukebox.
         4) Configure an SJI Jukebox.
         5) Configure an STL Silo.

What kind of Jukebox are you configuring? [1] 2
Scanning SCSI buses; this may take a while ... 
Installing 'Standard SCSI Jukebox' jukebox - /dev/scsi/changer/c12t500104F000828EA4d0.

What name do you want to assign to this jukebox device? L500
Attempting to detect serial numbers on the jukebox and drives ...

Will try to use SCSI information returned by jukebox to configure drives.

Turn NetWorker auto-cleaning on (yes / no) [yes]? yes

The following drive(s) can be auto-configured in this jukebox:
 1> LTO Ultrium-3 @ 2.0.0 ==> /dev/rmt/0cbn
 2> LTO Ultrium-3 @ 3.0.0 ==> /dev/rmt/1cbn
 3> LTO Ultrium-3 @ 13.0.0 ==> /dev/rmt/3cbn
 4> LTO Ultrium-3 @ 12.0.0 ==> /dev/rmt/2cbn
These are all the drives that this jukebox has reported.

To change the drive model(s) or configure them as shared or NDMP drives, 
 you need to bypass auto-configure. Bypass auto-configure? (yes / no) [no] no

Jukebox has been added successfully

The following configuration options have been set:

> Jukebox description to the control port and model.
> Autochanger control port to the port at which we found it.
> Networker managed tape autocleaning on.
> Barcode reading to on.
> Volume labels that match the barcodes.
> Slot intended to hold cleaning cartridge to 253.  Please insure that a
        cleaning cartridge is in that slot
> Number of times we will use a new cleaning cartridge to 5.
> Cleaning interval for the tape drives to 6 months.

You can review and change the characteristics of the autochanger and its associated devices using the NetWorker Management Console.

Would you like to configure another jukebox? (yes/no) [no] no
root@new_backup [] # nsrjb -HE -vvv
setting verbosity level to `3'
nsrjb: RAP error: No jukeboxes are currently usable.
root@new_backup [] # nsrjb -HE -vvv
setting verbosity level to `3'
nsrjb: RAP error: No jukeboxes are currently usable.

Se produce el error. Se ejecuta

root@new_backup [] # /etc/init.d/networker stop
root@new_backup [] # /etc/init.d/networker start

Se relanza  paso 9 y genera salida

setting verbosity level to `5'
nsrjb: initiate_jbox_rap_command: jb_res attrlist:
                     command: nsrjb -HE -vvvvv;
                        name: L500;
                   operation: Reset;
      operation init element: Yes;
       operation report mode: verbose5;
                      source: nsrjb;
nsrjb: initiate_jbox_rap_command: op_stat attrlist:
                     command: nsrjb -HE -vvvvv;
                        name: L500;
                        type: NSR operation status;
nsrjb: Info: Preparing to perform reset operation on jukebox `L500'.
nsrjb: Info: Operation `initialize elements status' is in progress on jukebox `L500'.
nsrjb: Info: Performing operation `Eject' on device `/dev/rmt/1cbn'.
nsrjb: Info: Operation `Eject' in progress on device `/dev/rmt/1cbn'
nsrjb: Info: Preparing to unload volume `AAB312' from device `/dev/rmt/1cbn' to slot 199.
nsrjb: Error: read open error: drive status is There is not a tape in the drive
nsrjb: Info: Unloading volume `AAB312' from device `/dev/rmt/1cbn' to slot 199.
nsrjb: Info: Unload sleep for 5 seconds.
nsrjb: error, Jukebox command terminated with errors.

Se relanza nuevamente paso 9)  se obtiene

root@new_backup [] # nsrjb -HE -vvvvv
setting verbosity level to `5'
nsrjb: initiate_jbox_rap_command: jb_res attrlist:
                     command: nsrjb -HE -vvvvv;
                        name: L500;
                   operation: Reset;
      operation init element: Yes;
       operation report mode: verbose5;
                      source: nsrjb;
nsrjb: initiate_jbox_rap_command: op_stat attrlist:
                     command: nsrjb -HE -vvvvv;
                        name: L500;
                        type: NSR operation status;
nsrjb: Info: Preparing to perform reset operation on jukebox `L500'.
nsrjb: Info: Operation `initialize elements status' is in progress on jukebox `L500'.
nsrjb: Info: There is nothing to unload in jukebox `L500'.