Tổng quan công nghệ Net backup - Phần 2

NetBackupTechnicalOverview
DayTwo
NetBackup Technical Overview - Day Two1

Agenda
DayTwo
SAN Client
NetBackup Appliances
Copilot for Oracle
NetBackup Licensing

SAN Client

• LAN backup and restore no longer meets SLAs
• Availability – Minimize the recovery window in case of downtime.
• Shrinking BackupWindows and increasing amounts of data to protect within those
windows.
• High performance data transfer for the client and offloads the LAN with the backup
traffic.
• Avoid slow LAN backups and restores and take advantage of high-speed backup and
restore to disk and tape over the SAN.
• Replacement of SAN Media Server
Today’s Challenges

Use Cases
SAN Media Server
–Designed for application servers
with lots of data to backup
quickly
–Self serving – only processes
jobs from the local machine
–Uses Operating System tape
drivers and SCSI PassThrough
–Does not support shared disk
storage
–Full media server footprint
SAN Client
–Uses the smaller client only
footprint
–Available on all platforms
supported by SAN Media Server
• Uses Operating System tape drivers
and SCSI PassThrough methods to
transport data to FT Pipe Servers
(server side)
–Client does not have to be
upgraded as often as Media
Server.

SAN Media Server Usage
Tape &
Disk storage media
• SAN Media server on the Application hosts
(Big NetBackup footprint)
Disk media with data
from application hosts
Application hosts and SAN Media Servers
(Big NBU footprint)
• Ability to send Non-Multiplexed and
Multiplexed backups of multiple
streams toTape and Disk storage
media over the SAN.
SAN• Counts significantly against the
master server scalability limitations.

• SAN Client is a NetBackup optional feature that provides high-speed backups and restores of
NetBackup clients.
• SAN Client supports both Disk storage andTape storage. NetBackup allows the storage devices to be
connected to the FT media servers by any means.
• SAN Client uses SCSI protocol to send backup and restore data over the FC SAN to/from a Fibre
Transport (FT) Media Server – which directs backup and restore traffic to/from storage units.
– Result is higher backup/restore performance.
– SAN Client provides all the performance benefits of the SAN Media Server with none of the
associated impact on the client system (has smaller footprint, lower resource consumption, and less
complex NetBackup upgrade scenarios that SAN Media Server).
– Supports Multiplexing and Multistreaming
What is SAN Client

SAN Client Usage
• SANClients on the Application hosts
(Small NetBackup footprint)
Tape &
Disk storage media
Disk media with data
from application hosts
• Ability to send Non-Multiplexed and
Multiplexed backups of multiple
streams toTape and Disk storage
media over the SAN.
Application hosts and SAN Clients
(Small NBU footprint)
FT Media Servers
FT SAN
Zone
SAN
• Does not significantly affect
Master/EMM scalability.

Differences
SAN Media Server
• Full Media Server footprint
• Designed for application servers with lots of
data to backup quickly
• Self serving – only processes jobs from the
local machine
• Uses Operating System tape drivers and
SCSI PassThrough to transport data to
storage
• Admin privileges are required for
maintenance
SAN Client
• Uses the smaller Client only footprint
• Available on all platforms supported by SAN
Media Servers
• One FT Media Server can serve multiple
Clients
• Uses Operating System tape drivers and
SCSI PassThrough methods to transport
data to FT Media Servers
• Client does not have to be upgraded as
often as Media Server

Terms
Term Description
FibreTransport
NetBackup FibreTransport (FT) is a method of data transfer. It uses Fibre Channel
and a subset of the SCSI command protocol for data movement over a SAN rather
thanTCP/IP over a LAN. FT connections between NetBackup clients and NetBackup
servers are referred to as FT pipes.
SAN client
SAN client is a NetBackup client on which the FibreTransport service is activated.
SAN Client acts as Initiator of FT pipes.
FT media server FT media server is a NetBackup media server on which the FibreTransport services
are activated. FT media server acts asTarget of FT pipes.
FT Service Manager
FT Service Manager (FSM) runs in the same process as EMM. FSM interacts with the
FT services that run on SAN clients and on FT media servers. FSM discovers,
configures, and monitors FT resources and events.
Target Mode Driver
Target mode driver replaces the default, initiator mode driver.Target mode applies
only to QLogic HBAs.

• Enter an Enterprise Client license key on Master server to activate SAN Client.
• PBX service must run on the SAN clients.
• Only 64bit Solaris SPARC and Linux x86_64 platforms are supported as FibreTransport
servers.
• Define the zones on the switch so that the client(s) and server(s) are in the same zone.The
FibreTransport zone (or backup zone) should include only specific HBA ports of the hosts that
use FibreTransport.
• For the connections to the SAN clients, use a QLogic HBA that NetBackup supports for Fibre
Transport. For these HBAs, you must configure them to use the NetBackup target mode
driver.
• HBAs and their drivers must support 256K size buffers for data transfer.
• NetBackup master server and all NetBackup media servers that use the feature must be at
NetBackup 6.5 or later.
Requirements

• No special installation is required for the core NetBackup FibreTransport
components.
• Step1: Configure FT media server
1. Start nbhba mode on the media server(via nbftsrv_config –nbhba)
2. Mark the HBA ports(via nbhba –modify)
3. Configure the FT services(via nbftsrv_config)
• Step 2: Configure SAN client
1. Configure firewalls on SAN clients
2. Configure SAN client drivers
3. Configure the SAN client FT service(via bpclntcmd -sanclient 1)
4. Start the SAN client FT service (via bp.start_all except windows)
Installation and Configuration

FTMS Configuration
Start nbhba mode on the media server
Mark the specific HBA port
initiator mode
target mode driver binds to the marked
HBA port

Components and Configuration
EMM databaseMaster/EMM server
FT Media Server
nbftsrvr
nbfdrv64SAN
Client
nbftclnt
FSM
bpclntcmd -sanclient 1 admincmd/nbftsrv_config
SAN Client
MachineType
FTTables
GUI/ CLI
Initiator Target
bp.conf
SANCLIENT=
1
Enterprise Client license

Media ServerView
2 ports FC HBA

SAN ClientView
If SAN client operating system is
configured correctly, it
recognizes each media server
HBA port in target mode as two
ARCHIVE Python devices.

FibreTransport Properties – Master Server
17
FT properties control how your SAN clients use the FibreTransport services for
backups. Master properties apply to all SAN clients.
NetBackup Technical Overview - Day Two

Host Properties – FT Media Server
18
FibreTransport properties apply to the SAN client or clients that the selected
media servers back up.

Host Properties – SAN Client
19
FibreTransport client properties apply to the selected SAN clients.

Jobs Display
20
Transport column in the Jobs tab window shows
the type of transport between the SAN client
and the NetBackup media server: FT for Fibre
Transport or blank for inactive or for a LAN.

Job Details
21
Messages in the Status window
show the status of jobs that use FT
transport.
Transport Type field in the header
area shows the same information as
the Transport column in the Jobs
tab.

Best Practices for SAN Zoning
• FT Backup Zone should include only the Fibre Transport traffic between the SAN clients and FT media
servers.
• Veritas recommends creating zones with only a single initiator per zone. Multiple targets in a single
zone are acceptable, only if all of the targets are similar.
• Be aware of performance degradation when a port is configured for multiple zones.
• For fault tolerance, spread connectivity across HBA cards and not ports.
• It is recommended to perform SAN zoning based on WWN.
• To promote multistream throughput, each SAN client should detect all target mode devices of HBA
port or ports in the zone.
• Whenever possible avoid using ISLs between SAN Clients and the Fibre Transport Media Servers with
which they communicate.

Appliances

Understanding NetBackup appliances
24
• Based on Front-EndTerabytes (FETB)
• Separate from hardware cost
• Offers numerous advantages (replication, retention, refresh)
Licensing
• Defined by hardware, firmware and software
• Uses an appliance-specific version number
• Correspond to a specific NetBackup version
Versioning
• Software and appliance functionality is normally equivalent, but may not be identical
• Refer to http://netbackup.com/compatibility, in the NetBackup Appliances section.
Compatibility

NetBackup 8.1.2 Sales Training2525
NetBackup purpose-built backup appliances vs. build your own
NetBackup Appliances Overview
Management
Acquisition
Deployment
Management
Acquisition
Deployment
Services
Software Hardware
Security
Monitoring Automated

All-in-one

Simplified

 Simplified deployment experience
 Pre-assembled and tested
 Built-in security platform
 Operational and production ready in
minutes
 Unified patches and upgrades
 Tuned for optimal performance
 24x7 appliance monitoring and
automated CallHome
 MyAppliance customer portal
 All-in-one hardware, software, and
storage solution
 Fully integrated and optimized
 Known compatibility & performance
 Unified support experience
Patches
!
Support
!
Time
!
Testing
!
!
KeychallengestotheBYObackupsolutionincludehiddencosts($$$)and
additionaltime($$$)todeployment,increasingtotalcostofownershipovertime.
Storage
!
Tuning
!
Upgrades
!
NetBackup Appliance Solutions
Cost-effective and low risk
Build-your-own Backup Solution
High costs and risks
! 

NETBACKUP APPLIANCES
Cpcapacity
2 - 11732
Flexible Storage
Capacity
Reredundancy
634 - 877
Redundancy
and Reliability
Sesecurity
11 - 9778
Symantec Data
Center Security
Scscalability
5414 - 33
Highly Scalable
Design
Nbnetbackup
193 - 331
Powered by
NetBackup
Wnwan opt
513 - 089
WAN
Optimization
Inintegration
009 - 112
Broad Platform
Integration
Dededuplication
143 - 112
Built-in Data
Deduplication
Pfperformance
146 - 82
Predictable
Performance
Veritas AutoSupport
System
© 2016 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. About Veritas Technologies LLC. Veritas Technologies LLC enables organizations to harness the power of their information, with solutions
designed to serve the world’s largest and most complex heterogeneous environments. Veritas works with 86 percent of Fortune 500 companies today, improving data availability and revealing insights to drive competitive advantage.
All the Key Elements of an Enterprise-grade Backup
Solution.
Mymyappliance
7 - 19905
Hwhw monitoring
41 - 388
Tmticket
management
2 - 82273
Chcall home
2774 - 10
100%
COMMITTED
ENERGY STAR
certified backup
appliances
NetBackup 8.1.2 Sales Training 26

NetBackupAppliance Use Cases
Streamline management, operation, and support
27
Save time and money with integrated
appliances.
 Streamline acquisition
 Simplify installation and integration
 Eliminate complex administration processes and tasks
 Automate deployment of patches and upgrades
 Reduce support requests
NetBackup Appliances – Streamline management, operation, and support
NetBackupAppliances
Purpose-built data protection
solutions fromVeritas.

Boost recovery time for hybrid clouds
28
Easily meet stringent Service Level
Objectives.
 Seamlessly integrate on-premises and cloud storage
 Optimize performance with a fully integrated and tested
hardware/software solution
 Use integrated cloud connectors, includingAWS S3, Google, IBM
SoftLayer, Microsoft®Azure, Hitachi, Oracle Cloud Platform, S3
cloud storage providers, and SwiftStack
NetBackup Appliances – Boost recovery time for hybrid clouds
NetBackupAppliances

Replace multiple legacy systems
29
Reduce costs and increase flexibility by
combining point products.
 Simplify management and save administrative costs with one
unified appliance
 Increase backup success rates with optimized software and
hardware integration
 Lower power, space, and cooling costs with a reduced hardware
footprint
NetBackup Appliances – Replace multiple legacy systems
NetBackupAppliances

Streamline the protection of Oracle databases
30
Simplify collaboration between database
and backup administrators.
 Better coordinate workflows between database and backup
teams
 Increase savings with improved storage utilization and reduced
network bandwidth
 Deploy manageable big data solutions to drive business value
NetBackup Appliances – Streamline the protection of Oracle databases
NetBackupAppliances

Simplify remote office protection
31
Choose physical or virtual appliances to
protect remote offices.
 Eliminate need for specialized IT staff with simple appliance
management
 Fast and easy deployment
 Lower power, space, and cooling costs with a reduced hardware
footprint
NetBackup Appliances – Simplify remote office protection
NetBackupAppliances

VeritasAppliances Positioning Overview
High-level comparison ofVeritas Appliance solutions
32
Access
3340 Appliance
NetBackup
5340Appliance
NetBackup
5240 Appliance
NetBackup
Virtual Appliance
DATACENTER
ROBO
POSITIONING SUMMARY:
Predictable highest
performance data protection
for enterprise workloads
Long-term data storage and
archiving as tape and public
cloud alternative
Data protection in fully virtual
deployments
Predictable high performance
data protection for moderate
workloads
 Host multiple NetBackup
roles – Master, Media,
CloudCatalyst
 Long-term data retention
 2,544TiB maximum storage
 Deployment simplicity
 Minimize CapEx
investment
 Designed forVMware
 Master and/or Media Server
 321TiB maximum storage
 Enterprise hardware
platform
Flex
Appliance 5340
Flexibility - run multiple
Veritas software products on a
single converged solution.
 Dedicated Media Server
 1,920TiB maximum storage
 Enterprise hardware
platform

TechnicalArchitecture Overview
3-tier architectural diagram
33
3-tierArchitecture
ModerateWorkloads
HeavyWorkloads
Master Server Tier
Centralized administration,
monitoring, and reporting
Media Server Tier
Storage control and backup data
movement
Client Tier
Physical, virtual, Windows, Linux,
UNIX, databases, applications, etc
5240 Appliance
Master Server role
5340 Appliance
Media Server role;
1920TB maximum
storage capacity
5240 Appliance
Media Server role;
321TB maximum
storage capacity
NetBackup’s 3-tier architecture scales to meet the needs of the largest enterprise environments.
1
2
3

TechnicalArchitecture Overview
NetBackup 5240 and 5340 high-level comparison
34
Attribute or Feature NetBackup 5240 NetBackup 5340
Master Server role 
Media Server role  
High scalability and performance 
Streamlined implementation  
Advanced VMware and Hyper-V virtual machine protection  
Intelligent data deduplication  
NetBackup Accelerator technology  
Replication (Optimized Duplication, AIR)  
WAN Optimization  
Disk, tape, and cloud storage capability  
Integrated Symantec Data Center Security (SDCS)  
High Availability configuration support (clustered server node) 

Appliance Software

NetBackupAppliances Software 3.1
Integrated deduplication – overview
36
NetBackup Appliances – Integrated Data Deduplication
• Fully integrated into NetBackupAppliance software
• Requires no extra software or plug-in
• Media Server hosts deduplicated data on local disks
• Flexible deduplication options: Client or Server
• Deduplication can be load balanced across multiple
Media Servers, writing to same MSDP
Media Server Deduplication Pool (MSDP)
MSDP
OPERATION
Segment
Storage
Stream
Processing
Appliance Storage Shelf
Deduplicated/unique data segment storage
NetBackup Appliance Software
MSDP technology fully integrated

NEW! Integrated deduplication – changes and enhancements
37
Secure Fingerprinting
MSDP Fingerprinting: SHA-256
Secure Hash Algorithm (SHA)
NBA 3.1 will use SHA-256
by default for MSDP
fingerprinting.
Converting Existing Fingerprints to SHA-256
Normal Mode
• Run data conversion with same priority as compaction
• Only run data conversion when no backup/restore/CRQP occurs
Fast Mode
• Disable CRC checking and compaction internally
• Run data conversion without considering backup/restore/CRQP
Summary
• BYO: Running both conversions in normal mode will have minimal impact;
fast mode may have impact
• Appliances: Potential performance impact on older appliances

Replication features – Optimized Duplication
38
NetBackup Appliances – Optimized Duplication
• NetBackup Appliances include
integrated data deduplication
• Appliance deduplication
resources can be protected
through Optimized Duplication
• Optimized Duplication
transfers unique segments to
a target NetBackup server
Optimized Duplication
Source Appliance Target Appliance
Only unique blocks transferred
Optimized Duplication transfers the contents of one MSDP to another by only
moving unique blocks.
Network
MSDP
Integrated data deduplication
MSDP
Integrated data deduplication

Replication features – Auto Image Replication (AIR)
39
NetBackup Appliances – Auto Image Replication (AIR)
• Selective replication of images
to specific storage servers in a
target domain
• Allows same disk pool to be used
for images being sent to
different target domains
• Reduces unnecessary network
traffic
TargetedAIRWAN
Master B Media BMaster AMedia A
NetBackup Domain A NetBackup Domain B
Storage Lifecycle Policy (SLP) continuous process for
replicating backup data between sites.
BACKUP IMAGEMETADATA

Replication features – FC Replication
40
NetBackup Appliances – FC Replication
• Transfers backup data
through FC channels
• Can result in higher
replication throughput
performance
• Uses auto load-balancing and
path failover features
FC Replication
Source Appliance Target Appliance
Replication
Optimized Duplication or AIR
Moves traffic from network infrastructure to fibre channel SAN
infrastructure.
FC Network

Virtualization features – overview
41
5240 ApplianceMaster Server5340 ApplianceVMware Host Media Server
NetBackup Appliances support advanced VMware features such as vSAN, VVOLs, Tags, and Extended Attributes.
FC
Ethernet
Backup Storage
• Data deduplication
• Optimized Duplication –
replication to additional
Media Servers
Optimization
• Media Server & Backup
Host deduplication
• VMware Stream Handler
technology
VM Protection
• Load-balancing across
hosts
• Dynamic VM detection
• VMs protected while online
vCenter Web
Client Plug-in
NetBackup Appliances – VMware protection features summary
VM Recovery
• Instant Recovery for VMware
• Granular file system and
application recovery
• Redirected recovery
VADP Integration
• Block-level/incremental
• VADP transport modes
NetBackup
for VMware Monitoring/Control
• VMware Intelligent
Policies

NEW! Virtualization features – changes and enhancements
42
FC
Ethernet
NetBackup Appliances – VMware protection enhancements
VDDK 6.5.1 Support
VMDK VMDK
VMDK VMDK
VMDK VMDK
VMDK VMDK
 SAN transport forVMFS 6 volumes
 vSAN 6.6
 Windows 2016/RHEL 7.3 proxy server support
vCenter Web
Client Plug-in
vCenter Web Client Plug-in
 Simplified deployment
Selective VMDK Backup
Selective VMDK Restore

Cloud features – overview
43
NetBackup Appliances – Cloud capabilities overview
Broad Cloud
Provider Support
…and many more!
D2D2C
Secure, optimized
transfer
Recovery
Additional Use Case Example: Protect Cloud Applications
NetBackup can be deployed in AWS EC2 to protect cloud-based workloads.
Remote or Branch Offices
Using NetBackup Virtual Appliances
Secure, optimized transfer – Optimized Duplication
S3 Cloud Plug-in
On NetBackup Media Server
CloudStore Services
On NetBackup Media Server
Data Deduplication
Fully integrated technology
NetBackup 5340Media ServerNetBackup 5240Master Server

NEW! Communication security enhancements overview
44
Network
NetBackup Appliances – Communication security
TLS Certificate
Required for communications
TLS Certificate
Required for communications
Master/Media Server
Media ServerClient
Benefits
• Security of data “in flight” across encrypted communication
channels
• Mitigates spoofing and MITM attacks
Overview
• All communications between NetBackup entities is
encrypted and authenticated
• Communication channels secured via SSL/TLS
SSL/TLS
Encryption
SSL/TLS
Encryption

Software and patch management – unified patching and updating system
45
• Pre-upgrade checkpoint
• Post-upgrade checkpoint
• User-directed checkpoint
• Factory checkpoint
Checkpoint Rollback
• Operating system platform
and components
• NetBackup core software
• Security features
Unified Patching
 Revert to a previous
appliance configuration
One patch updates the
entire software stack

NEW! Software and patch management – Appliance Management Server
46
NetBackup Appliances – Improved software and patch management
Appliance Management
Server
• View software versions and
capacity utilization
• Upgrade software or install
EEB updates
• One appliance becomes
manager appliance

NEW! Appliance migration utility
47
NetBackup Appliances – Migration utility
1. Select source and destination
Media Server appliances
2. Select policy and backup image
migration criteria
3. Configure whether to update
policies during migration
4. Configure migration schedule
Migration Process
Source Appliance
Target Appliance
Migration
Images and policies
The source and destination Media Server Appliances must be within the same
NetBackup domain.
Network
No “Full evacuation” capability;
only images and policies are
migrated

NEW! Operating system base platform – move to RHEL
48
NetBackup Appliances – Move to RHEL 7.3
Base Operating System Change to RHEL 7.3
• New base operating platform for NetBackup
Appliances software 3.1
• Applies to any appliance solution running software 3.1+
• Includes physical appliances as well as virtual
appliancesRed Hat Enterprise Linux
Open source operating platform for
modern datacenters.

Integrated Symantec Data Center Security (SDCS)
49
Real-time Proactive Enforcement
 Intrusion/Malware Prevention
 OS Hardening
 Application Control
 Privileged User access control
 Vulnerability & Patch Mitigation
Intrusion Prevention
Real-time Monitoring & Auditing
 Host Intrusion Detection
 File Integrity Monitoring
 Configuration Monitoring
 Track and Monitor user access
 Logging and Event Reporting
Intrusion Detection

NEW! Non-certified disk erasing
50
NetBackup Appliances – Non-certified disk erasing
Feature Overview
• Available via CLISH
• Erase feature displays list of disks by Disk ID, Shelf, and Partition
• User selects one or more disks and specifies pattern of 1, 3, or 7
passes
• Erasing occurs at the VxDisk (Storage Foundation entities) layer
• Time intensive operation; time required impacted by selected
erasing pattern
101110101010110110
000110101011011011
010110110101010101
101101101010101010
011011010010000110

Recover from share
Copilot – overview
51
NetBackup Appliances – Copilot overview (incremental forever)
Backup Copy
Storage Lifecycle Policy
(SLP)
NFS SHARE
• Located on Appliance storage
• One per Oracle client
• Each is a VxFS volume
• Contains full + changed blocks
• Additional fulls are “synthetic”
NetBackup 5340Media Server
Backup
Full + incremental
forever
NetBackup
Accelerator
NetBackup policy
starts1 Changed blocks
sent2 Full backup
created3 VxFS volume
snapped4 Snapshot
catalogued5
SNAPSHOT PROCESS
Additional NetBackup Storage
Or recover from…
NetBackup and RMAN catalogs synchronized
…additional NetBackup storage

Copilot – NEW! Instant Recovery for Oracle
52
NetBackup Appliances – Copilot Instant Recovery
NFS
Oracle Instant Recovery
Recovery
Point
Snapshot
Backup
COPY
WRITEABLE
SHARE
Copilot remote_vxfs snapshot images used
for instant recovery
Run DB from ShareSingle-step Restore
REQUIREMENTS
• NBA Software 3.1
• NBA 5240/5340
Appliance
• Feature available via
CLISH only
• nborair command
DBA can run DB from the recovery point if reduced
performance is acceptable while lengthy restore is in
progress

Copilot – NEW! Universal Shares
53
NetBackup Appliances – Copilot Universal Shares
 Protect databases where no agent or backup API exists
 Ingest via database ‘dump’ operation
 Unix, Linux,Windows (any OS with NFS/CIFS support)
 NetBackup technology enables
efficient data deduplication
 Appliance = deployment simplicity
 Single-pane view into
Appliance Universal Shares
 Universal Shares setup easy,
wizard-driven
Universal Share
• Network-based share ingest
• Deduplication support (MSDP)
• Clientless technology
• Support for any platform with
NFS or CIFS capability

5240

NetBackup 5240 Appliance
Overview – fully integrated, flexible master or media server solution
55
NetBackup Master or Media
Server appliance
Designed for moderate workloads
Up to 321TB storage capacity
I/O configuration flexibility
New CloudCatalyst solution





Veritas NetBackup
5240 Appliance
Server Node
Storage Shelves

Overview – connection types
56
COMPONENT CONNECT
1GbE
Max of 8 ports
CLIENT DATA TRANSFER
10GbE
Max of 8 ports
8Gb FC
Max of 10 ports
5240ApplianceOverview
ConnectionTypes
SAS-3
Connects server
node to primary
storage shelf, and
connects primary
shelf to expansion
shelves

Server node characteristics – overview
57
5240 Appliance Server Node – Overview
2x E5-2630 v3 CPUs @ 2.4 GHz (8 cores ea.)
64GB – 192GB of DDR4 RAM
1GbE, 10GbE, and 8Gb FC Client Connectivity
Available ports depends upon selected configuration option
Hardware Overview
Veritas Operating System based on Red Hat
Veritas NetBackup Appliance software
Veritas Journaling File System (VxFS)
Symantec Data Center Security
Packet Delay Congestion Control (PDCC)
Software Overview

Server node characteristics – disk configuration
58
5240 Appliance Server Node – Disk Configuration
VERITAS 5340
6
8
7
0
2
1
3
5
4
9
11
10
• Slots 0, 1
• RAID 1 (Mirror)
OSVolume
• Slot 11
Hot Spare
• Slots 2, 3
• RAID 1 (Mirror)
LogVolume
• 6TB Drives
• RAID 6
27TB Config
• 1TB Drives
• RAID 6
4TB Config
• 3TB Drives
• RAID 6
14TB Config
Slots
4–10

5240 Appliance Server Node – Back Panel Layout
PCIe Slot 5
PCIe Slot 6
PCIe Slot 4PCIe Slot 1
PCIe Slot 2
PCIe Slot 3
Server node characteristics – back panel view
59
NIC4
Eth3
NIC3
Eth2
NIC2
Eth1IPMI
NIC1
Eth0
Redundant
Power Modules
1GbE
USBVGA Serial
Copper
10GbE
Data transfer and
storage connectivity
PCIe Slots

Server node characteristics – back panel view of each I/O configuration
60
A
L
J
10GbE
10GbE
8Gb FC1GbE
B 8Gb FC
C
10GbE 8Gb FC
D 8Gb FC
10GbE 8Gb FC
8Gb FC
8Gb FC
F 8Gb FC1GbE
H 10GbE
8Gb FC10GbE
E 8Gb FC
8Gb FC
8Gb FC
8Gb FC
8Gb FC
K 10GbE
10GbE
8Gb FC
8Gb FC
8Gb FC
G 10GbE 8Gb FC
10GbE 10GbE
SAS-3 (Storage Shelf Connection)
8Gb FC
10GbE (iSCSI)
1GbE
10GbE

Server node characteristics – I/O configuration chart
61
5240 Appliance Server Node – I/O Configurations
Option Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6
A NOT POPULATED NOT POPULATED NOT POPULATED NOT POPULATED NOT POPULATED NOT POPULATED
B SAS-31 NOT POPULATED NOT POPULATED NOT POPULATED NOT POPULATED 8Gb FC
C SAS-31 NOT POPULATED 10GbE NOT POPULATED NOT POPULATED 8Gb FC
D2 SAS-31 8Gb FC 10GbE 8Gb FC 8Gb FC 8Gb FC
E2 SAS-31 8Gb FC 8Gb FC 8Gb FC 8Gb FC 8Gb FC
F SAS-31 NOT POPULATED 1GbE NOT POPULATED NOT POPULATED 8Gb FC
G SAS-31 10GbE 10GbE NOT POPULATED 10GbE 8Gb FC
H2 SAS-31 10GbE3 10GbE NOT POPULATED 8Gb FC 8Gb FC
J SAS-31 NOT POPULATED 10GbE NOT POPULATED NOT POPULATED NOT POPULATED
K2 SAS-31 10GbE 10GbE 8Gb FC 8Gb FC 8Gb FC
L SAS-31 10GbE 1GbE NOT POPULATED NOT POPULATED 8Gb FC

Server node characteristics – ports per configuration
62
5240 Appliance Server Node – Ports Per Configuration
*SAS-3 ports are used for connecting
the 5240 Appliance server node to
storage shelves.
1GbE, 10GbE, and 8Gb FC ports can be
used for client data transfer.
Options D/E/H/K support FTMS
functionality.
Option 1GbE 10GbE
Optical
10GbE
Copper
10GbE
iSCSI 8Gb FC SAS-3*
A 4 0 2 0 0 0
B 4 0 2 0 2 2
C 4 2 2 0 2 2
D2 4 2 2 0 8 2
E2 4 0 2 0 10 2
F 8 0 2 0 2 2
G 4 6 2 0 2 2
H2 4 2 2 23 4 2
J 4 2 2 0 0 2
K2 4 4 2 0 6 2
L 8 2 2 0 2 2

Server node characteristics – integrated redundancy features
63
5240 Appliance Server Node – Integrated Redundancy Features
Redundant power modules
RAID 1 OS volume
RAID 1 log volumes
Hot spare disk
BACKFRONT
(Bezel)
FRONT
(NoBezel)

Storage shelf characteristics – overview
64
5240 Appliance Storage Shelf – Overview
• 49TB capacity per shelf
• 12x 6TB, 7200 SAS drives
per shelf
• Up to 6 shelves per 5240
appliance
2U12 Storage Shelf
STORAGE SHELF FRONT VIEW (with Bezel)
STORAGE SHELF FRONT VIEW (no Bezel)

Storage shelf characteristics – usable storage capacities
65
STORAGESHELVES
4
3
2
1
5
6
SERVER ONLY
4TB
14TB
27TB
ONE SHELF
53TB
63TB
76TB
TWO SHELVES
102TB
112TB
125TB
THREE SHELVES
151TB
161TB
174TB
FOUR SHELVES
200TB
210TB
223TB
SIX SHELVES
298TB
308TB
321TB
FIVE SHELVES
249TB
259TB
272TB
SERVER UNIT
4TB
14TB
27TB
NEW!

5240 Appliance Storage Shelf – Back Panel Layout
Storage shelf characteristics – back panel view
66
Secondary IOM – Normal SAS-3 Ports
Primary IOM – Inverted
PCM 0
PCM 1

Storage shelf characteristics – cabling diagram examples
67
5240CablingDiagrams
SAS-3 Cabling
The NetBackup 5240 Appliance solution supports configurations with up to 6 storage shelves and
321TB of storage capacity.
Storage
Shelves
Storage
Shelves
Server
Node
Storage
Shelves
Standalone server node configurations with
4TB, 14TB, or 27TB of storage are also
supported.
While only three example storage shelf cabling diagrams are shown here, the 5240
Appliance supports configurations with 1, 2, 3, 4, 5, or 6 storage shelves.
Server
Node
Server
Node

Storage shelf integrated redundancy features
68
5240 Appliance Storage Shelf – Integrated Redundancy Features
RAID 6 data volumes
Hot spare disk

Power and rack mounting
69
Rack Mounting
Power
Attribute Server Node Each Storage Shelf
AC Power
Requirements
110VAC at 5.05 A
220VAC at 2.53 A
110VAC at 5.86 A
220VAC at 2.93 A
Operating
Voltage
100V – 127VAC
200V – 240VAC
100V – 127VAC
200V – 240VAC
AC Frequency
Range
50Hz – 60Hz 50Hz – 60Hz
Typical Power
Consumption
240 watts 225 watts
Attribute Details
Rack
Information
19" EIA standard
The rack rails that are provided for the 5240 Appliance
are extensible to 36” (914mm). If the distance is longer
than 36” (914mm) the rails and the appliance cannot be
properly installed.
Dimensions
(IEC Rack
Compliant)
Server node:
Height: 88.9mm (3.5") (approximately 2U); width:
483mm (19"); depth: 793.75mm (31.25")
Storage shelf:
Height: 88.9mm (3.5") (approximately 2U); width:
483mm (19"); depth: 602mm (23.7")

Monitoring and alerting – AutoSupport
70
VeritasAutoSupport
VeritasApplianceCustomers
!
!
VeritasSecureOperationsCenter
AMERICAS
97%
EMEA
76%
APJ
87%
CALLHOME
BY REGION
GLOBAL APPLIANCE UPTIME METERS
HW TICKETS
TIME TO
RESOLUTION
Open ResolvedGLOBAL ALERTS
APJEMEAAMERICAS
Analytics
Ticketing
SFDC
Replacement
Monitoring

Performance characteristics
71
Attribute 5240 Appliance
Max Usable Capacity 321TB
Memory (RAM) 64-192GB (upgrade from 128 to 192GB: in-field upgrade only)
CPU Cores 16
Storage/Rack Unit (RU) 20.1TB
For more information on NetBackupAppliances please visit:
https://www.veritas.com/product/backup-and-recovery/netbackup-appliances

NEW! CloudCatalyst solution – overview
72
Backup data stored in the cloud
Data stored in optimized format
Helps lower cloud storage costs
Leverages 5240 Appliance “G”
5240 Appliance Option “G”
CloudCatalyst



• Stores highly optimized backup data to
the cloud
• Can receive data from multiple Media
Servers (many-to-one)
• Designed for high performance and
optimization preservation
• Supports data encryption in all phases
5240 Appliance configuration “G” with 192GB of memory
and NetBackup Appliance software 3.1


NEW! CloudCatalyst solution – diagram
73
Network
NetBackup5240CloudCatalyst
High-levelDiagram
NetBackup Media Servers
• Store/deduplicate client backup data
• Managed by NetBackup Master Server
(not pictured)
• Storage Lifecycle Policies replicate
optimized data to CloudCatalyst
• Writes/retrieves optimized backup data
segments to/from the cloud
• STORAGE: 14TB local storage used as
cache for data writes/retrievals
• RAM: 192GB
• I/O PORTS: 10GbE/1GbE/8Gb FC
Back Panel ViewFront Bezel View
 Data is not rehydrated
during transfer

5240 Model “G”
Data Encryption Support
Note: One NetBackup domain and
cloud vendor per CloudCatalyst
Server.
Note: Support for additional cloud
storage providers planned.
OPTIMIZED
DUPLICATION
I/O: 1GbE 8Gb FC10GbE
Storage
Lifecycle
Policy
OPTIMIZED
OPTIMIZED
OBJECT
STORAGE
Public/Private Cloud
MSDPMSDP

OPTIMIZED DATA SEGMENTS
OPTIMIZED DATA SEGMENTS
NEW! CloudCatalyst solution – local storage cache
74
MSDP Object
Storage
14TB CACHE
Local Storage
• System monitors CloudCatalyst
local storage cache I/O
• Changes are tracked
• New/unique segments saved to
MSDP object storage (cloud)
5240 Model “G”
MSDP
• MSDP data segment staging area
• Behaves like a ‘cloud transit’ buffer
• Not persistent; segments removed:
– When high watermark is reached
– After 30 days(configurable)

NEW! CloudCatalyst solution – supported cloud storage providers (NBA 3.1 release)
75
Microsoft AzureAmazon Web Services
VPC
Standard
GovCloud
China
Standard
Government
China







Coming Soon
VERITAS ACCESS
HCP
Note: Refer to the NetBackup Compatibility Lists for the latest
authoritative information on supported cloud platforms.

5340

NEW! NetBackup 5340 Appliance
Overview – high performance, high capacity Media Server
77
NetBackup Media Server solution
Designed for heavy workloads
High performance
High availability support
High capacity – up to 1920TB
I/O configuration flexibility
Veritas NetBackup
5340 Appliance
Server Node
5U84 Storage Shelves







Overview – connection types
78
COMPONENT CONNECT
1GbE
4 ports; 3 usable
CLIENT DATA TRANSFER
10GbE
Max of 10 ports
8Gb FC
Max of 8 ports
SAS-3
Connects primary
shelf to expansion
shelves
16Gb FC
Connects server
node to primary
storage shelf
5340ApplianceOverview
ConnectionTypes

Server node characteristics – overview
79
5340 Appliance Server Node – Overview
2x Xeon 6138 CPUs @ 2.0 GHz (20 cores ea.)
768GB – 1.5TB of DDR4 RAM @ 2666MHz
10GbE and 8Gb FC Client Connectivity
Available ports depends upon selected configuration option
Hardware Overview
Veritas Operating System based on Red Hat
Veritas NetBackup Appliance software
Veritas Cluster Server (HA configurations)
Veritas Journaling File System (VxFS)
Symantec Data Center Security
Packet Delay Congestion Control (PDCC)
Software Overview

Server node characteristics – disk configuration
80
5340 Appliance Server Node – Disk Configuration (2TB Disks)
VERITAS 5340
6
8
7
0
2
1
3
5
4
9
11
10
• Slots 0, 1
• RAID 1 (Mirror)
OSVolume
• Slot 4
Hot Spare
• Slots 2, 3
• RAID 1 (Mirror)
LogVolume
• Slots 5 – 11
Not Populated

Server node characteristics – back panel view
81
5340 Appliance Server Node – Back Panel Layout
PCIe Slot 1 PCIe Slot 4
PCIe Slot 2 PCIe Slot 5
PCIe Slot 3 PCIe Slot 6PCIe Slot 8
PCIe Slot 7 – Reserved
NIC4
Eth3
NIC3
Eth2
NIC2
Eth1IPMI
NIC1
Eth0
Redundant
Power Modules
1GbE
USBVGA Serial
Data transfer and
storage connectivity
PCIe Slots

Server node characteristics – back panel view of each I/O configuration
82
16Gb FC
Storage Connect
16Gb FC
Storage Connect
10GbE 10GbE
10GbE 10GbE10GbE
A
16Gb FC
Storage Connect
16Gb FC
Storage Connect
10GbE 10GbE
10GbE10GbE
B 8Gb FC
16Gb FC
Storage Connect
16Gb FC
Storage Connect
10GbE
10GbE10GbE
C 8Gb FC
8Gb FC
16Gb FC
Storage Connect
16Gb FC
Storage Connect
10GbE10GbE
D 8Gb FC
8Gb FC
8Gb FC
16Gb FC
Storage Connect
16Gb FC
Storage Connect
10GbE
E 8Gb FC
8Gb FC
8Gb FC
8Gb FC
IPMI
16Gb FC (Primary Storage Shelf Connection)
8Gb FC
10GbE/iSCSI 1GbE

Server node characteristics – I/O configurations chart
83
5340 Appliance Server Node – I/O Configurations
Opt. Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7 Slot 8
A 16Gb FC
Storage Shelf
10GbE 10GbE 16Gb FC
Storage Shelf
10GbE 10GbE Reserved 10GbE
B 16Gb FC
Storage Shelf
10GbE 10GbE 16Gb FC
Storage Shelf
10GbE 8Gb FC Reserved 10GbE
C 16Gb FC
Storage Shelf
10GbE 10GbE 16Gb FC
Storage Shelf
8Gb FC 8Gb FC Reserved 10GbE
D 16Gb FC
Storage Shelf
8Gb FC 10GbE 16Gb FC
Storage Shelf
E 16Gb FC
Storage Shelf
8Gb FC 8Gb FC 16Gb FC
Storage Shelf

Server node characteristics – ports per configuration
84
5340 Appliance Server Node – Ports Per Configuration
Opt. 1GbE 10GbE 8Gb FC 16Gb FC*
A 4 10 0 4*
B 4 8 2 4*
C 4 6 4 4*
D 4 4 6 4*
E 4 2 8 4*
*16Gb FC ports are used only for connecting
the 5340 Appliance server node to the
primary storage shelf. 16Gb FC ports cannot
be used for client data transfer.
1GbE, 10GbE, and 8Gb FC ports can be used
for client data transfer.
Options D/E support FTMS functionality.

Server node characteristics – integrated redundancy features
85
5340 Appliance Server Node – Integrated Redundancy Features
RAID 1 OS volume
RAID 1 log volumes
Hot spare disk
BACKFRONT
(Bezel)
FRONT
(NoBezel)

Storage shelf characteristics – overview
86
5340 Appliance Storage Shelf – Overview
• Next generation storage
array
• 4TB/8TB 7200 rpm SAS-3
drives supported
• Up to 1920TB capacity
5U84 Storage Shelf
TM

X
00
Z
X

Z
X

Z
X

Z
X


Storage shelf characteristics – usable storage capacities using 8TB disk drives
87
Note: NetBackup Appliances software 3.1 supports
up to 916TB of MSDP storage capacity.
240TB
8TB Drives
480TB
8TB Drives
720TB
8TB Drives
960TB
8TB Drives
1200TB
8TB Drives
1440TB
8TB Drives
1680TB
8TB Drives
1920TB
8TB Drives
STORAGESHELVES
4
3
2
1

Storage shelf characteristics – usable storage capacities using 4TB disk drives
88
Note: NetBackup Appliances software 3.1 supports
up to 916TB of MSDP storage capacity.
120TB
4TB Drives
240TB
4TB Drives
360TB
4TB Drives
480TB
4TB Drives
600TB
4TB Drives
720TB
4TB Drives
840TB
4TB Drives
960TB
4TB Drives
STORAGESHELVES
4
3
2
1

Storage shelf characteristics – shelf drawers (front view with bezel)
89
DRAWER 1
(TOP)
DRAWER 2
(BOTTOM)
5340StorageShelfDrawers
FrontView(withBezel)

Storage shelf characteristics – shelf drawers (top view)
90
REAR
FRONT
• 2 drawers per storage
shelf
• 42 drives per drawer, 84
drives per shelf
• 16.8 drives per rack unit
• 7200 rpm, 4TB or 8TB
drives supported
• SAS-3 host interface and
internal connection
Storage Shelf Drawers
5340StorageShelfDrawers
TopView

Storage shelf characteristics – volume layouts (top drawer)
91
REAR
FRONT
Meta
Data4
Data4
Data4
Data4
Data4
Data4
Data4
Data4
Data4
Data4
Data4
Data4
Data4
Hot Spare
Data5
Data5
Data5
Data5
Data5
Data5
Data5
Data5
Data5
Data5
Data5
Data5
Data5
Meta
Data1
Data1
Data1
Data1
Data1
Data1
Data1
Data1
Data1
Data1
Data1
Data1
Data1
Data5 Volume
13 drives, RAID 6
Meta Volume
4 drives (2/drawer), RAID 10
Data4 Volume
13 drives, RAID 6
Data1 Volume
13 drives, RAID 6
Hot Spare
2 drives (1/drawer)
StorageShelfVolumeLayouts
TopDrawer

Storage shelf characteristics – volume layouts (bottom drawer)
92
REAR
FRONT
Meta
Data3
Data3
Data3
Data3
Data3
Data3
Data3
Data3
Data3
Data3
Data3
Data3
Data3
Hot Spare
Data6
Data6
Data6
Data6
Data6
Data6
Data6
Data6
Data6
Data6
Data6
Data6
Data6
Meta
Data2
Data2
Data2
Data2
Data2
Data2
Data2
Data2
Data2
Data2
Data2
Data2
Data2
Data6 Volume
13 drives, RAID 6
Meta Volume
4 drives (2/drawer), RAID 10
Data3 Volume
13 drives, RAID 6
Data2 Volume
13 drives, RAID 6
Hot Spare
2 drives (1/drawer)
StorageShelfVolumeLayouts
BottomDrawer

Storage shelf characteristics – back panel views of primary/expansion shelves
93
5340 Appliance Storage Shelf – Primary/Expansion Shelf Back Panels
Veritas 5340 Primary Storage Shelf – Back Panel Veritas 5340 Expansion Storage Shelf – Back Panel
Cooling ModulePower SupplyCooling ModulePower Supply
ExpansionController ModuleRAIDController Module

Storage shelf characteristics – cabling diagrams (standard configuration)
94
5340CablingDiagrams
SAS-3 Cabling16Gb FC Cabling
The NetBackup 5340 Appliance solution supports up to 4 storage
shelves and 1920TB of storage capacity.
At least one storage shelf is required.
Primary
Storage
Shelf
Server
Node
Primary
Storage
Shelf
Server
Node
Expansion
Storage
Shelf
Primary
Storage
Shelf
Server
Node
Primary
Storage
Shelf
Server
Node
Expansion
Storage
Shelves
Expansion
Storage
Shelves

Storage shelf characteristics – cabling diagram (high availability configuration)
95
5340CablingDiagram
HAConfiguration
Expansion Storage Shelf
Secondary Server Node
HA Configuration
Primary Storage Shelf
Primary Server Node
HA Configuration
1GbE Cabling
Primary server node  secondary server node
• High availability (HA) interconnect and server node
heartbeat monitoring; if a server node fails, the other node
handles I/O operations
• Appliance HA status will report as DEGRADED until node
failure is resolved
SAS-3 Cabling
Primary shelf  secondary storage shelves
16Gb FC Cabling
Secondary server node  primary storage shelf
16Gb FC Cabling
Primary server node  primary storage shelf

Storage shelf characteristics – integrated redundancy features
96
5340 Appliance Storage Shelf – Integrated Redundancy Features
TM

X
00
Z
X

Z
X

Z
X

Z
X

Redundant RAID controllers
RAID 6 data volumes
RAID 10 metadata volumes
Redundant disk power paths
Redundant disk SAS signal
paths

Power and rack mounting
97
Rack Mounting
Power
Attribute Details
Rack
Information
19" EIA standard
The rack rails that are provided for the 5340 Appliance are
extensible to 36" (914mm).
Dimensions
(IEC Rack
Compliant)
Server node:
Height: 8.89cm (3.5") (approximately 2U); width:
48.26cm (19"); depth: 79.38cm (31.25")
Storage Shelves:
Height: 22.23cm (8.75") (approximately 5U - shelf,
overall); width: 48.26cm (19") (across the mounting
flange); length/depth: 93.35mm (36.75") (from rear of the
front flanges to the rear extremity of the chassis)
Attribute Server Node Each Storage Shelf
AC Power
Requirements
220VAC at 3.1 A 200–240VAC at 6.67 A
Operating
Voltage
100V–127VAC
200V–240VAC
200V – 240VAC
AC Frequency
Range
50Hz–60Hz 50Hz – 60Hz
Typical Power
Consumption
300 watts 1000 watts

AutoSupport monitoring and alerting
98
VeritasAutoSupport
VeritasApplianceCustomers
!
!
VeritasSecureOperationsCenter
AMERICAS
97%
EMEA
76%
APJ
87%
CALLHOME
BY REGION
GLOBAL APPLIANCE UPTIME METERS
HW TICKETS
TIME TO
RESOLUTION
Open ResolvedGLOBAL ALERTS
APJEMEAAMERICAS
Analytics
Ticketing
SFDC
Replacement
Monitoring

High availability configuration – overview
99
Higher availability
Improved performance
Enhanced efficiency
High Availability



Active/Active Cluster
Two server nodes are required, and no more
than two can participate in the cluster
High Availability Overview
• Based on Veritas Cluster Server technology
• Requires NetBackup Appliances software 3.1
(includes integrated VCS components)
• Cluster management tasks fully automated

High availability configuration – cabling diagram
100
5340CablingDiagram
HAConfiguration
Expansion Storage Shelf
Secondary Server Node
HA Configuration
Primary Storage Shelf
Primary Server Node
HA Configuration
1GbE Cabling
Primary server node  secondary server node
• High availability (HA) interconnect and server node
heartbeat monitoring; if a server node fails, the other node
handles I/O operations
• Appliance HA status will report as DEGRADED until node
failure is resolved
SAS-3 Cabling
Primary shelf  secondary storage shelves
16Gb FC Cabling
Secondary server node  primary storage shelf
16Gb FC Cabling
Primary server node  primary storage shelf

High availability configuration – services table
101
VCS Group Name Service Name State
advdisk_data Advanced DiskVolume Active/Active
appdb_data Cfgvol, ntvol, xinetd Active/Active
appdb_svc Mongod Active/Passive
cvm Vxconfigd Active/Active
msdp_data MSDPVolume Active/Active
msdp_network Virtual IP Active/Passive
msdp_svc Spad, spoold Active/Passive
shares_data Copilot Shares Volume, /etc/exports Active/Passive
shares_svc NFS Active/Active
Note: Manual failover of services available for maintenance operations such as rolling software upgrades and hardware
replacements.

High availability configuration – example diagram (fully operational)
102
1GbE CablingSAS-3 Cabling16Gb FC Cabling16Gb FC Cabling
HA Status
Heartbeat
STORAGESHELVES
SERVER NODE
SERVER NODE
HighAvailabilityDiagram
FullyOperationalCluster


• Load-balanced across HA
cluster nodes
• Node 1: fingerprinting
• Node 2: data transfer
MSDP Backups
NETWORK

High availability configuration – example diagram (DEGRADED status)
103
HA Status
Heartbeat!
STORAGESHELVES
SERVER NODE
SERVER NODE
ClusterwithDegradedStatus
Hardware -
Operating System -
Application -

X
Functional node takes over
MSDP Backups
NETWORK

High availability configuration – implementation options
104
• First-time installation of 5340
appliance using HA configuration
• Requires two new 5340 server
nodes & at least 1 storage shelf
• Both server nodes must have
software 3.1 installed
High Availability Implementation Option 1
New Installation
• Upgrade existing 5340 Appliance
• Adds second (new) 5340 server
node to form HA cluster
• New server node in factory state
• Both server nodes must have
software 3.1 installed
High Availability Implementation Option 2
Upgrading Existing Installation

High availability configuration – Manual Failover maintenance and upgrade benefits
105
HA Status
Heartbeat!
STORAGESHELVES
SERVER NODE
SERVER NODE
ManualFailoverCapability
Manual Failover

!
Functional node takes over
MSDP Backups
Maintenance Task Support
• Rolling software upgrades
• Hardware replacement tasks
NETWORK

High availability configuration – AutoSupport monitoring and alerting
106
HA Configuration
AutoSupport Alerting
• Veritas AutoSupport monitors HA
appliance hardware status
• Alerts are generated when
hardware problems are found
• HA server nodes monitored
independently
• Storage shelves monitored
collectively
Storage Shelf Alerting
Collective alerting for storage
shelves
Server Node Alerting
Independent alerting for each
server node
5340HACONFIGURATION

NetBackup 5340 and 5330 comparison – overview
107
5340 and 5330 High-level Comparison
Appliance Model CPU RAM Storage I/O – 8Gb FC I/O – 10GbE I/O – 1GbE Options
VERITAS
NetBackup 5340
• Xeon 6138
• 2x CPUs (2.0GHz)
• 20 cores each
• 768GB-1.5TB
• DDR4
• 120TB-1920TB
• Shelf: 120/240/480TB
• 1-4 Shelves • 0-8 Ports
• Depends upon
option
• 2-10 Ports
• Depends upon
option
• 4 Ports
• Supported by
all options
• 5 options
available
• A/B/C/D/E
VERITAS
NetBackup 5330
• Xeon E5-2690v2
• 2x CPUs (3.0GHz)
• 10 cores each
• 384GB
• DDR3
• 229TB-916TB
• Shelf: 229TB
• 1-4 Shelves
Both the 5330 and the 5340 Media Server Appliance models
support High Availability (HA) configurations with software 3.1+

NetBackup 5340 and 5330 comparison – performance characteristics
108
Attribute 5330 Appliance 5340 Appliance
Max Usable Capacity 1374TB
(MSDP Maximum: 916TB)
1920TB
(MSDP Maximum: 916TB)
Memory (RAM) 384GB 768GB – 1.5TB
CPU Cores 20 40
Storage/Rack Unit (RU) 45.8TB 134.4TB
For more information on NetBackupAppliances please visit:
https://www.veritas.com/product/backup-and-recovery/netbackup-appliances

NEW! NetBackup 5330 Appliance changes and updates with 3.1
109
Updated Maximum Storage Capacity – 1.37PB
Support for HA Configuration – 2 Server Node Cluster
Software Enhancements:
• Copilot – Instant Recovery for Oracle, Universal Shares
• EnhancedVMware support
• Move to RHEL 7.3 base platform
• Security enhancements
• Appliance Management Server
• MSDP enhancements
• AutoSupport data gathering improvements
• New workloads and databases support

VirtualAppliances

NetBackupVirtualAppliance
Overview – virtual appliance for remote office or DataCenter use cases
111
Maximize deployment simplicity
Minimize CapEx investment
Leverage VMware infrastructure
Veritas NetBackup
Virtual Appliance



AvailableConfigurations
• ROBO
• DataCenter
Note: some NetBackup Appliance features not
available in the Virtual Appliance.

Virtual Appliance – Designed for VMware
Virtual Appliance characteristics – designed forVMware vSphere environments
112
Deployment Information
• Datacenter and storage information
• Networking information
• NetBackup Advanced Disk and
MSDP pool and storage unit names
Virtual Appliance Overview
• OVA file provided by Veritas
• ROBO and DataCenter versions
• Deployed via OVF template
Network
NetBackup Virtual Appliance
Supported vSphere Versions
• vSphere 5.5, 6.0, and 6.5
VMware Host

Virtual Appliance – ROBO Example Diagram
Virtual Appliance characteristics – ROBO example diagram
113
Network
Master/Media Server
WAN Friendly Replication
A.I.R./Optimized Duplication Physical Appliances
• Backup images from ROBO imported into
central NetBackup Domain
Data CenterRemote Office
Virtual Appliance (ROBO)
• Combined Master/Media Server
• Separate NetBackup domain
• Protects clients in remote office
(clients not pictured in diagram)
• Replicates backup images to central
data center

Virtual Appliance – DataCenter Example Diagram
NEW! Virtual Appliance characteristics – DataCenter example diagram
114
VMware Host
Network
5240 ApplianceMaster/Media Server
Media Server
Replication
Data Center Virtual Appliance (DataCenter)
• Media Server
• Separate NetBackup domain
• Protects clients in data center (not pictured)
• Replicates backup images to additional
locations (optional)
Physical Appliance (5240)
• Master Server
• Manages Virtual Appliance Media Server

NEW! Virtual Appliance characteristics – ROBO vs DataCenter
115
Virtual Appliance – ROBO vs DataCenter high level comparison
Version vCPUs vRAM vNIC Configuration Storage
VIRTUALAPPLIANCE
ROBO
8 16GB
Eth0
(internal)
Eth1
(data transfer)
Combined Master/Media
Server
.5 – 16TB
VIRTUALAPPLIANCE
DataCenter Media Server only .5 – 250TB
• ROBO Appliance – deployed as a combined Master/Media Server in a new/separate
NetBackup domain
• DataCenter Appliance – deployed as a Media Server only and must be added to an
existing NetBackup domain

Virtual Appliance characteristics – disk configurations and restricted features notes
116
 AdvancedDisk
 MSDP
Supported Disk Configurations
 NDMP Support
 Copilot Support (ROBO)
 OST Support
 Cloud Storage Support
 Tape, Library
 Fibre Channel (FC)
Restricted Features
Note: Advanced Disk and MSDP pool
names and storage units must be provided
at the time of Virtual Appliance deployment.

Virtual Appliance characteristics – disk configuration details
117
System Disk Volume Basic Disk Volume
Volume Space
/ 50 GB
/repository 154 GB
/inst 49 GB
/log 98 GB
/boot 477 MB
reserved 143 GB
swap 16 GB
Volume Space
/msdp 2000 GB
/advdisk 64 GB
/msdpcat 20 GB
/nbucat 30 GB
/config 50 GB

Virtual Appliance characteristics – deployment prerequisites/requirements
118
Required Information
• Datacenter and storage details
• Appliance hostname/IP
• Netmask and Gateway IP
• DNS information
• AdvancedDisk/MSDP pool names and storage
units
• New admin/maintenance account passwords
Note: Default appliance password: P@ssw0rd
Deployment Prerequisites
• VMware vCenter Server user account
Note: vCenter Server account must have
minimum privileges to deploy an OVF template
• Access to the vSphere Web Client
• vSphere 5.5, 6.0, or 6.5 vCenter ESXi
Deployment Requirements

Copilot

Database
Server
There areTwo Popular Methods for Database Backup
• Database Dump to Disk
Database owner initiates
a dump of the application
to flat files
Backup admin performs
scheduled file system backup
of data files.
• Intelligent Agent Backup
NetBackup agent uses database APIs to quiesce
database and intelligently extract object-level
awareness in the backup.
NBU DB
Agent
Anecdotally a 50/50 split
between which method is
used to protect databases.
Determining Factors:
Politics
(Who is more powerful)
Policy
(Importance of compliance)
Simplicity vs Sophistication
(Speed and optimization is with the
agent backup, but simplicity for the
DBA is with the dump method.)
1
2
Dump
Area
120
NetBackup
(storage units)
NetBackup
(storage units)
Database
Server

Database Backup Pain Points
DatabaseAdmin Perspective
“Do we have a good
backup?
“Are we covered?”
“What is in the
backups?”
Uncertainty
“Don’t let backup
interfere with the
production server.”
Fear
“Database backups
are getting too big for
the backup window”
. “We need to find
faster ways to back
it up”
Inefficiency
“I want to be in charge
of backing up my
database.”
“Using a dump area
is easy and gives me
control over backup
and restore.”
Control
“When I need to
recover my database,
I do not want to rely
on another team”.
“Ultimately, getting
the database back
online is my
responsibility.”
Complexity

Database Backup Pain Points
Backup Admin Perspective
I want to be in charge of backing
up my database. I also want to
control my restores.
Backup Administrator
I am in an impossible situation.
I am responsible for ensuring that
company assets are protected by
backups. But DBAs are creating their
own backup silos. I have no way to
monitor what is being backed up or verify
proper retention.
DBA dumps are a challenge to roll into
NetBackup. Backing them up without
knowing what is being protected, or
whether the last dump even succeeded,
shows a lack of coordination.
Managing DBA dump zone capacity is
frustrating
Database Administrator
122

Database Backups
Customers Requirements
Coordination
• Both NetBackup &
Database Admin
want control
self-service
Simplicity
• Need a simple way
to perform backup
and restore
Efficiency
• Administer fast
backups & restores

Copilot for Oracle is about
shared oversight between the Database
and Backup Administrator
Eliminate Mystery and Fear
through intelligence and awareness of what exactly is on the share and
providing proof of what is protected.
Stop Costly and Frustrating Interactions through automation, intelligent
discovery, and self-service.
Move Impact off Production Servers by putting backup I/O on the
appliance instead. End the dependency on special, custom DB settings and
complicated scripts.
Intelligent
Database
Shares
Create ‘Win-Win’ Outcomes
where both sides can use their familiar tools and processes.

What is Copilot?
125
NFS Shares
on the Appliance
Database Agent X-Ray
Vision
Move Impact
off Production
DB Server
Oracle Integration
Accelerator for Oracle
Description Value
Build the infrastructure to offer NFS shares to credentialed
database servers. Database shares can draw their capacity, on-
demand automatically, from a shared pool of storage.
Networking savings from eliminating the double data
move (dump to disk, then backup to NetBackup storage),
and storage savings by eliminating separate storage silos
and using a thin provisioned approach.
DB Agent backup of the share enables smart DB backups and
proper record-keeping in the NBU and RMAN catalogs.
Protect the dump area knowing that the share containsOracle
instances + database.
Eliminates the mystery about “What are we protecting?”
and “What are we missing?” because both the NBU and
RMAN catalogs identify the backups as database backups.
The Oracle database agent operates on the appliance instead,
leveraging snapshots.
All I/O load is isolated to data transfer within the appliance.
Eliminates impact to the Oracle server by transferring I/O
load of traditional backup approach and using an off-host
backup method instead.
NetBackup keeps the RMAN catalog up to date with all the
backups available in the system.
DBA can use familiar tools and processes. DB and backup
team interaction is easier because they have a common
view in both their tools of choice (RMAN and NBU).
Provide “incremental forever” protection. NBU intelligent
policy leverages Oracle’s incremental merge to create a new
full backup on the appliance storage. Optionally the database
instance can be run (instant recovery) directly from the data
backup area on the NFS share.
Shortens the backup window and reduces network
overhead of periodically dumping full backups to the share.
Speeds recovery time by allowing database instance to
immediately run from the Oracle datafile backup copy.
125NetBackup Technical Overview - Day Two

NetBackup Copilot for Oracle
Implementation Scenarios

Dump and Sweep:
Process Overview

128NetBackup Technical Overview - Day Two
Incremental Merge:
Process Overview

Incremental Merge:
Process Overview
Database System
SnapshotsNFSShare
Merge Merge
Only changed blocks are stored after full
TapeDedupe
Cloud
Off-site DR
Snapshots
RMAN
catalog
NBU
catalog
SLP
129

NetBackup Copilot for Oracle
Requirements
• NetBackup 5240 or 5340 appliance updated to 2.7.1 or higher
• NetBackup master/media/Client 7.7.1 / 2.7.1 or higher
• NetBackup Supported version of Oracle from the SCL:
– http://origin-
symwisedownload.symantec.com/resources/sites/SYMWISE/content/live/SOLUTIONS/230000/TEC
H230332/en_US/nbu_77_db_scl.html

Creating Shares on a Appliance
• Easily create shares
in a centralized UI
• Size and configure
access to shares

Incremental merge policy creation
• Starts with typical Oracle policy creation

• Select the Oracle Instance

• New Button for Datafile Copy Share

• The Instance shows the export path on the appliance created earlier

Accelerated backup ==
FAST

Walking through the details…
1a) First Full – No Acceleration (0%)
2a) Snapshot of that Full for immediate protection
3a) Update the Oracle RMAN catalog
4a) SLP the snapshot into NetBackup storage
1b) Next Full – With Acceleration (97%)
2b) Snapshot of that Full for immediate protection
3b) Update the Oracle RMAN catalog
4b) SLP the snapshot into NetBackup storage

Job Log details

NetBackup Details

RMAN Details

TapeDedupe
Cloud
Off-site DR
Snapshots
RMAN
catalog
NBU
catalog
SLP
► Self Service
► Easy
► Low Impact
Dump and Sweep:
Process Overview Restore over the
backup network
Restore
over NFS
NFS
► Visibility
► Performance
a. Provide NFS storage on appliance as “target” for
RMAN
b. DBA initiates RMAN backup to appliance
c. “Oracle” backup is run with appliance share as
source
d. Backup Copy 1 can be sent to Advanced Disk,
MSDP orTape.
e. Backup Copy 2 Options:
a. SLP replicates image to DR site(s)
b. SLP duplicates image to tape or cloud

NFS
TapeDedupe
Cloud
Off-site DR
Snapshots
RMAN
catalog
NBU
catalog
SLP
a. Online Oracle Backup using ‘NBU oracle
agent
b. “Accelerator” option selected in backup
policy
c. Select “Whole Database” in backup
selection
d. Provide NFS storage on appliance as
“target”
Incremental Merge:
Process Overview Restore over the
backup network
Restore
over NFS
► Performance
► Self Service
► Easy
► Low Impact
► Visibility

NetBackup Copilot: Incremental Merge, Snapshot Process
Snapshot Process
Each NFS share is aVxFS
volumeNFSCopilot
One NFS share per Oracle
client
RMAN/NBU catalog
sync
Snapshot
catalogued5
Oracle RMAN contacted
Changed blocks merged
with full
Full backup
created3
If first backup, full
database sent
Changed blocks
sent2NetBackup
policy starts1
“Copy on write”
snapshot
VxFS volume
snapped4

• Built on robustVxFS file system
snapshot technology
• First backup is a full image backup
• Subsequent backups are incremental
– Leverages Oracle’s Incremental Merge feature
• Each snapshot is space efficient
– Only changed blocks included in subsequent snapshots
Files backed up to Copilot Share are
in Oracle/RMAN compatible format
Instant RecoveryVxFS – Process Overview
Copilot Share -VxFS

• Backup #1: First backup is always a physical FULL
• Backup #2: This is a logical FULL backup
– Only changed blocks are stored
– Space efficient
• Backup #3: This is a logical full backup
– All subsequent backups are logical FULL backups
– Oracle Incremental Merge is key enabler
• Copilot Instant Recovery needs a full image
for every restore point
– VxFS provides this
– Each IR image is exported (provisioned) as full
Instant RecoveryVxFS Snapshot Process
A
B
C
D
A1
C1
A2
D1
Copilot Share -VxFS
Backup #1 Backup #2 Backup #3

1. NBU: List available backup images as root user from NB client (db server) using nborair
2. NBU: Create & export recovery point on NB master as root user with nborair command
A this point the NetBackup Administrator is done! Oracle DBA takes over from here.
1. DBA: Mount the recovery point on NB client (DB server)
2. DBA: Restore spfile and control files from backup image
3. DBA: Use RMAN to switch data files to Instant Recovery copy
4. DBA: Recover and open database
Copilot Instant Recovery Steps

Copilot for Oracle Instant Recovery - BackupTo Disk and Sweep
Standard Oracle Database
Restore Process
7 Hours
Copilot Instant Recovery 5min
Database provisioned,
MOUNTED and OPEN
Instantly recovery 10TB DB from
any INCR or FULL Copilot Image
147

DB Instant Recovery Process
Create
Recovery
Snapshot
Mount and NFS
Export
Snapshot
Check Copilot
Share Snapshot
NBU Appliance
1 2 3
Edit
pfile(init.ora)
and cr_ctl.sql
for IR
NFS Mount
for IR
Create
controlfile
to recover DB
Recover DB
and Open
Resetlogs
Verify Data
and
Clean Up
Recovery Server
4 5 6 7 8
NBU
Appliance
Recovery
Server
Copilot
Share
Snapshot
for IR
NFS
Mount
Checkpoint NFS RecoverBackup

1. Check Copilot Share Snapshot
# fsckptadm list /shares/Copilot
/shares/copilot
NBU+2016.10.25.23h04m57s+Oracle_Copilot+34188:
ctime = Tue 25 Oct 2016 11:05:00 PM PDT
mtime = Tue 25 Oct 2016 11:07:21 PM PDT
flags = largefiles
# /opt/VRTS/bin/df -t vxfs -o ckptall
- (/dev/vx/dsk/nbuapp/dbvol_copilot:NBU+2016.10.25.23h04m57s+Oracle_Copilot+34188): 67108848 blocks 945792 files
Create
Recovery
Snapshot
Mount and NFS
Export
Snapshot
Check Copilot
Share Snapshot
1 2 3
Edit
pfile(init.ora)
and cr_ctl.sql
for IR
NFS Mount
for IR
Create
controlfile
to recover DB
Recover DB and
Open Resetlogs
Verify Data
and
Clean Up
4 5 6 7 8

2. Create Recovery Checkpoint for IR
# fsckptadm -r create recovery /shares/Copilot
# /opt/VRTS/bin/df -t vxfs -o ckptall
- (/dev/vx/dsk/nbuapp/dbvol_copilot:NBU+2016.10.25.23h04m57s+Oracle_Copilot+34188): 67108848 blocks 945792 files
- (/dev/vx/dsk/nbuapp/dbvol_copilot:recovery): 67108864 blocks 945792 files
# fsckptadm list /shares/Copilot
/shares/copilot
recovery:
flags = largefiles, removable
NBU+2016.10.25.23h04m57s+Oracle_Copilot+34188:
flags = largefiles
Create
Recovery
Snapshot
Mount and NFS
Export
Snapshot
Check Copilot
Share Snapshot
1 2 3
Edit
pfile(init.ora)
and cr_ctl.sql
for IR
NFS Mount
for IR
Create
controlfile
to recover DB
Recover DB and
Open Resetlogs
Verify Data
and
Clean Up
4 5 6 7 8

3. Mount and export Checkpoint for NFS export
# mkdir /recovery
# mount -t vxfs -o ckpt=recovery,rw /dev/vx/dsk/nbuapp/dbvol_copilot:recovery /recovery
# df -h /recovery
Filesystem Size Used Avail Use% Mounted on
/dev/vx/dsk/nbuapp/dbvol_copilot:recovery
32G 3.2G 29G 10% /recovery
# vi /etc/exports
#default exports establish by NetBackup
…
…
/shares/copilot rhel-guest.nbappliance.lab(rw,no_root_squash,secure)
/recovery rhel-guest.nbappliance.lab(rw,no_root_squash,secure) --> add
Create
Recovery
Snapshot
Mount and NFS
Export
Snapshot
Check Copilot
Share Snapshot
1 2 3
Edit
pfile(init.ora)
and cr_ctl.sql
for IR
NFS Mount
for IR
Create
controlfile
to recover DB
Recover DB and
Open Resetlogs
Verify Data
and
Clean Up
4 5 6 7 8

3. Mount and export Checkpoint for NFS export (cont.)
# service nfs restart
Shutting down NFS daemon: [ OK ]
Shutting down NFS mountd: [ OK ]
Shutting down NFS quotas: [ OK ]
Shutting down NFS services: [ OK ]
Shutting down RPC idmapd: [ OK ]
Starting NFS services: [ OK ]
Starting NFS quotas: [ OK ]
Starting NFS mountd: [ OK ]
Starting NFS daemon: [ OK ]
Starting RPC idmapd: [ OK ]
# exportfs
/shares/copilot
rhel-guest.nbappliance.lab
/recovery rhel-guest.nbappliance.lab
Create
Recovery
Snapshot
Mount and NFS
Export
Snapshot
Check Copilot
Share Snapshot
1 2 3
Edit
pfile(init.ora)
and cr_ctl.sql
for IR
NFS Mount
for IR
Create
controlfile
to recover DB
Recover DB and
Open Resetlogs
Verify Data
and
Clean Up
4 5 6 7 8

4. NFS mount for instant recovery
# mount -t nfs -o rw,hard,intr,nfsvers=3,proto=tcp copilot.nbappliance.lab:/recovery /recovery
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/rhel-root 28G 4.1G 24G 15% /
devtmpfs 1.8G 0 1.8G 0% /dev
tmpfs 1.9G 466M 1.4G 26% /dev/shm
tmpfs 1.9G 8.5M 1.8G 1% /run
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/sdb1 50G 15G 36G 29% /home
/dev/sda1 497M 96M 402M 20% /boot
copilot.nbappliance.lab:/shares/Copilot 32G 3.2G 29G 10% /copilot
copilot.nbappliance.lab:/recovery 32G 3.2G 29G 10% /recovery
Create
Recovery
Snapshot
Mount and NFS
Export
Snapshot
Check Copilot
Share Snapshot
1 2 3
Edit
pfile(init.ora)
and cr_ctl.sql
for IR
NFS Mount
for IR
Create
controlfile
to recover DB
Recover DB and
Open Resetlogs
Verify Data
and
Clean Up
4 5 6 7 8

5. Create pfile(init.ora) and script for Instant Recovery
*.audit_trail='none'
*.compatible='12.1.0.2.0'
*.control_files='/recovery/control01.ctl','/recovery/control02.ctl'
*.db_block_size=8192
*.db_domain=''
*.db_name='CLONEDB'
#*.db_recovery_file_dest='/recovery/arch/'
*.db_recovery_file_dest_size=5G
*.open_cursors=300
*.pga_aggregate_target=50M
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=300M
*.memory_target=500M
*.undo_tablespace='UNDOTBS1'
*.db_files=4096
*.log_archive_dest_1='location=/recovery/arch/'
*.log_archive_format='%t_%s_%r.dbf'
*.log_buffer=10485760
*.nls_date_format='YYYY/MM/DD HH24:MI:SS'
STARTUP NOMOUNT PFILE='/recovery/initCLONEDB.ora'
CREATECONTROLFILE REUSE SET DATABASE "CLONEDB" RESETLOGS
ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 2
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 '/recovery/redo01.dbf' SIZE 50M BLOCKSIZE 512,
GROUP 2 '/recovery/redo02.dbf' SIZE 50M BLOCKSIZE 512,
GROUP 3 '/recovery/redo03.dbf' SIZE 50M BLOCKSIZE 512
DATAFILE
'/recovery/data_D-ORCL3_I-792782354_TS-EXAMPLE_FNO-5_01rjcklk_s-1_I-
792782354_Oracle_Copilot',
…
…
'/recovery/data_D-ORCL3_I-792782354_TS-USERS_FNO-4_06rjckm4_s-6_I-
792782354_Oracle_Copilot'
CHARACTER SETWE8MSWIN1252;
/recovery/initCLONEDB.ora /recovery/cr_ctl.sql
Create
Recovery
Snapshot
Mount and NFS
Export
Snapshot
Check Copilot
Share Snapshot
1 2 3
Edit
pfile(init.ora)
and cr_ctl.sql
for IR
NFS Mount
for IR
Create
controlfile
to recover DB
Recover DB and
Open Resetlogs
Verify Data
and
Clean Up
4 5 6 7 8

6. Create controlfile to recover DB
$ cd /recovery
$ mkdir arch
$ export ORACLE_SID=CLONEDB
$ env|grep SID
ORACLE_SID=CLONEDB
$ sqlplus / as sysdba
SQL*Plus: Release 12.1.0.2.0 Production on Wed Oct 26 00:25:05 2016
Copyright (c) 1982, 2014, Oracle. All rights reserved.
Connected to an idle instance.
SQL> @cr_ctl
Control file created.
Create
Recovery
Snapshot
Mount and NFS
Export
Snapshot
Check Copilot
Share Snapshot
1 2 3
Edit
pfile(init.ora)
and cr_ctl.sql
for IR
NFS Mount
for IR
Create
controlfile
to recover DB
Recover DB and
Open Resetlogs
Verify Data
and
Clean Up
4 5 6 7 8

7. Recover and Open Resetlogs
$ rman target /
Recovery Manager: Release 12.1.0.2.0 - Production on Wed Oct 26 00:26:59 2016
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
connected to target database: CLONEDB (DBID=1388827487, not open)
RMAN> catalog backuppiece '/recovery/arch_D-ORCL_I-1388827487_SCN-3549532_09rj9go7_Oracle_Copilot';
using target database control file instead of recovery catalog
cataloged backup piece
backup piece handle=/recovery/arch_D-ORCL_I-1388827487_SCN-3549532_09rj9go7_Oracle_Copilot RECID=1 STAMP=926209677
RMAN> catalog backuppiece '/recovery/arch_D-ORCL_I-1388827487_SCN-3549532_0arj9go7_Oracle_Copilot';
cataloged backup piece
backup piece handle=/recovery/arch_D-ORCL_I-1388827487_SCN-3549532_0arj9go7_Oracle_Copilot RECID=2 STAMP=926209696
Create
Recovery
Snapshot
Mount and NFS
Export
Snapshot
Check Copilot
Share Snapshot
1 2 3
Edit
pfile(init.ora)
and cr_ctl.sql
for IR
NFS Mount
for IR
Create
controlfile
to recover DB
Recover DB and
Open Resetlogs
Verify Data
and
Clean Up
4 5 6 7 8

7. Recover and Open Resetlogs (cont.)
$ sqlplus / as sysdba
SQL*Plus: Release 12.1.0.2.0 Production on Wed Oct 26 00:32:11 2016
Copyright (c) 1982, 2014, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
SQL> recover database using backup controlfile until time ‘2016-11-16-18:10:00’; (or cancel)
Media recovery complete.
SQL> alter database open resetlogs;
Database altered.
SQL> alter tablespace temp add tempfile '/recovery/temp01.dbf' size 100m;
Tablespace altered.
Create
Recovery
Snapshot
Mount and NFS
Export
Snapshot
Check Copilot
Share Snapshot
1 2 3
Edit
pfile(init.ora)
and cr_ctl.sql
for IR
NFS Mount
for IR
Create
controlfile
to recover DB
Recover DB and
Open Resetlogs
Verify Data
and
Clean Up
4 5 6 7 8

8. Verify Recovered Data and Clean Up Checkpoint
SQL> select avg(salary) from test_table_ORCL;
AVG(SALARY)
-----------
115738.75
Create
Recovery
Snapshot
Mount and NFS
Export
Snapshot
Check Copilot
Share Snapshot
1 2 3
Edit
pfile(init.ora)
and cr_ctl.sql
for IR
NFS Mount
for IR
Create
controlfile
to recover DB
Recover DB and
Open Resetlogs
Verify Data
and
Clean Up
4 5 6 7 8
# umount /recovery -> DB server
# vxumount -f /recovery -> NBUA
# fsckptadm remove recovery /shares/Copilot

Licensing

NetBackup Licensing Models: Overview
160
Capacity Licensing Traditional Licensing
Licensing
Method
• Amount of data protected
• Amount of data protected
• Amount of infrastructure hosting protected data
• Number of backup components
• Amount of functionality desired
Metering Front-End Terabytes (FETB)
Physical machines (servers, clients), processor tiers,
NAS filer tiers, operating system, application, tape
drives, FETB
Licensable
Components
1 13+
Versions/
Editions
Complete Edition Big Data Edition
Limited Edition NDMP Edition
Enterprise Server
Server
VERITAS APJ New Hire Training 2018NetBackup 8.1.2 Sales Training

161 NetBackup 8.1.2 Sales Training
NetBackup
Complete Edition
Best in Class Unified Enterprise
Data Protection across all
environments
Can combine with Big Data
Workload and NDMP Edition.
Cannot combine with Limited
Edition
• Standard Client
• Enterprise Client
• Enterprise Server
• DPOO
• Library Based Tape Drive
• Vault Option
• Shared Storage Option
• OpsCenter Analytics
Per FETB
NetBackup
Traditional
Build your own
solution
• Std & Enterprise Client
• Enterprise Server
• Data Protection
Optimization Option
• NDMP Option
• Library Based Tape Drive
• Replication Director
• Shared Storage Option
• Vault Option
• OpsCenter Analytics
• Application and Database
License Pack
• Self Service
• Enterprise Vault Agent
• Cloud Catalyst
Perpetual, Subscription Perpetual
NetBackup
Big Data Workload
Best in Class Unified Enterprise
Data Protection for Big Data
Workloads across all
environments
Can combine with Complete
and NDMP Edition. Cannot
combine with Limited Edition
Per FETB
Perpetual
• Application and Database License Pack
• SAP Agent
• Self Service
NetBackup
NDMP Edition
Protection of file data on NAS
filers using NDMP policies or
NDMP data movers
Unified Enterprise Data
Protection aimed at mid market
customers with Linux/Win/x86
only environments
NDMP File Data Only
Can combine with Complete
and Big Data Workload Edition.
Cannot combine with Limited
Edition
250TB Limit; No Unix
CANNOT combine with
Complete, Big Data Workload or
NDMP Edition
NetBackup
Limited Edition
Per FETB Per FETB
Perpetual Perpetual
Various meters
Add On Purchase:
Appl. & Database Add On
• Server • NDMP Option • Replication Director
Data Protection for all workloads

Thank you!
Copyright © 2017 Veritas Technologies. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarksof Veritas Technologies or its affiliates in the
U.S. and other countries. Other names may be trademarks of their respective owners.
This document is provided for informational purposes only and is not intended as advertising. All warranties relating to the information in this document, either express or
implied, are disclaimed to the maximum extent allowed by law. The information in this document is subject to change without notice.
Kamal Naresh
Kamal.naresh@veritas.com
+65 9147 3144

Tổng quan công nghệ Net backup - Phần 2

More Related Content

What's hot (20)

Similar to Tổng quan công nghệ Net backup - Phần 2 (20)

Recently uploaded (20)

Tổng quan công nghệ Net backup - Phần 2