1 / 44

VNX SnapSure

VNX SnapSure. Upon completion of this module, you should be able to: Describe VNX SnapSure theory and operations Configure SnapSure Plan and manage SnapSure. VNX SnapSure. Lesson 1 : VNX SnapSure Theory of Operations. This lesson covers the following topics: Purpose of SnapSure

abram
Download Presentation

VNX SnapSure

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. VNX SnapSure Upon completion of this module, you should be able to: Describe VNX SnapSure theory and operations Configure SnapSure Plan and manage SnapSure VNX SnapSure

  2. VNX SnapSure Lesson 1: VNX SnapSure Theory of Operations This lesson covers the following topics: Purpose of SnapSure Key components of SnapSure SnapSure theory of operations VNX SnapSure storage usage Checkpoint scheduling VNX SnapSure

  3. SnapSure Overview VNX SnapSure

  4. User’s Views of Data Monday View Read-only Tuesday View Read-only Wednesday View Read-only Production biz_proposal biz_proposal biz_proposal Live biz_proposal Production File System Checkpoints VNX SnapSure

  5. Key Components • Production File System (PFS) • Checkpoint • Logical point-in-time view of data • Also known as a “snapshot” • SavVol • Stores original data blocks to preserve the point in time view • Bitmap • Identifies changed data blocks in the PFS • Blockmap • Records the location of data blocks in the SavVol VNX SnapSure

  6. Theory of Operation: Part 1 of 7 SavVol PFS Bitmap 0 0 0 0 0 0 F E D A B C PFS SavVol Blockmap1 Ckpt 1 Data Storage Area Creating a checkpoint VNX SnapSure

  7. Theory of Operation: Part 2 of 7 SavVol PFS Bitmap 0 0 0 0 0 0 A B C D E F PFS SavVol Blockmap1 2 1 K H Ckpt 1 Data Storage Area 1. Write request is made 2. Check the Bitmap value VNX SnapSure

  8. Theory of Operation: Part 3 of 7 PFS SavVol Bitmap 0 1 0 0 1 0 Hold A D E F C B K H PFS SavVol Blockmap1 2 1 1. Issue write hold 2. Copy original data into SavVol blocks 3. Map PFS block to SavVol block 4. Update bitmap value to 1 5. Release write hold 3 4 2 5 1 5 2 Ckpt 1 B E Writing to the PFS VNX SnapSure

  9. Theory of Operation: Part 4 of 7 PFS SavVol Bitmap 0 0 0 0 0 0 C F D A H K PFS SavVol PFS SavVol Blockmap2 Blockmap1 2 1 5 2 Ckpt 1 Ckpt 2 • Bitmap is reset to zero values • A new blockmap is created for Ckpt2 B E Creating a second checkpoint VNX SnapSure

  10. Theory of Operation: Part 5 of 7 PFS SavVol Bitmap 1 1 0 0 0 1 F K A C D H Hold J L S PFS SavVol PFS SavVol Blockmap2 Blockmap1 2 1 1 3 3 4 2 1 5 2 4 5 2 New 1. Issue write hold 2. Copy data into SavVol 3. Update Ckpt2’s blockmap 4. Update bitmap values 5. Release write hold Ckpt 1 Ckpt 2 5 6 A H B E F Writing to the PFS with Ckpt2 VNX SnapSure

  11. Theory of Operation: Part 6 of 7 PFS SavVol Bitmap Old 1 1 0 0 0 1 F A S K D J L H K C C D PFS SavVol PFS SavVol Blockmap1 Blockmap2 2 1 1 3 Active 3 2 3 1 2 4 5 2 Ckpt 1 Ckpt 2 5 6 1. Read Bitmap values 2. “0” - Retrieve data from PFS 3. “1” - Retrieve data from SavVol A H B E F VNX SnapSure Reading from active checkpoint

  12. Theory of Operation: Part 7 of 7 PFS SavVol Bitmap 1 1 0 0 0 1 Active F E L B J C K D A S PFS SavVol PFS SavVol C D Blockmap1 Blockmap2 2 1 1 3 Old 3 2 1 2 4 5 2 Ckpt 2 Ckpt 1 5 6 1. Read older checkpoint’s blockmap 2. Aggregate oldest values 3. Verify active checkpoint’s blockmap for location A H B E F Reading from old checkpoint VNX SnapSure

  13. SavVol Storage Considerations • All checkpoints of a PFS share the same SavVol VNX SnapSure

  14. SavVol Automatic Extension • Automatic extension is triggered by High Water Mark (HWM) • HWM is 90% by default • Will not exceed 20% of total VNX space by default • SavVol automatic extensions increase in 20 GB increments, or by 10% if SavVol was manually created • To disable automatic SavVol extension, set HWM to 0% • First, SnapSure uses remaining space in SavVol • Then, SnapSure will overwrite the oldest checkpoint • Refresh checkpoints to recycle SavVol storage VNX SnapSure

  15. Checkpoint Scheduling Overview VNX SnapSure

  16. VNX SnapSure Lesson 1: Summary During this lesson the following topics were covered: Purpose of SnapSure Key components of SnapSure SnapSure theory of operations VNX SnapSure storage usage Checkpoint scheduling VNX SnapSure

  17. VNX SnapSure Lesson 2: Configuring SnapSure This lesson covers the following topics: Checkpoint creation and verification Displaying existing checkpoints Accessing the checkpoint Configuring checkpoint scheduling VNX SnapSure

  18. Creating a Checkpoint • Data Protection > Snapshots > File System Checkpoints VNX SnapSure

  19. Displaying Checkpoints VNX SnapSure

  20. Accessing Checkpoints via CVFS • SnapSure navigation feature for end users to view and restore checkpoint data without any Administrator involvement • CIFS or NFS read-only access • “.ckpt” is the name of the hidden directory containing checkpoint data • Name may be modified via param file • Naming convention of individual checkpoints • yyyy_mm_dd_hh_mm_ss_<Data_Mover_timezone> • CVFS names can be changed when remounting the checkpoint VNX SnapSure

  21. NFS Client Checkpoint Access [root@linux08b student8]# ls -la total 10323052 drwxr-xr-x. 5 root root 1024 Sep 18 22:34 . dr-xr-xr-x. 27 root root 4096 Sep 16 01:43 .. dr-xr-xr-x. 2 root bin 1024 Sep 18 22:25 .etc -rw-r--r--. 1 root root 2857369600 Sep 16 01:48 filename -rw-r--r--. 1 root root 1652555776 Sep 16 01:48 filename2 -rw-r--r--. 1 root root 6055657472 Sep 16 01:50 filename3 drwxr-xr-x. 2 root root 8192 Sep 11 14:13 lost+found [root@linux08b student8]# [root@linux08b student8]# ls -la .ckpt total 33 dr-xr-xr-x. 2 root root 512 Sep 18 22:47 . drwxr-xr-x. 5 root root 1024 Sep 18 22:34 .. drwxr-xr-x. 5 root root 1024 Sep 16 01:48 2013_09_18_21.46.01_GMT drwxr-xr-x. 5 root root 1024 Sep 18 21:50 2013_09_18_21.51.29_GMT drwxr-xr-x. 5 root root 1024 Sep 18 21:56 2013_09_18_21.57.24_GMT [root@linux08b student8]# .ckpt directory has to be explicitly specified Checkpoints appear as directories VNX SnapSure

  22. NFS Client Checkpoint Access (continued) [root@linux08b student8]# cd .ckpt [root@linux08b .ckpt]# ls -l total 24 drwxr-xr-x. 5 root root 1024 Sep 16 01:48 2013_09_18_21.46.01_GMT drwxr-xr-x. 5 root root 1024 Sep 18 21:50 2013_09_18_21.51.29_GMT drwxr-xr-x. 5 root root 1024 Sep 18 21:56 2013_09_18_21.57.24_GMT [root@linux08b .ckpt]# [root@linux08b .ckpt]# cd 2013_09_18_21.46.01_GMT [root@linux08b 2013_09_18_21.46.01_GMT]# [root@linux08b 2013_09_18_21.46.01_GMT]# ls -la total 10323049 drwxr-xr-x. 5 root root 1024 Sep 16 01:48 . dr-xr-xr-x. 2 root root 512 Sep 18 22:42 .. dr-xr-xr-x. 2 root bin 1024 Sep 18 21:25 .etc -rw-r--r--. 1 root root 2857369600 Sep 16 01:48 filename -rw-r--r--. 1 root root 6055657472 Sep 16 01:50 filenames -rw-r--r--. 1 root root 1652555776 Sep 16 01:48 filname drwxr-xr-x. 2 root root 8192 Sep 11 14:13 lost+found [root@linux08b 2013_09_18_21.46.01_GMT]# [root@linux08b 2013_09_18_21.46.01_GMT]# VNX SnapSure

  23. CIFS Client Checkpoint Access • In the address field of Windows Explorer, enter \.ckpt to list the checkpoints associated with the file system share Manually type the path to .ckpt VNX SnapSure

  24. Accessing Checkpoints via Shadow Copy Client • CIFS clients can also access checkpoint data via Shadow Copy Client • Native with Windows 2003 and later OS versions • Download available for Windows 2000 and XP • Select “Previous Versions” tab on the file system share Properties window VNX SnapSure

  25. Displaying Checkpoint Schedules • Data Protection > Snapshots > File System Checkpoints > Schedules Tab • Schedule states • Active • Pending • Paused • Complete VNX SnapSure

  26. Creating a Checkpoint Schedule Use relative prefix to make script writing easier Checkpoint names may be assigned VNX SnapSure

  27. SnapSure Considerations VNX SnapSure

  28. VNX SnapSure Lesson 2: Summary During this lesson the following topics were covered: Checkpoint creation and verification Displaying existing checkpoints Accessing the checkpoint Configuring checkpoint scheduling VNX SnapSure

  29. VNX SnapSure Lesson 3: Planning SnapSure This lesson covers the following topics: Planning checkpoint schedules Performance considerations VNX SnapSure

  30. Schedule Planning VNX SnapSure

  31. PFS Performance Implications VNX SnapSure

  32. Client Performance Implications • Refreshing a checkpoint affects user or application access • During a refresh, the checkpoint is deleted and a new one is created with the same name • Checkpoint being refreshed will have all read I/O activity suspended • If a checkpoint becomes inactive or corrupted, read/write activity on the PFS will continue • The PFS does not depend on the checkpoint, but the checkpoint depends on the PFS VNX SnapSure

  33. SavVol Performance and Disk Type • SavVol writes are sequential, while reads are random VNX SnapSure

  34. VNX SnapSure Lesson 3: Summary During this lesson the following topics were covered: Planning checkpoint schedules Performance considerations VNX SnapSure

  35. VNX SnapSure Lesson 4: Managing Checkpoints This lesson covers the following topics: Storage management for checkpoints Modifying SnapSure schedules Memory management for checkpoints VNX SnapSure

  36. Checkpoint Storage Consumption • Checkpoint Properties page VNX SnapSure

  37. Listing Checkpoints via CLI [nasadmin@VNXB ~]$ fs_ckpt fs16 -list id ckpt_namecreation_timeinusefullmarktotal_ ckpt_ savvol_ usage_on used savvol 16 Monday 09/18/2013-05:33:52-EDT y 90% 8% 1% 17 Tuesday 09/18/2013-05:39:20-EDT y 90% 8% 1% 18 Wednesday 09/18/2013-05:45:15-EDT y 90% 8% 1% 20 ProdData1 09/24/2013-12:10:00-EDT y 90% 8% 1% 21 ProdData2 09/24/2013-13:10:00-EDT y 90% 8% 1% ProdData3 09/24/2013-14:10:00-EDT y 90% 8% 1% Info 26306752329: The value of ckpt_usage_on_savvol for read-only checkpoints may not be consistent with the total_savvol_used. [nasadmin@VNXB ~]$ VNX SnapSure

  38. Recycling SavVol Storage • One way to create more SavVol space without extension is to refresh checkpoints VNX SnapSure

  39. Managing Checkpoints VNX SnapSure

  40. Modifying Checkpoint Schedules • Schedules may be modified once they are active by accessing their Properties page VNX SnapSure

  41. Memory Requirements for SnapSure • SnapSure allocates up to 1 GB of Data Mover memory for checkpoint blockmaps • 512 MB if DM RAM is less than 4 GB • Both SnapSure and VNX Replicator require Data Mover memory allocation • Blockmap entries are paged into Data Mover memory for fast access VNX SnapSure

  42. Viewing Blockmap Status [nasadmin@VNXB ~]$ server_sysstat server_3 -blockmap server_3 : total paged in = 0 total paged out = 1 page in rate = 0 page out rate = 0 block map memory quota = 1572864(KB) block map memory consumed = 392(KB) [nasadmin@VNXB ~]$ VNX SnapSure

  43. VNX SnapSure Lesson 4: Summary During this lesson the following topics were covered: Storage management for checkpoints Modifying SnapSure schedules Memory management for checkpoints VNX SnapSure

  44. Summary Key points covered in this module: • SnapSure creates a point-in-time view of a file system that is not a copy or a mirror image of the original file system • CVFS is a navigation feature that provides NFS and CIFS clients with read-only access to online, mounted checkpoints from within the PFS namespace • Checkpoint creation and refreshes can be scheduled on arbitrary, multiple hours of a day, days of a week or days of a month VNX SnapSure

More Related