December 2006 Remote to Core – Part 2 - Implementation S T R I C T L Y P R I V A T E A N D C O N F I D E N T I A L This deck is for Remote to Core presentation purposes and process understanding. It is not intended to replace detailed installation, deployment guidelines or standards documentation maintained by those groups primarily responsible for the associated tasks described. Author: J. Napier
JP Morgan Remote to Core Implementation as presented by John Napier PMP, CSM. A core component of JP Morgan Chase's Data Protection Initiative (DPI)
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
December 2006
Remote to Core – Part 2 - Implementation
S T
R I
C T
L Y
P R
I V A
T E
A N
D
C O
N F
I D E
N T
I A L
This deck is for Remote to Core presentation purposes and process understanding. It is not intended to replace detailed installation, deployment guidelines or
standards documentation maintained by those groups primarily responsible for the associated tasks described.
Symantec NetBackup utilizes Network Appliance Snapvault functionality to perform backups on NFS-mounted and/or CIFS-mapped file systems residing on NetApp filers. The Netbackup job scheduler initiates a NetApp Snapvault backup; a NetApp Snapshot copy is created on the primary NetApp storage system and is then replicated to a NetApp secondary storage system
Based on the quick creation of a snapshot and a transfer of only changed blocks via NetApp Qtree Snapmirror replication, fast backups and restores can be easily accomplished from local to remote locations.
Backups in the form of Snapshot copies on the primary(Remote) and secondary(Core) NetApp storage systems are managed (creation, retention, deletion) with NetBackup.
All backup data stored is in file format, including all incremental backups, and each incremental backup can be viewed as a full backup image by any administrator or end-user with associated access control and security rights. Data to be restored can be quickly located with a full view into what the environment looked like at the time the backup was created, and as far back as data retention will permit.
The “file system” view of backups can be accessed by end users as well, and empowers the user to perform self-restores, if the administrator permits.
Standard Solution for Remote to Core provides for 30days local backup protection and 60 days remote backup retention – all backups on disk and online.
4
High-Level Process Framework
Preliminary Site List
T. Kovinchick
Network Bandwidth AnalysisM. Ulery
Backup Policy Review
B. Diechler
Server/Share Mapping
R. Calviello
DCO/Facilities
T. Kovinchick
No
No
R2C Process Framework30-Nov-2006
# of Links/Type of LinksCapacity Available
during Backup Window
Policies for 30/60 Standard RetentionExtended Policies
Site Metrics(Inventory/TapeMedia
Share MappingServers/Volumes/Sizes/
Site Survey FormIP Addresses
Yes
Discovery and Evaluation
Site Remediation
Required
Installation and configuration
From – To Mapping
Equipment Order/ArrivalT.Kovinchick
NetApp
Remote Filer ConfigurationNAS Deploy
NetBackup Policy SetupB. Deichler
Core Volume(s) Configured
NAS Deploy
Data Seeding (Robocopy)
ScriptR. Calviello
Remote Filer Installation/Availability
NetApp First Full Backup to Core
Share Data Seeded
Baseline Data Movement
Config Sheet
K.Spakrs
SA Create vststab
entries for mount points
TBD
Follow-Up Volume Usage/
AdjustmentNAS Ops
Standard NetApp to QA
Build Team Check List
NetApp K.Sparks
Facilities/Network Ready
Validation K.Sparks
This workflow loop will be further
detailed in future versios
Post-Site Processes still to be defined
30-45 Day Revisit/ReSize identified
5
Current State Diagram – Remote Site
AD AD AD
SAN Fabric
FAStTStorage
ADAD
Tape drive
Ethernet Ethernet
PC PC PCPCPC PC
“Microsoft Only” Users
AD Backup
Tape drive
DomainController
Standard Medium Office DeploymentClustered Novell/Netware Servers (or)Clustered Windows 2000/3 Servers1Pair each for Print, File, Build/AppEMC/FastT SAN storageLocal Tape Backup(NBU,other)
6
Target State Diagram
Eth
ern
et
SV/SM
NDMP
Core
Daily Backup Image Resides at Core(60d)
Filer Initiates Snapshot Snapshot is Remote-side Backup(30d) Begins Snapvault Replication
Remote
AD AD AD
SAN Fabric
FAStTStorage
ADAD
Tape drive
Ethernet Ethernet
ADBackup
Tape drive
DomainController
FAS 270C
PC PC PCPCPC PC
“Microsoft Only” Users
Not in use after client migration
7
High-Level Process – Bringing Filer Online
Network Configuration – established in System Configuration sheet
Interfaces to User Network
Prefer Etherchannel GbE or 100Mb (multi-mode VIF, Active-Active Trunk)
Minimally Multi-Homed GbE or 100Mb (single-mode VIF, Active-Passive)
Interfaces to WAN (Snapvault replication) – utilize same interfaces.
Volumes and Share Creation – established through F&P Share Discovery and Backup Policy
Includes NFS mount points for UNIX-based NBU instances
Disable standard OnTap scheduled snapshots on non-Root volumes
Limit Qtrees to 6 per volume (to control QSM snapshot limits of 255 per volume)
Join filer to AD Domain
Map shares Source/Target for Robocopy Process (if Filer not initially used as Primary storage)
Applications running on F&P Shares should be identified in advance. Applications typically generate a higher data change rate and need to be tracked accordingly.
8
Netbackup SnapVault Mgmt (NSVM) Req’s.
NetApp Hardware Any platform combination that SnapVault supports
Data ONTAP Primary: Data ONTAP 6.5.2 or laterSecondary: Data ONTAP 7.1 or later
Media Server N/A (but Master must be NetBackup 6.0 or later)
Applications File SharingOracle (8i or later) on Solaris
9
High-Level NSVM Setup
NetBackup
NBU 6 Enterprise Server installed on Master & Media Servers
NDMP Option licensed and installed within NBU
Veritas ICS is installed
NBU Advanced Client is licensed and installed
NetApp/OnTap
SnapVault Primary and SnapVault Secondary licenses added
NDMP on the filers is ON
Enable SnapVault
Disable local Snapshot schedules
10
High-Level Process – NSVM Setup (continued)
Setup NDMP Credentials for NDMP Host
Verify information
Grant Access on Primary
Grant Access on Secondary
Create SnapVault Target Volume on SnapVault Secondary(Filer)
11
High-Level Process – NSVM Setup (continued)
All NSVM SnapVault backups are managed via NetBackup for both backups and restores.
NSVM Manages the Snapshot copies (retention/copies) on the Primary and Secondary)
Storage Unit type is set to Disk and Disk type is set to SnapVault
Media Server is appropriate selected
The SnapVault server should be specified as the name of the NetApp Secondary system
Specify the absolute pathname to volume as the volume that was created on the Secondary
12
High-Level Process – Setup NBU Policy Attributes
Policy Type is WindowsNT
Policy Storage Unit is the Storage unit setup in earlier step
Check off
Set # of Snapshots to keep on the primary to 30
Schedules:
Name Schedule – Type (FULL) – Frequency
Destination (Snapshots Only)
Retention (Manages retention of copies on Secondary) – 60 Days
Clients
Backup Selections
13
High-Level Process – Notes:
Backup Policy changes
Backup policies should be aligned to remote volumes and incorporate all qtree paths within the volume having similar retention policy
Any policy requirement for longer than 60day retention should have an alternate Secondary(target) vault volume defined.
Currently – the “first” snapvault relationship between a new Remote site and Core, should be manually performed from NAS Admin in a create & break process.
In our environment, we have seen NBU fail to create Snapvault relationships for first time Remote sites.
Configurations for NBU must have the Media Server and Advanced Client components running on the same platform. Either both on Windows or both on Solaris.
If UNIX is the Media Server/Advanced Client platform, then all shares must have NFS exports added.
30-Day Adjustment: Remote volumes should be originally configured with extra capacity (estimate 20%) as data change rate and snapshot consumption for the first 30 days of backups will not be known. After 30days of Snapshots/Backups are accumulated, the volumes can be re-adjusted to normal free-space levels. Flex-vols allow for dynamic growth or size reduction.
14
Reference - Remote to Core Netbackup Snapvault Naming
Netbackup PolicyName: snapvault_stxarlbna01_STX4501PRTVN02 format: snapvault_remote filer_remote volumeDSU: (host)stxjipcna01 (vol) stxarlbna01_vault1 format: snapvault server/core filer, core filer volume created for remote filerPath: \vol\stxarlbna01_STX4501PRTVN02\qtree1, format: path for all qtrees within volume having same retention \vol\stxarlbna01_STX4501PRTVN02\qtree2, \vol\stxarlbna01_STX4501PRTVN02\qtree3, \vol\stxarlbna01_STX4501PRTVN02\qtree4
\vol\stxarlbna01_STX4501PRTVN02\qtree2
\vol\stxarlbna01_STX4501PRTVN02\qtree3
\vol\stxarlbna01_STX4501PRTVN02\qtree4
NBU Naming of Snapshots from Bkup Policy:NAS+NBU+PFI+ino0s041+snapvault_stxarlbna01_STX4501PRTVN02+sv+stxarlbna02_STX4501PRTVN02+2006.12.01.21h00m17s