Solaris is a Unix operating system originally developed by Sun Microsystems. Solaris is most advanced enterprise operating system. It delivers security, speed, and simplicity for enterprise

Data Center Consolidation

Data center consolidation is the process of reducing the volume of physical IT assets through highly efficient and scalable technologies. Organizations leverage data center consolidation to reduce operating costs.

Analyse and Solve Serious Hardware and Sofware Problems

Listing several basic hardware and software troubleshooting steps with respect to operating systems, software programs, and computer hardware.

Mission Critical Systems

A mission critical system is a system that is essential to the survival of a business or organization. When a mission critical system fails or is interrupted, business operations are significantly impacted.

The best server hardware to maximize IT performance

Data center hardware advances target new workloads such as big data processing, as well as higher efficiency for existing apps and services. The best server hardware for your data center depends on existing and planned application architectures, data center operations staff skills and of course the IT budget.

Monday, July 13, 2020

How to Set Up the Control Domain

1. Determine whether you have cryptographic devices in the control domain.
Note that only UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 platforms have
cryptographic devices (MAUs). Because newer platforms, such as SPARC T4 systems and
Fujitsu M10 systems, do not have separate cryptographic units, there is no need to assign a
cryptographic accelerator on these platforms.
primary# ldm list -o crypto primary

2. Assign cryptographic resources to the control domain, if applicable.
The following example would assign one cryptographic resource to the control domain,
primary. This leaves the remainder of the cryptographic resources available to a guest domain.
primary# ldm set-mau 1 primary

3. Assign virtual CPUs to the control domain.
For example, the following command would assign 8 virtual CPUs to the control domain,
primary. This leaves the remainder of the virtual CPUs available to a guest domain.
primary# ldm set-vcpu 8 primary

4. Initiate a delayed reconfiguration on the control domain.
primary# ldm start-reconf primary

5. Assign memory to the control domain.
For example, the following command would assign 4 gigabytes of memory to the control
domain, primary. This leaves the remainder of the memory available to a guest domain.
primary# ldm set-memory 4G primary

6. Add a logical domain machine configuration to the service processor (SP).
For example, the following command would add a configuration called initial.
primary# ldm add-config initial

7. Verify that the configuration is ready to be used at the next reboot.
primary# ldm list-config
factory-default
initial [current]
This ldm list-config command shows that the initial configuration set will be used after
you perform a power cycle.


Create Primary Control Domain:-
root@proddb01:~# svcadm enable ldmd
root@proddb01:~# ldm add-vcc port-range=5000-5100 primary-vcc0 primary
root@proddb01:~# ldm add-vds primary-vds0 primary

root@proddb01:~# ldm add-vsw net-dev=net1 primary-vsw0 primary
root@proddb01:~# ldm list-services primary
root@proddb01:~# ldm set-vcpu 32 primary
root@proddb01:~# ldm start-reconf primary
root@proddb01:~# ldm set-memory 64G primary
root@proddb01:~# ldm add-config initial
root@proddb01:~# ldm list-config
factory-default
initial [current]
root@proddb01:~# shutdown -y -i 6


Initial Configuration of the Control Domain

Initially, all system resources are allocated to the control domain. To allow the creation of other
logical domains, you must release some of these resources.

Do not attempt to use memory dynamic reconfiguration (DR) to perform the initial
configuration of the control domain. Although you can use memoryDR to perform this
configuration without needing a reboot, it is not recommended. The memoryDR approach
might take a very long time (longer than a reboot) and could even potentially fail. Instead, use
the ldm start-reconf command to place the control domain in delayed reconfiguration mode
before you change the memory configuration. Then, you can reboot the control domain after
you complete all the configuration steps.

Setting Up Services and the Control Domain

Howto Create Default Services
1. Create a virtual console concentrator (vcc) service for use by the virtual network terminal server
daemon (vntsd) and as a concentrator for all logical domain consoles.
For example, the following command would add a virtual console concentrator service
(primary-vcc0) with a port range from 5000 to 5100 to the control domain (primary).
primary# ldm add-vcc port-range=5000-5100 primary-vcc0 primary

2. Create a virtual disk server (vds) to allowimporting virtual disks into a logical domain.
For example, the following command adds a virtual disk server (primary-vds0) to the control
domain (primary).
primary# ldm add-vds primary-vds0 primary

3. Create a virtual switch service (vsw) to enable networking between virtual network (vnet)
devices in logical domains.
Assign a GLDv3-compliant network adapter to the virtual switch if each logical domain must
communicate outside the box through the virtual switch.
■ In Oracle Solaris 10, add a virtual switch service on network adapter driver to the control
domain.
primary# ldm add-vsw net-dev=net-driver vsw-service primary
For example, the following command adds a virtual switch service (primary-vsw0) on
network adapter driver nxge0 to the control domain (primary):
primary# ldm add-vsw net-dev=nxge0 primary-vsw0 primary

■ In Oracle Solaris 11, add a virtual switch service (primary-vsw0) on network adapter driver
net0 to the control domain (primary):
primary# ldm add-vsw net-dev=net-driver vsw-service primary
For example, the following command adds a virtual switch service (primary-vsw0) on
network adapter driver net0 to the control domain (primary):
primary# ldm add-vsw net-dev=net0 primary-vsw0 primary

■ The following applies to the Oracle Solaris 10 OS only and should not be performed on an
Oracle Solaris 11 system.

This command automatically allocates aMAC address to the virtual switch. You can specify
your ownMAC address as an option to the ldm add-vsw command. However, in that case, it
is your responsibility to ensure that theMAC address specified does not conflict with an
already existingMAC address.

If the virtual switch being added replaces the underlying physical adapter as the primary
network interface, it must be assigned theMAC address of the physical adapter, so that the
DynamicHost Configuration Protocol (DHCP) server assigns the domain the same IP
address. See “EnablingNetworking Between the Control/ServiceDomain and Other
Domains” on page 61.
primary# ldm add-vsw mac-addr=2:04:4f:fb:9f:0d net-dev=nxge0 primary-vsw0 primary

4. Verify the services have been created by using the list-services subcommand.
Your output should look similar to the following:
primary# ldm list-services primary

VDS

NAME             VOLUME         OPTIONS         DEVICE
primary-vds0

VCC
NAME                 PORT-RANGE
primary-vcc0         5000-5100

VSW
NAME                 MAC                   NET-DEV     DEVICE         MODE
primary-vsw0      02:04:4f:fb:9f:0d nxge0             switch@0       prog,promisc

Sunday, June 30, 2019

Veritas NetBackup OpsCenter upgrade


Veritas NetBackup OpsCenter upgrade




Pre-Checks:
1. OpsCenter should run on same version as Netbackup is running or should run on higher version. OpsCenter/OpsCenter Analytics must always be running the same or higher version.
2. Make sure that OpsCenter is compatible with Operating System and Netbackup.
3. OpsCenter should always run on a dedicated server and not on a NBU master
4. Ensure that all required ports are open on OpsCenter Server.

OpsCenter Port requirement:

Steps to Upgrade OpsCenter Analytics
1.    Backup OpsCenter Database
OpsCenter is shipped with a database backup script that performs backup of the database , the corresponding database password file, and the encryption key file without interrupting its operations, which is referred to as hot backup. On UNIX as well as Windows platforms, the script overwrites the existing database files before backing up or restoring them.
Note:
Regular file system backups are not sufficient for backing up the OpsCenter database. You must schedule periodic hot backups for the OpsCenter database to avoid losing any important data.
To back up the OpsCenter database
  1. Log on to the OpsCenter database server host in one of the following ways:
Windows
As an administrator or user in the Administrator group
UNIX
root
  1. Open the Windows command prompt or the UNIX console.
  2. Run the backup script that is appropriate for your platform. Specify one of the following backup directories depending on your platform:
LINUX
/opt/SYMCOpsCenterServer/bin/dbbackup.sh /u01/backup/OpsCenter/

  1. The backup script backs up the database files, database password files, and encryption key file in the backup directory that you specified.
  2. Ensure the compatibility of the OpsCenter with the OS Version ad Bit.
  3. Download OpsCenter installation file to the OS.
  4. Run the installation and follow the process.

Note: OpsCenter should always run on a dedicated server and not on a NBU master

Documentation:

Backing up the OpsCenter database

Download OpsCenter:

How to Backup OpsCenter Database:

Upgrading OpsCenter on UNIX

Use the following procedure to upgrade to OpsCenter software on UNIX hosts.
Note:
Veritas recommends that you do not cancel or interrupt the installation process once it is started.
To upgrade OpsCenter Server on UNIX
  1. If you plan to upgrade your backup product and OpsCenter, ensure that you upgrade OpsCenter first. When upgrading OpsCenter, always upgrade the OpsCenter Server first followed by the Agent and then the View Builder.
  2. Open a UNIX console and log on as root on the target host.
  3. Mount the OpsCenter product DVD on the OpsCenter Server that you want to upgrade.
  4. Untar OpsCenter_7.7_Unix.tar.gz
  5. Cd /u01/share/soft/OpsCenter_7.7_Unix
  6. Type the following command: ./install. Press Enter.
  7. [root@em01 OpsCenter_7.7_Unix]# ./install
  1. The Welcome message is displayed. Press Enter to continue.
  1. The installer then checks if OpsCenter Server is installed on the system or not. It prompts you in case OpsCenter Server is already installed. The installer also examines the system for existing packages. 
  1. The following prompt is displayed:

Where should the existing OpsCenter database and configuration files be backed up? 
An 'OpsCenterServer_backup' directory will be created within the directory that you specify to store these 
files. (/var/symantec/)
Type the directory name in which the existing OpsCenter database and configuration files can be saved and then press Enter.
To accept the default directory path (/var/symantec), press Enter.
  1. The installer displays a list of components that will be installed or upgraded like PBX, OpsCenter Server, OpsCenter user interface and so on. Review this list and press Enter to continue.
  1. The installer prompts you with the following question:
installOpsCenterServer is now ready to upgrade OPSCENTERSERVER.
Are you sure you want to upgrade OPSCENTERSERVER? [y,n,q] (y)
Press Enter to continue OpsCenter upgrade.
  1. The installer prompts you with the following question:
Participate in the NetBackup Product Improvement program? [y,n,q] (y)
Press Enter if you want to participate in the NetBackup Product Improvement program or press n if you do not want to participate.
  1. The installer prompts you with the following question:
Do you want to import users from <remote AT host name> to OpsCenter AT?
Press Enterto import users from the earlier OpsCenter versions.
For more details, refer to the About Importing Authentication Settings section.
If the import fails, you need to reset password of all OpsCenter(vx) users.
  1. By default, in OpsCenter, the database is upgraded in the beginning. However, you can choose to first upgrade the OpsCenter software.
The database upgrade process starts. In this process, the OpsCenter data is migrated to the new OpsCenter database version. The database process may take time depending on your database size.
The following message is displayed:
The database upgrade is in progress. This may take some time based on the database size. You can see the progress and current status in /var/tmp/(directory)/db/log/dbManager_<timestamp>_.log file.
After complete installation, the logs are copied to the following location:/var/VRTS/install/logs/LogDirectory/db/log
LogDirectory is generated during the upgrade progress.

  1. The installer displays the OpsCenter packages that are installed. Depending on the installed packages, the following message may be displayed:
The following packages were found on the system. However the package
versions are older than the ones required by OpsCenter.
 
VRTSOpsCenterServer existing version was found on the system, 
but OpsCenter requires VRTSOpsCenterServer new version
VRTSOpsCenterGUI existing version was found on the system, 
but OpsCenter requires VRTSOpsCenterGUI new version
VRTSOpsCenterLegacyServer existing version was found on the system, 
but OpsCenter requires VRTSOpsCenterLegacyServer new version
The installer then uninstalls the older packages and installs new version of OpsCenter Server.
  1. OpsCenter Server is installed. Configuration changes are made to the system.
  2. All the OpsCenter processes are started. The following information is also displayed:
o    Web URL to access OpsCenter console
o    Location of install log and summary files.


Note:
After successful upgrade, OpsCenter database password is set to an auto-generated string, if the earlier password is still the default one, that is 'SQL'. Veritas recommends that you change the database password after the installation.
If you had changed the default password in the earlier version, you do not need to change it again. The installer retains the old password that you can use in the current version.

Decommissioning a media server

Decommissioning Netbackup Media Server


Following information about is decommissioning a NetBackup media server.

Your path through the nbdecommission wizard depends on how you respond to the wizard prompts. Depending on your environment and how you respond to prompts, the wizard may advise you to perform an action and then exit. To continue in the wizard, you must run the wizard again after you perform the advised action. You may have to exit and rerun the wizard several times.

If active jobs exist on the media server, you must cancel them before the command can begin to decommission the media server. Alternatively, you can wait until they finish.

The OldServer does not have to be up and responsive.
Veritas recommends that you preview the media server references before you decommission a media server.

The nbdecommission command logs to the standard NetBackup administrator commands log directory.
Two procedures exist, as follows:
1. Replace an old media server with a new media server
2. Decommission a media server.

To replace an old media server with a new media server
1. Run the nbdecommission command on the master server or on a media server that is not the object of this operation. The following is the command syntax:

On Windows:
install_path\NetBackup\bin\admincmd\nbdecommission -oldserver OldServer [-newserver NewServer] [-file decom_ops.txt]

On UNIX:
/usr/openv/netbackup/bin/admincmd/nbdecommission -oldserver OldServer [-newserver NewServer] [-file decom_ops.txt]
Replace OldServer with the name of the host to be decommissioned.

-newserver is optional. If you specify a new server, the new server becomes the default media server for the replacement operations. If you do not specify a new server, the wizard prompts you for the new server for each storage type that contains valid backup images. This method is useful if you want to move backup images to different media servers. For example, you can move backup images from tape storage to one media server and backup images from disk storage to another media server.
-file is optional. It writes the command operations to the specified file. Replace decom_ops.txt with a name that denotes its purpose or contents. Veritas recommends that you use the -file option to maintain a record of the command operations.

2. Follow the prompts and perform the requested actions.
For example, the command may make changes on the master server and on multiple media servers. You may be required to restart the NetBackup services on those servers so that the changes take effect.

To decommission a media server
a) Run the following command on the master server or on a media server that is not the object of this operation. The OldServer does not have to be up and responsive.

On Windows:
install_path\NetBackup\bin\admincmd\nbdecommission -oldserver OldServer

On UNIX:
/usr/openv/netbackup/bin/admincmd/nbdecommission -oldserver OldServer
Replace OldServer with the name of the host to be decommissioned.

b) Follow the prompts and perform the requested actions.


bphdb exit status = 5449: The script is not approved for execution


Registering authorized locations used by a NetBackup database script-based policy


To add an authorized location

    Open a command prompt on the client.
    Use nbsetconfig to enter values for an authorized location. The client privileged user must run these commands.

On UNIX:
root@erpddb01:/usr/openv/netbackup/bin/nbsetconfig
nbsetconfig>DB_SCRIPT_PATH = /export/home/oraprod/scripts
nbsetconfig>DB_SCRIPT_PATH = /export/home/oraprod/scripts/rmanfull.daily
nbsetconfig>
<ctrl-D>

Reference: NetBackup Support Knowledge base


Tuesday, June 25, 2019

Issue with Robots Missing Path


  è To Check Robots with missing path
o   Java GUI
n  Under Media and Device Mgmt àUnder Devices àSelect Robots
o   Command
n  /usr/openv/volmgr/bin/tpconfig –d
80  Drive161   hcart3 TLD(6)  DRIVE=7             /dev/nst27                                                       UP
81  Drive162             hcart3 TLD(6)  DRIVE=8   /dev/nst28                                                       UP
82  Drive108             hcart3 TLD(6)  DRIVE=9   /dev/nst29                                                       UP

Currently defined robotics are:
  TLD(1)     robotic path = /dev/sg291
  TLD(3)     robotic path = /dev/sg76
  TLD(4)     robotic path = /dev/sg52
  TLD(5)     robotic path = /dev/sg98
  TLD(6)     robotic path = /dev/sg87
  TLD(7)     robotic path = /dev/sg74

EMM Server = usvhvoilms001
 or
/usr/openv/volmgr/bin/tpconfig -l
  èDelete the robot with missing path either java GUI or Command
o   Java GUI (Recommended)
n  Under Media and Device Mgmt àUnder Devices àSelect Robots àSelect the robot with missing path  àRight Click and Select Delete
o   Command
n  /usr/openv/volmgr/bin/tpconfig –delete  -robot <robot number>
  èRestart Media Manager processes.
  èIf received any error while deleting robot, please follow this steps
o   Please check any resource holding this robot using this command
n  /usr/openv/netbackup/bin/admincmd/nbrbutil –dump
n  If you see any resource holding this robot please use this command to release it nbrbutil -resetMediaServer <media server name>
or
nbrbutil -releaseMDS
nbrbutil -releaseMedia

  èCheck the robot at Operating System Level
o   /usr/openv/volmgr/bin/scan
o   /usr/openv/volmgr/bin/tpautoconf –r
o   cat /proc/scsi/scsi
If found robot at OS level, please run Device Config Wizard on Master server and rescan the devices on master server and follow the on screen steps to add the robot.

èRestart Media Manager processes.
  èTo Confirm Robot is added
o   Java GUI
n  Under Media and Device Mgmt àUnder Devices àSelect Robots
o   Command
n  /usr/openv/volmgr/bin/tpconfig –d or
/usr/openv/volmgr/bin/tpconfig -l
  èTo Test the robot
o   Use /usr/openv/volmgr/bin/robtest.