Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to EMC Dteata domain advanced command troubleshoot
Similar to EMC Dteata domain advanced command troubleshoot (20)
More from solarisyougood
More from solarisyougood (20)
Recently uploaded
Recently uploaded (20)
EMC Dteata domain advanced command troubleshoot
- 1. 1 Data Domain Autosupport Part 1 Hardware and Licenses
- 2. 2 Autosupport Overview ========== GENERAL INFO ========== GENERATED_ON=Sun Jun 14 06:55:32 PDT 2015 GENERATED_EPOCH_TIME=1434290132 TIME_ZONE=US/Pacific VERSION=Data Domain OS 5.5.2.1-486029 SYSTEM_SERIALNO=1F41505202 CHASSIS_SERIALNO=1F41505202 Serial No. of Chassis and System MODEL_NO=DD890 Model Number HOSTNAME=dd890-1.lss.emc.com LOCATION=Santa Clara, California ADMIN_EMAIL=iplabstaff@emc.com Filesystem has been up 43 days, 17:16. General Info
- 3. 3 Autosupport Overview Memory Usage Summary Total memory: 96666 MiB Memory Information Free memory: 14755 MiB Total swap: 49151 MiB Free swap: 49151 MiB System Memory The Memory Information is important if you want to upgrade the system. Most systems are shipped with 2 possible Memory Configurations. Capacity Upgrade kit contains Memory and an Expanded Capacity License
- 4. 4 Networking Hardware Net Show Hardware This example shows 2x 10 Gig Optical Ports available with no link Net Show Hardware ----------------- Port Speed Duplex Supp Speeds Hardware Address Physical Link Status ----- -------- ------- ----------- ----------------- -------- ----------- eth0a 1000Mb/s full 10/100/1000 00:a0:d1:cf:15:0d Copper yes eth0b 1000Mb/s full 10/100/1000 00:a0:d1:cf:15:0c Copper yes eth4a unknown unknown 1000/10000 00:1b:21:8f:d8:28 Fiber no eth4b unknown unknown 1000/10000 00:1b:21:8f:d8:29 Fiber no ----- -------- ------- ----------- ----------------- -------- ----------- This section shows: • Network Cards that are physically present • Supported Link Speed • Connection Speed – if Link is present
- 5. 5 Disk Status Disk Status provides an overview of where installed disks are assigned. This example shows a system with Extended Retention so there are disks in: • Head Unit • Active Tier – Where data is first ingested • Archive Tier – Target for Long-term data based on migration policies Disk Status ----------- Normal - Storage operational Disk States Active tier Archive tier Head unit ----------- ----------- ------------ --------- In Use 238 84 3 Spare 17 6 1 TOTAL DISKS 255 90 4 ----------- ----------- ------------ ---------
- 6. 6 Enclosure Information Enclosure show command Provides a complete output of all hardware information. CLI – shows full details GUI – selected subset of information is presented “enclosure show” command can be used with the following options: Chassis Controllers CPUs Fans I/O-cards Memory NVRAM Power supply Temperature-sensors
- 7. 7 Enclosure Information Continued Enclosure show summary In this example, Enclosure 1 (the DD890 head) has 4 internal disks Each ES30 shelf has 15 Disks Enclosure Show Summary ---------------------- Enclosure Model No. Serial No. State OEM Name OEM Value Capacity --------- --------- -------------- ------ -------- --------- -------- 1 DD890 1F41505202 Online 4 Slots 2 ES30 APM00111100155 Online 15 Slots 3 ES30 APM00111100151 Online 15 Slots 4 ES30 APM00111100154 Online 15 Slots 5 ES30 APM00111100574 Online 15 Slots 6 ES30 APM00111100157 Online 15 Slots 7 ES30 APM00111100156 Online 15 Slots --------- --------- -------------- ------ -------- --------- -------- 7 enclosures present. Provides an overview of installed Disk Shelves.
- 8. 8 Enclosure Information continued IO Card Information This section provides I/O Card information. Slot indicates the card’s physical location Device indicates card type. Interface describes the cards • Slot 0 – 4 Port 1Gb Ethernet • Slot 2 – 2 Port 8Gb Fiberchannel • Slot 4 – 4 Port SAS2 Card • Slot 11 – 2 Port 10 Gb Ethernet Port describes the name of each specific port – more later.
- 9. 9 Enclosure Information continued IO Card Information cont. The last column describes the MAC or WWPN address. • WWPN is used for FC Zoning • WWPN is configurable since DDOS 5.3 • Use SCSI Target command to configure More information in DDOS Command Reference Guide Exercise Extreme Caution when configuring WWPN Example shows a DD990 with Extended Retention enabled • Observe 4 SAS Adapters with 4x6Gb ports each This information can be seen in the Topology View later.
- 10. 10 Enclosure Information continued Controller Information • Model & Serial Number • Disks in Controller Head − Store Configuration − Log files • CPU details − Model − Speed − Cores Intel ARK Site for CPU Details Controller: Model DD990 Capacity 4 Serial No 3FZ1723104 Number of Controllers 1 Controller 1 Interface LSISAS1068E B3 Firmware 01.27.06.00 Part No. L3-00159-02E Serial No. SP23413163 Status OK Controller HDDs: Disk Slot Size(GB) Part No. Serial No. Rev ---- ---- -------- ------------------------ ---------- ---- 1 1 600 HITACHI HUC10606_CLAR600 PZJRG1JD C330 2 2 600 HITACHI HUC10606_CLAR600 PZJRUS0D C330 3 3 600 HITACHI HUC10606_CLAR600 PZJRGBXD C330 4 4 600 HITACHI HUC10606_CLAR600 PZJRTSLD C330 ---- ---- -------- ------------------------ ---------- ---- CPUs: Model Stepping Speed(MHz) Cores Hyperthreading ----------------------------- -------- ---------- ----- -------------- Intel(R) Xeon(R) CPU E7- 4870 2 2394 10 disabled Intel(R) Xeon(R) CPU E7- 4870 2 2394 10 disabled Intel(R) Xeon(R) CPU E7- 4870 2 2394 10 disabled Intel(R) Xeon(R) CPU E7- 4870 2 2394 10 disabled ----------------------------- -------- ---------- ----- --------------
- 11. 11 Enclosure Information continued NVRAM Information • Slot where NVRAM Card is installed • Battery charging details • If the Batteries are not charged, the filesystem will not start. NVRAM Cards: Card Component Value ---- ------------------- ----------------------------------------------- 1 Slot 6 Firmware version 1.2.6 Memory size 1.93 GiB Errors 0 memory (0 uncorrectable), 0 PCI, 0 controller Board temperature 37 C CPU temperature 67 C Number of batteries 3 Card model no 521-0012-0001-6 Card serial no F61105B30301 Battery model no 521-0021-0001 Battery serial no F61028M20013 ---- ------------------- ----------------------------------------------- NVRAM Batteries: Card Battery Status Charge Charging Time To Temperature Voltage Status Full Charge ---- ------- ------ ------ -------- ----------- ----------- ------- 1 1 ok 97 % enabled 0 mins 25 C 8.132 V 2 ok 97 % enabled 0 mins 25 C 8.126 V 3 ok 97 % enabled 0 mins 25 C 8.140 V ---- ------- ------ ------ -------- ----------- ----------- -------
- 12. 12 Enclosure Information continued Enclosure show topology • Observe dual path connectivity from the controller to all 6 shelves (2-7) − Confirm that both paths display correctly (Path A and Path B) − If results are not the same for each path, there might be an issue with a connector or a cable. • This order can be changed in the event the system is re-cabled • Same information can be seen via disk port show summary Enclosure Show Topology ----------------------- Port enc.ctrl.port enc.ctrl.port enc.ctrl.port ---- - ------------- - ------------- - ------------- 2a > 2.A.H: 2.A.E > 6.A.H: 6.A.E > 5.A.H: 5.A.E 2b > 4.B.H: 4.B.E > 7.B.H: 7.B.E > 3.B.H: 3.B.E 2c 2d 3a > 3.A.H: 3.A.E > 7.A.H: 7.A.E > 4.A.H: 4.A.E 3b > 5.B.H: 5.B.E > 6.B.H: 6.B.E > 2.B.H: 2.B.E 3c 3d ---- - ------------- - ------------- - ------------- Path A Path A Path B Path B
- 13. 13 PCI Slot Information System show hardware This command shows the location of all PCI Cards, device type and the Ports Detailed System PCI Info ------------------------ Slot Vendor Device Ports ---- ------------ ------------------------ -------------- 0 Intel 82576 Gigabit 0a, 0b 1 (empty) (empty) 2 LSI Logic SAS31601E 2a, 2b, 2c, 2d 3 LSI Logic SAS31601E 3a, 3b, 3c, 3d 4 Intel Dual Port 10GbE(82599EB) 4a, 4b 5 Qlogic Corp. QLE2562 8Gb FC 5a, 5b 6 EMC DD00 NVRAM Card ---- ------------ ------------------------ --------------
- 14. 14 PCI Slot Information System show hardware This example shows a DD9500 • Slot M has unique Port naming • System contains − 4 Port 10Gb Ethernet Cards − 2 Port 16Gb Fiber Channel Cards
- 15. 15 PCI Slot Information disk show hardware This command shows the Hardware information of the disks – manufacturer, capacity and type Disk Show Hardware ------------------ Disk Slot Manufacturer/Model Firmware Serial No. Capacity Type (enc/disk) ---------- ---- --------------------- -------- --------------- ---------- ---- 1.1 1 WDC_WD1003FBYX-01Y7B0 01.01V01 WD-WCAW30677581 931.51 GiB SATA 1.2 2 WDC_WD1003FBYX-01Y7B0 01.01V01 WD-WCAW30321273 931.51 GiB SATA 1.3 3 WDC_WD1003FBYX-01Y7B0 01.01V01 WD-WCAW30673531 931.51 GiB SATA 1.4 4 WDC_WD1003FBYX-01Y7B0 01.01V01 WD-WCAW30700036 931.51 GiB SATA 2.1 0 HUA722020ALA330 JKAOA3FB B9K8W32F 1.81 TiB SATA 2.2 1 HUA722020ALA330 JKAOA3FB B9K68DGF 1.81 TiB SATA 2.3 2 HUA722020ALA330 JKAOA3FB B9K90XAF 1.81 TiB SATA 2.4 3 HUA722020ALA330 JKAOA3FB B9K8ZEBF 1.81 TiB SATA
- 16. 16 Licenses Shelf Licenses • Beginning with DDOS 5.1, a “Shelf License” is required for either − Active Tier − Archive Tier (Extended Retention) • Shelf License prevents Archive Tier shelves from being used in Active Tier • Contact Sales Operations Team for shelf licensing issues • Extended Retention shelves cannot be “converted” to Active Tier licensing Licenses -------- Feature : CAPACITY-ACTIVE ------------------------- ## License Key Model Capacity* -- -------------------------------- ----- --------- 1 V6LK-K22T-EPRP-Z5RM-U6B4-3E3J-AC ES30 21.8 TiB 2 6L47-L9BC-DXFH-25NG-2T94-ZYRY-U2 ES30 21.8 TiB 3 R7RA-3A4U-83H8-FDKE-YTM1-A3DK-1D ES30 21.8 TiB 4 FZSS-MFS6-LZ7R-9WUL-D9DS-VTNW-TJ ES30 21.8 TiB 5 T8YV-JL7N-JP9E-H86F-9ZF5-UX5V-B5 ES30 21.8 TiB 6 9FA1-5PJ4-74AG-KFGB-ZZUK-KTZC-WW ES30 21.8 TiB Feature : CAPACITY-ARCHIVE -------------------------- ## License Key Model Capacity* -- -------------------------------- ----- --------- 1 X4RM-L5U8-J7YA-GG2B-YJYB-3LBK-XY ES30 21.8 TiB 2 YDTP-EMDP-N4P7-9G9L-RF1W-JU52-J5 ES30 21.8 TiB 3 ZC3H-6WCR-CP8A-MGDA-9RCT-UR77-95 ES30 21.8 TiB 4 4TCN-SY5L-BRFH-TLJ4-P7NM-ZN29-RW ES30 21.8 TiB 5 NHWW-V2R3-DLUS-12TP-2LSA-UMBR-7D ES30 21.8 TiB 6 SL87-N1M1-SR9Z-KXKC-SB3L-P8FN-VJ ES30 21.8 TiB -- -------------------------------- ----- --------- Licensed Archive Tier Capacity: 130.9 TiB*
- 17. 17 Licenses Feature Licenses • Feature Licenses enable the usage of additional DDOS features, e.g. Encryption. • Depending on the Version of the DDOS you may see different features listed, not available in prior versions. In this example, Secure-Multi-Tenancy. • Licenses are purchased on a per Head Basis. • Feature Licenses are not transferable − If you perform a Head Upgrade the customer must purchase new licenses. Feature licenses: ## License Key Feature -- ------------------- -------------------- 1 FXAT-GRGW-YRSE-TDFE ENCRYPTION 2 TZSX-SCWT-CSZA-FFED SECURE-MULTI-TENANCY 3 HDDH-ECZT-EYYR-SSAD DDBOOST 4 RBVZ-ATTC-BBHC-GDDF REPLICATION 5 TYHE-HWBR-GZHD-HADT VTL -- ------------------- --------------------
- 18. 18 Licenses Feature Licenses Expanded Storage As already mentioned in the Hardware Part, if you want to expand a system beyond a certain capacity you will require a Memory Upgrade in addition to an Expanded Storage License Feature licenses: ## License Key Feature -- ------------------- ---------------- 1 XZEG-HTXC-TGHW-TZFD ARCHIVER 2 WEWC-FVDB-DABA-AHVR EXPANDED-STORAGE 3 AAYV-CSCW-AYAY-GWBR DDBOOST 4 FXCC-WGSZ-BFDT-YVRB VTL -- ------------------- ----------------
- 19. 19 Licenses Feature License Encryption The Encryption Feature enables Encryption of the complete Filesystem of a DD System. There is no further granularity for this feature. Encryption uses AES 128 or AES 256 standard – more details can be found at: https://inside.emc.com/docs/DOC-26072 Feature licenses: ## License Key Feature -- ------------------- -------------------- 1 FXAT-GRGW-YRSE-TDFE ENCRYPTION 2 TZSX-SCWT-CSZA-FFED SECURE-MULTI-TENANCY 3 HDDH-ECZT-EYYR-SSAD DDBOOST 4 RBVZ-ATTC-BBHC-GDDF REPLICATION 5 TYHE-HWBR-GZHD-HADT VTL -- ------------------- --------------------
- 20. 20 Licenses Feature Licenses Secure Multi Tenancy The Secure-Multi-Tenancy License was introduced in DDOS 5.5 It is used for customers sharing a single Data Domain System among multiple “tenants.” More detail is available at https://inside.emc.com/docs/DOC-23573 Feature licenses: ## License Key Feature -- ------------------- -------------------- 1 FXAT-GRGW-YRSE-TDFE ENCRYPTION 2 TZSX-SCWT-CSZA-FFED SECURE-MULTI-TENANCY 3 HDDH-ECZT-EYYR-SSAD DDBOOST 4 RBVZ-ATTC-BBHC-GDDF REPLICATION 5 TYHE-HWBR-GZHD-HADT VTL -- ------------------- --------------------
- 21. 21 Licenses Feature Licenses DDBoost and Replication DDBoost and Replication Licenses are needed per Data Domain System, source and target, to enable Managed File Replication Feature licenses: ## License Key Feature -- ------------------- -------------------- 1 FXAT-GRGW-YRSE-TDFE ENCRYPTION 2 TZSX-SCWT-CSZA-FFED SECURE-MULTI-TENANCY 3 HDDH-ECZT-EYYR-SSAD DDBOOST 4 RBVZ-ATTC-BBHC-GDDF REPLICATION 5 TYHE-HWBR-GZHD-HADT VTL -- ------------------- --------------------
- 22. 22 Licenses Feature License VTL / IBMi There are two types of VTL feature Licenses • Windows/Open Systems clients require a VTL License • IBMi or AS/400 clients backing up via VTL require an I/OS License Feature licenses: ## License Key Feature -- ------------------- ----------- 1 BESX-HSER-FYAC-TGBS I/OS 2 XTSR-ZYWE-ZGFW-FHAE REPLICATION 3 DCHF-SBCC-ASWG-TVGB VTL -- ------------------- -----------
- 23. 23 Licenses Feature License Gateway Systems They are no longer sold but, should you encounter a customer with a legacy Data Domain Gateway System, you will find two types of licenses: • Half Capacity • Full Capacity Licenses -------- ## License Key Feature -- ------------------- ----------------- 1 DZSG-BFSZ-GAWC-VHHF CAPACITY-FULLSIZE 2 YEVW-ZBYT-RSXD-VEDH REPLICATION -- ------------------- -----------------
- 24. 24 Licenses Feature License Archive Another deprecated license you might encounter is Archivestore. This was a $0 license intended to identify systems whose primary use case was archiving rather than backup. This identification strategy did not work because a lot of Sales AMs automatically added the license to the system because it was no cost.
- 25. 25 Autosupport Space Reporting Filesys show space Active Tier: Resource Size GiB Used GiB Avail GiB Use% Cleanable GiB* ---------------- -------- --------- --------- ---- -------------- /data: pre-comp - 1750964.6 - - - /data: post-comp 173462.2 130406.5 43055.8 75% 3464.6 /ddvar 132.9 18.8 107.3 15% - ---------------- -------- --------- --------- ---- -------------- * Estimated based on last cleaning of 2015/06/18 17:23:51. Gib = Gibibyte https://en.wikipedia.org/wiki/Gibibyte /data: pre-comp The amount of pre-compressed data on the system /data: post-comp The amount of space actually used after dedup & compr. /ddvar: The space reserved for DDOS & Logs
- 26. 26 Autosupport Space Reporting Filesys show space Active Tier: Resource Size GiB Used GiB Avail GiB Use% Cleanable GiB* ---------------- -------- --------- --------- ---- -------------- /data: pre-comp - 1750964.6 - - - /data: post-comp 173462.2 130406.5 43055.8 75% 3464.6 /ddvar 132.9 18.8 107.3 15% - ---------------- -------- --------- --------- ---- -------------- * Estimated based on last cleaning of 2015/06/18 17:23:51. • Size Gib /data/post-comp: usable space This value may change – refer to https://support.emc.com/kb/181295 • Use% Shows the amount of space used on your system. Refer to https://support.emc.com/kb/181217 for more information on system utilization
- 27. 27 Autosupport Space Reporting Filesys show space Active Tier: Resource Size GiB Used GiB Avail GiB Use% Cleanable GiB* ---------------- -------- --------- --------- ---- -------------- /data: pre-comp - 1750964.6 - - - /data: post-comp 173462.2 130406.5 43055.8 75% 3464.6 /ddvar 132.9 18.8 107.3 15% - ---------------- -------- --------- --------- ---- -------------- * Estimated based on last cleaning of 2015/06/18 17:23:51. Cleanable GiB* is an estimated value and NOT what you will gain as free space after the next cleaning run. https://support.emc.com/kb/181047 Cleaning finished 17:23 – scheduled to start 1am = 16 h 23 min for cleaning Filesystem Cleaning Configuration --------------------------------- 52 Percent Throttle Filesystem cleaning is scheduled to run "Thu" at "0100". DO NOT CLEAN MORE THAN ONCE A WEEK !!!
- 28. 28 Autosupport Space Reporting Filesys show space Example of a system running Extended Retention: • Active Tier • Archive Tier • Total Active Tier: Resource Size GiB Used GiB Avail GiB Use% Cleanable GiB* ---------------- -------- --------- --------- ---- -------------- /data: pre-comp - 3702382.5 - - - /data: post-comp 368779.2 261204.8 107574.4 71% 10964.7 /ddvar 308.1 14.8 277.6 5% - ---------------- -------- --------- --------- ---- -------------- Archive Tier: Resource Size GiB Used GiB Avail GiB Use% Cleanable GiB* ---------------- -------- --------- --------- ---- -------------- /data: pre-comp - 1296180.4 - - - /data: post-comp 128395.8 75106.2 53289.6 58% - ---------------- -------- --------- --------- ---- -------------- Total: Resource Size GiB Used GiB Avail GiB Use% Cleanable GiB* ---------------- -------- --------- --------- ---- -------------- /data: pre-comp - 4998563.0 - - - /data: post-comp 497175.0 336311.0 160864.0 68% 10964.7 /ddvar 308.1 14.8 277.6 5% - ---------------- -------- --------- --------- ---- --------------
- 29. 29 Autosupport Space Reporting Filesys show compression From: 2015-06-16 16:00 To: 2015-06-23 16:00 Pre-Comp Post-Comp Global-Comp Local-Comp Total-Comp (GiB) (GiB) Factor Factor Factor (Reduction %) --------------- --------- --------- ----------- ---------- ------------- Currently Used: 1750964.7 130406.5 - - 13.4x (92.6) Written:* Last 7 days 155311.1 7712.0 8.1x 2.5x 20.1x (95.0) Last 24 hrs 39555.9 1345.3 12.3x 2.4x 29.4x (96.6) --------------- --------- --------- ----------- ---------- ------------- Pre-Comp = Data written before compression Post-Comp = Storage used after compression Global-Comp Factor = Pre-Comp / (Size after de-dupe) Local-Comp Factor = (Size after de-dupe) / Post-Comp Total-Comp Factor = Pre-Comp / Post-Comp Reduction % = ((Pre-Comp - Post-Comp) / Pre-Comp) * 100 Currently used shows the same information as filesys show space
- 30. 30 Autosupport Space Reporting Filesys show compression From: 2015-06-16 16:00 To: 2015-06-23 16:00 Pre-Comp Post-Comp Global-Comp Local-Comp Total-Comp (GiB) (GiB) Factor Factor Factor (Reduction %) --------------- --------- --------- ----------- ---------- ------------- Currently Used: 1750964.7 130406.5 - - 13.4x (92.6) Written:* Last 7 days 155311.1 7712.0 8.1x 2.5x 20.1x (95.0) Last 24 hrs 39555.9 1345.3 12.3x 2.4x 29.4x (96.6) --------------- --------- --------- ----------- ---------- ------------- Pre-comp: data precompressed sent to System Post-Comp: data stored on System – usable for amout that is approx. replicated Global-Comp: Effect of deduplication Local-Comp: Effect of Zip
- 31. 31 Autosupport Space Reporting Filesys show compression Please read this documents for further clarification of filesys show compression https://support.emc.com/docu48770_Case-Study-of-Filesys-Show- Compression-and-Filesys-Show-Space.pdf?language=en_US https://emc--c.na5.visual.force.com/articles/How_To/86266-Understanding- DataDomain-Compression
- 32. 32 Autosupport Space Reporting Filesys show compression • Overview for understanding the effects of dedup, local compression and the Meta- data related to that backup. • Not usable for space reporting since it doesn’t reflect on deletions as mentioned in the article above File System Compression (total, type 9) --------------------------------------- Files: 139,191; bytes/storage_used: 17.3 Original Bytes: 1,877,774,018,815,796 Globally Compressed: 262,632,674,536,121 Locally Compressed: 107,938,983,799,644 Meta-data: 835,251,098,900 File System Compression (last 7 days, type 9) --------------------------------------------- Files: 3,585; bytes/storage_used: 18.8 Original Bytes: 186,041,235,236,773 Globally Compressed: 23,539,408,407,960 Locally Compressed: 9,797,695,970,104 Meta-data: 74,271,551,688 File System Compression (last 24 hours, type 9) ----------------------------------------------- Files: 685; bytes/storage_used: 20.2 Original Bytes: 56,627,165,012,843 Globally Compressed: 6,313,408,878,904 Locally Compressed: 2,789,103,230,415 Meta-data: 19,907,475,352
- 33. 33 Autosupport Space Reporting File Distribution • Number of backup files on the System and Age • Can help to understand the retention of data depending on the software and protocol used. File Distribution ----------------- 139,191 files in 49,066 directories Count Space ----------------------------- -------------------------- Age Files % cumul% GiB % cumul% --------- ----------- ----- ------- -------- ----- ------- 1 day 685 0.5 0.5 52738.2 3.0 3.0 1 week 2,900 2.1 2.6 120526.2 6.9 9.9 2 weeks 3,946 2.8 5.4 138273.0 7.9 17.8 1 month 8,631 6.2 11.6 316196.9 18.1 35.9 2 months 6,863 4.9 16.5 407256.6 23.3 59.2 3 months 108,596 78.0 94.6 572292.0 32.7 91.9 6 months 6,572 4.7 99.3 139919.8 8.0 99.9 1 year 409 0.3 99.6 1610.7 0.1 100.0 > 1 year 589 0.4 100.0 0.0 0.0 100.0 --------- ----------- ----- ------- -------- ----- -------
- 34. 34 Autosupport Space Reporting File Distribution TSM Filedevice example File Distribution ----------------- 4,281 files in 9 directories Count Space ----------------------------- -------------------------- Age Files % cumul% GiB % cumul% --------- ----------- ----- ------- -------- ----- ------- 1 day 5 0.1 0.1 65.1 0.1 0.1 1 week 4 0.1 0.2 129.5 0.2 0.3 2 weeks 0 0.0 0.2 0.0 0.0 0.3 1 month 4 0.1 0.3 119.0 0.2 0.5 2 months 1 0.0 0.3 17.1 0.0 0.5 3 months 0 0.0 0.3 0.0 0.0 0.5 6 months 3 0.1 0.4 13.6 0.0 0.5 1 year 4,254 99.4 99.8 68208.9 99.1 99.6 > 1 year 10 0.2 100.0 251.0 0.4 100.0 --------- ----------- ----- ------- -------- ----- -------
- 35. 35 Autosupport Space Reporting File Distribution by size Count Space ----------------------------- -------------------------- Size Files % cumul% GiB % cumul% --------- ----------- ----- ------- -------- ----- ------- 1 KiB 67,810 48.7 48.7 0.1 0.0 0.0 10 KiB 121 0.1 48.8 0.0 0.0 0.0 100 KiB 23 0.0 48.8 0.0 0.0 0.0 500 KiB 1,298 0.9 49.8 0.3 0.0 0.0 1 MiB 182 0.1 49.9 0.1 0.0 0.0 5 MiB 1,497 1.1 51.0 3.5 0.0 0.0 10 MiB 271 0.2 51.2 2.0 0.0 0.0 50 MiB 3,539 2.5 53.7 105.1 0.0 0.0 100 MiB 49,498 35.6 89.3 4232.4 0.2 0.2 500 MiB 1,064 0.8 90.0 163.3 0.0 0.3 1 GiB 3,249 2.3 92.4 446.9 0.0 0.3 5 GiB 505 0.4 92.7 1307.4 0.1 0.4 10 GiB 1,435 1.0 93.8 11128.7 0.6 1.0 50 GiB 4,582 3.3 97.0 128322.5 7.3 8.3 100 GiB 29 0.0 97.1 2248.1 0.1 8.5 500 GiB 4,085 2.9 100.0 1598250.7 91.4 99.9 > 500 GiB 3 0.0 100.0 2602.1 0.1 100.0 --------- ----------- ----- ------- -------- ----- ------- <3% of files are between 100-500 GiB >91% of capacity is consumed by approximately 4,100 files VTL with 400 GB virtual tape cartridges
- 36. 36 Autosupport Space Reporting File Distribution by size Count Space ----------------------------- -------------------------- Size Files % cumul% GiB % cumul% --------- ----------- ----- ------- -------- ----- ------- 1 KiB 1 0.0 0.0 0.0 0.0 0.0 10 KiB 0 0.0 0.0 0.0 0.0 0.0 100 KiB 0 0.0 0.0 0.0 0.0 0.0 500 KiB 0 0.0 0.0 0.0 0.0 0.0 1 MiB 1 0.0 0.0 0.0 0.0 0.0 5 MiB 1 0.0 0.1 0.0 0.0 0.0 10 MiB 0 0.0 0.1 0.0 0.0 0.0 50 MiB 8 0.2 0.3 0.1 0.0 0.0 100 MiB 0 0.0 0.3 0.0 0.0 0.0 500 MiB 0 0.0 0.3 0.0 0.0 0.0 1 GiB 0 0.0 0.3 0.0 0.0 0.0 5 GiB 0 0.0 0.3 0.0 0.0 0.0 10 GiB 5 0.1 0.4 41.6 0.1 0.1 50 GiB 4,265 99.6 100.0 68762.6 99.9 100.0 100 GiB 0 0.0 100.0 0.0 0.0 100.0 500 GiB 0 0.0 100.0 0.0 0.0 100.0 > 500 GiB 0 0.0 100.0 0.0 0.0 100.0 --------- ----------- ----- ------- -------- ----- -------
- 37. 37 Consumption • Reports details of • daily capacity consumption • 13 most recent days • weekly consumption • 13 most recent weeks • Reconciles available space resulting from • Consumption • Data ingest • Data received via replication • DDFS overhead (metadata+fragmentation) • Space Reclaimed from Cleaning • Data deleted after filesystem cleaning • This report shows: • available space trends • capacity usage trends Space Consumption Formula
- 38. 38 Mtree Statistics Mtree list shows the amount of data written to a specific Mtree Mtree List ------------ Name Pre-Comp (GiB) Status -------------------- -------------- ------ /data/col1/S-Barcode 686169.4 RW /data/col1/backup 896735.1 RW /data/col1/coruscant 168041.1 RW -------------------- -------------- ------ D : Deleted Q : Quota Defined RO : Read Only RW : Read Write RD : Replication Destination RLGE : Retention-Lock Governance Enabled RLGD : Retention-Lock Governance Disabled RLCE : Retention-Lock Compliance Enabled
- 39. 39 Mtree Statistics Mtree show compression is similar to filesys show compression but on an Mtree Basis. Mtree Show Compression /data/col1/S-Barcode --------------------------------------------- From: 2015-06-16 16:00 To: 2015-06-23 16:00 Pre-Comp Post-Comp Global-Comp Local-Comp Total-Comp (GiB) (GiB) Factor Factor Factor (Reduction %) ------------- -------- --------- ----------- ---------- ------------- Written:* Last 7 days 46679.0 2178.0 7.5x 2.8x 21.4x (95.3) Last 24 hrs 23368.8 668.4 13.3x 2.6x 35.0x (97.1) ------------- -------- --------- ----------- ---------- ------------- * Does not include the effects of pre-comp file deletes/truncates
- 40. 40 Griffin Integration with Avamar Avamar uses a different reporting concept than Data Domain. Because every backup is a Full, Avamar reports on the volume of data scanned rather than the amount of data transmitted. This leads to numbers that are astronomically large compared to what you would expect. Unfortunately, these numbers are unusable for DD Statistics and Quotas From a Data Domain perspective, the parts in red are incorrect, the blue ones are correct Filesys Compression -------------- From: 2015-06-18 06:00 To: 2015-06-25 06:00 Pre-Comp Post-Comp Global-Comp Local-Comp Total-Comp (GiB) (GiB) Factor Factor Factor (Reduction %) --------------- ---------- --------- ----------- ---------- ------------- Currently Used: 52764703.0 305557.3 - - 172.7x (99.4) Written:* Last 7 days 7804221.2 21939.9 169.9x 2.1x 355.7x (99.7) Last 24 hrs 689837.1 1831.5 173.9x 2.2x 376.7x (99.7) --------------- ---------- --------- ----------- ---------- -------------
- 41. 41 Griffin Integration with Avamar Mtree Statistics The parts in red are not correct, the blue ones are Mtree Show Compression /data/col1/avamar-1409074175 --------------------------------------------- From: 2015-06-18 06:00 To: 2015-06-25 06:00 Pre-Comp Post-Comp Global-Comp Local-Comp Total-Comp (GiB) (GiB) Factor Factor Factor (Reduction %) ------------- --------- --------- ----------- ---------- ------------- Written:* Last 7 days 6956516.2 17971.9 180.5x 2.1x 387.1x (99.7) Last 24 hrs 689173.2 1810.9 175.2x 2.2x 380.6x (99.7) ------------- --------- --------- ----------- ---------- ------------- * Does not include the effects of pre-comp file deletes/truncates Mtree Show Compression /data/col1/Default --------------------------------------------- Pre-Comp Post-Comp Global-Comp Local-Comp Total-Comp (GiB) (GiB) Factor Factor Factor (Reduction %) ------------- -------- --------- ----------- ---------- ------------- Written:* Last 7 days 65525.9 1880.0 24.3x 1.4x 34.9x (97.1) Last 24 hrs 421.0 17.9 15.0x 1.6x 23.5x (95.7) ------------- -------- --------- ----------- ---------- -------------
Editor's Notes
- Hello and Welcome to EMC Presales Accreditation for Q3 2015. My name is Russell Brown and I work for EMC in Sydney, Australia. After many years in Data Protection Presales, I now manage the team who is responsible for your quarterly accreditation along with many other programs related to Sales and Presales "Enablement" for EMC's "Core Technologies". As we close out 2015 and start into 2016, you will see many new approaches to "Enablement". During this transition, please feel free to reach out to us and keep us informed about what is working and which areas could use some attention. We will do our best to respond to your needs so that you can better support our customers and our partners. As you are probably aware, there is a mountain of information contained in each Data Domain Autosupport. Rather than cover everything in a single 8 hour long training, what we have decided to do is to create an ongoing series of modules to focus on each individual component of the autosupport. This Data Domain Autosupport module is the first module in that series and it will cover two portions of the Autosupport. Those two parts are: Hardware configuration and Licenses installed on a Data Domain system. All other parts of the Autosupport will be covered during future installments in this series.
- In the first part of the autosupport you will find the General Info section which contains all information about timezone, DDOS Version, Serial Number and Model Number of this specific system. You can also see the current hostname, location and the Admin Email that has been entered for this system.
- System Memory is shown further down in the autosupport. The memory information is important in case you want to upgrade systems to the maximum storage capacity. The larger systems can be purchased with 2 different Memory Configurations. To upgrade the capacity, a kit will be required which contains both Physical Memory modules and an Expanded Capacity License
- Networking Hardware This part shows the Network Cards that are physically present and the link speed. In this example you can see that the system has two 10 Gig Optical Ports with no link
- Disk Status gives a short overview of the installed disks and where they are assigned from a logical point of view. This example shows a system that is using extended retention software. The Active Tier is the Area where data is initially written. The Archive Tier is the area where data is moved for long term retention An example of this would be - backup data that is kept for a long period of time that meets one of the configured migration policies would be moved from the Active Tier to the Archive Tier
- The Enclosure Show command provides a complete output of all hardware information. It is part of the autosupport output but it can also be issued from the Command Line Interface. Some parts of the information is also visible in the GUI but some information can only be seen via CLI The "Enclosure Show" command can be used with several options: One example is Chassis This would be typed: enclosure show chassis enclosure 1 Other options are: Controllers Cpus Fans Io-cards Memory Nvram Powersupply Temperature-sensors This command can show a lot of details like Fan Speed, Temperature and more. Each of these options will not be covered in depth in this module since these options are primarily used by tech support. If you are interested in the details of these options, please run the command on your local Data Domain system and check the output.
- Enclosure show summary provides an overview of the installed disk shelves. In this example you can see enclosure 1 which is the DD890 Head with 4 internal disks in the head unit and 6 ES30 shelves with 15 disks each
- The IO Card information gives you an overview of all cards in your Data Domain System. Slot gives the physical location in the chassis, Device gives you the type of interface. Ports shows the connectivity for the specific cards and the Address gives you an address depending on the type of the card. More information about this is on the next slide
- The last column describes the Mac or WWPN address. WWPN will be used for FC Zoning. With DD OS 5.3 or later, this information can be modified using the SCSI Target command. For more information please refer to the DDOS Command Reference Guide and handle with care. This example shows a DD990 with Extended Retention enabled so you can see 4 SAS Adapters with 4 ports each. This information can be seen again later when we look at the Topology View.
- In this slide you can see the specific information about the Controller – or Enclosure 1 It shows the Model Number and the Serial Number of the System This Head contains 4 600 GB Disks which are used for storing configuration information and internal files. You can also see the CPU’s that are used in this DD990, this is a question that is often raised by customers. Although it is not an EMC site, here is a link to the Intel web page which provides more performance and configuration details for the CPUs used in this DD990. Although it doesn't really matter, customers who like science projects and those who enjoy theorizing about how Data Domain could be improved, often want to know which chipset or processor family the Data Domain CPUs belong to – Nehalem, Sandy Bridge, etc. In this case the CPUs are from the Westmere-EX family http://ark.intel.com/products/53579/Intel-Xeon-Processor-E7-4870-30M-Cache-2_40-GHz-6_40-GTs-Intel-QPI
- This Slide shows the NVRAM Card configuration. The Slot shows the physical location in the chassis. In this example only one NVRAM Card is present but some models can use 2 NVRAM cards. For the DD890 there are two configurations. Older models use 2 NVRAM Cards and newer models use 1 NVRAM Card. In case the Batteries go bad over time the cards will need to be replaced. When installing a new DD System the Batteries need to be charged otherwise the filesystem will not start.
- The Enclosure show topology command shows the dual path connectivity from the controller to the Expansion shelves. The details shown include the Enclosure Number The Controller for the Shelf - either A or B The Cable Port location either - Host or Expansion The way I think of the cabling sequence is that the Host port is always the one in the chain closest to the host. Whereas the Expansion port might not have another shelf connected to it. If you're familiar with the old days of SCSI termination, you could think of this as being similar to the end of the SCSI chain. Verify that each shelf is connected down two paths. In this example, "Path A" shows Port "a" on SAS Controller "2" being connected to Shelves 2, 6 and 5 in sequence on the "A" controllers. "Path B" shows Port "b" on SAS Controller "3" being connected to Shelves 5, 6 and 2 in sequence on the "B" controllers. If this order becomes interrupted, you might have a cable or connector problem. Unlike most other storage systems, Data Domain Systems are not dependent on the order of the shelves. So, even if the shelves are re-cabled in a different order – the system will continue to work. This information can also be viewed using the command disk port show summary which is also part of the autosupport output
- System show hardware shows the location of all PCI Cards and the Ports. In this example you can see the internal Gigabit Ethernet card in Slot 0 and 2 LSI SAS Adapters in Slots 2 and 3
- This example shows a DD9500 output of system show hardware. You can see Slot M with specific Port Naming The system also contains 4 Port 10 Gb Ethernet Cards and 2 Port 16 Gb Fiber Cards
- Disk show hardware shows the hardware information from the disks, This includes the Manufacturer and most importantly the capacity of the disks.
- Beginning with DDOS 5.1, Expansion shelves require a license when being added to a System. There are Licenses per Tier. The Licenses separate the shelves for use in either the Active Tier or the Extended Retention Tier. Shelves cannot be added to a different type of tier. This means that you cannot add an Extended retention Tier Shelf to an Active Tier. Please contact the Sales Operations Team in case you need to switch licenses for use in a different Tier.
- Licenses enable special features. For example, Encryption. Depending on the Version of the DDOS you may see different features being added. In this example you see Secure Multi Tenancy. Licenses are sold on a per Head basis regardless of how you use the specific function. If you want to perform DD Boost backups you will need a DD Boost license. The single license is good regardless of whether you're backing up 1 TB or 1 PB of data. Licenses are attached to the head which means, if you perform a head upgrade you will also need to purchase new Licenses.
- As already mentioned in the discussion about Memory, if you want to expand a system beyond a certain capacity you will require a Memory Upgrade as well as an Expanded Storage License
- The Encryption Feature allows the encryption of the complete Filesystem of a Data Domain System. There is no lower level granularity. For example, I can not encrypt just one selected MTree. I must encrypt the entire filesystem. Encryption can use AES 128 or AES 256 standards. For further information please refer to the inside emc page DOC-26072
- The Secure Multi Tenancy License was introduced with DDOS 5.5 and DDBoost Version 3.0. It allows the usage of Secure Multi Tenancy features. More Details on this feature can be found on the Inside EMC Doc 23573
- DDBoost and Replication Licenses are needed on all hosts that will use the DDBoost protocol for Clone Controlled or Managed File Replication.
- There are two types of VTL use cases. If you perform “normal” open-systems VTL backups, that's your Windows, UNIX, Linux, you will need a VTL License. If you need to perform VTL backups of IBM/i (formerly known as iSeries or the AS/400), you will also need an I/OS License
- This license is pretty much just FYI - in case you happen to see one and wonder what it is. The Data Domain Gateway Systems, which are no longer sold, had a licensing model which had two options. Half and Full capacity.
- Another deprecated license you might encounter is Archivestore. This was a $0 license intended to identify systems whose primary use case was archiving rather than backup. This identification strategy did not work because a lot of Sales AMs automatically added the license to the system because it was no cost.
- The command being used to display this information is filesys show space. All numbers displayed here are in Gibibytes If you don’t know what a Gibibyte is, please ask Michael Colby. Oh no… wait a minute … It looks like either Michael or Ditmar were nice enough to include a Wikipedia link. At this level, “Filesys Show Space” has no granularity. The reporting does not differentiate between storage Tier or MTree or any other allocation within the DD Filesystem. Filesys Show Space only shows the view of the entire filesystem. A later slide will address reporting on Extended Retention capacity. /data/pre-comp shows the amount of pre-compressed data stored on the complete system regardless of application and protocol that was used to write the data to the Data Domain system. /data/post-comp shows the amount of space actually used after the effects of deduplication and compression. /ddvar shows the space that is used for the DDOS and its logfiles. This space cannot be modified.
- The Size Gib in /data post-compression is also referred to as the usable space. This is the quantity of physical storage available after accounting for RAID-6. In this example, the usable space is 173 TiB. 130 TiB have already been used and there are still 43 TiB available. This means that 75% of the physical storage space has been consumed which is shown in the “Use%” column. The value of the usable space is not a fixed number. Metadata and structural overhead in the filesystem will cause 2 identical systems to report different amounts of usable space even though their hardware is exactly the same. This is a common question customers will want to have explained to them. Please refer to the Knowledge Base Article 181295 for further information on these calculations. Please monitor the Use% number and make sure that you do not exceed 85% of system capacity utilization. For further information on this topic please refer to the knowledge base article - 181217
- The value for the number of Cleanable Gibibytes is only an estimated value. It is not possible to determine in advance the amount of data storage space that will be freed with a cleaning run. For further information on this estimate please see the Knowledge Base Article 181047. The cleaning in this example finished at 5:23 PM so, checking the autosupport further, you can see that cleaning is scheduled to run on Thursday at 1AM. That means that this system took 16 hours and 23 minutes to run cleaning. A healthy system should be able to finish cleaning within 24 hours. Do not clean more than once a week because this will result in Segment locality issues. If you think that you need to run cleaning more frequently, you probably need more capacity.
- This example shows the filesys show space output of a data domain system using extended retention software. The Archive Tier, what we now call Extended Retention tier, is an independent deduplication area and has its own deduplication statistics.
- Filesys show compression is another command that shows filesystem usage. Currently, this command will show the same information that you have already seen in filesys show space.
- The Last 7 days and last 24 hours show the amount of data sent to the System and how much was stored in these timeframes. The Post-Compression Number is a valid measure of the amount of traffic you would need to replicate in a specific timeframe such as daily or weekly. Global Compression factor shows the effect of deduplication Local Compression factor shows the effect of the compression that happens after the deduplication of the data This is based on the compression method enabled for DDFS – either LZ or GZ Total Compression Factor is the result of the effects of both Global and Local compression. This number is what most people quote as the deduplication rate.
- This course does not have a quiz but, for your own personal knowledge about filesys show compression we recommend you review the two documents listed on this page.
- As stated in the link on the previous slide, filesys show compression helps you understand the overall effect of deduplication and local compression. It also shows the Meta-data related to the specific backups. This information is not usable for space reporting because it does not reflect file deletions correctly
- Reviewing the file distribution can help you understand how a systems is being used. For example, if a customer is using NetWorker, you will see a large number of files because every Advanced File Type Device or DD Boost Device configured will dynamically create 100 directories each with 100 sub-directories. For a NetWorker system with 10 Data Domain devices configured, you would expect to see at least 100 x 100 x 10 = 100,000 files The file Age distribution can help explain further information about the usage of the system. In mixed data type environments or if certain software like TSM is used, interpreting the data aging is extremely difficult and can lead to a misunderstandings about the nature of the data.
- In this example you see a TSM Filedevice on a Data Domain. This file distribution provides no insight into data retention since TSM only backs up new and changed files over time.
- The “file distribution by size” helps you understand the size of your files – a lot of 1Kibibyte files typically points to NetWorker. The size of files depends on the behavior of the application. NetWorker for example creates files that are the size of the saveset. In this example you can see a mixed use case with both Filedevices and VTL. The majority of data is stored in 400 GB large files which represent Virtual Tape Cartridges If the analysis of this information does not jump off the page at you, please take a look at the fact that 3% of the files on the system contain 91% of the capacity used. I’ve used red and green boxes to highlight this.
- This is a TSM example where TSM is using a Filesize between 10 and 50 GB
- Space consumption reporting provides the details of daily capacity consumption for the last 13 days and for the past 13 weeks. This report also provides details about the components of that space usage. Those components are: space consumed by local data ingest space consumed by data received via replication space consumed as a result of DDFS overhead space freed up after file system cleaning completes and space from deleted data is reclaimed This report has been referred to by some as a “space burn” report. It can provide the basis for a trend analysis of capacity usage. This report indicates whether available space is increasing or decreasing over time and what are the components of that space consumption. For example: Available space could be decreasing because more data is being ingested locally as a result of data growth or due to the addition of new data sets not previously backed up. Space could be decreasing because the amount of data ingested via replication is increasing. Space could be decreasing because less space is being reclaimed by file system cleaning, which could be an indication that retention times are increasing.
- Mtree list gives you an overview on the amount of data that was written to each Mtree as well as the state of each Mtree.
- Mtree show compression has the same behavior as filesys show compression. It shows the amount of data ingested during the last 7 days and in the past 24 hours. This report provides de-duplication statistics for each Mtree.
- Now let’s have a look at the Avamar / Griffin Integration. Avamar has a completely different data architecture and was not originally designed to write to a Data Domain System. Because Avamar does Full backups only, it reports on the total size of the data scanned on each client. These numbers are reported to Data Domain although due to the nature of Avamar’s client side de-duplication, that full volume of data is never sent to the Data Domain system. This results in a huge amount of data “virtually” transmitted to the Data Domain. These numbers cause confusion with the Data Domain statistics. In this example you see a report that Avamar has sent 7.8 Petabyte of data to DD during the past 7 days. This is an average of 1.1 PB per day. In reality, only about 3 TB per day has been transmitted to the Data Domain system. These reporting discrepancies lead to situations like the case where quotas can not be managed for an Mtree with an Avamar workload. This will be explained in the next slide.
- This example shows that in a mixed use case situation, you cannot rely on the Avamar reported numbers. You will need to manually sum the Non-Avamar Mtrees to create a valid pre-comp statistic. The Avamar Mtree displays some outlandish numbers but the numbers shown for the Default Mtree are realistic.