How Do I Take Thread Dumps on Solaris 10 ?

October 26, 2017, 7:30 am

≫ Next: What is the Difference of Acronis Backup 12.5 Standard and Advanced Edition

≪ Previous: How To Define Veritas Netbackup Licensing Model

Currently, many applications are using JVM for processing, the active process are divided into various java threads. The list of java threads that are currently active in the JVM is called as thread dump. Sometimes we are faced with a condition where the java thread is running not as it should be, then checks are needed for investigation. To check for java threads needed tools. There are several ways to take thread dumps from a JVM.

For our case, we will use jstack with Solaris 10 environment as our case test. Here's how to take thread dump with jstack in a Solaris 10 environment.

1. List the PID of all active java processes
[joe01@testbed01]$ uname -a
SunOS utest01 5.10 Generic_150400-30 sun4v sparc SUNW,SPARC-Enterprise-T5220
[joe01@testbed01 ]$ ps -ef| grep java
stystem 3498 3469   0   Sep 26 ?         550:55 /usr/jre1.6.0_07/bin/java -Dprogram.name=run.sh -server -Xms256m -Xmx3072m -XX:
stystem 26440    1   0   Oct 05 ?          98:35 /app/st/jdk1.6.0_12/bin/java -server -Xmx1020M -XX:TargetSurvivorRatio=90 -X
stystem 24938 24919   0 20:56:18 pts/5       0:00 grep java
stystem 7233     1   0   Oct 05 ?         100:47 /app/st/jdk1.6.0_12/bin/java -server -Xmx1020M -XX:TargetSurvivorRatio=90 -X
stystem 2073     1   0   Oct 05 ?          26:10 /app/st/jdk1.6.0_12/bin/java -server -Xmx1020M -XX:TargetSurvivorRatio=90 -X
stystem 2842     1   0   Oct 05 ?          75:55 /app/st/jdk1.6.0_12/bin/java -server -Xmx1020M -XX:TargetSurvivorRatio=90 -X
stystem 1284     1   0   Oct 05 ?          85:36 /app/st/jdk1.6.0_12/bin/java -server -Xmx1020M -XX:TargetSurvivorRatio=90 -X
stystem 28953     1   0   Oct 05 ?         179:41 /app/st/jdk1.6.0_12/bin/java -Djava.security.properties=/app/st/jre1.7.0_

2. Run the jstack to request thread dump from the JVM. The command line will be jstack -l
[joe01@testbed01]pwd
/app/rapcorp/jdk1.6.0_12/bin
[joe01@testbed01]$ ls -ltr jstack
-rwxr-xr-x   1 rapcorpadm rapcorp      47788 Apr 28 2016 jstack
[joe01@testbed01]$ ./jstack -h
Usage:
    jstack [-l]
        (to connect to running process)
    jstack -F [-m] [-l]
        (to connect to a hung process)
    jstack [-m] [-l]
        (to connect to a core file)
    jstack [-m] [-l] [server_id@]
        (to connect to a remote debug server)

Options:
    -F to force a thread dump. Use when jstack does not respond (process is hung)
    -m to print both java and native frames (mixed mode)
    -l long listing. Prints additional information about locks
    -h or -help to print this help message

[joe01@testbed01]$ ./jstack -l 26440| more
2017-10-25 15:50:37
Full thread dump Java HotSpot(TM) Server VM (11.2-b01 mixed mode):

"Attach Listener" daemon prio=3 tid=0x00afb400 nid=0x718d waiting on condition [0x00000000..0x00000000]
   java.lang.Thread.State: RUNNABLE
[joe01@testbed01]$ ./jstack -F 25468
ttaching to process ID 25468, please wait...
Exception in thread "main" java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at sun.tools.jstack.JStack.runJStackTool(JStack.java:118)
        at sun.tools.jstack.JStack.main(JStack.java:84)
Caused by: java.lang.RuntimeException: Type "nmethodBucket*", referenced in VMStructs::localHotSpotVMStructs in the remote VM, was not present in the remote VMStructs::localHotSpotVMTypes table (should have been caught in the debug build of that VM). Can not continue.
        at sun.jvm.hotspot.HotSpotTypeDataBase.lookupOrFail(HotSpotTypeDataBase.java:361)
        at sun.jvm.hotspot.HotSpotTypeDataBase.readVMStructs(HotSpotTypeDataBase.java:252)
        at sun.jvm.hotspot.HotSpotTypeDataBase.(HotSpotTypeDataBase.java:87)
        at sun.jvm.hotspot.bugspot.BugSpotAgent.setupVM(BugSpotAgent.java:562)
        at sun.jvm.hotspot.bugspot.BugSpotAgent.go(BugSpotAgent.java:494)
        at sun.jvm.hotspot.bugspot.BugSpotAgent.attach(BugSpotAgent.java:332)

For convenion way, we throw the result to a file.

↧

What is the Difference of Acronis Backup 12.5 Standard and Advanced Edition

January 7, 2018, 2:22 am

≫ Next: How NetBackup Backups the VMware Virtual Machine

≪ Previous: How Do I Take Thread Dumps on Solaris 10 ?

Acronis Backup 12.5 is the latest version backup software from Acronis. Acronis claimed if the this version is the world’s easiest and fastest backup solution for all data, whether it is located on-premises, in remote systems, in private and public clouds, or on mobile devices. With enhanced backup validation and blockchain-based authentication of your backups with Acronis Notary™.

Acronis presents a complete solution for data protection. The emergence of virtualization, the explosion of data generation, and the opportunities offered by Cloud services bring new challenges for effective backup program maintenance and disaster recovery for critical data.

Acronis software are designed to move, secure, and restore critical data wherever they are in a physical, virtual, or clouded environment. With Integrated Platform and new generation technology, Acronis' innovative solutions are designed to ease management burdens and reduce total cost of ownership, and increase your recovery time goals.

The Acronis Backup 12.5 backup software has two edition, namely : Acronis Backup 12.5 Standard and Acronis Backup 12.5 Advanced edition. The difference lies in the features that can be used, where the advanced edition has more features that can be used. Here are the feature list.

Acronis Backup 12.5 Standard Edition Features List :

Patented disk-imaging technology
Storage – disks, NAS, SAN, Acronis Cloud Storage
VMware vSphere®, Microsoft Hyper-V®
User data backup
Touch-friendly web-based centralized and remote management console
Customizable dashboards
Acronis Active Protection™
Microsoft Exchange®, SQL Server®, SharePoint®, Active Directory®
Application-aware backup

Complete Business Protection
Windows Server 2016
Windows Server 2012R2/2012, 2008R2/2008, 2003R2/2003
Windows Small Business Server 2011/2008/2003R2/2003
Windows Server 2016/2012R2/2012 Essentials and Foundation
Windows Storage Server 2012R2/2012, 2008R2/2008, 2003
Windows MultiPoint Server 2012/2011/2010
Windows® 10
Windows 8/8.1/7/Vista/XP support
Mac® OS X support
Linux® (various distributions)
Linux-based management console
VMware ESX/ESXi™ (agentless and agent-based VM backup)
VMware changed-block tracking (CBT)
VMware ESXi Virtual host backup
VMware vSphere Hypervisor (free ESXi) support with agent-based backup
VMware vSphere VM Replication with WAN optimization
VMware vSphere Replication Replica Seeding
Hyper-V agentless and agent-based VM backup
Hyper-V changed-block tracking (CBT) and resilient-change trackng (RCT)
Hyper-V virtual host backup
Microsoft Exchange database backup with log truncation
Microsoft SharePoint
Microsoft Active Directory
Microsoft Office 365® mailbox backup
Microsoft Azure® VM backup
Amazon AWS EC2® instance backup
Disk-imaging backup
File backup
Dynamic disks
GPT disks
Acronis Disk Director Lite in on-premise installation

World’s Fastest Recovery
Acronis Universal Restore
Mounting of disk backup as a virtual drive
VMware ESXi host bare-metal recovery
Hyper-V host bare-metal recovery
Granular restore of Microsoft Office 365 mailboxes and emails
Granular restore of Microsoft Exchange
Granular restore of Microsoft SQL Server
Mounting of SQL databases from the backup storage
Flexible SQL recovery modes (RECOVERY, NORECOVERY, STANDBY)
Granular restore of Microsoft SharePoint
Recovery of Microsoft Active Directory domain controllers
Integrated search and preview of Office 365 emails before recovery
Integrated search and preview of Exchange emails before recovery
Restore of iPhone/iPad contacts, photos, videos, calendars, reminders from Acronis Cloud Storage subscription
Restore of Android device contacts, photos, videos, calendars, text messages from Acronis Cloud Storage subscription
Acronis Active Protection™
Convert backup to virtual machine
Acronis vmFlashback (CBT-based incremental VM restore)
Acronis Bootable Media
WinPE plug-in for on-premise console
Acronis Startup Recovery Manager

Flexible Storage and Backup Options
Acronis Cloud Storage: files and folders
Acronis Cloud Storage: disks and partitions
Acronis Cloud Storage: iPhone/iPad contacts, photos, videos, calendars, reminders, via iOS API
Acronis Cloud Storage: Android contacts, photos, videos, calendars, text messages via Android API    Local and external disk drives
Network shares
SFTP
Acronis Secure Zone
Backup validation as part of backup plan
Backup contents search
Backup encryption (in-flight and at-rest)
VSS support (consistent backup of applications)
Backup compression
Flexible backup rotation and retention policies
Backup retention cleanup as part of backup plan
Multi-destination backup (backup replication)
Acronis Storage support

Intuitive, Scalable Management
Touch-friendly web-based centralized management console
Customizable dashboards
Email notifications
Condition-based backup scheduling
Event-based backup scheduling
Remote installation
Remote update
Smart alerting

Acronis Backup 12.5 Standard Edition Features List
All the features in the standard edition plus the features below.

Complete Business Protection
iPhone®, iPad®, Android® backup     To Acronis Cloud Storage
Oracle Database backup with log truncation
Citrix® XenServer
Red Hat® Virtualization
Linux KVM
Oracle® VM Server
NetApp SAN Storage Snapshots for VMware vSphere Backup
Backup of Exchange and SQL Server clusters

World’s Fastest Recovery
Acronis Instant Restore (run VM from a backup)
PXE server
Remote bare-metal recovery
Automated bare-metal recovery
Enhanced validation, powered by Acronis Instant Restore

Flexible Storage and Backup Options
Acronis Notary™
Acronis ASign™
Centralized managed storage (Acronis Storage Node)
Central storage deduplication
Tape drive, autoloader, library support, including media management
Script-based location targeting
Scheduled backup validation
Scheduled backup replication
Scheduled backup retention
Off-host backup staging (moving)
Off-host backup replication (copying)
Off-host backup validation
Off-host backup retention (cleanup)

Intuitive, Scalable Management
Shared backup plans
Centralized data catalog with search
Advanced reporting
Admin roles (role-based administrative access)
Centralized backup policies for machine groups

Source: acronis.com

↧

How NetBackup Backups the VMware Virtual Machine

July 17, 2018, 4:59 pm

≫ Next: What Is New In XenServer 7.5

≪ Previous: What is the Difference of Acronis Backup 12.5 Standard and Advanced Edition

The growth of MWware virtual machine is getting more and more masive. Not only as a complement but now has replaced the physical server that takes up space, cost, power supply, and other large resouce. The need for data protection from vmware has been anticipated by veritas by issuing a product that is capable of securing existing data in the vmware virtual machine called as NetBackup for VMware.

NetBackup for VMware provides backup and restore of the VMware virtual machines that run on VMware ESX servers. NetBackup for VMware takes advantage of VMware vStorage APIs for data protection. The backup process is off-loaded from the ESX server to a VMware backup host.

Generally, Netbackup performs a backup process on vmware consists of 4 steps, namely:

Phase 1 : The NetBackup master server initiates the backup.
Phase 2 : The NetBackup client on the VMware backup host initiates a VMware snapshot on the virtual machine.
Phase 3 :Windows: VSS synchronizes the file system on the virtual machine. Linux: The SYMCquiesce utility can quiesce the file system on supported Linux operating systems.
Phase 4 : The VMware server creates a snapshot on the virtual disk datastore. The NetBackup client reads the snapshot from the datastores and writes the data to the NetBackup storage unit.

NetBackup for VMware requires an Enterprise Client license for each ESX Server. To protect an application or database, note: an additional license for the appropriate NetBackup package is needed for each ESX server that hosts the application or database.

Source: Netbackup80adminguide

↧

What Is New In XenServer 7.5

July 18, 2018, 2:08 am

≫ Next: The 'BigData' Policy Type Was Introduced Since Netbackup 8.1

≪ Previous: How NetBackup Backups the VMware Virtual Machine

XenServer is a comprehensive server virtualization platform with enterprise-class features built in to easily handle different workload types, mixed operating systems and storage or networking configurations. For the most demanding app, and desktop virtualization use cases, its industry-leading scalability and performance under load, can cater to the largest XenApp or XenDesktop deployments. IT gets the benefit of features unique to XenServer, such as enhanced virtualized graphics with NVIDIA and Intel, and enhanced workload security with Direct Inspect APIs, all of which reduce virtual infrastructure costs and complexity.

The latest version of XenServer has reached the version 7.5. In the Citrxi website, there is the information about whats new of this version. Check it out.

Most Mature Graphics Capabilities
As pioneers of the virtual graphics space, XenServer 7 extends our leadership with the industry-first capability of vGPU XenMotion and as the only hypervisor to support GPUs from all three major vendors.

Improved User Productivity and Admin Flexibility with vGPU XenMotion
XenServer is the only hypervisor to support Live Migration of GPU-enabled VMs with vGPU XenMotion. vGPU XenMotion improves user experience and admin flexibility by enabling administrators to rebalance GPU-enabled VMs across pool hosts to improve VM performance. vGPU XenMotion also enhances user productivity, enabling users to remain productive during unexpected maintenance.

Enabling GPU vendor choice with AMD, Intel, or NVIDIA
XenServer is the only hypervisor to support Live Migration of GPU-enabled VMs with vGPU XenMotion. vGPU XenMotion improves user experience and admin flexibility by enabling administrators to rebalance GPU-enabled VMs across pool hosts to improve VM performance. vGPU XenMotion also enhances user productivity, enabling users to remain productive during unexpected maintenance.

Increased Administrative Flexibility
XenServer 7 offers new features that simplify snapshot lifecycle management, accelerate vSphere migration and greatly improve the administrative experience.

Simplified Administration with Snapshot Lifecycle Management
Now you can easily schedule hourly, daily, weekly, or monthly snapshots on a group of VMs. However, it doesn’t just take the snapshots, it aids in the management of your snapshot lifecycles. By allowing you to set the maximum number of snapshots to keep, XenServer deletes the oldest snapshot in a rolling fashion.

Live patch host without downtime, available only with XenServer
Live patching is an industry-first hypervisor capability brought to you with XenServer 7.1. It greatly reduces operational overhead by enabling IT admins to hot-patch (update) their active XenServers without rebooting. This capability is not found on any other commercial hypervisor and has been used in production by a large cloud computing provider for months.

Simplified administration and reduce overhead with new automated updates
Simplify patching at scale with new automated updates. XenServer now supports the automated application of fixes to multiple hosts. This new automated update technology batch patches multiple hosts by automatically downloading necessary fixes from Citrix, installing these patches in the correct order, and rebooting the hosts in sequence while redistributing VMs to prevent outages.

Greater migration flexibility with Linux virtual machine conversion
XenServer Conversion Manager now offers the ability to migrate Linux VMs from other hypervisors to XenServer. This offers greater migration flexibility for customers wanting to migrate off of VMware solutions. Customers wanting to deliver secure Linux virtual desktops and applications from XenDesktop can avoid the vTax by taking advantage of XenServer.

Great scalability and simplified administration with increased pool sizes
XenServer 7.5 quadruples the maximum pool size to 64 hosts. The benefits of deploying larger pools include fewer pools to manage, more flexible in-pool migration with shared storage, and more flexibility with High Availability, as well as fewer Machine Catalogs needed for large XenApp and XenDesktop deployments. This saves you time and administrative effort during your image update process and ongoing maintenance.

Extending XenApp & XenDesktop Integration
XenServer 7 extends alignment with XenApp and XenDesktop release cycles while the expanded XenServer Enterprise entitlement ensures you can leverage unique app and desktop performance integrations only available with XenServer.
Window Continuum Experience
With patent-pending technology from XenServer, XenDesktop is the only VDI platform to enable the Windows Continuum experience with Windows 10 virtual desktops. Now, XenDesktop enables Windows 10 virtual desktops to automatically toggle between tablet and desktop mode, in real-time, as the state of the hardware change, to provide the most native Windows 10 experience.

Accelerate Citrxi Provisioning Services performance with XenServer
Introducing new Provisioning Services (PVS) Accelerator technology that results in up to 25% faster desktop boot up times, up to 98% lower network bandwidth usage, and up to 93% reduced PVS CPU usage - only available with XenServer.

First-ever Long Term Service Release (LTSR) with XenServer 7.1
This XenServer LTSR enables up to 10 years of support (5 years mainstream and 5 years of extended support) making it the only hypervisor to have product lifecycle dates fully aligned with Citrix XenApp and XenDesktop, which can radically simplify infrastructure maintenance for customers choosing to deploy a full Citrix solution.

Extending the benefits of XenServer Enterprise to all XenApp adn XenDesktop deployments
XenApp and XenDesktop customers are now entitled to all of the features of XenServer Enterprise edition, regardless of their XenApp and XenDesktop license type. Additionally, all editions of XenApp and XenDesktop are now entitled to features like Machine Creation Services (MCS) Accelerator technology, previously a platinum-only feature

Enhancing the integration of Citrix and Nunatix solutions with XenServer
Positioning XenServer for broader Nutanix integration that will ultimately lead to providing Nutanix with access to unique XenServer features, such as provisioning services, high performance virtualized GPU, enhanced security and more. XenServer is the most tightly integrated hypervisor with XenApp and XenDesktop, you can now chose Nutanix HCI with XenServer for XenApp and XenDesktop while leveraging these unique integration benefits while saving money.

Hypervisor security revolutionized
XenServer, in partnership with Bitdefender, is the only hypervisor to enable the revolutionary security solution, Hypervisor Introspection - safeguarding against targeted and advanced attacks. XenServer 7.3 extends the platform’s security portfolio with support for Bromium Secure Platform – an application isolation security solution with Micro-VM technology to protect against malware and zero-day attacks.

Hypervisor Introspection (HVI)
While there are hundreds of millions of different types of malware released every year, hackers only have a limited set of techniques available to remotely gain a foothold of victims’ system. Hypervisor Introspection can detect and prevent these attacks techniques in real-time – a capability not available with any other security solution, delivering unparalleled protection to your virtual infrastructure. HVI prevented WannaCry, day-zero, without any updates needed, by blocking EternalBlue, the underlying exploitation tool used to spread WannaCry.

Micro-Virtualization
XenServer 7.3 extends the security of your XenDesktop Windows 10 infrastructure with hardware-based isolation of users’ application and tasks, to protect against malware and zero-day attacks with Bromium Secure Platform. Bromium is the first vendor to use virtualization-based security with micro-VM technology to completely isolate the application or task to ensure any malicious behavior within the micro-VM cannot impact the host or VDI environment.

Source: https://www.citrix.com/products/xenserver/

↧

The 'BigData' Policy Type Was Introduced Since Netbackup 8.1

July 18, 2018, 9:23 am

≫ Next: IBM Introduced Power9 Servers (E950 and E980) For Enterprise

≪ Previous: What Is New In XenServer 7.5

The exponential growth of data lead the companies to use Big Data applications to streamline data processing within the business. Nowadays, the use of big data applications like Hadoop and hyper Converged Systems like Nutanix Acropolis Hypervisor (AHV) has become the operating standard for companies who process masive amount of data, such as: telco companies, banking or e-commerce companies, etc.

Veritas NetBackup as one of the leading software in the data protection has been anticipating this needs. Netbackup has added a new type for backup the big data application by adding new policy type named as Bigdata. With the BigData policy type, the Netbackup will be inititated to backup the new data type different from pre-existing ones. The BigData policy type was introduced starting from NetBackup version 8.1.

If we want to use the BigData Policy type in Veritas Netbackup 8.1, it requires a special license, as listed below:

To back up and recover Nutanix AHV virtual machines, you need the Enterprise Client license.
To back up and recover a Hadoop file system, you need the Application and Database license pack.

A BigData policy differs from other policies in the following respects:

You must specify BigData as the policy type.
The entries that are provided to add clients and to define backup selections, differ based on the application that you choose to back up.
During backup selection, you must specify certain parameters and their appropriate values.

Source: veritas.com

↧

IBM Introduced Power9 Servers (E950 and E980) For Enterprise

August 28, 2018, 12:57 pm

≫ Next: Veritas NetBackup 8.1.2 Announced (What is New and New Key Features)

≪ Previous: The 'BigData' Policy Type Was Introduced Since Netbackup 8.1

IBM has introduced the latest and powerful servers, Power9, the enterprise-class scale-up servers combine simplified cloud management with leadership performance, scale, availability and security. The servers are called as The Power E980 and The Power E950.

The Power E980, is the most powerful, reliable, and scalable POWER9 server, is designed to support the industry’s most data-intensive applications while providing economic flexibility with Power Enterprise Pools and Capacity on Demand. The Power E950 brings unprecedented performance and scale to our 4-socket server with up to 48 POWER9 cores and up to 16 TB of memory. When you combine IBM Power Systems leadership cloud technology, security designed from the ground up, and system innovation to run large-scale, mission-critical applications, these systems are an ideal foundation for you to transform your IT infrastructure into a private or hybrid cloud.

These systems are designed to cloud enable even the most data-intensive, mission-critical workloads. PowerVM, the IBM Power Systems hypervisor for data and mission-critical applications, is built in to allow you to dynamically scale compute and memory on demand. This can be based on business needs, and with POWER9 providing accelerated and encrypted live VM mobility. PowerVC, IBM’s OpenStack-based cloud manager, simplifies cloud management and upwardly integrates into most heterogeneous cloud managers like VMware and IBM Cloud Private. IBM’s Capacity on Demand capabilities simplifies your consumption-based infrastructures, only paying for what you use with almost instant response to new workload demands. Whatever your cloud strategy looks like, IBM Power Systems are designed to support your organization to deploy cloud your way without compromising on system performance and flexibility.

↧

Veritas NetBackup 8.1.2 Announced (What is New and New Key Features)

August 28, 2018, 1:19 pm

≫ Next: NetBackup Status Code: 1000

≪ Previous: IBM Introduced Power9 Servers (E950 and E980) For Enterprise

Veritas Technologies announced the latest version of its Veritas NetBackup, version 8.1.2. The new version brings new major features to adapt the rapidly expanding data protection needs. Version 8.1.2 also brings new functionality for backup up VMware as well as other virtualized workloads.

New in NetBackup 8.1.2

Introducing a simple, web-based user interface with optimized workflows.
Secure, role-based administration with access control and audit tracking.
Agentless point-and-click restores of files on virtual machines.
Orchestrate snapshots of cloud workloads in AWS, Microsoft and Google.
Automate provisioning and ticket creation with extensive REST API libraries.
Faster upgrades with automatic client updates and more Appliance options.
Real-time usage and consumption reporting through Smart Meter.

Key Features in 8.1.2 – GA Release: Sep 12, 2018

New web UI – Enjoy a simple, secure, web-based user experience
Role-based access – Grant limited access to specific users and roles
VMware Instant Access – Faster, easier VM restores without agents
NetBackup for VMware Cloud on AWS – Protect VMware VMs in AWS
NetBackup for HBase – Database-aware backup of HBase systems
NetBackup for MongoDB – Database-aware backup of MongoDB systems
Protect cloud workloads – Orchestrate AWS, Microsoft, and Google snapshots
Automatic client updates – Faster and easier client software upgrades
Amazon Glacier Vaults – Enforce compliance controls through AWS
Parallel Streaming SDK – Developer kit to create 3rd party plug-ins
REST API libraries – Expanded calls to enable more programmatic functions
GDPR ready – User audit alerting flags for inspection
Veritas Smart Meter – Monitor usage and consumption from web portal

Source : https://www.veritas.com/product/backup-and-recovery/netbackup-8

↧

NetBackup Status Code: 1000

August 30, 2018, 7:13 pm

≫ Next: Flowmon Probe, Traffic Monitoring Enabler

≪ Previous: Veritas NetBackup 8.1.2 Announced (What is New and New Key Features)

I got the Netbackup jobs status code 1000 on my Java console, and the job was failed in one of my client server. From the Netbackup status code documentation the status code 1000 is related to the offline status of netbackp job on the client.

bpclient -client prdcrmux002c1 -l
Client Name: prdcrmux002c1
CURRENT HOST
    prdcrmux002c1 0
HOST INFO
    2 0 0 0 0 2 1 0 0 0 3 0 0 *NULL* 0
CLIENT OFFLINE
    1 1534291317

NetBackup status code: 1000
Message: Client is offline
Explanation: An attempt was made to run a manual job for a client that is offline.

Checking the prdcrmux002c1 client it was offline netbackup status on it. Trying to Netbackup daemon on the clinet up, re-start the job mannualy and everything run normally.

↧

Flowmon Probe, Traffic Monitoring Enabler

August 30, 2018, 7:56 pm

≫ Next: Configuring bp.conf Files in a DB2 Cluster Environment

≪ Previous: NetBackup Status Code: 1000

Sometimes the application team gets into trouble where ongoing communication between APIs is interrupted, or experiences a delay so that the response obtained has an error or even no response at all to the peer concerned. This kind of thing will certainly take time and resources from the application team or L2 or L3 team to do tracing, where the actual problem occurs. TCP dump is one way that can be done, but of course this will take time and additional space that must be provided. With the tools such as appliance issued by Flowmon that can do the job of checking the communication between peers on the network neatly and accurately with Flowmon Probe.

Do you know who is doing what and when in your network? With Flowmon Probe you will never miss any information about IP traffic communication. Take decisive actions to manage and secure your IT environment with high performance NetFlow/IPFIX exporters, which support even 100G wire speed processing.

Traffic monitoring enabler
Flowmon probe is an essential tool for modern network traffic monitoring. The Probe is a high-performance appliance providing network engineers with detailed
statistics on network communication in the form of IP flows (NetFlow v5/v9, IPFIX). These flow statistics provide detailed and accurate information about who communicates with whom, when, how long, how often, how much data has been sent and much more information from the L2 – L4 layers. This information is crucial to ensure network troubleshooting, network capacity planning, peering and SLA compliance, monitoring of users and devices, network security and other use cases.

Flowmon Probes do not affect network traffic in any way and overcome the limitations of generating flow data by routers and switches. Additionally, Flowmon Probes extend visibility with network performance and application layer monitoring which opens up completely new possibilities allowing administrators to identify performance
bottlenecks, enhance user experience and deal with more complex network issues. Flow statistics are exported to storage for further analysis by a Flowmon Collector or other NetFlow/IPFIX compatible application. Thanks to its monitoring capabilities, Flowmon Probe can resolve up to 95 % of all operational issues in the network.

Flowmon Probe Features :

Outstanding Performance
Choose from a wide range portfolio of virtual and hardware probes for all kinds of IP networks, even the fastest 100G environments.

Deep Insight
Track every communication in your network to streamline troubleshooting and reduce MTTR. Benefit from extended visibility across all network layers.
Built-in Collector
Store and analyse network traffic statistics from the layers L2-L4 and L7. Unleash the analytical power of built-in flow collector to manage and secure your IT environment.
No Intrusion
Deploy the Probe anywhere via broad link layer and tunneling protocol support. Probes are agent-less and transparent appliances with no impact on monitored Infrastructure.

Source: https://www.flowmon.com/en/products/flowmon/probe

↧

Configuring bp.conf Files in a DB2 Cluster Environment

September 5, 2018, 5:25 pm

≫ Next: QNAP TS-332X NAS Solution Launched

≪ Previous: Flowmon Probe, Traffic Monitoring Enabler

The use of the bp.conf file will vary, depending on the environment and applications that are running. The following is explained about the configuration of bp.conf on the clustered DB2 environment. The bp.conf settings will be done on master and client db2. The below is taking from Veritas Netbackup For DB2 documentation.

If you configure NetBackup for DB2 in a cluster environment, you need to create the NetBackup bp.conf files in multiple places.
Create the file in the following places:

In /usr/openv/netbackup/bp.conf on the physical client host. This file is the master bp.conf configuration file.
In the DB2 user's home directory on each virtual host.

NetBackup searches for the bp.conf file in the DB2 user's home directory first. Specifications in the user bp.conf file override those in the master bp.conf file.

Configuring a master bp.conf file

The following procedures explain how to create a master bp.conf file on the physical client host. This file allows other backups to be performed on the host.
To create a system-wide master bp.conf file

    Log into the physical host.Use vi(1) or another editor to open file /usr/openv/netbackup/bp.conf. Set the CLIENT_NAME entry to the physical host name of the NetBackup for DB2 client. This action allows other backups to be performed on the host.
    For example:
    CLIENT_NAME=client_name

Save and close the file.

Configuring a user bp.conf file

NetBackup options in the bp.conf file of the home directory of the DB2 instance owner take precedence over the same options in the master bp.conf file. The following procedure explains how to create a bp.conf file on the virtual machine that owns the DB2 instance.

To create a system bp.conf file on the virtual host
    Log into the computer that owns the DB2 instance.Use vi(1) or another editor to open file $DB2_INSTANCE_HOME/bp.conf. Add a line that sets the CLIENT_NAME entry to the virtual name of the DB2 instance.

    For example:
    CLIENT_NAME=client_name

    Save and close the file.

Source: Veritas Netbackup for DB2 documentation

↧

QNAP TS-332X NAS Solution Launched

September 8, 2018, 3:06 am

≫ Next: What's new in Backup Exec 20.1

≪ Previous: Configuring bp.conf Files in a DB2 Cluster Environment

QNAP has announced the worldwide availability of the TS-332X, the second member of its multifaceted 3-bay NAS family. The company claimed if this product is budget friendly, having better system performance and higher data protection. QNAP chosed the RAID 5 array for TS-332x because 30% the QNAP user managed this RAID type for their NAS system. The 3-bay TS-332X not only allows customer to build a RAID 5 array on your NAS with the fewest disks, but also features a 10GbE SFP+ port and three M.2 SATA 6Gb/s SSD slots to enable higher performance for tackling performance-demanding operations. Featuring a minimalist design, the affordable 10GbE-ready TS-332X can easily fit your commercial space.

The QNAP TS-332X NAS solution is simple in form yet provides a comprehensive array of features including SSD Caching and Auto Tiering and comes equipped with 10GbE SFP+ port and three M.2 SATA 6Gb/s SSD slots, making it a seamlessly integrable device for the startup and SMB environments.

The QNAP TS-332X Features :

Build a secure RAID 5 array with three disks for optimized storage capacity and protection against one disk failing.
One built-in 10GbE SFP+ port for accelerating massive file sharing and intensive data transfer.
Qtier™ technology and SSD caching enable 24/7 optimized storage efficiency.
Snapshots fully record system status and data, allowing you to protect files and data from accidental deletion and malware attacks.
Supports LXC and Docker® containers for rapidly deploying application services across platforms including the cloud, servers, and PCs.
Secure private cloud supporting centralized storage, backup, sharing, and disaster recovery; a scalable storage solution.

The QNAP TS-332X is equipped with an AnnapurnaLabs, an Amazon company Alpine AL-324 quad-core 1.7 GHz Cortex-A57 processor (64-bit) with 2GB/4GB DDR4 RAM (upgradable to 16GB) and provides three SATA 6Gb/s drive bays. When processing AES 256-bit full NAS volume encryption, the TS-332X also provides unmatched encryption performance while ensuring the safety of sensitive business data stored in the NAS. Alongside a pair of Gigabit LAN ports, the TS-332X features a 10GbE SFP+ port to fully support 10GbE high-speed networks, delivering a major speed increase for large-data applications, fast data transfer, backup & restoration, and containerized applications.

QNAP TS-332X Specifications :

TS-332X-4GB : AnnapurnaLabs, an Amazon company Alpine AL-324 quad-core 1.7GHz processor, 4 GB RAM
TS-332X-2GB : AnnapurnaLabs, an Amazon company Alpine AL-324 quad-core 1.7GHz processor, 2 GB RAM

3-bay tower model; AnnapurnaLabs, an Amazon company Alpine AL-324 quad-core 1.7GHz Cortex-A57 processor, 64-bit; hot-swappable 2.5/3.5-inch SATA 6 Gbps HDD/SSD; 3x M.2 2280 SATA 6Gbps SSD slots; 1x 10GbE SFP+ LAN port; 2x Gigabit RJ45 LAN ports; 3x USB 3.0 ports; 1x 3.5mm line-out audio jack; built-in speaker.

Source : https://www.qnap.com/en-us/product/ts-332x

↧

What's new in Backup Exec 20.1

September 9, 2018, 8:53 am

≫ Next: How to Colaborate Veritas Netbackup 8.1.2 with VMware vSAN datastores

≪ Previous: QNAP TS-332X NAS Solution Launched

Backup Exec 20.1 has been launched and now the newest version is also coming on the way. Here is the new features of Backup Exec 20.1 taken from veritas.com (Backup Exec 20.1 Read Me).

Item	Description
Backup Exec now introduces Subscription and Perpetual-based Licensing	The Subscription and Perpetual licensing models in Backup Exec are available in Bronze, Silver, and Gold packaging. The Subscription and Perpetual licensing models facilitate simpler transactions for businesses with fewer sets of licenses to manage for users.
	It makes it easy for users to do backups since they are paying based on the front end capacity they are protecting.
Enhanced protection for Linux virtual machines	Enhanced backup wizard when you select a Linux virtual machine from the list of servers. The wizard provides options to create a virtual-based backup or an agent-based backup. If you select a virtual-based backup, but you have not yet added the virtual machine's host to Backup Exec, the wizard enables you to add the host.
	Backup Exec users can now instantly recover any Linux virtual machine.
	The Recovery Ready feature can now validate the integrity of a Linux virtual machine backup.
Support for OpenDedupe Connectors	The OpenDedupe OST Connector now supports Azure Archival Storage and Amazon Glacier. With the integration between Backup Exec and OpenDedupe, you can now back up to this storage.
	For more information about this configuration tool, refer to the following technote:
	http://www.veritas.com/docs/000127295
Enhancing S3-Compatible Cloud service provider coverage	Backup Exec supports more cloud storage providers when the cloud storage is configured with the "compatible-with-s3" provider. For more information, refer to the following technote:
Enhancing S3-Compatible Cloud service provider coverage	http://www.veritas.com/docs/000126210
Backup Exec integrates with Veritas™ Information Map	Backup Exec integrates with Veritas™ Information Map. This integration helps organizations gain insight into their data by providing an immersive visual experience of the global information environment for an organization.

	Backup Exec can be configured to populate Information Map with metadata of an organization's unstructured data and identify areas of risk, value, waste, and interest.
Veritas Update replaces LiveUpdate	LiveUpdate has been replaced with Veritas Update to provide updates for Backup Exec.
Enhanced inbound firewall rules for Backup Exec	Backup Exec has enhanced the existing inbound firewall rules to provide access for only the required ports and restrict access to all other ports. This helps to minimize probability of a security lapse or violation.
Enhancements to Backup Exec with a powerful Deduplication engine	Backup Exec users can get improved speed, scale, and stability while backing up to the Backup Exec deduplication folder.
Payment Card Industry Data Security Standard (PCI DSS) support	Backup Exec can be installed for data protection in an environment configured to use TLS 1.2 that helps to comply with the Payment Card Industry Data Security Standard (PCI DSS) 3.1/3.2 requirements.
Transport Layer Security (TLS) 1.2 support	Backup Exec can be installed for data protection in an environment configured to use TLS 1.2.
Improved IPv6 support	Backup Exec client-side deduplication, NDMP Option, and RMAL features can also be used with the IPv6 (Pure and Dual Stack) protocol.
Support for SQL Server 2017	Backup Exec now protects SQL Server 2017. You can also host the Backup Exec database on SQL Server 2017.

↧

How to Colaborate Veritas Netbackup 8.1.2 with VMware vSAN datastores

September 9, 2018, 9:24 am

≫ Next: Veritas Netbackup 8.1 Security Services Status Codes

≪ Previous: What's new in Backup Exec 20.1

Both Netbackup and VMware are delivering the newest technology which is suitable with agile informarion age. The robust, simple and efficient are shown with Veritas Netbackup 8.1.2 and VMware vSAN 6.x.

VMware has issued the technical guidance how to use the Netbackup in VMware vSAN environement with two use case scenario below.

Use cases

Provide backups of virtual machines deployed on VMware vSAN datastores.
Provide restores of virtual machines deployed on VMware vSAN datastores.

Solution Architecture
NetBackup utilizes a master server, and optionally media servers and clients, to back up and restore virtual machines hosted on VMware vSAN datastores. NetBackup communicates with VMware vCenter Server to provide virtual machine backups and restores using VMware Storage APIs (VADP). Various NetBackup topologies can be deployed depending on the scaling requirements of the assets being protected.

Standalone Master Server Topology featuring NBD and NBDSSL Transport Modes

The simplest NetBackup data protection topology is to use a standalone NetBackup master server. In this configuration, a NetBackup master server can use either the NBD or NBDSSL transport mode to back up and restore VMs that reside on a vSAN datastore. Typically, storage will be directly attached to the master server in this topology.

Master and Media Server Topology featuring SCSI Hotadd, NBD, and NBDSSL Transport Modes

A highly scalable NetBackup data protection solution can be achieved by using a NetBackup master server along with one or more NetBackup media servers. With media servers deployed on the vSAN, the SCSI Hotadd transport mode is available for more efficient backup and restore operations. Snapshots are mounted to media servers using SCSI Hotadd during backup and restore operations. The use of multiple media servers enables load balancing of operations across multiple servers. The NBD and NBDSSL transport modes are still available in this topology. If network traffic via NBD or NBDSSL is to be minimized, NetBackup VMware policies allow for fine tuning of the ordering and availability of various transport methods. Finally, the NetBackup architecture is flexible enough that one or more NetBackup clients installed on the vSAN can also serve as backup and restore hosts communicating with a standalone master or separate media servers.

Solution Components

The NetBackup solution for backup and restore uses the following components:

VMware vCenter version 6.x
VMware vSAN 6.6.1, 6.7
NetBackup 8.1.2 master server to communicate with VMware vCenter servers
NetBackup 8.1.2 media servers in VMs to allow for additional scalability of the NetBackup solution
NetBackup 8.1.2 client in a VM to serve as a backup or restore host or to perform single file restore

Source: https://kb.vmware.com/s/article/56498

↧

Veritas Netbackup 8.1 Security Services Status Codes

September 9, 2018, 7:29 pm

≫ Next: Veritas Netbackup Status Code Related to Hadoop

≪ Previous: How to Colaborate Veritas Netbackup 8.1.2 with VMware vSAN datastores

The Netbackup Security service status code helps Backup Administrator to quickly mitigate the backup process fault related with web service and (or) authentication. Here are the security services status list, taken from Netbackup 8.1 Status Code Reference documentation.

The security services status codes appear in the exit status and command output for the bpnbat command when you authenticate a user with the NetBackup authentication daemon (nbatd) or the NetBackup web service (nbwmc) to get a user certificate or a session token.

Security services status code 93
Message: Web authentication failed.
Explanation: Web authentication has failed.
Recommended Action: Either the user name, domain name, domain type, or password is incorrect. Check the user authorization permission. Check the bpnbat logs for further diagnostics.

Security services status code 94
Message: Both AT authentication and Web authentication failed.
Explanation: Authentication for the NetBackup AT broker and the web application has failed.
Recommended Action: Ensure that both the NetBackup web service (nbwmc) and the NetBackup authentication daemon (nbatd) are running on the master server. Either the user name, domain name, domain type, or password is incorrect. Check the bpnbat logs for further diagnostics.

Security services status code 95
Message: AT authentication successful, web authentication failed.
Explanation: When the login type is not specified, both the NetBackup AT broker and the NetBackup web application logins are performed. However, authentication
for the NetBackup web application has failed.
Recommended Action: Ensure that the NetBackup web service (nbwmc) is running on the master server. Check the bpnbat logs for further diagnostics.

Security services status code 96
Message: Web authentication successful, AT authentication failed.
Explanation: When the login type is not specified, both the NetBackup AT broker and the NetBackup web application logins are performed. However, authentication
for the NetBackup AT broker has failed.
Recommended Action: Ensure that the NetBackup authentication daemon (nbatd) is running on the master server. Check the bpnbat logs for further diagnostics.

Security services status code 97
Message: Web logout failed.
Explanation: The logout operation to the NetBackup web application failed.
Recommended Action: Ensure that the NetBackup web service (nbwmc) is running on the master server.

Security services status code 98
Message: Web logout was successful, but the AT logout failed.
Explanation: When the logout type is not specified, both the NetBackup AT broker and the web application logouts are performed. However, the NetBackup authentication broker logout failed.
Recommended Action: Retry the operation. If the problem continues, save all of the error log information and call Veritas Technical Support.

Security services status code 99
Message: AT logout was successful, but the web logout failed.
Explanation: When the logout type is not specified, both the NetBackup AT broker and the web application logouts are performed. However, the NetBackup web application logout failed.
Recommended Action: Ensure that the NetBackup web service (nbwmc) is running on the master server.

Security services status code 100
Message: Both the AT and the web logout failed.
Explanation: The NetBackup AT broker and the web application logout failed.
Recommended Action: Ensure that the NetBackup web service (nbwmc) is running on the master server and retry the operation.

Security services status code 101
Message: The CA certificate is not present or is invalid.
Explanation: The NetBackup web login or logout failed because the NetBackup web authentication services' certificate could not be verified using a CA certificate
from the local trust store.
Recommended Action: Run the nbcertcmd–getCACertificate command to get a new CA certificate and try again. You can also run the nbcertcmd -listCACertDetails command to list the CA certificates that are in the local trust store. Ensure that the NetBackup web service (nbwmc) is running on the master server and retry the operation.

Security services status code 102
Message: Unable to connect to the NetBackup web authentication service.
Explanation: The NetBackup web login or logout failed because NetBackup cannot connect to the web authentication service.
Recommended Action: Ensure that the NetBackup web service (nbwmc) is running on the master server.

Security services status code 103
Message: Unable to send information to the NetBackup web authentication service.
Explanation: The NetBackup web login or logout failed because NetBackup cannot send information to the NetBackup web authentication service.
Recommended Action: Check if the NetBackup web service (nbwmc) is running and restart it, if required.

Security services status code 104
Message: Unable to read information from the NetBackup web authentication service.
Explanation: The NetBackup web login or logout failed because NetBackup cannot read the token information from the NetBackup web authentication service.
Recommended Action: Check if the NetBackup web service (nbwmc) is running and restart it, if required.

Security services status code 105
Message: Unable to retrieve user authentication details on the current host.
Explanation: The user authentication details from the NetBackup web login cannot be retrieved on the current host.
Recommended Action: Try to log in again with the bpnbat –login command. If the problem continues, save all of the error log information and contact Veritas Technical Support.

Security services status code 106
Message: Authentication successful but unable to store the user details on the
current host.
Explanation: The NetBackup web login authentication succeeded, but the user details were not stored on the current host.
Recommended Action: Try to log in again with the bpnbat –login command. If the problem continues, save all of the error log information and contact Veritas
Technical Support.

Security services status code 107
Message: Failed to get logged in user details; either the credentials are expired or are not available.
Explanation: The bpnbat -whoami command returns this error when it does not find the AT credentials and web token.

Source : Veritas NetBackup™ Status Codes Reference Guide Release 8.1

↧

Veritas Netbackup Status Code Related to Hadoop

September 16, 2018, 1:00 am

≫ Next: What's New in Backup Exec 20.2

≪ Previous: Veritas Netbackup 8.1 Security Services Status Codes

Backup operation fails with error 6599, 6609,6618,6647,6654,8857,6617 and 6616

The Hadoop data can be protected by Veritas Netbackup by using the NetBackup Parallel Streaming Framework (PSF). With PSF, The data is backed up in parallel streams wherein the DataNodes stream data blocks simultaneously to multiple backup hosts. The job processing is accelerated due to multiple backup hosts and parallel streams. By the Netbackup, the Hadoop data will be Backup, Archive, and Restore console to manage backup operations as the same as other data.

In the Hadoop data backup operation, sometimes we will be facing the situation where the job is not running properly, as an administrator we have to mitigate these issue as soon as possible. Fortunately, Veritas has been categorizing the error code or status code related to Hadoop issue in backup operation. Here is the Netbackup Status Code related to Hadoop :

Backup operation for Hadoop fails with error code 6599
This error is encountered in the following scenarios:

Backup operation for Hadoop fails if the directory or folder which is used as a
backup selection when you define BigData policy with Application_Type=hadoop contains a space or comma in its name.
Workaround: When you define backup selection list for BigData policy with Application_Type=hadoop, do not use comma or space for folder names.

Backup host has invalid Ticket Granting Ticket (TGT) in case of Kerberos enabled Hadoop cluster. Workaround: Renew the TGT.

Backup operation fails with error 6609
This error is encountered during the following scenarios:

The Hadoop plug-in files are deleted or missing from any of the backup hosts (single or multiple). Workaround: Download and install the Hadoop plug-in.
The Application_Type details are incorrect.
Workaround: Use hadoop instead of Hadoop while specifying Application_Type.

Backup operation failed with error 6618
Backup operation failed with error 6618 wherein the following error is displayed:
NetBackup cannot find the file to complete the operation.(6618). This error is encountered if you have provided an invalid directory as backup selection.
Workaround:
Provide a valid directory as backup selection in the BigData policy.

Backup operation fails with error 6647
Backup operation fails with error 6647 wherein the following error is displayed:
Unable to create or access a directory or a path. (6647)
This error is encountered in one of the following scenarios:

Directory is not snapshot-enabled.
Policy is configured to take snapshot of the root folder as backup selection, whereas one of the child folder is already snapshot-enabled.
Policy is configured to take snapshot of a child folder as backup selection, whereas one of the parent folder is already snapshot-enabled.
Policy is configured to take snapshot of a file as backup selection

Workaround:
Nested snapshot-enabled directories are not allowed in Hadoop. If the parent directory is already a snapshot-enabled, than any other child directory under the parent directory cannot be enabled for snapshot. For backup selection in Bigdata policy type, only snapshot-enabled directory must be selected for backup and any other child directories must not be selected.

Backup operation fails with error 6654
This error is encountered during the following scenarios:

If Hadoop credentials are not added in NetBackup master server
Workaround:
Ensure that the Hadoop credentials are added in NetBackup master server. Use the tpconfig command.
If Hadoop plug-in files are not installed on backup host.
Workaround: Ensure that the Hadoop plug-in files are installed on all backup hosts before you begin backup operation.

Backup operation fails with bpbrm error 8857
This error is encountered if you have not whitelisted NetBackup client on NetBackup
master server.
Workaround:
You must perform the whitelisting procedure on NetBackup master server if you
want to use the NetBackup client as the backup host.

Backup operation fails with error 6617
Backup operation failed with error 6617 wherein the following error is displayed:
A system call failed. Verify that the backup host has valid Ticket Granting Ticket (TGT) in case of
Kerberos enabled Hadoop cluster.
Workaround:
Renew the TGT.

Backup operation fails with error 6616
Backup operation fails with error 6616 wherein the following error is logged:
hadoopOpenConfig: Failed to Create Json Object From Config File.
Workaround:
Verify the hadoop.conf file to ensure that blank values or incorrect syntax is not
used with the parameter values.

Source: Veritas Netbackup for Hadoop Administrator's Guide

↧

What's New in Backup Exec 20.2

October 8, 2018, 12:26 am

≫ Next: Veritas NetBackup 8.1.2 Alert Notification Status Codes

≪ Previous: Veritas Netbackup Status Code Related to Hadoop

Veritas has released an updated for the Backup Exec 20.x with update 2. The update is intended for the latest Microsoft Azure and vSphere 6.7. Here is the new features of Backup Exect 20 update 2 :

Item	Description
Instant Cloud Recovery	Backup Exec users get Disaster Recovery powered by Azure Site Recovery. You can monitor the replication health and enable replication of on-premise virtual machines, whose hosts are configured with Azure Site Recovery. For more information about Azure Site Recovery, go to the following URL: https://azure.microsoft.com/services/site-recovery/
Support for vSphere 6.7	Backup Exec protects vSphere 6.7.
SupportforMicrosoftSharePointServer2016	Backup Exec now supports protection of SharePoint Server 2016. Granular restore is limited to farm-level components.
BackupExecnow protectsWindowsServer, version1803andWindows10,version1803. WindowsServer,version1803andWindows 10, version 1803	BackupExecnow protectsWindowsServer, version1803andWindows10,version1803.
Establish trust for vCenter/ESX(i) servers	Backup Exec users can now review and validatethesecuritySSLcertificatesinstalled on vCenter/ESX(i) hosts. Backup Exec users can now review and validatethesecuritySSLcertificatesinstalled on vCenter/ESX(i) hosts.

Source : https://www.veritas.com/content/support/en_US/doc/125172030-133605728-1

↧

Veritas NetBackup 8.1.2 Alert Notification Status Codes

October 8, 2018, 8:39 pm

≫ Next: Netbackup 8.1.2 Network Ports

≪ Previous: What's New in Backup Exec 20.2

Here is the Netbackup alert notification status code. The information is taken from Netbackup812 Reference Guide status code release 8.1.2.

Since NetBackup supports the ticketing systems, the status code can be delivered automatically to the Backup Administrator based on inbound email services. Netbackup support many ticketing system, such as : ServiceNow, Remedy, or HP Service Manager (HPSM).

Status code | Error message
1 The requested operation was partially successful
2 None of the requested files were backed up
6 The backup failed to back up the requested files
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
20 Invalid command parameter
21 Socket open 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
35 Cannot make required directory
36 Failed trying to allocate memory
37 Operation requested by an invalid server
39 Client name mismatch
40 Network connection broken
41 Network connection timed out
42 Network read failed
44 Network write failed
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
52 Timed out waiting for media manager to mount volume
54 Timed out connecting to client
58 Can't connect to client
59 Access to the client was not allowed
61 The vnetd proxy encountered an error
63 Process was killed by a signal
67 Client backup failed to read the file list
69 Invalid filelist specification
71 None of the files in the file list exist
72 The client type is incorrect in the configuration database
74 Client timed out waiting for bpstart_notify to complete
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
93 Media manager found wrong tape in drive
96 Unable to allocate new media for backup, storage unit has none available
98 Error requesting media (tpreq)
103 Error occurred during initialization, check configuration file
112 No files specified in the file list
114 Unimplemented error code
129 Disk storage unit is full
130 System error occurred
142 File does not exist
154 Storage unit characteristics mismatched to request
155 Disk is full
156 Snapshot error encountered
158 Failed accessing daemon lock file
159 Licensed use has been exceeded
174 Media manager - system error occurred
190 Found no images or media matching the selection criteria
191 No images were successfully processed
196 Client backup was not attempted because backup window closed
198 No active policies contain schedules of the requested type for this client
200 Scheduler found no backups due to run
213 No storage units available for use
219 The required storage unit is unavailable
227 No entity was found
232 A protocol error has occurred
233 Premature eof encountered
636 Read from input socket failed
800 Resource request failed
806 This mpx group is unjoinable
811 Failed to communicate with resource requester
818 Retention level mismatch
1002 Discovery detected a failed client
1542 An existing snapshot is no longer valid and cannot be mounted for subsequent operations
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 or is not configured for the storage server
2108 Requested NDMP machine does not have credentials or is not configured in NetBackup
2109 Requested Fibre Transport client machine was not found in NetBackup configuration
2110 Requested machine is not configured in NetBackup
2111 All storage units are configured with On Demand Only and are not eligible for jobs requesting ANY storage unit
2112 NetBackup media server version is too low for the operation
2113 Invalid or no disk array credentials are added for vserver
2505 Unable to connect to the database
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 entry found in 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 fetch snapshot metadata or state files
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
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
4241 Block-level incremental backups are not supported for this device
4243 Unable to connect to VirtualCenter server
4245 Invalid pathname for backup selection
4246 The requested operation was partially successful.
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
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
4290 Failed to create virtual machine snapshot. Virtual machine is busy performing another operation.
4292 Unable to activate change block tracking in current state of virtual machine
4293 Invalid credentials or an access violation
4294 The virtual machine is disconnected
5402 OS Authentication error - Could not connect to the database. Please check the OS credentials
5449 The script is not approved for execution
7600 An unknown internal error occurred.
7601 Failed to register service with PBX.
7603 Failed to initialize PBX.
7604 Failed to register PBX acceptor with the reactor.
7607 Failed to set socket to non-blocking mode.
7609 Failed to perform a reactor event handler operation.
7610 Failed to parse the specified object.
7611 A connection protocol error occurred.
7612 An unexpected protocol event occurred.
7613 A lookup failed for host.
7614 No valid source-target bindings exist for host.
7617 A JSON conversion error occurred.
7618 Failed to find JSON key.
7619 The specified state machine is still active.
7622 Input I/O is required.
7623 Output I/O is required.
7624 A SSL socket accept failed.
7625 A SSL socket connect failed.
7627 SSL initialization failed.
7628 VxSS initialization failed.
7631 Certificate path lookup failed.
7632 A protocol sanity verification failed.
7633 The state machine was terminated before completion.
7634 Failed to set up a UNIX Domain Socket listener for user.
7635 Failed to create a local acceptor.
7636 Failed to import socket from remote process.
7637 Failed to export socket to remote process.
7638 Failed to create a socket pair.
7639 Failed to create a peer name mapping.
7640 The peer closed the connection.
7641 Failed to find a common CA Root for secure handshake.
7642 Failed to verify Java GUI session token.
7643 Connection cannot be established because the host validation cannot be performed.
7645 Could not get name from certificate information.
7647 Proxy peer does not conform to proxy protocol.
7648 Connection cannot be established because the host validation failed.
7649 Data retrieved from the cache is not in a valid format.
7650 Data that is retrieved from the server is not in a valid format.
7651 Could not process audit reason.
7652 Secure communication proxy is not available for use.
7653 The Peer Certificate is revoked
7654 The Certificate Revocation List is invalid
7655 Certificate Revocation List is signed incorrectly
7656 Certificate Revocation List is out of date
7657 Cannot identify service type of acceptor
7658 Connection cannot be established because the host validation cannot be performed on the target host.
7659 Connection cannot be established because the host validation failed on the target host.
7660 The peer proxy cannot find usable certificates for the certificate protocol
8500 Connection with the web service was not established
8506 The certificate has expired

↧

Netbackup 8.1.2 Network Ports

October 9, 2018, 7:40 am

≫ Next: VMware vSphere 6.7 Update1, What's New ?

≪ Previous: Veritas NetBackup 8.1.2 Alert Notification Status Codes

As we know the Netbackup uses the TCP IP protocol for communication purposes among included processes. Since the client-server architecture was used, there will be a spesific ports will be used through the firewall within the networking infrastructure. For security reason, there will be filtering the trusted ports which will be allowed.

In my experience, the vnetd (13724) is the most famous port, because this port is used for the first time when the communication will be established among hosts which is involved in Netbackup environment. And now, since the Netbackup version 8.1 and newer, there will be an additional port called as VERITAS_PBX (1556) port. These two port (13724 and 1556) is used when connecting to legacy daemons on remote hosts, NetBackup 8.1 and newer servers first attempt to connect to VERITAS_PBX. If unsuccessful, the connection is retried to VNETD.

As stated at the Netbackup 8.1.2 Network Ports Reference Guide document, Netbackup uses so many ports for their internal communication between parties. Here's the port used by Netbackup 8.1 and newer.

Default Ports
Netbackup uses these two ports for configuring hosts.

Service Port	Port	Description
VERITAS_PBX	1556	Veritas Private Branch Exchange Service
VNETD	13724	NetBackup Network service

NetBackup master server ports
The ports listed below will be used by master servers.

Source	Destination	Service	Port
Master server	Media server	VERITAS_PBX	1556
Master server	Media server	VNETD	137241
Master server	Client	VERITAS_PBX	1556
Master server	Client	VNETD	13724
Master server	Java server	VERITAS_PBX	1556
Master server	Netware	VNETD	13724
Master server	Netware	BPCD	13782

NetBackup media server ports
The ports number listed below will be used by media server.

Source	Destination	Service	Port
Media server	Master server	VERITAS_PBX	1556
Media server	Master server	VNETD	13724
Media server	Media server	VERITAS_PBX	1556
Media server	Media server	VNETD	13724
Media server	Client	VERITAS_PBX	1556
Media server	Client	VNETD	13724
Media server	MSDP server	Deduplication 10 Manager (spad)	10102
Media server	MSDP server	Deduplication Engine (spoold)	10082
Media server	Netware client	VNETD	13724
Media server	Netware client	BPCD	13782

NetBackup client ports
The ports number listed below will be used by client server.

Source	Destination	Service	Port
Client	Master server	VERITAS_PBX	1556
Client	Master server	VNETD	13724
Client	Media server	VERITAS_PBX	1556
Client	Media server	VNETD	13724
Client	MSDP server	Deduplication Manager (spad)	10102
Client	MSDP server	Deduplication Engine (spoold)	10082

Java server ports
The ports number listed below will be used by Java application.

Source	Destination	Service Port
Java server	Master server	VERITAS_PBX	1556
Java server	Master server	VNETD	13724
Java server	Media server	VERITAS_PBX	1556
Java server	Media server	VNETD	13724

Java Console ports
The ports number listed below will be used by Java console.

Source	Destination	Service Port
Java server	Master server	VERITAS_PBX	1556
Java server	Master server	VNETD	13724
Java server	Media server	VERITAS_PBX	1556
Java server	Media server	VNETD	13724

NetBackup Web Services
The NetBackup installation process automatically runs the configurePorts script to configure NetBackup Web Services to run on any of the following sets of ports.

Port set	HTTPS port	Shutdown port
First set	8443	8205
Second set	8553	8305
Third set	8663	8405

Source : Netbackup 8.1.2 Network Ports Reference Guide

↧

VMware vSphere 6.7 Update1, What's New ?

October 22, 2018, 2:18 am

≫ Next: Netbackup Status 2107- EMM status: Requested media server does not have credentials or is not configured for the storage server

≪ Previous: Netbackup 8.1.2 Network Ports

During the VMworld event in Las Vegas, VMware has announced the new major update to their virtualization product, VMware vSphere 6.7 U1. This new release introducing new features and enhancements. Taken from VMware's blog official website witten by Adam Eckerle, here is the new things for this release.

Fully Featured HTML-5 based vSphere Client
vCenter Server Converge Tool
Enhancements for HCI and vSAN
Enhanced Content Library
vMotion for NVIDIA vGPU VMs;Support for Inter FPGA

vSphere Client
From vSphere 6.7 U1 onward, the vSphere Client is the only client you’ll need to manage vCenter Server. all administrative functions have now been completed for the vSphere Client. No more switching between clients to perform actions such as setting up a vCenter HA (VCHA) cluster or using vSphere Update Manager (VUM) to update VMware Tools. Many of the latest additions have not only showed up in the vSphere Client but they’ve also been improved in the process.

vCenter Server Converge Tool
This tool allows an administrator to migrate from an external Platform Services Controller (PSC) architecture into the simpler, easy-to-manage embedded PSC architecture. This means fewer VMs to manage, no more load balancers for HA, and no complex multi-site replication topologies. While we announced support for Enhanced Linked Mode (ELM) with embedded PSCs for vSphere 6.7 and vSphere 6.5 U2, many customers already had external PSC topologies.

Enhancements for HCI and vSAN
In this release VMware added a new workflow called Cluster Quickstart which provides one simple, efficient wizard to create a cluster, add hosts, and configure those hosts so they are all identical. This configuration includes HA & DRS, Enhanced vMotion Compatibility (EVC), a vSAN datastore, and networking including a Virtual Distributed Switch (VDS). With Cluster Quickstart you can go from zero to fully functioning cluster in a matter of minutes. And, when it is time to expand the cluster, there is a simple workflow to add new hosts and configure them using the cluster settings used during initial setup. This new workflow also includes a cluster validation that can be used to ensure all settings have been properly configured on all hosts and will report any discrepancies.

Enhanced Content Library
Content Library in vSphere 6.7 Update 1 enables the importing of OVA templates from a HTTPS endpoint and local storage, as well as syncing content from OVA templates to other vCenter Servers. As part of the import of OVA templates, Content Library handles and verifies the OVA bundle’s certificate and manifest files in adherence to security best practices. In addition, Content Library now natively supports VM templates (VMTX) and associated operations such as deploying a VM directly from Content Library. These improvements make working with Content Libraries more efficient and prevent the need to copy objects in and out of Content Library to do meaningful operations. Note that syncing of VM templates to another vCenter Server is not yet available in vSphere 6.7 Update 1.

vMotion for NVIDIA vGPU & Support for Intel FPGA
With vSphere 6.7 Update 1, VMware and NVIDIA have collaborated to significantly enhance the operational flexibility and utilization of virtual infrastructure accelerated with NVIDIA virtual GPU (vGPU) solutions which include the Quadro virtual Data Center Workstation, GRID vPC and GRID vApps.

For completed article can be found at this url.

Source : https://blogs.vmware.com

↧

Netbackup Status 2107- EMM status: Requested media server does not have credentials or is not configured for the storage server

December 10, 2018, 1:29 am

≫ Next: Broadcom Released Brocade® SANnav Management Portal and SANnav Global View

≪ Previous: VMware vSphere 6.7 Update1, What's New ?

NetBackup status: 2107, EMM status: Requested media server does not have credentials or is not configured for the storage server), because the READ host selected does not have credentials.

When we are facing to the situation where the duplication is failed do to this scenario..
It's been noticed in certain situations there are concerns over how NetBackup plays duplications using optimized duplication (opt-dup). Relying on the version deployed, backups may be performed the usage of one media server, but a duplication can use a distinct media server. With opt-dup duplications the media server defined to perform the examine operation has little or no requirement to do any paintings, because the work is finished by means of the storage server that's associated to the disk pool, where the preliminary backup is living. The media server action is to just initiate the challenge (similar to an orchestra conductor), it's left to the storage server to send the information to the far flung vacation spot and destination disk pool.

Relying upon the NetBackup and garage server configurations, there may be a opportunity opt-dup duplications can fail with credential mistakes, *if* the backup is finished to a disk pool which simplest has a single media server selected, but, the destination disk pool has multiple media servers selected. The trouble occurs because sources are allocated for the vacation spot garage unit, and if a media server selected is not a media server which has get right of entry to to the disk pool wherein the preliminary backup became done, a credential failure will seem and the duplication fails.

The truth we see a one-of-a-kind media server indexed, does no longer indicate this media server is sending records throughout the network, it’s just telling the storage server to do the work.
Whilst optimized duplications are completed the ALTREADHOST and the -COMMON_SERVER_FOR_DUP options are not adhered to. That is because despite the fact that another media server is registered as appearing the study operation, in actual fact the opt-dup operation remains finished by the storage server related to the authentic deduplication disk pool (OST plugin does the work).

The optimized duplications fail with STATUS 2107 (NetBackup status: 2107, EMM status: Requested media server does not have credentials or is not configured for the storage server), because the READ host selected does not have credentials.

NetBackup storage server and disk pool configurations do not have the same media servers defined at both the read and write sides of the optimized duplication process.

Solution of Netbackup status 2107
NetBackup is working as designed and this is documented in the Veritas NetBackup 7.5 Deduplication Guide page 39, and at the time this technical article was written, there are no known plans to alter this behaviour.

↧