Quantcast
Channel: Backup Activity
Viewing all 107 articles
Browse latest View live
↧

Media Manager status code 8 (Invalid Media ID)

July 20, 2016, 8:54 pm
$
0
0
Media Manager status code 8
Message: invalid media ID
Explanation: When a process performed a media-related operation, it encountered an empty or an incorrectly formatted media identifier. Or a media ID that was passed
to it cannot be operated on as requested.Media Manager status codes 463 Media Manager status codes

Recommended Action:
■ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See "Setting Media Manager debug logging to a higher level" in the NetBackup
Logging Reference Guide.
■ Ensure that the media ID, where requested, is not blank.
■ Ensure that the specified media IDs contain valid characters only: alphanumeric
characters, the period (.), the plus sign (+), and the underscore (_). A hyphen
(-) is also a valid character when not the first character in the media ID.
■ If media are specified to be ejected from a library, ensure the following: they
exist in the EMM database and are associated with the correct robot number.
■ Ensure that the media ID is from 1 to 6 characters in length.
■ Ensure that a valid media and seed were specified.
■ If the operation is an inventory request for an ACS robot, use the robtest utility
to verify the following: the ACS interface returns cleaning media IDs both in the
query volume list and in the query cleaning volume list.
Media Manager status code 9
Message: invalid media type
Explanation: A process that performed a media-related operation encountered
an unknown, missing, or incompatible media type specifier.
Recommended Action:
■ If you run a robot inventory on a robot of type ACS, TLH, or TLM, ensure the
following: the installed version of NetBackup supports and recognizes the vendor
media type that the robot control software returns.
■ If using a command line interface directly, verify that a valid media type has
been passed, according to vmadd(1m) command-line documentation.
■ Ensure that an operation valid only for cleaning media has not been requested
on a media ID that does not correspond to cleaning tape.
■ Ensure that the media type in all barcode rules is a valid media type or the
ordinal zero (0), to represent the default media type.

Source : www.veritas.com
↧
Search

Media Manager status code 9 (Invalid Media Type)

July 20, 2016, 9:34 pm
$
0
0
Media Manager status code 9
Message: invalid media type

Explanation: A process that performed a media-related operation encountered
an unknown, missing, or incompatible media type specifier.

Recommended Action:
■ If you run a robot inventory on a robot of type ACS, TLH, or TLM, ensure the
following: the installed version of NetBackup supports and recognizes the vendor
media type that the robot control software returns.
■ If using a command line interface directly, verify that a valid media type has
been passed, according to vmadd(1m) command-line documentation.
■ Ensure that an operation valid only for cleaning media has not been requested
on a media ID that does not correspond to cleaning tape.
■ Ensure that the media type in all barcode rules is a valid media type or the
ordinal zero (0), to represent the default media type.

Source : www.veritas.com
↧
↧

Media Manager status code 10 (Invalid Barcode)

July 20, 2016, 9:36 pm
$
0
0
Media Manager status code 10
Message: invalid barcode

Explanation: When a process performed a media-related operation, it encountered
an unknown, missing, or incompatible barcode.

Recommended Action:
■ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See "Setting Media Manager debug logging to a higher level" in the NetBackup
Logging Reference Guide.
■ Ensure that the barcode, where requested, is not blank.
■ Ensure that the specified barcodes contain valid characters only: Alphanumeric
characters, and the period (.), plus sign (+), and underscore (_). A hyphen (-)
is also a valid character when not the first character in the media ID.
■ Ensure that the number of characters in the barcode does not exceed the
maximum that is allowed for the robot type.
■ Ensure that the barcode tag in all barcode rules is a subset of a valid, supported
barcode format.

Source : www.veritas.com


↧

Media Manager status code 11 (Invalid Description)

July 20, 2016, 9:37 pm
$
0
0
Media Manager status code 11
Message: invalid description

Explanation: The volume description exceeds 25 ASCII characters in length, or
contains unprintable characters.

Recommended Action: When you add or change a volume record or barcode
rule record, ensure that the description field contains the following: no more than 25 ASCII characters that can be printed.

Source : www.veritas.com
↧

Media Manager status code 12 ( Invalid Robot Type)

July 20, 2016, 9:38 pm
$
0
0
Media Manager status code 12
Message: invalid robot type

Explanation: A requested operation encountered a case where a specified robot
type or a volume’s robot type is different. It differs from the type of robot that is
required to perform the operation in the current configuration.

Recommended Action:
■ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See "Setting Media Manager debug logging to a higher level" in the NetBackup
Logging Reference Guide.
■ Specify a robot type that supports the volume’s media type.
Media Manager status codes 465
Media Manager status codes
■ Check the EMM database and ensure that the specified robot type agrees with
the type for all volumes having the specified robot number.
■ If a robot type is required for the requested operation, ensure that a robot type
has been specified.

Source : www.veritas.com
↧
↧

NetBackup status code: 19 (getservbyname Failed)

July 20, 2016, 9:43 pm
$
0
0
NetBackup status code: 19
Message: getservbyname failed

Explanation: A call to getservbyname() failed. The getservbyname()function uses the name of the service to find a service entry in the services file. (Or NIS
services map on UNIX if it is configured.)

Recommended Action: Do the following, as appropriate:
■ Check the NetBackup Problems report for clues on why the failure occurred.
■ On a UNIX or Linux system, check that /etc/services and NIS services map (if applicable) have entries for the NetBackup services: bpcd, bpdbm, and bprd.
■ On a Windows system, verify that the %SystemRoot%\system32\drivers\etc\services file shows the correct entries
for the NetBackup Internet processes: bpcd, bpdbm, and bprd.
Ensure that the following numbers match the settings in the services file: The NetBackup Client Service Port number and NetBackup Request Service Port
number on the Network tab in the NetBackup Client Properties dialog box. To display this dialog box, start the Backup, Archive, and Restore interface and
click NetBackup Client Properties on the File menu. The values on the Network tab are written to the services file when the NetBackup Client service
starts. See "Verifying host name and service entries" in the NetBackup Troubleshooting Guide.
■ Check the level of network activity. An overloaded network can cause this error.
■ If these actions do not reveal the problem, create a debug log directory for the process that returned this status code. Then retry the operation and check the
resulting debug log. 

Source : www.veritas.com
↧

NetBackup status code: 20 (Invalid Command Parameter)

July 20, 2016, 10:02 pm
$
0
0
NetBackup status code: 20
Message: invalid command parameter

Explanation: One or more command parameters were not valid. This error can occur when incompatible levels of NetBackup are installed on a master and its media servers or clients. For example, a NetBackup master server has NetBackup 7.6 and the media server or the client has NetBackup 7.0. This error can also occur if the wrong parameters are used when you run a command line.

Recommended Action: Do the following, as appropriate:
■ Check the NetBackup Problems report for clues.
■ If the error occurs when you run a command on the command line, verify that the parameters are valid.
■ This status code may occur if nbjm passes parameters but does not have a required parameter. Check the nbjm unified logs (originator ID 117) for the list of parameters that were passed.
■ The following information pertains to NetBackup Snapshot Client.
■ If the following appears in the /usr/openv/netbackup/logs/bptm log as enabled on a third-party copy backup, multiplexing was enabled on a third-party copy backup:

bptm: cannot perform Third-Party-Copy for multiplexed backups
send_brm_msg: ERROR 20

bptm: EXITING with status 20
The Third-party Copy Device off-host backup method is incompatible with multiplexing (the writing of two or more concurrent backup jobs to the same storage device). You must disable multiplexing for any third-party copy backups. If multiplexing is enabled, the backup fails.
■ The media server may not have the correct 3pc.conf file entry for the client
disk that is needed for the backup.
The following appears in the /usr/openv/netbackup/logs/bpbkar log:
14:45:00.983 [15773] <4> bpmap_mm_get_devid: GET_DEVICE_INDEX 1
EMC:SYMMETRIX:601092014000
14:45:00.986 [15773] <4> bpbkar child_send_keepalives: keepalive
child started, pid = 15822
14:47:02.029 [15773] <4> bpmap_mm_get_devid: keepalive child:
15822 killed
14:47:02.030 [15773] <4> bpmap_mm_get_devid: DEVICE_INDEX -1
14:47:02.031 [15773] <16> bpmap_send_extend: ERR - can't obtain
device id string EMC:SYMMETRIX:601092014000
14:47:33.167 [15773] <16> bpbkar Exit: ERR - bpbkar FATAL exit
status = 227: no entity was found
14:47:33.167 [15773] <4> bpbkar Exit: INF - EXIT STATUS 227: no
entity was found
14:47:33.168 [15773] <2> bpbkar Exit: INF - Close of stdout complete2>4>16>16>4>4>4>4>
 
This shows that a particular device cannot be found in the 3pc.conf file on the media server (14:47:02.031 [15773] <16> bpmap_send_extend: ERR - can't obtain device id string EMC:SYMMETRIX:601092014000)16>.

The problem is one of the following:
  • The 3pc.conf file on the media server is outdated. Recreate the 3pc.conf file.
  • The media server is not on the same Fibre Channel network as the third-party copy device and client disk. As a result, the 3pc.conf file does not have a correct entry for the client disk. Run the bptpcinfo command with the -x client_name option; this option adds the client disk to the 3pc.conf file. For each disk that is added to the file by means of bptpcinfo -x client_name, you may need to add the device’s World Wide Name (WWN=).
See the NetBackup Snapshot Client Configuration online document.
See Snapshot Client Assistance in the NetBackup Snapshot Client Administrator’s Guide.

■ The HP VxFS snapshot mechanism requires a dedicated cache partition for each snapshot. A check is made in the mount table to make sure that the cache partition is not already in use. If the cache partition is already in use, status code 20 occurs.
Check the /usr/openv/netbackup/logs/bpbkar log for a message similar to the following:

bpfsmap: FTL - bpfsmap: snapshot cache already in use, /dev/arrayvg/vol4c
bpbkar Exit: ERR - bpbkar FATAL exit status = 20: invalid
command parameter
bpbkar Exit: INF - EXIT STATUS 20: invalid command parameter
 
If the snapshot cache partition is already in use, do one of the following: Set up your policy schedules to run at different times or use different cache partitions for each backup.
If the Allow multiple data streams option is enabled, each stream must have its own dedicated cache partition.
■ Compare the NetBackup version level on the server to the version level on the clients by doing the following:
  • On UNIX or Linux NetBackup servers and clients, check the /usr/openv/netbackup/bin/version file.
  • On Windows NetBackup servers, check the install_path\Netbackup\version.txt file or the About NetBackup item on the Help menu.
  • On Microsoft Windows clients, check the About NetBackup item on the Help menu.
  • If a Java interface displays the error, tell them how to enable the debug print manager in the Java startup file. Retry and compare the parameters that were logged on the Java log with the parameters listed in the commands usage statement.
■ For the Backup Media Server option for VMware backups, the storage unit that is specified in the policy must be unique to your media servers. If the storage
unit is also available on another media server, the snapshot job cannot succeed.
■ If these actions do not reveal the problem, create a debug log directory for the process that returned this status code (if the process uses legacy logging). Then
retry the operation and check the resulting log.

Source : www.veritas.com
↧

NetBackup status code: 24 (Socket Write Failed)

July 21, 2016, 12:56 am
$
0
0
NetBackup status code: 24
Message: socket write failed
Explanation: A write operation to a socket failed.

Recommended Action: Do the following, as appropriate:
■ Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine the cause from the Problems report, create
debug log directories for the processes that could have returned this status code. Then retry the operation and check the resulting debug logs.
■ A possible cause is a high network load. For example, this problem occurs with Cannot write to STDOUT when a Windows system that monitors network load
detects a high load. It then sends an ICMP packet to other systems to inform them that the route they use is disconnected. The log messages were similar
to the following:

01/31/96 14:05:23 ruble crabtree.null.com from client
crabtree.null.com: ERR - Cannot write to STDOUT. Err no= 242: No
route to host
01/31/96 14:05:48 ruble crabtree.null.com successfully wrote
backup id crabtree.null.com_0823125016, copy 1, fragment 1,
440864 Kbytes at 628.538 Kbytes/sec
01/31/96 14:05:51 netbackup crabtree.null.com CLIENT
crabtree.null.com POLICY Remote3SysFullW SCHED Sirius EXIT
STATUS 24 (socket write failed)
 
■ The following information applies only to Sun Solaris:
Verify that all operating system patches are installed. See the Operating Notes section of the NetBackup Release Notes.
■ The following information applies only to Windows systems:
Verify that the recommended service packs are installed. Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.

Source : www.veritas.com
↧
Search

NetBackup status code: 25 (Cannot Connect on Socket)

July 21, 2016, 1:18 am
$
0
0
NetBackup status code: 25
Message: cannot connect on socket
Explanation: A process that timed out while it connects to another process for a particular operation. This problem can occur in the following situation: when a process tries to connect to the NetBackup request daemon (bprd) or database manager daemon (bpdbm) and the daemon is not running. (On Windows, these daemons are the NetBackup Request Manager and the NetBackup Database Manager services.)
It can also occur in the following situations: the network or server is heavily loaded and has slow response time or an evaluation license key for NetBackup expired. However, the most common cause of this error is a host name resolution problem.

The following are other possible causes of this error caused by network connectivity
issues or a required process such as pbx_exchange not running.
■ nbjm is unable to connect to bpcd on the media server
■ nbpem is unable to connect to nbproxy
■ bptm on the media server is unable to connect to nbjm on the master server.
■ You cannot perform an immediate backup operation.

These errors are caused either by network connectivity issues or if a required
process such as pbx_exchange is not running.

Recommended Action: Do the following, as appropriate:
■ Verify that bpcompatd, vnetd, and Private Branch Exchange (PBX) are running.
Information on how to start PBX is available.
See "Resolving PBX problems" in the NetBackup Troubleshooting Guide.
■ If necessary, stop and restart NetBackup.
■On UNIX systems, enter the following:
/usr/openv/netbackup/bin/bp.kill_all
/usr/openv/netbackup/bin/bp.start_all
 
■ On Windows systems, enter the following:
install_path\NetBackup\bin\bpdown
install_path\NetBackup\bin\bpup
 
■ The following information applies only to a UNIX or Linux NetBackup master
server:
Verify that the bprd and the bpdbm processes are running. If these processes are not running, start them. On a Windows master server, verify that the NetBackup Request Manager and the NetBackup Database Manager services are running. If these services are not running, start them. If these processes or services are running, examine the All Log Entries report for the time of the failure to determine where the failure occurred.
Do one of the following:
■ If you cannot view the report or you get a cannot connect on socket error, verify again that the NetBackup Database Manager service or daemon is running. Then, create a debug log directory for bpdbm, retry the operation, and check the resulting debug log.
■ If you view the report and do not find a problem-related entry, create the debug log directories for the related processes that were running when the
error first appeared. (This process frequently is bpbrm.) Then, retry the operation and check the resulting debug logs.
■ Verify that the server list specifies the correct master server.
■ The following information applies only to Windows systems:
The master server is designated in the Server to use for backups and restores drop-down in the Specify NetBackup Machines and Policy Type dialog box. To display this dialog box, start the Backup, Archive, and Restore interface and click Specify NetBackup Machines and Policy Type on the File menu.

■ The following information applies only to UNIX and Linux systems:
The master server is the first SERVER entry in the bp.conf file.
■ Check the following Veritas Support website to ensure that all recommended
NetBackup patches are installed: www.veritas.com/support
Then select NetBackup followed by files and updates.
■ If failure occurs when you run a user-directed backup from a client, make sure that a user-directed backup schedule exists at the master server.
■ With NetBackup database extensions:
Make sure that the applicable database product has the correct permissions allowing NetBackup to write to the progress log on the client.
■ The following information applies only to UNIX systems:
If bpdbm has quit when the shutdown script runs on a media server, carefully read the K77netbackup script. It contains details on how to prevent this problem. The script is in /usr/openv/netbackup/bin/goodies.

If you change the server list on a master server, stop, and restart the following:
The NetBackup Database Manager and request daemons (UNIX) or the NetBackup Database Manager and NetBackup Request Manager services (Windows).
■ Check the services file.
■ The following information applies only to UNIX systems:
Verify that the /etc/services file (and NIS services if NIS is used) has entries for the NetBackup services: bpcd, bpdbm, and bprd.
On Windows, verify that the %SystemRoot%\system32\drivers\etc\services file has the correct entries for bpcd, bpdbm, and bprd.
Also, verify that the following numbers match the settings in the services file:
The NetBackup Client Service Port and the NetBackup Request Service Port on the Network tab in the NetBackup Client Properties dialog box. To display this dialog box, start the Backup, Archive, and Restore interface and click NetBackup Client Properties on the File menu. The values on the Network tab are written to the services file when the NetBackup Client service starts.
See Verifying host names and service entries in NetBackup in the NetBackup  Troubleshooting Guide.

■ On Sun Solaris, verify that all operating system patches are installed See the Operating Notes section of the NetBackup Release Notes.
■ On Windows, verify that the recommended service packs are installed.
■ When the base NetBackup license key expires, daemons (such as bprd and bpdbm) terminate on the NetBackup server. If these daemons are not running, you are likely to encounter status code 25 errors in the Administration console. Install a valid base NetBackup license key, restart the daemons, and restart the console.
■ For NetBackup Snapshot Client, the following applies: When many devices are configured on a media server, it may take a long time for the bptpcinfo command to generate the file 3pc. When the backup is run for the first time, the backup may fail with status 25. Make sure that the /usr/openv/volmgr/database/3pc.conf file exists. If it does, rerun the backup.
If the backup fails again, run the bptpcinfo manually to generate the file 3pc, then try the backup again.
↧
↧

NetBackup status code: 103 ( Error Occurred During Initialization, check configuration file)

July 21, 2016, 1:23 am
$
0
0
NetBackup status code: 103
Message: error occurred during initialization, check configuration file

Explanation: NetBackup Snapshot Client can perform two kinds of off-host backups by means of a data mover: the NetBackup media server method or the Third-Party
Copy Device method. For either method, an off-host data mover backup requires a configuration file (the 3pc.conf file) to identify the following devices on the SAN:
■ The client disks to back up
■ The devices on which to store the data 

If the media server has access to many disks and storage devices on the SAN, it may take too long to acquire the device information from the SAN. As a result, if no 3pc.conf file exists on the media server, the first multistream backup that uses a data mover method may fail.

Recommended Action: Create the 3pc.conf file manually before running the first multistream data mover backup. Use the following command to create the 3pc.conf file:
# bptpcinfo -a
The 3pc.conf file is created at /usr/openv/volmgr/database/3pc.conf. More information is available on the 3pc.conf file and how to create it.
See Configuring NetBackup for off-host data mover backups in the NetBackup Snapshot Client Configuration document.

Source : www.veritas.com
↧

Backup Exec 16 System Requirements

May 27, 2017, 8:25 am
$
0
0
If you have decided to use the Veritas Backup Exec 16 as your backup software in your organization, please remember in your mind, if there are system requirement to be fulfilled. Here ar the system requirements :

Server Operating System
  •     Microsoft® Windows 2016 Server Family
  •     Microsoft® Windows 2012 Server Family
  •     Microsoft® Windows 2012 R2 Server Family
  •     Microsoft® Windows Small Business Server 2011
  •     Microsoft® Windows Small Business Server 2008
  •     Microsoft® Windows 2008 R2 Server Family
  •     Microsoft® Windows 2008 x64 Server Family

Virtual Environments

  •     VMware vSphere 6.5
  •     VMware vSphere 6
  •     VMware vSphere 5.5
  •     VMware vSphere 5.1
  •     Microsoft® Hyper-V 2016
  •     Microsoft® Hyper-V 2012 and 2012 R2
  •     Microsoft® Hyper-V 2008 and 2008 R2

Client Operating Systems

  •     Microsoft® Windows 7, 8, 8.1, 10 Client x86 & x64 (Supported by Agent for Windows)
  •     Microsoft® Windows 2008 R2, 2012 R2, 2016 Server x64 (Supported by Agent for Windows)
  •     Novell OES 11 SP2 (Supported by Agent for Linux)
  •     Ubuntu 10.04, 11.10, 12.04, 12.10, 14.04 (Supported by Agent for Linux)
  •     Citrix XenServer 5.1, 6.3, 6.5 (Supported by Agent for Linux)
  •     Debian GNU/Linux 6.0.3, 7.0.5, 8.0 (Supported by Agent for Linux)
  •     RHEL 5.11, 6.0 & 7.0 (Supported by Agent for Linux)
  •     Oracle Linux (OL) 5.7, 6.5, 7.0 (Supported by Agent for Linux)
  •     CentOS 6.7, 7.0 (Supported by Agent for Linux)
  •     SUSE Linux Enterprise Server (SLES) 11 SP4, 12 SP1 (Supported by Agent for Linux)
  •     SDR for Windows 7, 8, 8.1 and Windows 2008 R2, 2012 R2, 2016 (Supported by Agent for Windows)
  •     Exchange 2007 SP3, 2010 SP3, 2013 SP1, 2016 CU4 (Supported by Agent for Applications and Databases)
  •     SharePoint Server 2010 SP2, 2013 SP1 (Supported by Agent for Applications and Databases)
  •     SQL Server 2005 SP4, 2008 SP4, 2008 R2 SP3, 2012 SP3, 2014 SP2, 2016 SP1 (Supported by Agent for Applications and Databases)
  •     Oracle 10g R2, 11g R2, 12c R1 Oracle 10g R2, 11g R2, 12c R1 (Supported by Agent for Windows and Linux)
  •     Enterprise Vault 9.0 SP4, 10.0 SP4, 11.0 SP1 12.1 (Supported by Agent for Applications and Databases)

Note: Veritas Backup Exec™ 16 cannot install media servers on 32-bit operating


Internet Browser

Internet Explorer 7.0 or later

Installation Disk Space

1.26 GB (Typical installation), 1.91 GB (includes all options)

Note: Disk space requirements may vary depending on the operations performed, the options installed, and the specific system configuration. The Backup Exec Database and catalogs require additional space. An additional 525 MB is required for SQL Express. Any disk storage that you use also requires additional space.

Memory - Backup Exec Server

Minimum Required: 1 GB RAM

Recommended: 2 GB RAM

Note: RAM Requirements may vary depending on the operations performed, the options installed, and the specific computer configuration Symantec Recovery Disk: 1 GB minimum (dedicated) for the multilingual version.

Memory - Backup Exec Central Administration Server

Minimum Required: 1 GB RAM above operating system’s requirement

Recommended: 2 GB RAM above operating system’s requirement
Note: RAM requirements may vary depending on the number of Backup Exec servers.


Virtual Memory Recommendations

20 MB above the Windows recommended size for total paging file size (total for all disk volumes)

Processor
Intel 64, Xeon (64bit), AMD64, or compatible

Processor - Backup Exec Deduplication Option
Minimum Required: 4 Cores
Recommended: 8 Cores
Screen Resolution
1024 x 768 minimum
SQL Server or SQL Express for Backup Exec Database
SQL Express 2014 SP2

Other Hardware
Network interface card or a virtual network adapter card
CD/DVD drive
A mouse or other pointing device

Storage Hardware
You can use storage media drives, robotic libraries, removable storage devices, and non-removable hard drives.
You can find a list of compatible types of storage at the following URL: http://www.veritas.com/docs/000024527.

Support is available for the first drive in each robotic library when you purchase Backup Exec. To enable support for each additional robotic library drive, you must purchase the Backup Exec Library Expansion Option.

For further information

Backup Exec 16 Software Compatibility List (SCL) https://www.veritas.com/docs/000115689

Source : veritas.com
↧

Veritas NetBackup 8.0 New Features

May 27, 2017, 9:37 am
$
0
0
Veritas Technologies has announced the launch of Veritas NetBackup 8.0 on December 01, 2016 in California, USA. Here is the new features exist on Netbacku 8.0
  • NetBackup servers must use a host name that is compliant with RFC 1123 and RFC 952
  • NetBackup 8.0 support additions :
  1. The following products and services are supported starting with NetBackup 8.0:
  2. VMware Backup Server vSphere 6.0 and its updates – VDDK 6.0.2
  3. Client – Windows Server 2016 (Client, File Systems)
  4. Bare Metal Restore (BMR) support for client and boot server on SUSE Linux
  5. Enterprise Server (SLES) 12 SP1
  6. Enterprise Vault 12
  7. Hyper- V for Windows Server 2016
  • NetBackup 8.0 introduces Host ID-based certificates that are based on UUIDs (Universally Unique Identifiers) assigned by NetBackup master server.
  • New encryption algorithm for Media Server Deduplication Pool (MSDP)
  • Update JRE using the nbcomponentupdate utility
  • The nbcomponentupdateutility supports JRE update for following products:
  1. NetBackup Master, Media, and Client
  2. NetBackup Remote Administration Console
  3. OpsCenter Server, Agent, and View Builder
  • Retention levels extended to 100
  • MSDP stream handler enhancements for Isilon filers using NDMP
  • Several shutdown commands will be deprecated in a future releasedaemons will be provided in an upcoming release. At that point, the followingcommands will no longer be available:
  1. bp.kill_all
  2. bpdown
  3. bpclusterkill
  • bpmedialist -count option will be deprecated in a future release
  • Removal of feature to upload logs to FTP server
  • Incremental reporting feature with nbdeployutil
  • Change to OpsCenter database default password
  • OpsCenter interface requires HTTPS protocol
  • Web services enabled in NetBackup 8.0
  • Support for Microsoft Azure cloud
  • The NetBackup CloudStore Service Container (nbcssc) service isnow highly available in a clustered environment
  • Use of certificate-based authentication in the NetBackup CloudStore Service Container
  • Cloud storage management
  • Added support for cloud storage configuration in a clustered environment
  • New directory added for cloud storage configuration files
  • A new directory named cloudis added to the following location:
  1. On Windows: NB_INSTALL_PATH\NetBackp\db\
  2. On UNIX:/usr/openv/netbackup/db/
  • Change in file path for the cloud storage configuration files
  • SharePoint 2016 Local System account requirements
  • For SharePoint 2016, the NetBackup Legacy Client Service and NetBackup Legacy
  • Network Service must run as the “Local System account”.
  • Support for SYMCquiesce for Linux VMs will be discontinued in a future release
  • Enhanced file mapping for VM backups
  • Support for VMware fault tolerant VMs
  • Support for VMware SAN multi-pathing on Linux
  • Additional support for individual VMware virtual machine disk restores
  • VMware web client plug-in time zone limitation removed
  • Backups of VMware VMs that have NVMe controllers not supported
  • Faster backup of Hyper-V virtual machines on Windows Server 2016
 Source : veritas.com

↧

Aruba Releases New Aruba 8400 Core Switch and ArubaOS-CX Operating System

June 12, 2017, 8:38 pm
$
0
0
Nowadays the traffic of data has been changed. The traffic is derived by the application of the mobile-cloud and IoT era. Adaptation of this situation, Aruba, a Hewlett Packard Enterprise company (NYSE: HPE) has announced a new enterprise core and aggregation switch and the industry’s most advanced operating system, ArubaOS-CX, designed for modern mobility, cloud, and IoT requirements. 



 
The Aruba 8400 Core Switch Series and ArubaOS-CX are purpose-built for emerging mobile-cloud business applications and changing traffic patterns that are being driven by the massive flood of data sources and growth in IoT.

The Aruba 8400 Switch Series delivers a breakthrough in campus core and aggregation, extending intelligence from the edge to the core and allowing CIOs to derive better business outcomes from their networks. While the Aruba 8400 provides the carrier-class availability and performance that organizations need in a core switch, the innovation goes beyond table stakes to address the need for immediate visibility, greater security, better insights into troubleshooting, and easier automation, giving enterprises true business agility as they move to mobile-first, cloud, and IoT-enabled businesses.

KEY FEATURES
  • High performance 19.2 terabits per second switching (1.2Tbps/slot) capacity
  • Carrier-class high availability with redundant management, power and fabric
  • ArubaOS-CX enables automation and usability using built-in REST APIs and Python scripts
  • Intelligent monitoring and visibility with Aruba Network Analytics Engine
  • Advanced Layer 2/3 feature set includes BGP, OSPF, VRF, and IPv6
  • Compact 8U chassis with high density, line rate 10GbE/40GbE/100GbE connectivity 
  • Multi-chassis link aggregation

Source : news.arubanetworks.com
↧
↧

What's New in vSAN 6.6

June 15, 2017, 1:17 am
$
0
0
vSAN is VMware’s industry-leading software powering Hyper-Converged Infrastructure solutions.

vSAN 6.6 enhances the industry’s most popular HCI solution with the first native HCI security, highly available stretched clusters, and 50% higher all-flash performance for business-critical and next-generation workloads.


Industry's First Native HCI Encryption
vSAN offers the first native HCI encryption solution for data-at-rest, protecting critical data from unwanted access. vSAN encryption delivers lower costs and greater flexibility by being hardware agnostic and by offering simplified key management. No more requirements to deploy specific self-encrypting drives (SEDs). vSAN encryption is also built for compliance with support for 2-factor authentication (SecurID and CAC) and is the first HCI solution with a DISA-approved STIG.

Stretched Cluster with Local Site Protection
New enhanced stretched clusters with local site protection provide protection against both site failures and local component failures at 50% lower cost than traditional solutions. With a comprehensive stretched cluster solution, you can extend the cost and simplicity benefits of HCI to your disaster recovery and business continuity needs.

vSAN Cloud Analytics
With vSAN Cloud Analytics, you can decrease operational costs with pro-active, real-time support notifications and recommendations. The analytics tool delivers custom, real-time alerts through vSAN Health Service with custom actionable insights and remediation recommendations.

Unicast Networking
vSAN now supports unicast networking to help simplify your initial vSAN setup. You can utilize unicast for vSAN networking and there is no need to setup multicast anymore. This enables vSAN to be deployed in a wider set of on-premise and cloud environments without requiring network changes.

vSAN Management Pack for vRealize Operations
The new vSAN Management Pack for VMware vRealize Operations Manager provides additional options for monitoring, managing and troubleshooting vSAN along with end-to-end infrastructure solutions. With the vSAN management pack, you can gain insights about the impact of vSAN in your infrastructure quickly, and bring your business greater efficiency in shorter time.

Always-On Protection with Enhanced Availability
With new always-on protection features, vSAN keeps your applications running and available despite potential hardware challenges. New Degraded Device Handling (DDH) intelligently monitors the health of drives and proactively evacuates data before failures can happen. New smart drive rebuilds and partial rebuilds deliver faster recovery during hardware failures and decrease cluster traffic for greater performance.

Intelligent Operations and Lifecycle Management
New intelligent operations and lifecycle management capabilities accelerate initial hardware setup, simplify software install, and deliver 1-click controller hardware lifecycle management for a more predictable hardware experience. You can reduce management time up to 80% for common tasks with 1-click automation.

Up to 50% Higher All-Flash Performance
Optimized data services further extend vSAN’s performance advantage by delivering up to 50% more IOPS per all-flash host versus previous versions of vSAN, enabling over 150K IOPS per host. The increased performance helps accelerate mission critical applications and provides higher consolidation ratios for workloads.

Support of Next-Generation Workloads
New validated architectures provide a proven path for deploying next-generation applications like Splunk, Big Data, and Citrix XenApp. In addition, vSAN for Photon is now available in Photon Platform 1.1 and a new Docker Volume Driver delivers support for multi-tenancy, policy based management, snapshots and clones.

Day 1 Support of New Hardware Technologies
Customers can accelerate new hardware adoption with Day 1 support of the latest flash technologies, including solutions like the new Intel Optane 3D XPoint NVMe SSDs. In addition, vSAN now offers larger caching drive options, including 1.6TB flash drives, so that customers can take advantage of the latest and larger capacity flash drives.

Certified File Services and Data Protection Solutions
The VMware Ready for vSAN Program enables customers to extend and complement their vSAN environment with proven, industry-leading data protection and file service solutions from 3rd party partners.

Source : vmaware.com
↧

Veritas Netbackup 8.0 Status Code

July 1, 2017, 10:29 am
$
0
0
Veritas Netbackup 8.0 comes with various improvements from the previous version, there are several new status codes present in this version. Here is the complete list of Netbackup status code for the version 8.0.


0    the requested operation was successfully completed
1    the requested operation was partially successful
2    none of the requested files were backed up
3    valid archive image produced, but no files deleted due to non-fatal problems
4    archive file removal failed
5    the restore failed to recover the requested files
6    the backup failed to back up the requested files
7    the archive failed to back up the requested files
8    unable to determine the status of rbak
9    a necessary extension package is not installed or not configured properly
10    allocation failed
11    system call failed
12    file open failed
13    file read failed
14    file write failed
15    file close failed
16    unimplemented feature
17    pipe open failed
18    pipe close failed
19    getservbyname failed
20    invalid command parameter
21    socket open failed
22    socket close failed
23    socket read failed
24    socket write failed
25    cannot connect on socket
26    client/server handshaking failed
27    child process killed by signal
28    failed trying to fork a process
29    failed trying to exec a command
30    cannot get passwd information
31    could not set user id for process
32    could not set group id for process
33    failed while trying to send mail
34    failed waiting for child process
35    cannot make required directory
36    failed trying to allocate memory
37    operation requested by an invalid server
38    could not get group information
39    client name mismatch
40    network connection broken
41    network connection timed out
42    network read failed
43    unexpected message received
44    network write failed
45    request attempted on a non reserved port
46    server not allowed access
47    host is unreachable
48    client hostname could not be found
49    client did not start
50    client process aborted
51    timed out waiting for database information
52    timed out waiting for media manager to mount volume
53    backup restore manager failed to read the file list
54    timed out connecting to client
55    permission denied by client during rcmd
56    client’s network is unreachable
57    client connection refused
58    can’t connect to client
59    access to the client was not allowed
60    client cannot read the mount table
63    process was killed by a signal
64    timed out waiting for the client backup to start
65    client timed out waiting for the continue message from the media manager
66    client backup failed to receive the CONTINUE BACKUP message
67    client backup failed to read the file list
68    client timed out waiting for the file list
69    invalid filelist specification
70    an entry in the filelist expanded to too many characters
71    none of the files in the file list exist
72    the client type is incorrect in the configuration database
73    bpstart_notify failed
74    client timed out waiting for bpstart_notify to complete
75    client timed out waiting for bpend_notify to complete
76    client timed out reading file
77    execution of the specified system command returned a nonzero status
78    afs/dfs command failed
79    unsupported image format for the requested database query
80    Media Manager device daemon (ltid) is not active
81    Media Manager volume daemon (vmd) is not active
82    media manager killed by signal
83    media open error
84    media write error
85    media read error
86    media position error
87    media close error
89    problems encountered during setup of shared memory
90    media manager received no data for backup image
91    fatal NB media database error
92    media manager detected image that was not in tar format
93    media manager found wrong tape in drive
94    cannot position to correct image
95    media id is not assigned to this host in the EMM database
96    unable to allocate new media for backup, storage unit has none available
97    requested media id is in use, cannot process request
98    error requesting media (tpreq)
99    NDMP backup failure
100    system error occurred while processing user command
101    failed opening mail pipe
102    failed closing mail pipe
103    error occurred during initialization, check configuration file
104    invalid file pathname
105    file pathname exceeds the maximum length allowed
106    invalid file pathname found, cannot process request
108    Action succeeded but auditing failed
109    invalid date specified
110    Cannot find the NetBackup configuration information
111    No entry was found in the server list
112    no files specified in the file list
114    unimplemented error code
116    VxSS authentication failed
117    VxSS access denied
118    VxSS authorization failed
120    cannot find configuration database record for requested NB database backup
121    no media is defined for the requested NB database backup
122    specified device path does not exist
123    specified disk path is not a directory
124    NB database backup failed, a path was not found or is inaccessible
125    a NetBackup catalog backup is in progress
126    NB database backup header is too large, too many paths specified
127    specified media or path does not contain a valid NB database backup header
128    NB database recovery failed, a process has encountered an exceptional condition
129    Disk storage unit is full
130    system error occurred
131    client is not validated to use the server
132    user is not validated to use the server from this client
133    invalid request
134    unable to process request because the server resources are busy
135    client is not validated to perform the requested operation
136    TIR info was pruned from the image file
140    user id was not superuser
141    file path specified is not absolute
142    file does not exist
143    invalid command protocol
144    invalid command usage
145    daemon is already running
146    cannot get a bound socket
147    required or specified copy was not found
148    daemon fork failed
149    master server request failed
150    termination requested by administrator
151    Backup Exec operation failed
152    required value not set
153    server is not the master server
154    storage unit characteristics mismatched to request
155    disk is full
156    snapshot error encountered
157    suspend requested by administrator
158    failed accessing daemon lock file
159    licensed use has been exceeded
160    authentication failed
161    Evaluation software has expired.
162    incorrect server platform for license
163    media block size changed prior resume
164    unable to mount media because it is in a DOWN, or otherwise not available
165    NB image database contains no image fragments for requested backup id/copy number
166    backups are not allowed to span media
167    cannot find requested volume pool in EMM database
168    cannot overwrite media, data on it is protected
169    media id is either expired or will exceed maximum mounts
170    third party copy backup failure
171    media id must be 6 or less characters
172    cannot read media header, may not be NetBackup media or is corrupted
173    cannot read backup header, media may be corrupted
174    media manager - system error occurred
175    not all requested files were restored
176    cannot perform specified media import operation
177    could not deassign media due to Media Manager error
178    media id is not in NetBackup volume pool
179    density is incorrect for the media id
180    tar was successful
181    tar received an invalid argument
182    tar received an invalid file name
183    tar received an invalid archive
184    tar had an unexpected error
185    tar did not find all the files to be restored
186    tar received no data
189    the server is not allowed to write to the client’s file systems
190    found no images or media matching the selection criteria
191    no images were successfully processed
192    VxSS authentication is required but not available
193    VxSS authentication is requested but not allowed
194    the maximum number of jobs per client is set to 0
195    client backup was not attempted
196    client backup was not attempted because backup window closed
197    the specified schedule does not exist in the specified policy
198    no active policies contain schedules of the requested type for this client
199    operation not allowed during this time period
200    scheduler found no backups due to run
201    handshaking failed with server backup restore manager
202    timed out connecting to server backup restore manager
203    server backup restore manager’s network is unreachable
204    connection refused by server backup restore manager
205    cannot connect to server backup restore manager
206    access to server backup restore manager denied
207    error obtaining date of last backup for client
209    error creating or getting message queue
210    error receiving information on message queue
212    error sending information on message queue
213    no storage units available for use
215    failed reading global config database information
216    failed reading retention database information
217    failed reading storage unit database information
218    failed reading policy database information
219    the required storage unit is unavailable
220    database system error
221    continue
222    done
223    an invalid entry was encountered
224    there was a conflicting specification
225    text exceeded allowed length
226    the entity already exists
227    no entity was found
228    unable to process request
229    events out of sequence - image inconsistency
230    the specified policy does not exist in the configuration database
231    schedule windows overlap
232    a protocol error has occurred
233    premature eof encountered
234    communication interrupted
235    inadequate buffer space
236    the specified client does not exist in an active policy within the configuration database
237    the specified schedule does not exist in an active policy in the configuration database
238    the database contains conflicting or erroneous entries
239    the specified client does not exist in the specified policy
240    no schedules of the correct type exist in this policy
241    the specified schedule is the wrong type for this request
242    operation would cause an illegal duplication
243    the client is not in the configuration
245    the specified policy is not of the correct client type
246    no active policies in the configuration database are of the correct client type
247    the specified policy is not active
248    there are no active policies in the configuration database
249    the file list is incomplete
250    the image was not created with TIR information
251    the tir information is zero length
252    An extended error status has been encountered, check detailed status
253    the catalog image .f file has been archived
254    server name not found in the NetBackup configuration
256    logic error encountered
257    failed to get job data
258    Vault duplication was aborted by administrator request
259    vault configuration file not found
260    failed to send signal
261    vault internal error 261
262    vault internal error 262
263    session id assignment failed
265    session id file is empty or corrupt
266    cannot find robot, vault, or profile in the vault configuration
267    cannot find the local host name
268    the vault session directory is either missing or inaccessible
269    no vault session id was found
270    unable to obtain process id, getpid failed
271    vault XML version mismatch
272    execution of a vault notify script failed
273    invalid job id
274    no profile was specified
275    a session is already running for this vault
276    invalid session id
277    unable to print reports
278    unable to collect pre eject information from the API
279    eject process is complete
280    there are no volumes to eject
281    vault core error
282    cannot connect to nbvault server
283    error(s) occurred during vault report generation
284    error(s) occurred during vault report distribution
285    unable to locate vault directory
286    vault internal error
287    vault eject failed
288    vault eject partially succeeded
289    cannot consolidate reports of sessions from container and slot-based vaults
290    one or more errors detected during eject processing
291    number of media has exceeded capacity of MAP; must perform manual eject using vltopmenu or vlteject
292    eject process failed to start
293    eject process has been aborted
294    vault catalog backup failed
295    eject process could not obtain information about the robot
296    process called but nothing to do
297    all volumes are not available to eject
298    the library is not ready to eject volumes
299    there is no available MAP for ejecting
300    vmchange eject verify not responding
301    vmchange api_eject command failed
302    error encountered trying backup of catalog (multiple tape catalog backup)
303    error encountered executing Media Manager command
304    specified profile not found
305    multiple profiles exist
306    vault duplication partially succeeded
307    eject process has already been run for the requested Vault session
308    no images duplicated
309    report requested without eject being run
310    Updating of Media Manager database failed
311    Iron Mountain Report is already created for this session
312    invalid container database entry
313    container does not exist in container database
314    container database truncate operation failed
315    failed appending to container database
316    container_id is not unique in container database
317    container database close operation failed
318    container database lock operation failed
319    container database open operation failed
320    the specified container is not empty
321    container cannot hold any media from the specified robot
322    cannot find vault in vault configuration file
323    cannot find robot in vault configuration file
324    invalid data found in retention map file for duplication
325    unable to find policy/schedule for image using retention mapping
326    specified file contains no valid entry
327    no media ejected for the specified vault session
328    invalid container id
329    invalid recall status
330    invalid database host
331    invalid container description
332    error getting information from EMM database
333    error getting information from media manager command line
334    unable to receive response from robot; robot not ready
335    failure occurred while suspending media for eject
336    failure occurred while updating session information
337    failure occurred while updating the eject.mstr file
338    vault eject timed out
339    vault configuration file format error
340    vault configuration tag not found
341    vault configuration serialization failed
342    cannot modify - stale view
343    robot already exists
344    vault already exists
345    profile already exists
346    duplicate MAP
347    vault configuration cache not initialized
348    specified report does not exist
349    incorrect catalog backup policy
350    incorrect vault catalog backup schedule
351    all configured vault steps failed
400    Server Group Type is Invalid
401    Server Group Already Exists
402    Server Group Already Exists with a different type
403    Server Group Active State is not valid
404    Server Group does not exist
405    Member’s server type not compatible with Server Group
406    The computer specified is not a member of the server group specified
407    Member’s NetBackup version not compatible with Server Group
408    Server Group is in use
409    Member already exists in server group
501    You are not authorized to use this application
502    No authorization entry exists in the auth.conf file for user name
503    Invalid username.
504    Incorrect password
505    Can not connect to the NB-Java authentication service on host on the configured port - (port_number).
506    connect to the NB-Java user service on host on port port_number.
507    Socket connection to the NB-Java user service has been broken
508    Can not write file.
509    Can not execute program
510    File already exists: file_name
511    NB-Java application server interface error
512    Internal error - a bad status packet was returned by NB-Java application server that did not contain an exit status code
513    bpjava-msvc: the client is not compatible with this server version (server_version).
514    NB-Java: bpjava-msvc is not compatible with this application version (application_version).
516    Could not recognize or initialize the requested locale - (locale_NB-Java_was_started_in).
517    Can not connect to the NB-Java user service via VNETD on host on port configured_port_number. If successfully logged in beforehand, retry your last operation. Check the log file for more details.
518    No ports available in range (port_number) through (port_number) per the NBJAVA_CLIENT_PORT_WINDOW configuration option.
519    Invalid NBJAVA_CLIENT_PORT_WINDOW configuration option value: (option_value).
520    Invalid value for NB-Java configuration option (option_name):(option_value).
521    NB-Java Configuration file (file_name) does not exist.
522    NB-Java Configuration file (file_name) is not readable due to the following error: (message).
523    NB-Java application server protocol error.
525    Cannot connect to the NB-Java authentication service via VNETD on (host) on port (vnetd_configured_port_number). Check the log file for more details.
526    bpjava authentication service connection failed
527    bpjava user service connection if connection to pbx on port 1556 fails
600    an exception condition occurred
601    unable to open listen socket
602    cannot set non blocking mode on the listen socket
603    cannot register handler for accepting new connections
604    no target storage unit specified for the new job
605    received error notification for the job
606    no robot on which the media can be read
607    no images were found to synthesize
608    storage unit query failed
609    reader failed
610    end point terminated with an error
611    no connection to reader
612    cannot send extents to bpsynth
613    cannot connect to read media server
614    cannot start reader on the media server
615    internal error 615. This error code is no longer used
616    internal error 616. This error code is no longer used
617    no drives available to start the reader process
618    internal error 618. This error code is no longer used
619    internal error 619. This error code is no longer used
620    internal error 620. This error code is no longer used
621    unable to connect to bpcoord
622    connection to the peer process does not exist
623    execution of a command in a forked process failed
624    unable to send a start command to a reader or a writer process on media server
625    data marshalling error
626    data un-marshalling error
627    unexpected message received from bpsynth
628    insufficient data received
629    no message was received from bptm
630    unexpected message was received from bptm
631    received an error from bptm request to suspend media
632    received an error from bptm request to un-suspend media
633    unable to listen and register service via vnetd
634    no drives available to start the writer process
635    unable to register handle with the reactor
636    read from input socket failed
637    write on output socket failed
638    invalid arguments specified
639    specified policy does not exist
640    specified schedule was not found
641    invalid media type specified in the storage unit
642    duplicate backup images were found
643    unexpected message received from bpcoord
644    extent directive contained an unknown media id. This error code is no longer used
645    unable to start the writer on the media server
646    unable to get the address of the local listen socket
647    validation of synthetic image failed
648    unable to send extent message to BPXM
649    unexpected message received from BPXM
650    unable to send extent message to bpcoord
651    unable to issue the database query for policy
652    unable to issue the database query for policy information
653    unable to send a message to bpccord. This error code is no longer used
654    internal error 654. This error code is no longer used
655    no target storage unit was specified via command line
656    unable to send start synth message to bpcoord. This error code is no longer used.
657    unable to accept connection from the reader
658    unable to accept connection from the writer
659    unable to send a message to the writer child process
660    a synthetic backup request for media resources failed
661    unable to send exit message to the BPXM reader
662    unknown image referenced in the synth context message from BPXM
663    image does not have a fragment map
664    zero extents in the synthetic image, cannot proceed
665    termination requested by bpcoord. This error code is no longer used
667    unable to open pipe between bpsynth and bpcoord. This error code is no longer used
668    pipe fgets call from bpcoord failed. This error code is no longer used
669    bpcoord startup validation failure. This error code is no longer used
670    send buffer is full
671    query for list of component images failed
800    resource request failed
801    JM internal error
802    JM internal protocol error
803    JM terminating
805    Invalid jobid
806    this mpx group is unjoinable
807    not externalized
811    failed to communicate with resource requester
812    failed to communicate with resource broker
813    duplicate reference string specified
818    retention level mismatch
819    unable to communicate with JM proxy
823    no BRMComm to join
830    drive(s) unavailable or down
831    image has been validated
832    failed to write discover data to a file
833    error parsing discovered XML data
900    retry nbrb request later
901    RB internal error
902    RB invalid argument
903    RB communication error
904    RB max reallocation tries exceeded
905    RB media server mismatch
906    RB operator denied mount request
907    RB user cancelled resource request
908    RB was reset
912    RB disk volume mount failed
913   
914    RB media reservation not found
915    RB disk volume mount must retry
916    Resource request timed out
917    RB multiplexing group not found
918    RB does not have a multiplexing group that uses this media id or drive name
1000    Client is offline
1001    discovery document error
1002    Discovery detected a failed client
1057    A data corruption has been detected
1058    A data inconsistency has been detected and corrected automatically.
1401    Invalid arguments received
1402    Hold id or Hold name argument is invalid
1403    Backup id argument is invalid
1404    Image copy number argument is invalid
1405    No images are found
1406    Invalid hold type
1407    Invalid hold state
1408    Database error
1409    Unable to connect to database
1410    No data found
1411    Catalog error
1412    Hold record is being updated
1413    Requested hold is not found
1414    Duplicate hold found
1415    Duplicate image found
1416    Partially failed due to duplicate image
1417    Partially failed due to unhold image
1418    Requested image is not found
1419    Partially failed due to invalid image copy
1420    Cannot expire on hold image copy.
1421    Active holds cannot be changed
1422    Cannot deassign media on hold
1423    Unable to retrieve hold status of the image copies
1424    Requested Legal hold is not found
1425    Requested Local hold is not found
1426    Retired holds cannot be changed
1450    CORBA exception received from Indexing service.
1451    Invalid command line option
1452    Backup ID: does not exists
1453    Invalid Operation ID
1454    Invalid Priority
1455    Missing value for option <-option>
1456    Required option is not found
1457    Too many arguments provided
1458    Unable to connect to Indexing Service
1459    Incorrect file path:
1460    No data found in the file
1461    invalid date
1462    End date is before start date
1463    Hours must be greater than or equal to 1
1464    For -force option, operation ID has to be 1
1465    nbindexutil -list option is missing the -indexserver option
1466    Invalid combination of options
1467    Number of files is 0 and hence not submitting the request for backup image
1468    There are no tar copies for snapshot image
1500    Storage unit does not exist or can't be used where specified
1501    Source operation cannot be used where specified
1502    Retention type cannot be used where specified
1503    Volume pool does not exist or can't be used where specified
1504    Server group does not exist or can't be used where specified
1505    alternate read server does not exist or can't be used where specified
1506    data classification does not exist
1508    Storage lifecycle policy exceeds maximum copies
1509    Storage lifecycle policy exceeds maximum backup operations
1510    storage lifecycle policy cannot have more than one snapshot operation
1511    storage lifecycle policy must have at least one fixed retention or snapshot rotation operation
1512    storage lifecycle policy must have at least one backup, import, or snapshot operation
1513    invalid priority
1514    invalid operation type
1515    multiplexing value is not valid or cannot be used where specified
1516    all storage units or groups must be on the same media server
1517    Invalid retention level
1518    backup image is not supported by storage lifecycle policy
1519    Images are in process
1521    Database not available
1522    Error executing database query
1523    Invalid fragment
1524    Duplicate image record
1525    Invalid lsu
1526    Storage lifecycle policy exceeds maximum import operations
1527    storage lifecycle policy can have only one of backup, import, and snapshot operations
1528    The source copy for an Auto Image Replication is not capable of replication
1529    The source copy for Auto Image Replication must specify a storage unit
1530    Only one Auto Image Replication allowed per copy
1531    An import storage lifecycle policy requires one copy with remote retention type
1532    Import failed because the imported image specifies an SLP name which does not exist
1533    Import failed because the imported image data class is different than the SLP data class
1534    Import failed because the imported image specifies an SLP name with no import operation
1535    Import failed because the imported image backup id conflicts with an existing image
1536    The storage unit or storage unit group cannot be deleted because an SLP references it
1537    Backup policy and storage lifecycle policy have conflicting configurations
1538    Data classification in the SLP conflicts with backup policy
1539    Backup policy generates snapshots but storage lifecycle policy does not handle them
1540    SLP expects snapshots but backup policy does not create them with SLP management enabled
1541    Snapshot creation failed
1542    An existing snapshot is no longer valid and cannot be mounted for subsequent operations
1543    Policy type is not compatible with SLP operations
1545    Schedule type is not compatible with SLP operations
1546    Capacity managed retention type is not compatible with SLP operations
1547    Expire after copy retention requires a dependent copy
1548    Retention type is not compatible with snapshot operation
1549    TIR information selection is not compatible with SLP operations
1552    The source and target storage units are not valid replication partners
1553    Checkpoints are not allowed with SLP operations
1554    Storage unit snapshot capability is not compatible with operation characteristics
1556    The SLP deletion failed because a backup policy refers to it.
1557    Must specify mirror retention when target storage unit is mirror capable.
1558    Mirror retention is not allowed when target storage unit is not mirror capable.
1559    SLP referenced in policy or schedule not found
1560    Fixed or rotation retention required without a replication operation
1561    Policy using NDMP conflicts with multiple Backup From Snapshot operations in storage lifecycle policy
1562    Backup schedule generates snapshots but storage lifecycle policy does not handle them
1563    SLP expects snapshots but backup schedule does not create them
1565    Policy snapshot method is not compatible with SLP snapshot operations
1566    Storage unit required for snapshot operation when no other operation present
1567    Only one NDMP backup of a snapshot per backup ID is allowed
1568    Only one IndexFromSnapshot operation is allowed per storage lifecycle policy
1569    Snapshot storage unit is not configured for primary snapshots. It cannot be used in snapshot operation.
1570    Policy type does not support Index from Snapshot
1571    Data mover type specified in policy does not support Index from Snapshot
1572    Storage unit must be specified for this operation
1573    Backup image cannot be expired because its SLP processing is not yet complete
1800    Invalid client list
2000    Unable to allocate new media for backup, storage unit has none available.
2001    No drives are available for this job
2002    Invalid STU identifier type
2003    Drive is not allocated
2004    Drive is already allocated
2005    MDS has received an invalid message from a media server.
2006    NDMP credentials are not defined in EMM
2007    Storage unit is not compatible with requesting job
2008    All compatible drive paths are down
2009    All compatible drive paths are down but media is available
2010    Job type is invalid
2011    The media server reported a system error.
2012    Media has conflicts in EMM
2013    Error record insert failed
2014    Media is not assigned
2015    Media is expired
2016    Media is assigned to another server
2017    Media needs to be unmounted from a drive
2018    Number of cleanings is invalid
2019    Media is in a drive that is not configured on local system
2020    Robotic library is down on server
2021    Allocation record insert failed
2022    Allocation status record insert failed
2023    Allocation identifier is not known to EMM
2024    Allocation request update failed
2025    Allocation request delete failed
2026    Allocation status request delete failed
2027    Media server is not active
2028    Media is reserved
2029    EMM database is inconsistent
2030    Insufficient disk space or high water mark would be exceeded
2031    Media is not defined in EMM
2032    Media is in use according to EMM
2033    Media has been misplaced
2034    Retry the allocation request later
2035    Request needs to pend
2036    Drive is in a robotic library that is up
2037    Drive is not ready
2038    Media loaded in drive is not write-enabled
2039    SCSI reservation conflict detected
2040    Maximum job count has been reached for the storage unit
2041    Storage unit is down
2042    Density mismatch detected
2043    Requested slot is empty
2044    Media is assigned to another application
2045    Storage unit is disabled since max job count is less than 1
2046    Media is unmountable
2047    Media is write protected
2048    Media is in use by the ACS robotic library
2049    Media not found in the ACS robotic library
2050    ACS media has an unreadable external label
2051    ACS media is not in the drive's domain
2052    An ACS Library Storage Module (LSM) is offline
2053    Media is in an inaccessible drive
2054    Media is in a drive that is currently in a DOWN state
2055    ACS physical drive is not available
2056    The file name used for the mount request already exists
2057    The scan host of the drive is not active
2058    LTID needs to be restarted on media servers before the device can be used
2059    The robotic library is not available
2060    Media needs to be rewound or unmounted from a drive
2061    The host is not an active node of a cluster
2062    Throttled job count has been reached for the storage unit
2063    Server is not licensed for the Remote Client Option
2064    Job history indicates that no media is available
2065    Job history indicates that no drive is available
2066    Disk pool not found
2067    Disk volume not found
2068    Disk volume mount point not found
2069    Disk volume mount point record insert failed
2070    The specified mount path will not fit in the allocated space
2071    Unable to find any storage servers for the request
2072    Invalid operation on static mount point
2073    Disk pool is down
2074    Disk volume is down
2075    Fibre Transport resources are not available
2076    DSM returned an unexpected error
2077    DSM has already mounted the volume
2078    The maximum number of mounts for the disk volume have been exceeded
2079    DSM has detected that an invalid file system is mounted on the volume
2080    Disk volume has no max writers count
2081    Disk volume has no max readers count
2082    The drive needs to be marked as available
2083    The media affinity group is not defined in EMM
2084    Media affinity group record insert failed
2085    Disk volume is not available
2086    Disk volume cannot be used for more than one copy in the same job
2087    Media allocation would exceed maximum partially full media limit
2088    Cleaning media is not available
2089    FT client is not running
2090    FT client has no devices configured
2091    FT client devices are offline
2092    FT server devices for client are offline
2093    No FT servers for this client are running
2094    STU cannot run Lifecycle backups
2095    STU cannot run VMWare backup
2096    NDMP operation does not support multiple inline copies
2097    Storage Unit group does not exist in EMM configuration
2098    Media pool is not eligible for this job
2099    Required drive or drive path is not configured
2100    Maximum number of mounts has been exceeded for tape media
2101    Media server not found in EMM database
2102    Storage unit does not support spanning
2103    Media server mismatch
2104    Storage units are not available
2105    Storage unit requested for replication job is not replication capable
2106    Disk storage server is down
2107    Requested media server does not have credentials for storage server
2504    Direct expiration of a mirror copy is not allowed
2800    Standard policy restore error
2801    Oracle policy restore error
2802    Informix-On-BAR policy restore error
2803    Sybase policy restore error
2804    MS-SharePoint policy restore error
2805    MS-Windows policy restore error
2806    NetWare policy restore error
2807    SQL-BackTrack policy restore error
2808    Windows File System policy restore error
2809    MS-SQL-Server policy restore error
2810    MS-Exchange policy restore error
2811    SAP policy restore error
2812    DB2 policy restore error
2813    NDMP policy restore error
2814    FlashBackup policy restore error
2815    AFS policy restore error
2816    DataStore policy restore error
2817    FlashBackup Windows policy restore error
2818    NBU Catalog policy restore error
2819    Enterprise Vault policy restore error
2820    NBU VMware policy restore error
2826    Master server failed to connect to backup restore manager on media server for restore
2828    Restore failed because the MS-SQL-Server services are down
2829    Restore failed due to MS-SQL-Server database in use
2830    Restore failed due to an incorrect path in the MS-SQL-Server MOVE script
2831    Restore error
2832    Restore failed due to rename file format error
2833    Restore failed due to partition restore error
2834    Restore failed due to failure to read change block bitmap
2835    Restore failed due to corrupt image
2836    Restore failed because the bitmap size read from the image header differs from the expected size
2837    Restore failed due to invalid metadata
2838    Restore failed because no raw partitions were found
2839    Restore failed due to invalid raw partition ID
2840    Restore failed due to out of sequence raw partitions
2841    Restore failed due to failure to read the header from the backup image
2842    Restore failed due to failure to read the VMware bitmap
2843    Restore failed due to failure to start VxMS
2844    Restore failed due to failure to read the FIID file
2845    Restore failed due to failure to retrieve the bitmap
2846    Restore failed due to failure to retrieve the fsmap
2847    Restore failed due to failure to start the bptm writer
2848    Restore failed due to failure to create the virtual machine
2849    Restore failed due to failure to delete the virtual machine snapshot
2850    Restore error
4200    Operation failed: Unable to acquire snapshot lock
4201    Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries
4202    Invalid or incompatible storage unit configured
4203    Invalid or unsupported backup selection filelist
4204    Incompatible client found
4205    Incorrect or no credentials found
4206    Authentication error occurred. NetBackup Client Service is running as Local System, this is likely incorrect.
4207    Could not fetch snapshot metadata or state files
4208    Could not send snapshot metadata or statefiles
4209    Snapshot metadata or statefiles cannot be created
4210    Incorrect or no content found in snapshot metadata
4211    Snapshot not accessible or invalid snapshot
4212    Recreation of snapshot failed
4213    Snapshot import failed
4214    Snapshot mount failed
4215    Snapshot deletion failed
4216    Snapshot cleanup failed
4217    Snapshot restore failed
4218    Snapshot deport failed
4219    Command operation failed: Third-party command or API execution failed
4220    Command operation failed: System command or API execution failed
4221    Found an invalid or unsupported configuration
4222    Operation failed: Unable to acquire policy lock to take snapshot
4223    Operation not completed
4224    STS Internal Error
4225    Unauthorized operation attempted by client or media on storage server
4226    Communication failure occurred with storage server
4227    STS Plug-in error occurred
4228    Storage server or plug-in version mismatch
4229    Insufficient resources or capabilities found by storage server
4230    Invalid storage topology or storage server configuration error
4231    STS Unexpected Error
4232    Invalid Discovery Query URI
4233    BIOS UUID client reference not allowed for vCloud
4234    VMware server login failure
4235    vCloud keyword used when vCloud not enabled
4236    vCloud policy includes multiple organizations
4237    Client does not meet policy requirements
4238    No server credentials configured for policy
4239    Unable to find the virtual machine
4240    Operation not supported
4243    Unable to connect to the VirtualCenter server
4245    Invalid pathname for backup selection
4246    The requested operation was partially successful.
4247    Index from snapshot for Replication Director NDMP Policy is not supported on AIX media server
4248    Index from snapshot operation failed with an internal error
4249    Index from snapshot operation failed, catalog already exists
4250    Index from snapshot operation failed, unable to find child image or file information
4251    Index from snapshot operation failed. Failed to write into index database
4252    Index from snapshot operation failed. Entry does not belong to any of the backup selection entries.
4253    Index from snapshot operation failed. SLP version mismatch for current and previous backup image.
4254    Invalid or no path found to create index database
4255    Index from snapshot using SnapDiff is disabled by the user
4256    Index from snapshot is not supported for the file system associated with backup selection
4257    Index from snapshot is not supported for the storage server
4258    Transient error encountered while taking Hyper-V VM snapshot
4259    Failed to find VirtualCenter host name in VMware Lookup Service
4260    Encountered SSO login failure
4261    Encountered VMware Internal Server Error
4262    Encountered VMware vCloud Suite API failure
4263    Encountered VMware SOAP API failure
4264    Encountered unexpected error while processing TagView XML
4265    Encountered a VMware Virtual Machine Server that does not support Tags
4266    Encountered a VMware Virtual Machine Server that does not offer Tag APIs
4267    Failed to initialize Java Runtime Environment
4268    Failed to retrieve resource pool information
4269    Found multiple virtual machines with same identity
4270    A snapshot of the virtual machine exists and the policy option specifies aborting the backup
4271    Maximum virtual machine snapshots exceeded
4272    Maximum delta files exceeded
4273    Unable to lock the backup or restore host for virtual machine snapshot operations
4274    Failed to remove virtual machine snapshot
4275    Unable to consolidate Virtual Machine Disks
4276    Unable to retrieve Virtual Machine Disk information
4277    Virtual machine path contains unsupported characters
4278    Unable to retrieve virtual machine information
4279    Unable to retrieve virtual machine vCloud information
4280    Virtual machine contains independent and Raw Device Mapping disks only
4281    Virtual machine contains independent disks only
4282    Virtual machine contains Raw Device Mapping disks only
4283    Error detected while processing disk identifiers
4287    A NetBackup snapshot of the virtual machine exists and the policy option specifies aborting the backup
4290    Failed to create virtual machine snapshot. Virtual machine is busy performing another operation
5400    Backup error - None of the request objects were found in the database
5401    Backup error - FRA (Fast Recovery Area) was requested, but it was not found in the database
5402    OS Authentication error - Could not connect to the database. Please check the OS credentials
5403    Oracle Authentication error - Could not connect to the database. Please check the Oracle credentials
5404    ASM validation error - PROXY backup is not supported for ASM
5405    Recovery Catalog Authentication error - Could not connect to the Recovery Catalog. Please check the Recovery Catalog credentials
5406    Archive log only backup requested, but database is not in ARCHIVELOG Mode
5407    Database is in the wrong state (must be OPEN) for the requested action
5408    OS Authentication error - Could not find credentials. If this instance is part of an instance group, make sure that the group has the credentials that match this OS Type
5409    Cloning is NOT supported for this client platform
5410    Oracle Intelligent Policy is NOT supported for this client platform
5411    Cannot do a hot backup of a database in NOARCHIVELOG mode
5412    Database is in the wrong state (must be OPEN or MOUNTED) for an Archive Log Backup
5413    Database is in the wrong state (must be OPEN or MOUNTED) for an FRA backup
5414    The request operation is not supported with this client version
5415    Cannot shut down read-only standby database
5416    Oracle cannot resolve the TNS connection identifier
5417    An error has occurred checking if the NFS server is an appliance
5418    The NFS server is not an appliance
5419    The database backup share directory is not available on the appliance.
5420    Whole Database - Datafile Copy Share selection is not supported for this client platform.
5421    None of the requested pluggable databases were found.
5422    Partial success - one or more of the requested pluggable databases were not found.
5423    None of the requested tablespaces were found in the requested pluggable databases
5424    Partial success - one or more of the requested pluggable databases did not contain any of the requested tablespaces
5425    None of the requested data files were found in the requested pluggable databases
5426    Partial success - one or more of the requested pluggable databases did not contain any of the requested data files
5427    Partial success - more than one error was encountered, please refer to the Detailed Status tab in the Job Details and review logs for more information
5428    No database backup shares were found.
5429    No files that are related to the instance or database were found in the database backup share
5430    Database must be in ARCHIVELOG mode to perform a cold backup of a pluggable database
5500    The NetBackup core web service service internal error
5501    Supplied URI is too short
5502    Supplied URI is not supported
5503    NetBackup core web service is terminating
5504    Query string in URI is bad
5505    Client name is required
5506    Failed to communicate with core web service proxy
5507    Unknown jobid
5508    Error in parsing XML document
5761    Failed to initialize Windows Socket library
5762    Peer is not a NetBackup Master or Media Server
5763    Encountered error during socket communication
5764    Command specified for execution is invalid or not allowed
5765    Failed to execute specified command (CreateProcess or exec)
5766    Failed to execute specified command (fork)
5767    Failed to get exit code of child process
5768    Failed to read complete output of executed command
5769    Failed to reap exit code of child process
5770    Failed to get cluster configuration
5771    Failed to write output received from remote command
5772    Failed to read unified logging configuration file
5773    Failed to get virtual name of Master Server
5774    Specified logs are not valid
5775    Invalid option specified
5776    Failed to spawn new process
5777    Failed to create the staging directory on Master Server
5778    Failed to read Logging Assistant database
5779    Failed to lock Logging Assistant database
5780    Failed to set non-inherit flag on database file handle
5781    Failed to prepare to save Logging Assistant database
5782    Failed to start to write Logging Assistant database
5783    Failed to save Logging Assistant database
5784    Failed to access or write the readme or progress file
5786    Logging Assistant record does not exist
5787    Logging Assistant record already exists
5788    Debug logging has not been set up for Logging Assistant record
5789    Failed to interpret bpdbjobs output for job detail
5790    Failed to fetch PureDisk configuration setting from Windows registry
5794    Failed to calculate debug logs size for preview
5796    Logging Assistant agent encountered failure writing on socket to Master Server
5798    Failed to list disk volumes on Master Server using bpmount
5799    Failed to get disk space information of volumes or mount points
5800    Failed to execute bpdbjobs to fetch job details
5801    Failed to fetch job details. Check if job exists.
5803    Failed to modify PureDisk configuration file
5804    Failed to modify Java GUI configuration file (Debug.properties)
5805    Remote host NetBackup version not supported by the Logging Assistant
5806    Unexpected contents of PureDisk configuration file (pdregistry.cfg)
5807    Failed to copy nbcplogs/nbsu output file from remote host
5808    Failed to load PBX configuration to change log level
5809    Invalid PBX Debug Log Level specified
5811    Temporary directory to use for logs collection does not exist
5812    nbcplogs exited with error
5813    nbcplogs did not collect any logs
5814    nbsu exited with error
5815    No activity for the Logging Assistant record is in progress
5816    Collect debug logs operation canceled
5817    Collect nbsu operation canceled
5819    Cancel operation requested
5820    Not a valid Logging Assistant temporary directory for clean-up
5821    Failed to get policy details
5902    Fingerprint of the certificate could not be generated
5903    CA certificate could not be verified
5904    Internal error.
5905    The host ID is not valid
5906    The token is not valid
5907    Unknown resource requested
5908    Unknown error occurred
5909    Token does not exist for this token value
5910    Host name is not specifie
5913    A token with this name already exists
5914    The security service is not available
5915    Request timed out
5916    Token name is not specified
5917    The reissue token cannot have the usage count greater than one
5918    The maximum usage count for the token should be provided within the valid range, which is from 1 to 99999
5919    Validity period specified for this token is not valid. The maximum validity period that you can specify is 999 days
5920    The specified token is associated with a different host name
5921    The specified token is associated with a different host ID
5922    The reissue token cannot be associated with the host name
5925    The required data is missing
5926    Certificate signing request is not valid
5927    The specified file could not be opened.
5929    The certificate is not in the Active state, so it cannot be renewed
5930    The request could not be authorized
5931    The host ID is empty
5932    Token usage count is not set
5933    The maximum token usage limit has been reached
5934    The token has expired
5936    The specified token name is not in a valid forma
5938    The revocation reason code is not valid
5939    This revocation reason code is not supported by the server
5940    The specified token is not a reissue token
5941    The host ID is not associated with any host
5942    Certificate could not be read from the local certificate store
5943    Lock cannot be acquired on the file for writing
5944    The host alias list has multiple host names
5945    Host alias is not specified
5946    Token is mandatory
5947    The host is not registered with the server
5948    Certificate could not be written to the local certificate store
5949    Certificate does not exis
5950    Certificate already exists
5953    The certificate deployment level is not valid
5954    The host name could not be resolved to the requesting host's IP address
5955    The host name is not known to the master server
5956    The existing certificate deployment level on the master server does not allow this operation
5957    The master server is unable to connect to the CA.
5958    The master server is unable to access the CA certificate
5959    The NetBackup AT credentials of the web service user are not valid.
5960    NetBackup AT configuration on the master server could not be initialized
5962    The host name does not match the existing name in the certificate
5963    Entity does not exist
5964    Data conversion error
5965    The host ID associated with this reissue token is assigned to another host. You need to revoke the certificate for the host ID before you continue
5966    The host has an active certificate. You need to revoke the certificate before you can disassociate the host from its host ID
5967    The file already exists
5968    The host information could not be retrieved while creating the certificate signing request
5969    Response from the NetBackup Web Management Console service could not be parsed
5970    The server time could not be fetched
5971    The token contains characters that are not supported
6000    The provided path is not whitelisted
6530    Unable to start SharePoint web service on server
6531    Validation of operating system user/password failed for client
7610    Failed to parse the specified object
8000    User does not have permission(s) to perform the requested operation
8500    Connection with the web service was not established
8504    The web service certificate is issued by an unknown Certificate Authority
8505    The certificate is not yet valid
8506    The certificate has expired
8507    The certificate could not be verified
8508    List of trusted Certificate Authorities could not be fetched
8509    The specified server name was not found in the web service certificate
8510    Web server certificate verification failed
8700    The host database web service is unavailable due to an internal error
8701    The host does not exist
8702    The web service cannot create the host because the host exists in the host database
8703    The web service cannot create the host because the alias name exists in the host database
8704    A conflict occurred while updating the host database. Kindly retry the operation
8706    The required field is missing from the input request
8707    The web service cannot update the host ID.
8708    Constraint violations are detected for the given attributes in the input request
8709    The destination file or directory already exists
8710    The disk space is insufficient on the host to upload
8711    The folder that is required to upload the telemetry data does not exist
8712    Failed to upload the file
8713    Failed to upload the file. The input file cannot be empty
8800    Communication with EMM failed-option>

Source : veritas.com
↧
Search

Netbackup Key Management Service (KMS) Status Codes

July 1, 2017, 11:00 am
$
0
0
The NetBackup Key Management Service (KMS) feature is included as part of the NetBackup Enterprise Server and NetBackup Server software. An additional license is not required to use this functionality. KMS runs on NetBackup and is a master server-based symmetric Key Management Service. The KMS manages symmetric cryptography keys for the tape drives that conform to the T10 standard. KMS has been designed to use volume pool-based tape encryption. KMS is used with the tape hardware that has a built-in hardware encryption capability. An example of a tape drive that has built-in encryption is the IBM ULTRIUM TD4 cartridge drive. 

KMS is also used with disk volumes associated with NetBackup AdvancedDisk storage solutions. KMS runs with Cloud storage providers. KMS runs on Windows and UNIX. KMS generates keys from your passcodes or it auto-generates keys. The KMS operations are done through the KMS command line interface (CLI) or the Cloud Storage Server Configuration Wizard (when KMS is used with Cloud storage providers). The CLI options are available for use with both nbms and nbmkmsutil.

Here is the list of KMS status code :

1    Failed to initialize the ORB
2    Failed to create a new Key Group
3    Failed to create a new Key
4    Failed to modify Key Group details
5    Failed to modify Key details
6    Failed to delete the Key Group
7    Failed to fetch Key Group details
8    Failed to fetch Key(s) details
9    Failed to fetch Key Store statistics
10    Failed to modify Host Master Key
11    Failed to modify Key Protection Key
12    Failed to register OBVs with ORB
13    Request timed out. NBSL service might be down
14    Failed to establish a session with NBSL
15    Failed to get Modifiable Facet Instance. KMS service might be down
16    Failed to narrow to Modifiable Facet Instance
17    Failed to get Queryable Facet Instance. KMS service might be down
18    Failed to narrow to Queryable Facet Instance
19    Failed to get Control Facet Instance. KMS service might be down.
20    Failed to narrow to Control Facet Instance
21    Failed to get Exim Facet Instance. KMS service might be down.
22    Failed to narrow to Exim Facet Instance
23    New Key Group creation is successful
24    New Key creation is successful
25    Key Group details are updated successfully
26    Key details are updated successfully
27    Key Group deletion is successful
28    No Key Groups were found
29    No Keys were found
30    Host Master Key update is successful
31    Key Protection Key update is successful
32    Missing or duplicate option: %s
33    All the options are mutually exclusive
34    Options %s %s are mutually exclusive
35    Invalid option or value: %s
36    Unknown option used
37    Invalid value for %s: %s
38    Invalid value for %s: %s
39    Invalid operation
40    Failed to get Key Group details
41    Failed to get Host Master Key ID
42    Failed to get Key Protection Key ID
44    Failed to get KMS service manager instance
45    Failed to quiesce Keystore
46    Failed to unquiesce Keystore
47    Failed to get keystore quiesce status
48    Key Store quiesce is successful
49    Key Store unquiesce is successful
50    Failed recover Key with known Tag
51    Key recovery is successful
52    Failed to delete the Key
53    Key deletion is successful
54    Authentication failed check NBAC credentials
55    Access denied on this operation check NBAC permissions
56    Authorization failed check NBAC credentials
57    Nothing to modify
58    Keystore successfully exported
59    Failed to export keystore
60    Successfully imported keystore file
61    Failed to import keystore file into the KMS Database
62    Failed to read file. Please check the format and try again
63    You must provide the Salt value to recover the key
1287    Invalid characters found in name: %s\n -- Valid character set: A-Z a-z
    0-9, _, -, :, . and space -- Name should start with A-Z or a-z or 0-9



Source : veritas.com
↧

Red Hat Hyperconverged Infrastructure 1.0 Formally Announced

July 4, 2017, 12:21 am
$
0
0
Red Hat, Inc. (NYSE: RHT) had announced the Red Hat Hyperconverged Infrastructure, the industry’s first production-ready fully open source hyperconverged infrastructure (HCI) solution. The Red Hat'way to implement the HCI is by combining innovative virtualization and storage technologies with a stable, proven operating platform. Red Hat Hyperconverged Infrastructure is designed to help enterprises to bring datacenter capabilities into locations with limited space, such as branch offices and other remote facilities.

Red Hat Hyperconverged Infrastructure uses Red Hat’s widely deployed virtualization platform, as well as software-defined storage, to more efficiently manage an integrated compute and storage infrastructure across a range of server hardware or networks. To accomplish this, Red Hat Hyperconverged Infrastructure was built with a suite of components, integrated to provide a unified experience from installation to management. These include:
 
  • Red Hat Virtualization – The company’s award-winning Kernel-based Virtual Machine (KVM)-powered enterprise virtualization platform.
  • Red Hat Gluster Storage – Highly scalable software-defined storage that can be converged on the same hardware as Red Hat Virtualization hosts, removing the need for additional compute infrastructures and simplifying deployment.
  • Red Hat Enterprise Linux – The world’s leading enterprise Linux platform offers a stable and reliable foundation.
  • Ansible by Red Hat – Deployment and management built on the leading simple, powerful, and agentless open source IT automation framework, providing automated installation and configuration from a central point.

The benefits that consolidation with a hyperconverged infrastructure provides:
  •     Eliminate storage as a discrete tier
  •     Easily virtualize business applications, maximizing resource utilization
  •     Single budget for compute and storage
  •     Single team managing infrastructure
  •     Simplified planning ans procurement
  •     Streamlined deployment and management
  •     Single support stack for compute and storage

Removing the storage tier by consolidating compute and storage onto a single server platform/tier offers streamlined deployment and management (enabled by Ansible by Red Hat and Red Hat CloudForms), a single support stack (one vendor to call now instead of two), and simplified planning and procurement (reducing the number of vendors to source from).

Source : http://redhatstorage.redhat.com
↧
↧

Red Hat Launched the Latest Version of Cloud Suite

July 4, 2017, 2:59 am
$
0
0
Red Hat has launched the lates version of Red Hat Cloud Suites. By this new suite, Red Hat give the business ovwner, developers and IT operartions the insights of their business needs quickly and cost-effectively while maintaining governance and security. Red Hat Cloud Suite also deliver a common interface and technology stack for development, operations, IT administrators, and lines of business.

Developers get the tools they need to rapidly deploy apps. Operators can monitor and govern services and apps simultaneously—across a hybrid infrastructure—from development through production. And CIOs can better align with business requirements.



Red Hat Cloud Suite includes:
  •     Red Hat OpenStack Platform
  •     Red Hat OpenShift
  •     Red Hat Virtualization
  •     Red Hat CloudForms
  •     Red Hat Satellite
  •     Red Hat Ceph Storage
  •     Red Hat Insights

Deploy apps faster
Red Hat Cloud Suite includes Red Hat OpenShift, a container-based app-development platform. It gives developers quick access to compute power so they can continuously integrate and deploy apps using a broad mix of languages and frameworks. OpenShift also lets developers deploy apps in containers or in VMs.

Choose your private-cloud infrastructure
At its infrastructure foundation, Red Hat Cloud Suite lets you build a private cloud on either Red Hat OpenStack Platform with public cloud-like scalability or Red Hat Enterprise Virtualization based on high-performance virtualization. Both choices provide secure and scalable foundations for hosting the development platform, Red Hat OpenShift Container Platform. Red Hat OpenStack Platform gives you massive scalability and now includes Red Hat Ceph Storage.

Manage across multiple cloud platforms
You can seamlessly administer the combination of infrastructure and app development in Red Hat Cloud Suite with a unified management framework: Red Hat CloudForms. It's complemented by life-cycle management from Red Hat Satellite. The suite also uses a Software-as-a-Service (SaaS)-based risk-management tool, Red Hat Insights, that collects infrastructure analytics so you can address technical risks before they impact operations.

Integrate with other software
Red Hat Cloud Suite works seamlessly with other Red Hat and third-party products. This lets you build true hybrid clouds across private and public domains as you establish a software-defined datacenter.

Source : redhat.com
↧

NetApp Released The NetApp AFF A-Series All Flash Arrays

August 10, 2017, 12:58 am
$
0
0
NetApp has released the all flash storage, named as NetApp All Flash FAS (AFF) system to address the enterprise storage requirements with high performance, superior flexibility, and best-in-class data management. Built on ONTAP® data management software.

NetApp AFF has several models, namely : AFF A200, AFF A300, AFF A700 and AFF A700s. The NetApp AFF A200 is  an entry point to NetApp's enterprise flash storage portfolio. It size is 2U chassis with two HA controllers and 24 SSD slots and the AFF A700 is the highest level of AFF.


 
Key Benefit of NetApp AFF Series
  • Accelerate applications with the fastest unified scale-out all-flash array of up to 7M IOPS at submillisecond latency and over 360PB effective capacity.
  • Transform your data center economics with best-in-class flash density: a complete flash system of 1PB in a 4U compact enclosure.
  • Reduce power use by 11 times and rack space by 19 times and cut support costs by 67%.
  • Unify data management for both SAN and NAS environments, from flash to disk to cloud.
  • Provision storage system and serve data within 10 minutes.
  • Reduce SSD storage by 5 to 10 times on average with inline data reduction technologies.
  • Remove network bottlenecks with high-speed connectivity of 32Gb FC and 40Gb Ethernet.
  • Safeguard your data with the best-in-class integrated data protection suite.

The Capability of AFF systems :
 Accelerate the speed of business while increasing operational efficiency:
  • Built on the flash-optimized NetApp WAFL® (Write Anywhere File Layout) system, ONTAP FlashEssentials enables consistent high performance to meet the demands of a multitude of workloads in a shared environment.
  • Consolidate all your workloads on the AFF systems, which deliver up to 600,000 IOPS at 1ms latency.
  • You can manage a massively scalable NAS container of up to 20PB and 400 billion files with a single namespace using FlexGroup volumes, while maintaining consistent high performance and resiliency.
Simplify IT operations while transforming data center economics:
  • You can reduce power consumption by up to 11 times and rack space by up to 19 times and slash support and performance-tuning costs to a third compared with hybrid
  • systems.
  • You can get flash at the cost of HDDs, thanks to NetApp data reduction technologies, enhanced with new inline data compaction.
  • Support all your backup and disaster recovery needs with a complete suite of integrated data protection and replication features.
  • Secure your data and simplify key management on any type of drive with NetApp Volume Encryption (NVE), software-based at-rest data encryption, and onboard  key manager.
Deploy flash everywhere with maximum flexibility while retaining control and security of your data:
  • You can move data and applications where they run best:  on an AFF system, on commodity hardware with soft
  • ware-defined storage, or in the cloud.
  • AFF offers the broadest application ecosystem integration for enterprise applications, VDI, database, and server virtualization.
  • Integrate flash into your infrastructure nondisruptively, eliminating silos, and scale out as your requirements grow
 Source : http://www.netapp.com/us/products/storage-systems
↧

How To Define Veritas Netbackup Licensing Model

September 14, 2017, 12:49 am
$
0
0
For the IT infrastructure manager  the TCO (Total Cost Ownership) of specific tool must be calculated carefully to avoid the improvidence budget.  Veritas Netbackup is an enterprise scale tool which requires huge budget if an organization used it.

To help the  IT infrastructure manager in calculating the budget for his Netbackup Veritas need, how much money spent for buying the license, Veritas has provided the tools and the way to calculate transparently.  There are two licensing models applied, namely : traditional licensing model and capacity licensing model.

NetBackup licensing models
NetBackup uses two licensing models:
  • The traditional licensing model counts the number of clients and servers, and then compares this information against licensed options.
  • The capacity licensing model calculates how much data at source is protected.
The Traditional Licensing Model
The traditional licensing model is based on the total number of protected clients in a NetBackup environment or on the total storage capacity.

The Capacity Licensing Model
Capacity licensing is based on the total amount of data that NetBackup protects on the client (or agent). When the capacity licensing model is used, NetBackup automatically gathers the information using the backup image header.

With the existing capacity licensing model, protected data is gathered using backup image header and then stored in the NetBackup catalog. Capacity information is gathered and a report is generated. The user then reconciles the information in the report with the actual capacity in use.

How capacity licensing uses Front-end Terabytes
The licensing fees for the use of NetBackup are based on the total number of Front-End Terabytes (FETBs) protected by NetBackup. Front-End Terabyte Calculation is a way of determining the total terabytes of data NetBackup protects. One FETB is 1 TB of protected data. The data can either be on clients or devices where the software is installed or where the software is used to provide backup functionality.


The nbdeployutil utility uses image headers in the NetBackup catalog to determine the terabytes of data that NetBackup protects. Any partial terabyte of data is rounded up to the next whole terabyte. The final total is the sum of the FETBs for each client or policy combination that the analyzer examines. The utility measures the actual data protected.


nbdeployutil utility options

The nbdeployutil utility is used to gather data and analyze licensing data, and then present the results in a spreadsheet as a report. The utility can be used to report on both the traditional or the capacity licensing model. The utility can be run automatically according to a customizable incremental schedule (for capacity reports only) or manually (for traditional and capacity reports).

Incremental capacity licensing reports run automatically.
In NetBackup 8.0, nbdeployutil supports incremental reporting. NetBackup triggers nbdeployutil to run based on a specified schedule, incrementally gather data, and generate capacity based licensing reports for the past 90 days. There are no scheduled reports in traditional licensing.



 

Note :
If you upgrade from an older version of nbdeployutil with incremental reporting to NetBackup 8.0 or later version, the operating system-based scheduler or Cron job is removed. NetBackup triggers nbdeployutil to run at a specified schedule, incrementally gather data, and generate capacity based licensing reports for the past 90 days.
 
Traditional or capacity licensing reports run manually
Run the nbdeployutil utility to gather data for a local master server, a remote master server, or a subset of clients. nbdeployutil can be run manually to generate a report for either the capacity or the traditional reporting model.
The utility generates the report in multiple steps. Data is gathered in the first step, and then analyzed and presented. 

The utility is located in the following directory:
On Windows: Install_dir\NetBackup\bin\admincmd\
On UNIX: /usr/openv/netbackup/bin/admincmd/

The performance of the nbdeployutil utility is dependent on the system running it as well as the size of the NetBackup catalog. The --gather command only executes as quickly as the bpimagelist command can run for 90 days' worth of images. The speed of report generation is dependent on the number of images and fragments. The operating system running the command also affects the utility's performance.

Depending on the environment, the nbdeployutil utility can take from several seconds to several minutes to run the --gather or the --report parameters.

Source: veritas.com
↧
Viewing all 107 articles
Browse latest View live
Search