Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

JP Morgan Remote to Core Implementation

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)

  • Login to see the comments

  • Be the first to like this

JP Morgan Remote to Core Implementation

  1. 1. December 2006 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 Remote to Core – Part 2 - Implementation 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
  2. 2. Contents  Solution  High-Level Process Framework  Bringing the Filer Online  Netbackup SnapVault Management (NSVM) Requirements  NSVM Setup  NBU Policy Attributes  Notes  Reference - Netbackup Snapvault Naming  Reference - FAS270C Wiring Detail 2
  3. 3. Solution: Netbackup Snapvault Management (NSVM)  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. 3
  4. 4. High-Level Process Framework 4
  5. 5. Current State Diagram – Remote Site Standard Medium Office Deployment Clustered Novell/Netware Servers (or) Clustered Windows 2000/3 Servers 1Pair each for Print, File, Build/App EMC/FastT SAN storage Local Tape Backup(NBU,other) AD 5
  6. 6. Target State Diagram Core Not in use after client migration Daily Backup Image Resides at Core(60d) Filer Initiates Snapshot Snapshot is Remote-side Backup(30d) Begins Snapvault Replication AD Remote 6
  7. 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. 7
  8. 8. Netbackup SnapVault Mgmt (NSVM) Req’s. NetApp Hardware Any platform combination that SnapVault supports Data ONTAP Primary: Data ONTAP 6.5.2 or later Secondary: Data ONTAP 7.1 or later NetApp Software Snapshot, SnapRestore[1] Primary: sv_ontap_pri Secondary: sv_ontap_sec NetBackup NetBackup Enterprise 6.0 or later NDMP Option Advanced Client Option NetApp SnapVault Option Protocols NFS, CIFS Client Solaris Windows NetBackup 6.0 or later Media Server N/A (but Master must be NetBackup 6.0 or later) Applications File Sharing Oracle (8i or later) on Solaris 8
  9. 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 9
  10. 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) 10
  11. 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 11
  12. 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 12
  13. 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. 13
  14. 14. Reference - Remote to Core Netbackup Snapvault Naming 14
  15. 15. Reference - FAS270C Wiring Diagram (M.Bachert) OF F OP EN OPEN OP EN OPEN ON FIBRE CHANNEL 1 F IBRE CHANNEL 2 10/100/1000 ET HERNET CONS OLE F AULT SH ELF 1Gb ID 2Gb PSU1 MODULE A PSU2 MODULE B FA ULT 10/100/1000 ETHERNE T FIB RE CHANNEL 1 CONS OLE FIBRE CHANNEL 2 CAUT ION CAUT ION ON OFF NETWORK SWITCH TERMINAL SERVER NETWORK SWITCH POWER POWER Hardware Dimensions Metric Height 5.25 in. 13.3 cm Width 17.6 in. 44.7 cm Depth 20 in. 50.85 cm Weight FAS270 U.S. Rack Units* 77 lbs. (loaded) 35 kg 3U (Rack Mount) Amps @ 100-120V Rated Hardware FAS270 Amps @ 200-240V Actual Rated Actual P/S Volt Range 7 3.95 3.5 1.9 100 – 240 VAC 15