Thursday, June 15, 2017

What's New in vSAN 6.6

 
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

Monday, June 12, 2017

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

 
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

Saturday, May 27, 2017

Veritas NetBackup 8.0 New Fatures

 
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

Backup Exec 16 System Requirements

 
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

Thursday, July 21, 2016

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

 
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

NetBackup status code: 25 (Cannot Connect on Socket)

 
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: 24 (Socket Write Failed)

 
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

Wednesday, July 20, 2016

NetBackup status code: 20 (Invalid Command Parameter)

 
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 complete

 
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).

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