‫ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺑﺎ‬

‫‪VMWare vSphere 5‬‬

‫ﺳﻴﺪ ﻣﺤﻤﺪ ﺟﻮﺍﺩ ﺍﺳﻤﺎﻋﻴﻠﻲ‬

‫‪[email protected]‬‬
‫ﭘﺎﻳﻴﺰ ‪91‬‬

‫‪1‬‬
2
3
 ‫ﻓﻬﺮﺳﺖ ﻣﻄﺎﻟﺐ‬

‫ﺻﻔﺤﻪ‬ ‫ﻣﻮﺿﻮﻉ‬

‫ﻓﺼﻞ ﺍﻭﻝ‪ :‬ﻣﻘﺪﻣﻪ ‪8 ....................................................................................................‬‬

‫ﻓﺼﻞ ﺩﻭﻡ‪ :‬ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ‪11 ......................................................................................‬‬

‫‪ 1-2‬ﻣﺪﻝ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ‪12 ........................ ................................ ................................................................‬‬

‫‪ 2-2‬ﻻﻳﻪﻫﺎﻱ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ‪13 ................................................................................................................‬‬

‫‪ 1-2-2‬ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺩﺳﺖﻳﺎﺑﻲ ‪14.............................................................................................................................‬‬

‫‪ 2-2-2‬ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﻛﺎﺭﺑﺮﺩ ‪17..................................................................................................................................‬‬

‫‪ 3-2-2‬ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﭘﺮﺩﺍﺯﺵ ‪19 .............................................................................................................‬‬

‫‪ 1-3-2-2‬ﻳﻚ ﺳﻴﺴﺘﻢ ﺑﺠﺎﻱ ﭼﻨﺪ ﺳﻴﺴﺘﻢ ﻭﭼﻨﺪ ﺳﻴﺴﺘﻢ ﺑﺠﺎﻱ ﻳﻚ ﺳﻴﺴﺘﻢ‪21 ............................ .‬‬

‫‪ 1-1-3-2-2‬ﭘﻴﻜﺮﺑﻨﺪﻱ ﻳﻚ ﺳﻴﺴﺘﻢ ﺑﻄﻮﺭﻱ ﻛﻪ ﺍﺯ ﺩﻳﺪ ﺧﺎﺭﺟﻲ ﭼﻨﺪ ﺳﻴﺴﺘﻢ ﺩﻳﺪﻩ ﺷﻮﺩ ‪21 .....‬‬

‫‪ 2-1-3-2-2‬ﭘﻴﻜﺮﺑﻨﺪﻱ ﭼﻨﺪﺳﻴﺴﺘﻢ ﺑﻄﻮﺭﻱ ﻛﻪ ﺍﺯ ﺩﻳﺪ ﺧﺎﺭﺟﻲ ﻳﻚ ﺳﻴﺴﺘﻢ ﺩﻳﺪﻩ ﺷﻮﻧﺪ ‪28 .....‬‬

‫‪ 4-2-2‬ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺷﺒﻜﻪ ‪30...................................................................................................................................‬‬

‫‪ 5-2-2‬ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺩﺍﺩﻩ ‪31.....................................................................................‬‬

‫‪ 6-2-2‬ﺍﻣﻨﻴﺖ ﺩﺭ ﺳﻴﺴﺘﻢﻫﺎﻱ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ‪35.....................................................................................................‬‬

‫‪ 7-2-2‬ﻣﺪﻳﺮﻳﺖ ﻣﺤﻴﻂ ﻣﺠﺎﺯﻱ ‪35.............................................................................................................................‬‬

‫ﭼﻨﺪ ﺍﺷﺘﺒﺎﻩ ‪36 ....................................... ................................ ................................‬‬ ‫‪ 3-2‬ﭼﻨﺪ ﺍﺻﻄﻼﺡ‬

‫‪ 1-3-2‬ﻛﻼﺳﺘﺮ ‪36............................................................................................................................................................‬‬

‫‪ 2-3-2‬ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺩﺳﻜﺘﺎپ ‪38.............................................................................................................................‬‬

‫‪ 3-3-2‬ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺳﺮﻭﺭ ‪41....................................................................................................................................‬‬

‫‪4‬‬
42 ............................................... VMware vSphere 5 ‫ ﻣﻌﺮﻓﻲ ﻣﺠﻤﻮﻋﻪ‬:‫ﻓﺼﻞ ﺳﻮﻡ‬

44 ......................................................................................... ................................ VMware ESXi 1-3

45 ...................................................................................................... VMware vCenter Server 2-3

46 .................................... ................................................................ vSphere Update Manager 3-3

46 ........................................................................ vSphere Client and vSphere web Client 4-3

47 ........................................................................................................ VMware vShield zones 5-3

47 .......................................................................................... VMware vCenter Orchestrator 6-3

48 .................................... ................................................................ ‫ ﭼﻨﺪ ﭘﺮﺩﺍﺯﺷﻲ ﻣﺘﻘﺎﺭﻥ ﻣﺠﺎﺯﻱ‬7-3

49 ....................................................... vSphere vMotion and vSphere Storage vMotion 8-3

49 .............................................................................................. ‫ ﺳﻴﺴﺘﻢ ﺯﻣﺎﻧﺒﻨﺪ ﻣﻨﺎﺑﻊ ﺗﻮﺯﻳﻊ ﺷﺪﻩ‬9-3

50 ........................................................................................................ vSphere Storage DRS 10-3

51 ..... ‫ ﺳﻴﺴﺘﻢ ﻛﻨﺘﺮﻝ ﻭﺭﻭﺩﻱ ﺧﺮﻭﺟﻲ ﺷﺒﻜﻪ ﻭ ﻛﻨﺘﺮﻝ ﻭﺭﻭﺩﻱ ﺧﺮﻭﺟﻲ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ‬11 3

51 ............................................................................................... (HA) ‫ ﻗﺎﺑﻠﻴﺖ ﺩﺳﺘﺮﺳﻲ ﻣﺴﺘﻤﺮ‬12-3

52 ........................................................................................................ (FT) ‫ ﺳﻴﺴﺘﻢ ﺗﺤﻤﻞ ﺧﻄﺎ‬13-3

54 ............ vSphere Storage API for data protection and VMware data recovery 14-3

54 ...................................................................... Xenserver , Hyper–V , VMware ‫ ﻣﻘﺎﻳﺴﻪ‬15-3

56 ............................................ vSphere 5 ‫ ﻧﺼﺐ ﻭ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﻣﺠﻤﻮﻋﻪ‬:‫ﻓﺼﻞ ﭼﻬﺎﺭﻡ‬

58 ......................................................................................... ESXi ‫ ﻧﺼﺐ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﻭ ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬1-4

58.................................................................................................................................................. ESXi ‫ ﻧﺼﺐ‬1-1-4

61............................................................................................................................. ESXi ‫ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺍﻭﻟﻴﻪ‬2-1-4

63 ....................................... ................................ ................................ vCenter Server ‫ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ‬2-4

5
‫‪ 1-2-4‬ﺳﺎﺧﺘﺎﺭ ﻭ ﺳﺮﻭﻳﺲ ﻫﺎﻱ ‪63 .......................................................................................... vCenter Server‬‬

‫‪ 2-2-4‬ﻧﻴﺎﺯﻣﻨﺪﻱﻫﺎﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻭ ﺳﺨﺖﺍﻓﺰﺍﺭﻱ ‪65........................................................... vCenter Server‬‬

‫‪ 3-2-4‬ﺁﻣﺎﺩ ﺳﺎﺯﻱ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ‪68 ..................................................................... ................................‬‬

‫‪ 4-2-4‬ﻧﺼﺐ ‪70............................................................................................................................. vCenter Server‬‬

‫‪ 5-2-4‬ﻧﺼﺐ ‪ vCenter Server‬ﺩﺭ ﺣﺎﻟﺖ ‪72 ............................................................................. linked mode‬‬

‫‪ 3-4‬ﻧﺼﺐ ‪ vSphere Client‬ﺑﺮﺍﻱ ﻭﺭﻭﺩ ﺑﻪ ‪73 ......................................................... vCenter Server‬‬

‫‪ 4-4‬ﻧﺼﺐ ‪75 ..................................................................... ................................ vSphere Web Client‬‬

‫ﻓﺼﻞ ﭘﻨﺠﻢ‪ :‬ﺩﺳﺘﮕﺎﻩﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺩﺍﺩﻩ ‪78 ...........................................................‬‬

‫‪ 1-5‬ﺍﻧﻮﺍﻉ ﺳﻴﺴﺘﻢﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ‪79 .................................... ................................................................‬‬

‫‪ 1-1-5‬ﺫﺧﻴﺮﻩﺳﺎﺯﻫﺎ ﺑﺎ ﺍﺗﺼﺎﻝ ﻣﺴﺘﻘﻴﻢ ﺑﻪ ﺳﺮﻭﺭ ‪79................................................................................................‬‬

‫‪ 1-1-5‬ﺳﻴﺴﺘﻢﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺍﺷﺘﺮﺍﻛﻲ ‪79........................................................................................................‬‬

‫‪ 1-1-1-5‬ﺫﺧﻴﺮﻩﺳﺎﺯﻫﺎﻱ ‪80 ......................................... ................................................................ SAN‬‬

‫‪ 2-1-1-5‬ﺫﺧﻴﺮﻩ ﺳﺎﺯﻫﺎﻱ ‪81 ........................................................................................................ NAS‬‬

‫‪ 2-5‬ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﻳﻚ ‪82 ...................................................................................................... ISCSI SAN‬‬

‫‪ 1-2-5‬ﻧﺼﺐ ‪82...................................................................................................................................... Open Filer‬‬

‫‪ 2-2-5‬ﻣﺪﻳﺮﻳﺖ ‪85................................................................................................................................. Open Filer‬‬

‫ﻓﺼﻞ ﺷﺸﻢ‪ :‬ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﻭ ﻣﺪﻳﺮﻳﺖ ﺳﻴﺴﺘﻢ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ‪95 .....................................‬‬

‫‪ 1-6‬ﺍﻳﺠﺎﺩ ﺩﻳﺘﺎﺳﻨﺘﺮ ﻭ ﺍﺿﺎﻓﻪ ﻛﺮﺩﻥ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ ESXi‬ﺑﻪ ‪95 ................................................ vCenter‬‬

‫‪ 2-6‬ﺳﺎﺧﺖ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ‪97 ................................................................................................................‬‬

‫‪ 3-6‬ﺗﺨﺼﻴﺺ ﻣﻨﺎﺑﻊ ﺑﻪ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ‪98 .......................................................................................‬‬

‫‪ 4-6‬ﺳﺎﺧﺖ ﻛﻼﺳﺘﺮ ﻭ ﺍﺿﺎﻓﻪ ﻛﺮﺩﻥ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ ESXi‬ﺑﻪ ﺁﻥ ‪100........................ ................................‬‬

‫‪6‬‬
‫‪ 5-6‬ﻓﻌﺎﻝﺳﺎﺯﻱ ﻭﻳﮋﮔﻲ ‪ DRS‬ﺩﺭ ﻛﻼﺳﺘﺮ ‪102........................ ................................................................‬‬

‫‪103................................................................................................................................ Automation level 1-5-6‬‬

‫‪ 2-5-6‬ﮔﺮﻭﻩ ﺑﻨﺪﻱ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻭ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪105 ....................................................................... ESXi‬‬

‫‪ 3 5 6‬ﺍﻋﻤﺎﻝ ﺳﻴﺎﺳﺘﻬﺎﻱ ‪ DRS‬ﺩﺭ ﺭﺍﺑﻄﻪ ﺑﺎ ﺍﺟﺮﺍﻱ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺑﺮ ﺭﻭﻱ ﺳﺮﻭﺭﻫﺎﻱ ‪107 ............. ESXi‬‬

‫‪ 6-6‬ﻣﺪﻳﺮﻳﺖ ﻭ ﺗﻘﺴﻴﻢ ﺑﻨﺪﻱ ﻣﻨﺎﺑﻊ ﺑﺎ ‪108.............................................................. Resource Pools‬‬

‫‪ 7-6‬ﺗﻜﺜﻴﺮ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ‪109.......................................... ................................ ................................‬‬

‫‪7‬‬
‫ﻓﺼﻞ ﺍﻭﻝ‬

‫ﻣﻘﺪﻣﻪ‬

‫ﻧﻮﺷﺘﻪﺍﻱ ﻛﻪ ﺩﺭ ﭘﻴﺶﺭﻭ ﺩﺍﺭﻳﺪ ﻓﺼﻠﻬﺎﻳﻲ ﺍﺯ ﭘﺎﻳﺎﻥ ﻧﺎﻣﻪ ﺩﻭﺭﻩﻱ ﻛﺎﺭﺷﻨﺎﺳﻲ ﺍﻳﻨﺠﺎﻧﺐ ﺑﺎ ﻣﻮﺿﻮﻉ "ﻣﺠﺎﺯﻱﺳﺎﺯﻱ‬

‫ﻭ ﺳﻴﺴﺘﻢﻫﺎﻱ ﭘﺮﺩﺍﺯﺵ ﺍﺑﺮﻱ" ﺍﺳﺖ ﻛﻪ ﺑﺎ ﻛﻤﻲ ﺗﻐﻴﻴﺮ ﺑﺪﻳﻦﺷﻜﻞ ﺩﺭﺁﻣﺪﻩ ﻭ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺷﻤﺎ ﺧﻮﺍﻧﻨﺪﻩﻱ ﻋﺰﻳﺰ‬

‫ﻗﺮﺍﺭ ﮔﺮﻓﺘﻪ ﺍﺳﺖ‪.‬‬

‫ﻣﻮﺿﻮﻉ ﺍﺻﻠﻲ ﺍﻳﻦ ﻧﻮﺷﺘﻪ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺳﺮﻭﺭ ﺍﺳﺖ ﻛﻪ ‪ vSphere‬ﺑﻪ ﻋﻨﻮﺍﻥ ﻳﻚ ﻧﻤﻮﻧﻪ ﺍﺯ ﺗﻜﻨﻮﻟﻮژﻱﻫﺎﻱ‬

‫ﻣﻮﺟﻮﺩ ﻣﻮﺭﺩ ﺑﺮﺭﺳﻲ ﻗﺮﺍﺭ ﮔﺮﻓﺘﻪ ﺍﺳﺖ‪.‬‬

‫ﺳﻴﺴﺘﻤﻬﺎﻱ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺳﺮﻭﺭ ﺑﻪ ﻃﻮﺭ ﻛﻠﻲ ﺍﺯ ﺩﻭ ﻗﺴﻤﺖ ﺍﺻﻠﻲ ﺗﺸﻜﻴﻞ ﻣﻲﺷﻮﻧﺪ‪ :‬ﻳﻜﻲ ﺑﺨﺶ ﻓﻮﻕﻧﺎﻇﺮ‬

‫ﻛﻪ ﺑﺮ ﺭﻭﻱ ﺳﺨﺖﺍﻓﺰﺍﺭ ﻗﺮﺍﺭ ﮔﺮﻓﺘﻪ)ﺍﻟﺒﺘﻪ ﺩﺭ ﻓﻮﻕﻧﺎﻇﺮ ﻧﻮﻉ‪ 2‬ﺍﻳﻦ ﺑﺨﺶ ﺑﺮ ﺭﻭﻱ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻣﺎﺷﻴﻦ ﻣﻴﺰﺑﺎﻥ‬

‫ﻗﺮﺍﺭ ﻣﻲﮔﻴﺮﺩ( ﻭ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺑﺮ ﺭﻭﻱ ﺁﻥ ﺍﺟﺮﺍ ﻣﻲﺷﻮﻧﺪ ﻭ ﻣﺴﺌﻮﻟﻴﺖ ﺍﺟﺮﺍ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻭ‬

‫‪8‬‬
‫ﺗﻘﺴﻴﻢ ﻣﻨﺎﺑﻊ ﺑﻴﻦ ﺁﻧﻬﺎ ﺭﺍ ﺑﺮﻋﻬﺪﻩ ﺩﺍﺭﺩ؛ ﻭ ﺩﻳﮕﺮﻱ ﺑﺨﺶ ﻣﺪﻳﺮﻳﺖ ﻛﻪ ﺑﻪ ﻛﻤﻚ ﺁﻥ ﻣﻲﺗﻮﺍﻥ ﺳﺮﻭﺭﻫﺎﻱ ﻓﻴﺰﻳﻜﻲ‬

‫ﻭ ﻣﺎﺷﻴﻦﻫﺎﻱ ﺍﺟﺮﺍ ﺷﺪﻩ ﺑﺮ ﺭﻭﻱ ﺁﻥﻫﺎ ﺭﺍ ﻣﺪﻳﺮﻳﺖ ﻛﺮﺩ‪.‬‬

‫ﺩﺭ ﺣﺎﻝ ﺣﺎﺿﺮ ﺷﺮﻛﺘﻬﺎﻱ ﺑﺴﻴﺎﺭﻱ ﺑﻪ ﺣﻴﻄﻪ ﺳﻴﺴﺘﻤﻬﺎﻱ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺳﺮﻭﺭ ﻭﺍﺭﺩ ﺷﺪﻩﺍﻧﺪ‪ .‬ﺩﺭ ﺑﺨﺶ ﻓﻮﻕ‬

‫ﻧﺎﻇﺮ‪ ،‬ﻣﺎﻳﻜﺮﻭﺳﺎﻓﺖ ‪ Hyper-v‬ﺭﺍ ﻣﻌﺮﻓﻲ ﻣﻲﻛﻨﺪ؛ ‪ VMWare‬ﻛﻪ ﺍﺯ ﭘﻴﺸﺘﺎﺯﺍﻥ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺍﺳﺖ ‪ ESX‬ﻭ‬

‫‪ ESXi‬ﺭﺍ ﺍﺭﺍﺋﻪ ﻛﺮﺩﻩ ﺍﺳﺖ؛ ﺍﻭﺭﺍﻛﻞ ﻧﻴﺰ ‪ Oracle VM Server‬ﺭﺍ ﺑﻌﻨﻮﺍﻥ ﻓﻮﻕﻧﺎﻇﺮ ﻣﻌﺮﻓﻲ ﻣﻲﻛﻨﺪ؛ ﻭ ﺩﺭ‬

‫ﻧﻬﺎﻳﺖ ‪ Xen‬ﻛﻪ ﻳﻚ ﻓﻮﻕ ﻧﺎﻇﺮ ﻣﺘﻦ ﺑﺎﺯ ﺍﺳﺖ ﺗﻮﺳﻂ ﺳﻴﺘﺮﻳﻜﺲ ﺍﺭﺍﺋﻪ ﺷﺪﻩ ﺍﺳﺖ‪ .‬ﺍﻟﺒﺘﻪ ‪ Xen‬ﺑﻌﻨﻮﺍﻥ ﻳﻚ‬

‫ﻛﺎﻣﭙﻮﻧﻨﺖ ﻫﻤﺮﺍﻩ ﺑﺎ ﺍﻛﺜﺮ ﺗﻮﺯﻳﻊﻫﺎﻱ ﻟﻴﻨﻮﻛﺲ ﺍﺭﺍﺋﻪ ﻣﻲﺷﻮﺩ‪ .‬ﺿﻤﻨﺎ‪ ،‬ﺗﻮﺯﻳﻊ ‪ Red Hat‬ﻟﻴﻨﻮﻛﺲ ‪ KVM ،‬ﺭﺍ ﻧﻴﺰ‬

‫ﺑﻌﻨﻮﺍﻥ ﻳﻚ ﻓﻮﻕﻧﺎﻇﺮ ﺍﺭﺍﺋﻪ ﻛﺮﺩﻩ ﺍﺳﺖ‪ .‬ﺩﺭ ﺑﺨﺶ ﻣﺪﻳﺮﻳﺖ ﻧﻴﺰ ﻫﺮ ﻳﻚ ﺍﺯ ﺍﻳﻦ ﺷﺮﻛﺘﻬﺎ ﺍﺑﺰﺍﺭﻫﺎﻱ ﺑﺮﺍﻱ‬

‫ﻣﺪﻳﺮﻳﺖ ﻓﻮﻕ ﻧﺎﻇﺮﻫﺎﻱ ﺧﻮﺩ ﺍﺭﺍﺋﻪ ﻣﻲﺩﻫﻨﺪ‪ .‬ﺍﺯ ﺟﻤﻠﻪ ﺍﻭﺭﺍﻛﻞ ﻛﻪ ‪ Oracle VM Manager‬ﺭﺍ ﺍﺭﺍﺋﻪ ﻣﻴﻜﻨﺪ؛ ﻭ‬

‫ﻳﺎ ‪ vCenter Serve‬ﻛﻪ ﺍﺑﺰﺍﺭﻳﺴﺖ ﺑﺮﺍﻱ ﻣﺪﻳﺮﻳﺖ ﻣﺠﻤﻮﻋﻪ ‪ .vSphere‬ﻣﻀﺎﻑ ﺑﺮ ﺍﻳﻦ ﺷﺮﻛﺘﻬﺎﻱ ﺛﺎﻟﺜﻲ ﻧﻴﺰ‬

‫ﺑﺮﺍﻱ ﻣﺪﻳﺮﻳﺖ ﺍﻳﻦ ﭘﻠﺘﻔﺮﻡﻫﺎ ﺍﺑﺰﺍﺭﻫﺎﻳﻲ ﺍﺭﺍﺋﻪ ﺩﺍﺩﻩﺍﻧﺪ‪.‬‬

‫ﺍﻳﻦ ﻧﻮﺷﺘﻪ ﻣﺸﺘﻤﻞ ﺑﺮ ‪ 6‬ﻓﺼﻞ ﺑﻮﺩﻩ ﻛﻪ ﺑﻪ ﺩﺭ ﺍﺩﺍﻣﻪ ﺗﻮﺿﻴﺤﺎﺕ ﻣﺨﺘﺼﺮﻱ ﺭﺍﺟﻊ ﺑﺎ ﻫﺮ ﻳﻚ ﺍﺯ ﻓﺼﻮﻝ ﺍﺭﺍﺋﻪ‬

‫ﻣﻲﺷﻮﺩ‪:‬‬

‫ﻓﺼﻞ ﺍﻭﻝ‪ :‬ﻫﻤﻴﻦ ﺳﻄﻮﺭﻳﺴﺖ ﻛﻪ ﺩﺭ ﺣﺎﻝ ﺣﺎﺿﺮ ﺍﺯ ﻧﻈﺮ ﻣﻲﮔ ﺬﺭﺍﻧﻴﺪ؛ ﻭﺷﺎﻳﺪ ﮔﺰﺍﺭﺩﻥ ﻧﺎﻡ ﻓﺼﻞ ﺑﺮ ﺁﻥ‬

‫ﺍﻧﺪﻛﻲ ﮔﺮﺍﻥ ﺑﺎﺷﺪ‪.‬‬

‫ﻓﺼﻞ ﺩﻭﻡ‪ :‬ﺷﺮﺡ ﻛﺎﻣﻠﻴﺴﺖ ﺍﺯ ﺗﻜﻨﻮﻟﻮژﻱﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺩﺭ ﺭﺩﻩﻫﺎﻱ ﻣﺨﺘﻠﻒ ﻛﻪ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺳﺮﻭﺭ‬

‫ﺑﻪ ﻋﻨﻮﺍﻥ ﺯﻳﺮﺷﺎﺧﻪﺍﻱ ﺍﺯ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺩﺭ ﺍﻳﻦ ﻓﺼﻞ ﺑﻪ ﺗﻔﺼﻴﻞ ﺑﺮﺭﺳﻲ ﻣﻲﺷﻮﺩ‪ .‬ﺗﻮﺻﻴﻪ ﻣﻲﺷﻮﺩ ﺑﺠﻬﺖ ﺭﻓﻊ‬

‫ﺍﺑﻬﺎﻡ ﻭ ﺗﺴﻠﻂ ﺑﻴﺸﺘﺮ ﺑﺮ ﻣﻔﺎﻫﻴﻢ‪ ،‬ﺍﻳﻦ ﻓﺼﻞ ﺭﺍ ﻣﻄﺎﻟﻌﻪ ﻛﻨﻴﺪ‪.‬‬

‫‪9‬‬
‫ﻓﺼﻞ ﺳﻮﻡ‪ :‬ﺩﺭ ﺍﻳﻦ ﻓﺼﻞ ﻣﺠﻤﻮﻋﻪ ‪ vSphere‬ﺑﻌﻨﻮﺍﻥ ﻳﻚ ﺗﻜﻨﻮﻟﻮژﻱ ﻗﺪﺭﺗﻤﻨﺪ ﺩﺭ ﺯﻣﻴﻨﻪ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ‬

‫ﺳﺮﻭﺭ ﻣﻌﺮﻓﻲ ﺷﺪﻩ ﻭ ﺗﻤﺎﻣﻲ ﻣﻮﻟﻔﻪﻫﺎ ﻭ ﺍﺑﺰﺍﺭﻫﺎﻱ ﻣﻮﺟﻮﺩ ﺩﺭ ﺁﻥ ﺑﻄﻮﺭ ﻣﺸﺮﻭﺡ ﻣﻮﺭﺩ ﺑﺮﺭﺳﻲ ﻗﺮﺍﺭ ﻣﻲﮔﻴﺮﺩ‪.‬‬

‫ﻓﺼﻞ ﭼﻬﺎﺭﻡ‪ :‬ﺩﺭ ﺍﻳﻦ ﻓﺼﻞ ﻓﺮﺍﻳﻨﺪ ﻧﺼﺐ ﺍﺟﺰﺍ ﻣﺨﺘﻠﻒ ‪ vSphere‬ﻭ ﻧﻴﺎﺯﻣﻨﺪﻳﻬﺎﻱ ﺳﺨﺖﺍﻓﺰﺍﺭﻱ ﻭ‬

‫ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﺑﺮﺍﻱ ﻧﺼﺐ ﻫﺮ ﻳﻚ ﺍﺯ ﺍﻳﻦ ﺍﺟﺰﺍ ﺑﻄﻮﺭ ﻛﺎﻣﻞ ﺑﺮﺭﺳﻲ ﻣﻲﺷﻮﺩ‪.‬‬

‫ﻓﺼﻞ ﭘﻨﺠﻢ‪ :‬ﺍﺯ ﺁﻧﺠﺎﻳﻲ ﻛﻪ ﺳﻴﺴﺘﻢﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺍﻫﻤﻴﺖ ﺑﺎﻻﻳﻲ ﺩﺭ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺳﺮﻭﺭ ﺩﺍﺭﻧﺪ؛ ﻭﺍﻳﻨﻜﻪ‬

‫ﺑﺴﻴﺎﺭﻱ ﺍﺯ ﻗﺎﺑﻠﻴﺖﻫﺎﻱ ﻣﺠﻤﻮﻋﻪ ‪- vSphere‬ﻛﻪ ﺷﺮﺡ ﺁﻧﻬﺎ ﺩﺭ ﺍﺩﺍﻣﻪ ﺧﻮﺍﻫﺪ ﺁﻣﺪ‪ -‬ﻓﻘﻂ ﻭ ﻓﻘﻂ ﺩﺭ ﺳﺎﻳﻪ‬

‫ﺫﺧﻴﺮﻩ ﺳﺎﺯﻫﺎﻱ ‪ share‬ﺷﺪﻩ ﻗﺎﺑﻞ ﺍﺳﺘﻔﺎﺩﻩ ﺧﻮﺍﻫﻨﺪ ﺑﻮﺩ‪ .‬ﺑﻨﺎﺑﺮﺍﻳﻦ ﺩﺭ ﺍﻳﻦ ﻓﺼﻞ ﺷﺮﺡ ﻣﺨﺘﺼﺮﻱ ﺍﺯ ﺳﻴﺴﺘﻢﻫﺎﻱ‬

‫ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺑﻴﺎﻥ ﻣﻴﺸﻮﺩ؛ ﻭ ﺩﺭ ﻫﻤﻴﻦ ﻓﺼﻞ ﺗﻮﺳﻂ ‪ Openfiler‬ﻳﻚ ﺳﻴﺴﺘﻢ ‪ iSCSI‬ﺑﺮﺍﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺩﺭ‬

‫‪ vSphere‬ﺭﺍﻩﺍﻧﺪﺍﺯﻱ ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩ‪.‬‬

‫ﻓﺼﻞ ﺷﺸﻢ‪ :‬ﺩﺭ ﺍﻳﻦ ﻓﺼﻞ ﻧﺤﻮﻩ ﻣﺪﻳﺮﻳﺖ ﺩﻳﺘﺎ ﺳﻨﺘﺮ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻩ ﺷﺪﻩ ﺭﺍ ﺑﻪ ﻛﻤﻚ ‪ ، vCenter Server‬ﺭﺍ‬

‫ﺑﺮﺭﺳﻲ ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩ‪.‬‬

‫‪10‬‬
‫ﻓﺼﻞ ﺩﻭﻡ‬

‫ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ‬

‫ﺩﺭ ﻓﺼﻞ ﻗﺒﻞ ﺍﺷﺎﺭﻩ ﻣﺨﺘﺼﺮﻱ ﺑﻪ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺩﺍﺷﺘﻴﻢ ﻭ ﺗﺎ ﺣﺪ ﻛﻤﻲ ﺑﺎ ﺁﻥ ﺁﺷﻨﺎ ﺷﺪﻳﻢ‪ .‬ﺩﺭﺍﻳﻦ ﻓﺼﻞ ﺑﺎ‬

‫ﺍﺭﺍﺋﻪ ﻳﻚ ﺗﻌﺮﻳﻒ ﻛﻠﻲ ﻭ ﻫﻤﭽﻨﻴﻦ ﻳﻚ ﻣﺪﻝ ﻣﺮﺟﻊ‪ ،‬ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺭﺍ ﺑﻪ ﻃﻮﺭ ﻣﻔﺼﻞ ﺑﺮﺭﺳﻲ ﻣﻲﻛﻨﻴﻢ‪.‬‬

‫ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺭﻭﺷﻲ ﺑﺮﺍﻱ ﺩﻭﺭ ﻧﮕﻪ ﺩﺍﺷﺘﻦ ﻛﺎﺭﺑﺮﺩﻫﺎ‪ 1‬ﻭ ﻣﻮﻟﻔﻪﻫﺎﻱ‪ 2‬ﺯﻳﺮﻳﻦ ﺁﻧﻬﺎ ﺍﺯ ﺳﺨﺖﺍﻓﺰﺍﺭﻱ ﻛﻪ ﺁﻧﻬﺎ ﺭﺍ‬

‫ﺍﺟﺮﺍ ﻭ ﭘﺸﺘﻴﺒﺎﻧﻲ ﻣﻲﻛﻨﺪ ﻭ ﻫﻤﭽﻨﻴﻦ ﺗﻜﻨﻮﻟﻮژﻱ ﺍﺳﺖ ﻛﻪ ﻳﻚ ﺩﻳﺪ ﻣﻨﻄﻘﻲ ﻭ ﻣﺠﺎﺯﻱ ﺍﺯ ﻣﻨﺎﺑﻊ ﻣﻮﺟﻮﺩ ﺍﺭﺍﺋﻪ‬

‫ﻣﻲﻛﻨﺪ‪ .‬ﺍﻳﻦ ﺩﻳﺪ ﻣﺠﺎﺯﻱ ﻣﻤﻜﻦ ﺍﺳﺖ ﺗﻔﺎﻭﺕ ﺑﺴﻴﺎﺭ ﺯﻳﺎﺩﻱ ﺑﺎ ﺩﻳﺪ ﻓﻴﺰﻳﻜﻲ ﻭﺍﻗﻌﻲ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬

‫ﺑﺮﺍﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﻣﻲ ﺗﻮﺍﻥ ﺍﻫﺪﺍﻑ ﺯﻳﺮ ﺭﺍ ﺑﺮﺷﻤﺮﺩ‪:‬‬

‫‪3‬‬
‫ﺳﻄﺢ ﺑﺎﻻﺗﺮﻱ ﺍﺯ ﻛﺎﺭﺍﻳﻲ‬ ‫‪-‬‬
‫‪4‬‬
‫ﻗﺎﺑﻠﻴﺖ ﺗﻮﺳﻌﻪ ﭘﺬﻳﺮﻱ‬ ‫‪-‬‬
‫‪1‬‬
‫ﺗﻮﺍﻧﺎﻳﻲ ﺩﺳﺘﺮﺳﻲ ﻣﺴﺘﻤﺮ‬ ‫‪-‬‬

‫‪applications 1‬‬
‫‪components 2‬‬
‫‪performance 3‬‬
‫‪scalability 4‬‬

‫‪11‬‬
 ‫ﻗﺎﺑﻠﻴﺖ ﺍﻃﻤﻴﻨﺎﻥ ﺑﺎﻻﺗﺮ‬ ‫‪-‬‬

‫ﻣﺪﻳﺮﻳﺖ ﺁﺳﺎﻥ ﺗﺮ‬ ‫‪-‬‬

‫ﺍﻣﻨﻴﺖ ﺑﻴﺸﺘﺮ‬ ‫‪-‬‬

‫ﻗﺒﻞ ﺍﺯ ﺍﺩﺍﻣﻪ ﺑﺤﺚ ﺫﻛﺮ ﻳﻚ ﻧﻜﺘﻪ ﺿﺮﻭﺭﻱ ﺑﻨﻈﺮ ﻣﻲﺭﺳﺪ ﻭ ﺁﻥ ﺍﻳﻨﻜﻪ ﺩﺭ ﺍﻳﻦ ﻧﻮﺷﺘﻪ ﻭ ﺑﺴﻴﺎﺭﻱ ﺍﺯ ﻛﺘﺐ ﺑﺎ‬

‫ﻣﻮﺿﻮﻉ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺍﺻﻄﻼﺣﺎﺕ ﺯﻳﺎﺩﻱ ﺩﻳﺪﻩ ﻣﻲﺷﻮﺩ ﻛﻪ ﻫﺮﻛﺪﺍﻡ ﺗﻌﺮﻳﻒﻫﺎﻱ ﻣﺘﻔﺎﻭﺗﻲ ﺍﺯ ﺍﻳﻦ ﺍﺻﻄﻼﺣﺎﺕ‬

‫ﺍﺭﺍﺋﻪ ﻣﻲﺩﻫﻨﺪ؛ ﻭﺑﻪ ﻧﻈﺮ ﻣﻲﺭﺳﺪ ﺩﻟﻴﻞ ﺍﻳﻦ ﺍﻣﺮ ﺗﻌﺎﺭﻳﻒ ﻣﺘﻔﺎﻭﺗﻲ ﻫﺴﺘﻨﺪ ﻛﻪ ﺷﺮﻛﺖﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ‬

‫ﻣﺤﺼﻮﻻﺕ ﺧﻮﺩ ﺍﺯ ﺗﻜﻨﻮﻟﻮژﻱﻫﺎ ﺍﺭﺍﺋﻪ ﻣﻲﺩﻫﻨﺪ‪ .‬ﺑﻴﺸﺘﺮ ﻣﻄﺎﻟﺐ ﻭ ﺗﻌﺮﻳﻒﻫﺎ ﻭ ﺍﺻﻄﻼﺣﺎﺕ ﻣﻮﺟﻮﺩ ﺩﺭ ﺍﻳﻦ ﻧﻮﺷﺘﻪ‬

‫ﺑﺮ ﮔﺮﻓﺘﻪ ﺍﺯ ﻛﺘﺎﺏ ‪ virtualization managers guide‬ﻧﻮﺷﺘﻪ ‪ Dan Kusnetzky‬ﺍﺯ ﺍﻧﺘﺸﺎﺭﺍﺕ ‪OREILLY‬‬

‫ﺍﺳﺖ ﻛﻪ ﺑﻨﻈﺮ ﻣﻲﺗﻮﺍﻧﺪ ﻣﺮﺟﻊ ﻣﻨﺎﺳﺒﻲ ﺑﺎﺷﺪ‪.‬‬

‫ﺍﻳﻦ ﺭﺍ ﮔﻔﺘﻢ ﺗﺎ ﺍﮔﺮ ﺩﺭ ﻛﺘﺐ ﻣﺨﺘﻠﻒ ﺑﺎ ﺗﻌﺎﺭﻳﻔﻲ ﻣﺘﻔﺎﻭﺕ ﻭ ﺣﺘﻲ ﺗﻘﺴﻴﻢ ﺑﻨﺪﻱﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺍﺯ‬

‫ﺗﻜﻨﻮﻟﻮژﻱﻫﺎﻱ ﻣﺘﻔﺎﻭﺕ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﻣﻮﺍﺟﻪ ﺷﺪﻳﺪ‪ ،‬ﺩﭼﺎﺭ ﺳﺮﺩﺭﮔﻤﻲ ﻭ ﺍﺑﻬﺎﻡ ﻧﺸﻮﻳﺪ‪.‬‬

‫‪ 1-2‬ﻣﺪﻝ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ‬

‫ﺍﻏﻠﺐ ﺍﻭﻗﺎﺕ ﺑﺎ ﺍﺭﺍﺋﻪ ﻳﻚ ﻣﺪﻝ ﻣﺮﺟﻊ‪ ،‬ﻣﻲﺗﻮﺍﻥ ﻓﻬﻢ ﻳﻚ ﻣﺴﺌﻠﻪ ﻭ ﻳﺎ ﻳﻚ ﺗﻜﻨﻮﻟﻮژﻱ ﺭﺍ ﺁﺳﺎﻥ ﻛﺮﺩ‪ .‬ﺷﻜﻞ ‪-2‬‬

‫‪ 1‬ﻳﻚ ﻣﺪﻝ ﻣﻌﺮﻭﻑ ﺍﺯ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺭﺍ ﺍﺭﺍﺋﻪ ﻣﻲﻛﻨﺪ‪ .‬ﺍﻟﺒﺘﻪ ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﻛﻪ ﻣﻌﻤﻮﻻ ﻣﺪﻝ ﻫﺎﻱ ﻣﺮﺟﻊ ‪،‬‬

‫ﺑﺎﮔﺬﺷﺖ ﺯﻣﺎﻥ ﻭ ﺗﻐﻴﻴﺮ ﺗﻜﻨﻮﻟﻮژﻱﻫﺎ ﺑﺎﻳﺴﺘﻲ ﺭﻭﺯﺁﻣﺪ ﺷﻮﻧﺪ ﺗﺎ ﺍﻋﺘﺒﺎﺭ ﺧﻮﺩ ﺭﺍ ﺣﻔﻆ ﻛﻨﺪ ﻭ ﻫﻤﭽﻨﺎﻥ ﺑﻌﻨﻮﺍﻥ ﻳﻚ‬

‫ﻣﺪﻝ ﻣﺮﺟﻊ ﺑﺎﻗﻲ ﺑﻤﺎﻧﻨﺪ‪.‬‬

‫‪High Availability 1‬‬

‫‪12‬‬
 ‫ﺷﻜﻞ ‪ . 1 2‬ﻻﻳﻪﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ‬

‫‪ 2-2‬ﻻﻳﻪﻫﺎﻱ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ‬

‫ﻫﺮ ﻳﻚ ﺍﺯ ﻻﻳﻪﻫﺎ ﺑﺨﺸﻲ ﺍﺯ ﻳﻚ ﺳﻴﺴﺘﻢ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ ﺭﺍ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﻣﻲﻛﻨﺪ ﻛﻪ ﺩﺭ ﺍﺩﺍﻣﻪ ﻫﺮ ﻳﻚ ﺍﺯﺁﻧﻬﺎ‬

‫ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬

‫‪13‬‬
 ‫‪1‬‬
‫‪ 1-2-2‬ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺩﺳﺖﻳﺎﺑﻲ‬

‫ﺗﻜﻨﻮﻟﻮژﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻭ ﺳﺨﺖﺍﻓﺰﺍﺭﻱ ﻛﻪ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﺍﻳﺠﺎﺩ ﻣﻲ ﻛﻨﺪ ﻛﻪ ﺍﺑﺰﺍﺭ‪ 2‬ﺑﻪ ﻫﺮ ﻛﺎﺭﺑﺮﺩﻱ ﺩﺳﺖ ﭘﻴﺪﺍ‬

‫ﻛﻨﻨﺪ‪ ،‬ﺑﺪﻭﻥ ﺍﻳﻨﻜﻪ ﻫﺮﻳﻚ )ﺍﺑﺰﺍﺭ ﻭ ﻛﺎﺭﺑﺮﺩ( ﺍﻃﻼﻋﺎﺕ ﺯﻳﺎﺩﻱ ﺩﺭ ﻣﻮﺭﺩ ﺩﻳﮕﺮﻱ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪ .‬ﻛﺎﺭﺑﺮﺩ ﺍﺑﺰﺍﺭﻱ ﺭﺍ‬

‫ﻣﻲﺑﻴﻨﺪ ﻛﻪ ﺑﺎ ﺁﻥ ﻛﺎﺭ ﻣﻲﻛﻨﺪ ﻭ ﺍﺑﺰﺍﺭ ﻧﻴﺰ ﻛﺎﺭﺑﺮﺩ ﺭﺍ‪ .‬ﺩﺭ ﺑﻌﻀﻲ ﻣﻮﺍﺭﺩ ﺟﻬﺖ ﺍﻓﺰﺍﻳﺶ ﻛﺎﺭﺍﻳﻲ‪ ،‬ﺳﺨﺖﺍﻓﺰﺍﺭﻫﺎﻱ‬

‫ﺧﺎﺹ ﺩﺭ ﺩﻭ ﻃﺮﻑ ﺷﺒﻜﻪ ﻧﺼﺐ ﻣﻲﺷﻮﻧﺪ‪.‬‬

‫ﺷﻜﻞ ‪ 2-2‬ﺍﻳﻦ ﻣﺪﻝ ﺍﺯ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺭﺍ ﻧﺸﺎﻥ ﻣﻲﺩﻫﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 2 2‬ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺩﺳﺘﻴﺎﺑﻲ‬

‫ﺩﺭ ﺍﻳﻦ ﺗﻜﻨﻮﻟﻮژﻱ ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺳﻄﻮﺡ ﺑﺎﻻﺗﺮ ﺍﺷﺎﺭﻩ ﺷﺪ‪ ،‬ﺩﺍﺩﻩﻫﺎ ﻭ ﭘﺮﺩﺍﺯﺵ ﺩﺭ ﻃﺮﻑ ﺳﺮﻭﺭ ﺍﺳﺖ‪ ،‬ﺍﻣﺎ‬

‫ﻭﺭﻭﺩﻱ ﻭ ﺧﺮﻭﺟﻲ ﻛﺎﺭﺑﺮﺩﻫﺎ ﻭﺑﺮﻧﺎﻣﻪﻫﺎ ﺗﻮﺳﻂ ﻛﻼﻳﻨﺖ ﻭ ﺩﺭ ﻃﺮﻑ ﺩﻳﮕﺮ ﺍﺗﻔﺎﻕ ﻣﻲﺍﻓﺘﺪ ﻭ ﻳﺎ ﺑﻪ ﺑﻴﺎﻥ ﺩﻳﮕﺮ‬

‫ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺩﺳﺘﺮﺳﻲ ﺍﻳﻦ ﺍﻣﻜﺎﻧﺮﺍ ﻓﺮﺍﻫﻢ ﻣﻲ ﺁﻭﺭﺩ ﻛﻪ ﻛﻼﻳﻨﺘﻲ ﻛﻪ ﺩﺭ ﻃﺮﻑ ﺩﻳﮕﺮ ﺷﺒﻜﻪ ﻗﺮﺍﺭ ﺩﺍﺭﺩ‪ ،‬ﺭﺍﺑﻂ‬

‫ﻛﺎﺭﺑﺮﻱ ﻛﺎﺭﺑﺮﺩﻱ ﻛﻪ ﺩﺭ ﺳﺮﻭﺭ ﺩﺭ ﺣﺎﻝ ﺍﺟﺮﺍ ﺍﺳﺖ ﻣﺸﺎﻫﺪﻩ ﻧﻤﺎﻳﺪ؛ ﻭ ﻛﺎﺭﺑﺮﺩ ﻭﺭﻭﺩﻱﻫﺎﻱ ﻣﺎﻭﺱ ﻭ ﺻﻔﺤﻪﻛﻠﻴﺪ‬

‫‪Access Virtualization 1‬‬

‫‪Device 2‬‬

‫‪14‬‬
‫ﻭ ﺩﻳﮕﺮ ﻭﺭﻭﺩﻱﻫﺎ ﺭﺍ ﺍﺯ ﻛﺎﺑﺮ ﺳﻤﺖ ﻛﻼﻳﻨﺖ ﺩﺭﻳﺎﻓﺖ ﻛﻨﺪ‪ .‬ﻧﻜﺘﻪ ﻣﻬﻢ ﺩﻳﮕﺮﻱ ﻛﻪ ﺩﺭ ﺍﻳﻦ ﺗﻜﻨﻮﻟﻮژﻱ ﻭﺟﻮﺩ ﺩﺍﺭﺩ‬

‫ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﻣﻤﻜﻦ ﺍﺳﺖ ﻛﺎﺭﺑﺮﺩ ﺩﺭ ﺣﺎﻝ ﺍﺟﺮﺍ ﺩﺭ ﺳﺮﻭﺭ ﻛﻪ ﺍﺯ ﻃﺮﻳﻖ ﻛﻼﻧﻴﺖ ﻗﺎﺑﻞ ﺩﺳﺘﺮﺳﻲ ﺍﺳﺖ‪ ،‬ﻳﻚ‬

‫ﺑﺮﻧﺎﻣﻪ ﻟﻴﻨﻮﻛﺴﻲ ﺑﺎﺷﺪ ﻭﻟﻲ ﻛﻼﻳﻨﺖ ﻣﺜﻼ ﺩﺍﺭﺍﻱ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻭﻳﻨﺪﻭﺯ ﺑﺎﺷﺪ‪ .‬ﻳﻌﻨﻲ ﻫﻴﭻ ﻧﻴﺎﺯﻱ ﻧﻴﺴﺖ‬

‫ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻭ ﺣﺘﻲ ﭘﻠﺘﻔﺮﻡ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﺳﺮﻭﺭ ﻭ ﻛﻼﻳﻨﺖ ﻫﻴﭻ ﺷﺒﺎﻫﺘﻲ ﺑﻪ ﻳﻜﺪﻳﮕﺮ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ‪ .‬ﺷﻜﻞ ‪-2‬‬

‫‪ 3‬ﺍﻳﻦ ﻣﻔﺎﻫﻴﻢ ﺭﺍ ﺑﻪ ﺗﺼﻮﻳﺮﻛﺸﻴﺪﻩ ﺍﺳﺖ‪ .‬ﺍﺣﺘﻤﺎﻻ ﺷﻤﺎ ﻫﻢ ﻣﺘﻮﺟﻪ ﺷﺪﻩﺍﻳﺪ ﻛﻪ ﺍﻳﻦ ﺗﻜﻨﻮﻟﻮژﻱ‪ ،‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ‬

‫ﻓﺼﻞ ﺍﻭﻝ ﻫﻢ ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩﺷﺪ‪ ،‬ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺑﻪ ﻋﻨﻮﺍﻥ ﺳﺮﻭﻳﺲ ﻳﺎ ﻫﻤﺎﻥ ‪ saas‬ﺩﺭ ﺳﻴﺴﺘﻢﻫﺎﻱ ﭘﺮﺩﺍﺯﺵ ﺍﺑﺮﻱ‬

‫ﺍﺳﺖ‪.‬‬

‫ﺷﻜﻞ ‪ . 3 2‬ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺩﺳﺖﻳﺎﺑﻲ‪ .‬ﺍﺟﺮﺍ ﺳﻤﺖ ﺳﺮﻭﺭ ‪ ،‬ﺩﺳﺘﺮﺳﻲ ﺳﻤﺖ ﻛﻼﻳﻨﺖ‬

‫ﺍﻟﺒﺘﻪ ﭼﻮﻥ ﺍﺳﻢ ﭘﺮﺩﺍﺯﺵ ﺍﺑﺮﻱ ﺁﻣﺪ ﻧﺒﺎﻳﺪ ﻓﻜﺮ ﻛﻨﻴﻢ ﻛﻪ ﺍﻳﻦ ﻳﻚ ﺗﻜﻨﻮﻟﻮژﻱ ﺟﺪﻳﺪ ﺍﺳﺖ ﭼﺮﺍ ﻛﻪ ﺳﺎﺑﻘﻪ ﺍﻳﻦ‬

‫ﺗﻜﻨﻮﻟﻮژﻱ ﺑﻪ ﺳﺎﻝ ‪ 1980‬ﻭ ﺣﺘﻲ ﻗﺒﻞ ﺍﺯ ﺁﻥ ﺑﺎﺯﻣﻲﮔﺮﺩﺩ؛ ﺯﻣﺎﻧﻲ ﻛﻪ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺩﺳﺘﺮﺳﻲ ﺗﻮﺳﻂ‬

‫ﺳﺎﺯﻧﺪﮔﺎﻥ ‪ main frame‬ﻳﻌﻨﻲ ‪) Burroughs ، IBM‬ﻛﻪ ﺩﺭ ﺣﺎﻝ ﺣﺎﺿﺮ ﺟﺰﺋﻲ ﺍﺯ ‪ Unisys‬ﺍﺳﺖ( ‪ RCA‬ﻭ‬

‫‪15‬‬
‫ﺩﻳﮕﺮﺍﻥ ﺍﺭﺍﺋﻪ ﻣﻲﺷﺪ‪ .‬ﺑﺪﻳﻦﺻﻮﺭﺕ ﻛﻪ ﻣﺠﻤﻮﻋﻪﺍﻱ ﺍﺯ ﭘﺎﻳﺎﻧﻪﻫﺎ‪ 1‬ﺑﻪ ﻛﺎﺭﺑﺮﺩﻫﺎﻱ ﺩﺭ ﺣﺎﻝ ﺍﺟﺮﺍ ﺑﺮ ﺭﻭﻱ ﺳﺮﻭﺭﻫﺎﻱ‬

‫ﺩﻳﺘﺎﺳﻨﺘﺮ‪ 2‬ﺩﺳﺘﺮﺳﻲ ﺩﺍﺷﺘﻨﺪ‪.‬‬

‫ﺩﺭ ﺣﺎﻝ ﺣﺎﺿﺮ ﺷﺮﻛﺖﻫﺎﻱ ﺯﻳﺎﺩ ﺩﺭ ﺍﻳﻦ ﺯﻣﻴﻨﻪ ﻣﺸﻐﻮﻝ ﺑﻪ ﻓﻌﺎﻟﻴﺖ ﻫﺴﺘﻨﺪ ﻛﻪ ﺍﻟﺒﺘﻪ ﻣﺎ ﺩﺭ ﺍﺩﺍﻣﻪ ﻣﻬﻤﺘﺮﻳﻦ‬

‫ﺁﻥ ﺭﺍ ﻧﺎﻡ ﻣﻲﺑﺮﻳﻢ‪.‬‬

‫ﺳﻴﺘﺮﻳﻜﺲ )‪ : (Citrix‬ﺳﻴﺘﺮﻳﻜﺲ ﻳﻜﻲ ﺍﺯ ﭘﻴﺸﺮﻭﺗﺮﻳﻦ ﺷﺮﻛﺖﻫﺎ ﺩﺭ ﺍﻳﻦ ﺯﻣﻴﻨﻪ ﺍﺳﺖ‪ .‬ﻣﺤﺼﻮﻻﺕ ﺍﻭﻟﻴﻪ ﺍﻳﻦ‬

‫ﺷﺮﻛﺖ ﻛﻪ ‪ main frame‬ﻧﺎﻣﻴﺪﻩ ﻣﻲﺷﺪ ﺍﺟﺎﺭﻩ ﻣﻲﺩﺍﺩ ﺗﻌﺪﺍﺩﻱ ﻛﻼﻳﻨﺖ ﺑﺎ ﺳﻴﺴﺘﻢﻫﺎﻱ ﻣﺘﻔﺎﻭﺕ ﺑﻪ ﻛﺎﺭﺑﺮﺩﻫﺎﻱ‬

‫ﻭﻳﻨﺪﻭﺯﻱ ﻭ ﺳﻮﻻﺭﻳﺲ )ﻳﻮﻧﻴﻜﺲ( ﻛﻪ ﺩﺭ ﺣﺎﻝ ﺍﺟﺮﺍ ﺑﺮ ﺭﻭﻱ ﺳﺮﻭﺭ ﺑﻮﺩﻧﺪ ﺩﺳﺘﺮﺳﻲ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ‪ .‬ﺑﻌﺪﻫﺎ ﺍﻳﻦ‬

‫ﺳﻴﺴﺘﻢ ﺑﻪ‪ meta frame‬ﺗﻐﻴﻴﺮ ﻧﺎﻡ ﺩﺍﺩ‪ .‬ﺍﻳﻦ ﺳﻴﺴﺘﻢ ﺍﻣﺮﻭﺯﻩ ﺑﺎ ﻧﺎﻡ ‪ XenApp‬ﺷﻨﺎﺧﺘﻪ ﻣﻲﺷﻮﺩ‪.‬‬

‫ﻣﺎﻳﻜﺮﻭﺳﺎﻓﺖ‪ :‬ﺍﻳﻦ ﺷﺮﻛﺖ ﻧﻴﺰ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺩﺳﺖ ﻳﺎﺑﻲ ﺭﺍ ﺑﺎ ﺍﻓﺰﻭﺩﻥ ﺍﺑﺰﺍﺭﻫﺎﻳﻲ ﺩﺭ ﻭﻳﻨﺪﻭﺯ ‪ 95‬ﻭ ﺳﺮﻭﺭ‬

‫‪ NT‬ﺷﺮﻭﻉ ﻛﺮﺩ‪ .‬ﺗﻜﻨﻮﻟﻮژﻱ ﻣﺎﻳﻜﺮﻭﺳﺎﻓﺖ‪ Microsoft Terminal Service،‬ﻧﺎﻣﻴﺪﻩ ﻣﻲﺷﻮﺩ‪.‬‬

‫‪ ، IBM ، HP‬ﺍﻭﺭﺍﻛﻞ )‪ Sun‬ﺳﺎﺑﻖ( ﻭ ﺩﻳﮕﺮ ﭘﺸﺘﻴﺒﺎﻧﺎﻥ ﻳﻮﻧﻴﻜﺲ‪ x–windows :‬ﺩﺭ ﺩﺍﻧﺸﮕﺎﻩ ‪ MIT‬ﺑﻌﻨﻮﺍﻥ‬

‫ﺑﺨﺸﻲ ﺍﺯ ﻳﻮﻧﻴﻜﺲ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﺷﺪ‪ x-windows .‬ﻛﻪ ﻣﺤﺼﻮﻝ ﻫﻤﻜﺎﺭﻱ ﭼﻨﺪ ﺷﺮﻛﺖ ﺑﺰﺭگ ﺣﺎﻣﻲ ﻳﻮﻧﻴﻜﺲ‬

‫ﺍﺯﺟﻤﻠﻪ ‪ ) DEC ، HP ، IBM‬ﻛﻪ ﺩﺭ ﺣﺎﻝ ﺣﺎﺿﺮ ﺟﺰﺋﻲ ﺍﺯ ‪ HP‬ﺍﺳﺖ( ﻭ ﭼﻨﺪ ﺷﺮﻛﺖ ﺑﺰﺭگ ﺩﻳﮕﺮ ﺑﻮﺩ‪ ،‬ﻳﻜﻲ ﺍﺯ‬

‫ﻣﻬﻤﺘﺮﻳﻦ ﺍﺑﺰﺍﺭﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺩﺳﺘﺮﺳﻲ ﺍﺯ ﺳﺎﻝ ‪ 1980‬ﺑﻪ ﺑﻌﺪ ﻣﻲ ﺑﺎﺷﺪ‪.‬‬

‫ﺭﺩﻫﺖ ‪ ،‬ﺳﻮﺯﻩ ﻭ ﺩﻳﮕﺮ ﺗﻮﺯﻳﻊ ﻫﺎﻱ ﻟﻴﻨﻮﻛﺲ‪ :‬ﺍﺯ ﺯﻣﺎﻧﻲ ﻛﻪ ‪ x- windows‬ﺑﻪ ﻃﻮﺭ ﺗﺠﺎﺭﻱ ﻋﺮﺿﻪ ﺷﺪ ﺗﻮﺯﻳﻊ‬

‫ﻫﺎﻱ ﻟﻴﻨﻮﻛﺲ ﻫﻢ ﺷﺮﻭﻉ ﺑﻪ ﺳﺎﺯﮔﺎﺭﻱ ﻭ ﺍﺭﺍﺋﻪ ﺁﻥ ﺑﻪ ﻋﻨﻮﺍﻥ ﻣﻮﻟﻔﻪﻫﺎﻱ‪ 3‬ﺧﻮﺩ ﻛﺮﺩﻧﺪ؛ ﺑﻪ ﻃﻮﺭﻱ ﻛﻪ ﺗﻤﺎﻡ‬

‫ﺳﺮﻭﻳﺲ ﻫﺎﻳﻲ ﻛﻪ ‪ x-windows‬ﺩﺭ ﻳﻮﻧﻴﻜﺲ ﭘﺸﺘﻴﺒﺎﻧﻲ ﻣﻲ ﺷﻮﺩ‪ ،‬ﺩﺭ ﻣﺤﻴﻂ ﻫﺎﻱ ﻟﻴﻨﻮﻛﺲ ﻫﻢ ﺍﺭﺍﺋﻪ ﻣﻲﺷﻮﺩ‪.‬‬

‫‪Terminals 1‬‬
‫‪Data Center 2‬‬
‫‪Componenets 3‬‬

‫‪16‬‬
 ‫‪1‬‬
‫‪ 2-2-2‬ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﻛﺎﺭﺑﺮﺩ‬

‫ﺗﻜﻨﻮﻟﻮژﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻛﻪ ﺑﻪ ﻛﺎﺭﺑﺮﺩﻫﺎ ﺍﺟﺎﺯﻩ ﻣﻲﺩﻫﺪ ﺑﺮ ﺭﻭﻱ ﺳﻴﺴﺘﻢﻋﺎﻣﻞﻫﺎﻱ ﻣﺘﻔﺎﻭﺕ ﻭ ﺣﺘﻲ ﺑﺮ ﺭﻭﻱ‬

‫ﺳﻜﻮﻫﺎﻱ‪ 2‬ﺳﺨﺖﺍﻓﺰﺍﺭﻱ ﻣﺘﻔﺎﻭﺕ ﺍﺟﺮﺍ ﺷﻮﻧﺪ؛ ﻭ ﺍﻳﻦ ﻳﻌﻨﻲ ﻛﺎﺭﺑﺮﺩ ﻃﻮﺭﻱ ﻧﻮﺷﺘﻪ ﺷﺪﻩ ﻛﻪ ﺑﺮ ﺭﻭﻱ ﻳﻚ‬

‫ﻓﺮﻳﻢﻭﺭﻙ ﺍﺟﺮﺍ ﺷﻮﺩ‪ .‬ﻣﻮﺍﺭﺩ ﭘﻴﺸﺮﻓﺘﻪ ﺍﻳﻦ ﺗﻜﻨﻮﻟﻮژﻱ‪ ،‬ﺍﻳﻦ ﻗﺎﺑﻠﻴﺖ ﺭﺍ ﺍﻳﺠﺎﺩ ﻣﻲﻛﻨﺪ ﻛﻪ ﺩﺭ ﺻﻮﺭﺕ ﺍﺯ ﻛﺎﺭ‬

‫ﺍﻓﺘﺎﺩﻥ‪ 3‬ﻳﺎ ﺑﻪ ﺍﺻﻄﻼﺡ ﻓﻴﻞ ﺷﺪﻥ ﻳﻚ ﻛﺎﺭﺑﺮﺩ‪ ،‬ﺁﻥ ﻛﺎﺭﺑﺮﺩ ﺩﻭﺑﺎﺭﻩ ﺍﺟﺮﺍ ﺷﺪﻩ ﻭ ﻳﺎ ﻳﻚ ﻧﺴﺨﻪ ﺟﺎﻳﮕﺰﻳﻦ‪ 4‬ﺍﺟﺮﺍ‬

‫ﺷﻮﺩ؛ ﻭ ﻳﺎ ﺍﻳﻨﻜﻪ ﺑﺮﺍﻱ ﺩﺳﺘﻴﺎﺑﻲ ﺳﻄﺢ ﺑﺎﻻﻳﻲ ﺍﺯ ﺗﻮﺳﻌﻪ ﭘﺬﻳﺮﻱ‪ ، 5‬ﻳﻚ ﺗﻮﺍﺯﻥ ﺑﺎﺭ ﻛﺎﺭﻱ‪ 6‬ﺑﻴﻦ ﭼﻨﺪ ﻧﻤﻮﻧﻪ ﺍﺯ ﻳﻚ‬

‫ﻛﺎﺭﺑﺮﺩ ﺍﻳﺠﺎﺩ ﻛﺮﺩ‪ .‬ﺍﻳﻦ ﻗﺎﺑﻠﻴﺖﻫﺎ ﺩﺭﺣﺎﻟﻲ ﻋﻤﻠﻴﺎﺗﻲ ﻭ ﻗﺎﺑﻞ ﺍﺟﺮﺍ ﺍﺳﺖ ﻛﻪ ﺣﺘﻲ ﺩﺭ ﺑﺴﻴﺎﺭﻱ ﺍﺯ ﻣﻮﺍﺭﺩ ﻧﻴﺎﺯﻱ ﺑﻪ‬

‫ﻣﻌﻤﺎﺭﻱ ﺩﻭﺑﺎﺭﻩ ﻭ ﺩﻭﺑﺎﺭﻩ ﻧﻮﻳﺴﻲ ﻛﺎﺭﺑﺮﺩ ﻧﻴﺰ ﻧﺨﻮﺍﻫﺪ ﺑﻮﺩ‪.‬‬

‫ﻫﻤﭽﻨﻴﻦ ﺍﻳﻦ ﺗﻜﻨﻮﻟﻮژﻱ ﺑﺮ ﺭﻭﻱ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﺍﺟﺮﺍ ﻣﻲﺷﻮﺩ ﺗﺎ ﻛﺎﺭﺑﺮﺩ ﻣﻮﺭﺩﻧﻈﺮ ﻛﭙﺴﻮﻟﻪ ﺷﺪﻩ ﻭ ﻳﺎ ﺑﺮ ﺭﻭﻱ‬

‫ﻳﻚ ﻣﺤﻴﻂ ﺳﺎﺧﺘﮕﻲ ﺍﺟﺮﺍ ﺷﻮﺩ‪.‬‬

‫ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﻛﺎﺭﺑﺮﺩ‪ ،‬ﺩﺍﺭﺍﻱ ﺩﻭ ﺣﺎﻟﺖ ﺳﻤﺖ ﺳﺮﻭﺭ‪ 7‬ﻭ ﺳﻤﺖ ﻛﺎﺭﺑﺮ‪ 8‬ﻣﻴﺒﺎﺷﺪ ﻛﻪ ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺩﺭ ﺷﻜﻞ ‪-2‬‬

‫‪ 4‬ﺑﻪ ﺗﺼﻮﻳﺮ ﻛﺸﻴﺪﻩ ﺍﺳﺖ‪.‬‬

‫‪Application Virtualization 1‬‬

‫‪Platform 2‬‬
‫‪fail 3‬‬
‫‪instance 4‬‬
‫‪scalability 5‬‬
‫‪Load Balancing 6‬‬
‫‪Server side 7‬‬
‫‪Client Side 8‬‬

‫‪17‬‬
 ‫ﺷﻜﻞ ‪ . 4 2‬ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﻛﺎﺭﺑﺮﺩ‬

‫ﺣﺎﻝ ﻫﺮﻳﻚ ﺍﺯ ﺩﻭ ﺣﺎﻟﺖ ﺭﺍ ﻣﻮﺭﺩ ﺑﺮﺭﺳﻲ ﻗﺮﺍﺭ ﻣﻲ ﺩﻫﻴﻢ‪:‬‬

‫ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﻛﺎﺭﺑﺮﺩ ﺳﻤﺖ ﻛﺎﺭﺑﺮ‪ :‬ﺍﻳﻦ ﺗﻜﻨﻮﻟﻮژﻱ ﻳﻚ ﻣﺤﻴﻂ ﻣﺤﺎﻓﻈﺖ ﺷﺪﻩ ﺑﻮﺟﻮﺩ ﻣﻲﺁﻭﺭﺩ ﻛﻪ ﺍﺟﺎﺯﻩ‬

‫ﻣﻲﺩﻫﺪ ﺗﺎ ﻛﺎﺭﺑﺮﺩ ﺑﺘﻮﺍﻧﺪ ﺍﺯ ﺩﻳﮕﺮ ﻛﺎﺭﺑﺮﺩﻫﺎﻱ ﺩﺭ ﺣﺎﻝ ﺍﺟﺮﺍ ﺩﺭ ﻣﺤﻴﻂ ﻭﺣﺘﻲ ﺍﺯ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﻫﻢ ﺍﻳﺰﻭﻟﻪ ﺷﻮﺩ؛‬

‫ﻭ ﺍﻳﻦ ﺑﻌﻀﻲ ﺑﺴﻴﺎﺭﻱ ﺍﺯ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻫﺎﻳﻲ ﻛﻪ ﻗﺒﻼ ﻧﻤﻲﺗﻮﺍﻧﺴﺘﻨﺪ ﺩﺭ ﻛﻨﺎﺭ ﻳﻜﺪﻳﮕﺮ ﻭ ﺑﺮ ﺭﻭﻱ ﻳﻚ ﺳﻴﺴﺘﻢ ﺍﺟﺮﺍ‬

‫ﺷﻮﻧﺪ ﺍﺯ ﺍﻳﻦ ﺑﻪ ﺑﻌﺪ ﻣﻲﺗﻮﺍﻧﻨﺪ ﺩﺭ ﻛﻨﺎﺭ ﻳﻜﺪﻳﮕﺮ ﺍﺳﺘﻔﺎﺩﻩ ﺷﻮﻧﺪ‪ .‬ﻫﻤﭽﻨﻴﻦ ﺑﺴﻴﺎﺭﻱ ﺍﺯ ﻧﺮﻡﺍﻓﺰﺍﺭﻫﺎ ﻛﻪ ﺑﺮﺍﻱ‬

‫ﻧﺴﺨﻪﻫﺎﻱ ﻗﺒﻠﻲ ﻳﻚ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻧﻮﺷﺘﻪ ﺷﺪﻩﺍﻧﺪ ﻣﻲﺗﻮﺍﻧﻨﺪ ﺑﺮ ﺭﻭﻱ ﻧﺴﺨﻪﻫﺎﻱ ﺟﺪﻳﺪﺗﺮ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﺍﺟﺮﺍ‬

‫ﺷﻮﻧﺪ‪ .‬ﻭ ﻣﻮﺭﺩ ﺩﻭﻡ ﺯﻣﺎﻧﻲ ﻣﻔﻴﺪ ﺧﻮﺍﻫﺪ ﺑﻮﺩ ﻛﻪ ﺳﺎﺯﻣﺎﻥ ﺑﺮﺍﻱ ﺑﺎﻻ ﺑﺮﺩﻥ ﻛﺎﺭﺍﻳﻲ ﻭ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺗﻜﻨﻮﻟﻮژﻱ‬

‫ﺟﺪﻳﺪﺗﺮ ﻗﺼﺪ ﺍﺭﺗﻘﺎ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﺭﺍ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ ﻭﻟﻲ ﺑﻪ ﺟﻬﺖ ﻧﺒﻮﺩ ﻧﺴﺨﻪ ﻫﺎﻱ ﺳﺎﺯﮔﺎﺭ ﺑﺎ ﻧﺴﺨﻪ ﺟﺪﻳﺪ‬

‫‪18‬‬
 ‫ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ‪ ،‬ﺍﻳﻦ ﻛﺎﺭ ﻣﻘﺪﻭﺭ ﻧﺒﺎﺷﺪ‪.‬‬

‫ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﻛﺎﺭﺑﺮﺩ ﺳﻤﺖ ﺳﺮﻭﺭ‪ :‬ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ‪ ،‬ﻋﻼﻭﻩ ﺑﺮ ﺩﺍﺷﺘﻦ ﻣﺰﺍﻳﺎ ﺣﺎﻟﺖ ﺳﻤﺖ ﻛﺎﺭﺑﺮ ﻣﻲﺗﻮﺍﻥ ﺍﺯﺁﻥ‬

‫ﺑﺮﺍﻱ ﺍﺟﺮﺍﻱ ﭼﻨﺪ ﻧﻤﻮﻧﻪ ﺍﺯ ﻳﻚ ﻧﺮﻡﺍﻓﺰﺍﺭ ﺑﺮﺍﻱ ﺍﺭﺍﺋﻪ ﺑﻪ ﭼﻨﺪ ﻛﺎﺭﺑﺮ ﺑﻬﺮﻩ ﺑﺮﺩ‪ .‬ﻣﺜﻼ ﻣﻲ ﺗﻮﺍﻥ ﺑﻪ ﻃﻮﺭ ﻫﻤﺰﻣﺎﻥ ﺑﺮ‬

‫ﺭﻭﻱ ﻳﻚ ﺳﺮﻭﺭ‪ 10‬ﻧﻤﻮﻧﻪ ﺍﺯ ‪ 2007 office word‬ﺭﺍ ﺍﺟﺮﺍ ﻛﺮﺩﻩ ﻭ ﺍﺯ ﻃﺮﻳﻖ ﺗﺮﻣﻴﻨﺎﻝ ﺑﻪ ‪ 10‬ﻛﺎﺭﺑﺮ ﺳﺮﻭﻳﺲ‬

‫ﺩﺍﺩ‪ .‬ﻭ ﻳﺎ ﺍﻳﻨﻜﻪ ﺩﺭ ﻫﻨﮕﺎﻡ ﺩﺭﺧﻮﺍﺳﺖ ﻳﻚ ﻧﺴﺨﻪ ﺍﺯ ﻳﻚ ﻛﺎﺭﺑﺮﺩ ﭼﻨﺪ ﻧﻤﻮﻧﻪ ﺍﺯ ﺁﻥ ﺑﻪ ﺭﻭﻱ ﭼﻨﺪ ﻣﺎﺷﻴﻦ ﻣﺨﺘﻠﻒ‬

‫ﺍﺟﺮﺍ ﺷﻮﺩ ﺗﺎ ﺩﺭ ﺻﻮﺭﺕ ﺍﺯ ﻛﺎﺭ ﺍﻓﺘﺎﺩﻥ ﻳﻜﻲ‪ ،‬ﺍﺯ ﺩﻳﮕﺮﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺷﻮﺩ‪.‬‬

‫ﺩﺭ ﺣﺎﻝ ﺣﺎﺿﺮ ﺑﺴﻴﺎﺭﻱ ﺍﺯ ﺷﺮﻛﺖﻫﺎ ﺳﻴﺴﺘﻢﻫﺎﻱ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﻛﺎﺭﺑﺮﺩ ﺭﺍ ﺍﺭﺍﺋﻪ ﻣﻲﺩﻫﺪ ﻛﻪ ﺍﺯ ﺁﻥ ﺟﻤﻠﻪ‬

‫ﻣﻲﺗﻮﺍﻥ ﺑﻪ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺍﺷﺎﺭﻩ ﻛﺮﺩ‪.‬‬

‫ﺳﻴﺘﺮﻳﻚ ﻛﻪ ﺩﺭ ﻫﻤﻪ ﺯﻣﻴﻨﻪﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﻓﻌﺎﻝ ﺍﺳﺖ ﺩﺭ ﺍﻳﻦ ﺯﻣﻴﻨﻪ ﻧﻴﺰ ﻳﻜﻲ ﺍﺯ ﭘﻴﺸﺘﺎﺯﻳﻦ‬

‫ﺍﺳﺖ‪ XenApp .‬ﺍﻳﻦ ﺷﺮﻛﺖ ﻳﻚ ﻣﺤﺼﻮﻝ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﻛﺎﺭﺑﺮﺩ ﺳﻤﺖ ﻛﺎﺭﺑﺮ ﺍﺳﺖ‪.‬‬

‫ﻣﺎﻳﻜﺮﻭﺳﺎﻓﺖ ﺍﺯ ﺳﺎﻝ ‪ 2006‬ﺑﺎ ‪ Softricity‬ﺑﻪ ﺍﻳﻦ ﻋﺮﺻﻪ ﻭﺍﺭﺩ ﺷﺪ ﻛﻪ ﺑﻌﺪﻫﺎ ﺁﻥ ﺭﺍ ﺑﻪ‪ SoftGrid‬ﺗﻐﻴﻴﺮﻧﺎﻡ‬

‫ﺩﺍﺩ‪ .‬ﺩﺭ ﺣﺎﻝ ﺣﺎﺿﺮ ﺗﻜﻨﻮﻟﻮژﻱ ﻣﺎﻳﻜﺮﻭﺳﺎﻓﺖ ﺭﺍ ﺑﺎ ﻧﺎﻡ ‪ Microsoft Application Virtualization‬ﻳﺎ ‪App-V‬‬

‫ﺷﻨﺎﺧﺘﻪ ﻣﻲﺷﻮﺩ‪ App-V .‬ﻫﻢ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺳﻤﺖ ﻛﺎﺭﺑﺮ ﻭ ﻫﻢ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺳﻤﺖ ﺳﺮﻭﺭ ﺭﺍ ﺍﺭﺍﺋﻪ ﻣﻲﺩﻫﺪ‪.‬‬

‫‪ VMware‬ﻧﻴﺰ ﺩﺭ ﺳﺎﻝ ‪ Thin App ، 2008‬ﺭﺍ ﺍﺭﺋﻪ ﻛﺮﺩ ﻛﻪ ﻳﻚ ﺗﻜﻨﻮﻟﻮژﻱ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﻛﺎﺭﺑﺮﺩ ﺳﻤﺖ‬

‫ﻛﺎﺭﺑﺮ ﺍﺳﺖ‪.‬‬

‫‪ AppZero virtualization‬ﻫﻢ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﺑﻪ ﺳﺎﺯﻣﺎﻥﻫﺎ ﻣﻲﺩﻫﺪ ﺗﺎ ﺑﺘﻮﺍﻧﻨﺪ ﻧﺮﻡﺍﻓﺰﺍﺭﻫﺎﻳﺸﺎﻥ ﺭﺍ ﺩﺭ ﺩﺍﺧﻞ‬

‫ﻳﻚ ﻣﺤﻴﻂ ﻣﺠﺎﺯﻱ ﻛﻪ ‪ VAA‬ﻧﺎﻣﻴﺪﻩ ﻣﻲﺷﻮﺩ ﻛﭙﺴﻮﻟﻪ ﻧﻤﺎﻳﻨﺪ‪.‬‬

‫‪1‬‬
‫‪ 3-2-2‬ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﭘﺮﺩﺍﺯﺵ‬
‫ﺗﻜﻨﻮﻟﻮژﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻭ ﺳﺨﺖﺍﻓﺰﺍﺭ ﻛﻪ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﻣﻲ ﺩﻫﺪ ﺗﺎ ﭘﻴﻜﺮﺑﻨﺪﻱ ﺳﺨﺖﺍﻓﺰﺍﺭ ﻓﻴﺰﻳﻜﻲ ﺍﺯ ﺩﻳﺪ‬

‫‪Process Virtualization 1‬‬

‫‪19‬‬
‫ﺳﺮﻭﻳﺲﻫﺎﻱ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻭ ﻛﺎﺭﺑﺮﺩ ﻣﺨﻔﻲ ﺑﻤﺎﻧﺪ‪ .‬ﺍﻳﻦ ﺗﻜﻨﻮﻟﻮژﻱ ﺍﺟﺎﺯﻩ ﻣﻲﺩﻫﺪ ﺗﺎ ﭼﻨﺪ ﺳﻴﺴﺘﻢ ﺑﺘﻮﺍﻧﻨﺪ ﻳﻚ‬

‫ﺳﻴﺴﺘﻢ ﺩﻳﺪﻩ ﺷﻮﻧﺪ ﻭﻳﺎ ﺑﺮﻋﻜﺲ؛ ﻳﻚ ﺳﻴﺴﺘﻢ ﺑﺘﻮﺍﻧﺪ ﺍﺯ ﺩﻳﺪ ﺧﺎﺭﺟﻲ ﭼﻨﺪﻳﻦ ﺳﻴﺴﺘﻢ ﺩﻳﺪﻩﺷﻮﺩ‪ .‬ﺍﺯ ﻣﺰﺍﻳﺎﻳﻲ‬

‫ﺍﻳﻦ ﻧﻮﻉ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﻣﻲ ﺗﻮﺍﻥ ﺑﻪ ﺍﻓﺰﺍﻳﺶ ﻛﺎﺭﺍﻳﻲ‪ ،‬ﺩﺳﺘﺮ ﺳﻲ ﺑﻪ ﺳﻄﺢ ﺑﺎﻻﻳﻲ ﺍﺯ ﮔﺴﺘﺮﺵ ﭘﺬﻳﺮﻱ‪ ،‬ﻗﺎﺑﻠﻴﺖ‬

‫ﺍﻋﺘﻤﺎﺩ ﺑﺎﻻﺗﺮ‪ ،1‬ﺩﺳﺘﺮﺳﻲ ﻫﻤﻴﺸﮕﻲ‪ ، 2‬ﺩﺳﺘﻴﺎﺑﻲ ﺑﻪ ﺳﺮﻋﺖ ﺑﻴﺸﺘﺮ ﺩﺭ ﭘﺮﺩﺍﺯﺵ ‪ ،‬ﻫﻤﭽﻨﻴﻦ ﺍﻳﺠﺎﺩ ﻣﺤﻴﻂ ﻫﺎﻱ‬

‫ﻣﺘﻔﺎﻭﺕ ﺑﺮ ﺭﻭﻱ ﻳﻚ ﺳﻴﺴﺘﻢ ﻓﻴﺰﻳﻜﻲ ﻣﻨﻔﺮﺩ‪ ،‬ﺍﺷﺎﺭﻩ ﻛﺮﺩ‪.‬‬

‫ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﭘﺮﺩﺍﺯﺵ ﺩﺍﺭﺍﻱ ﭘﻨﺞ ﻓﺮﻡ ﻣﺨﺘﻠﻒ ﺍﺳﺖ‪:‬‬

‫‪3‬‬
‫‪ -‬ﻧﺎﻇﺮ ﭘﺮﺩﺍﺯﺵ ﻣﻮﺍﺯﻱ‬
‫‪4‬‬
‫‪ -‬ﻧﺎﻇﺮ ﻣﺪﻳﺮﻳﺖ ﺑﺎﺭ ﻛﺎﺭﻱ‬
‫‪5‬‬
‫‪ -‬ﻧﺎﻇﺮ ﻗﺎﺑﻠﻴﺖ ﺩﺳﺘﺮﺳﻲ ﺑﺎﻻ‪ /‬ﺑﺎﺯﮔﺸﺖ ﺍﺯ ﺧﻄﺎ‪ /‬ﺑﺎﺯﻳﺎﺑﻲ ﺳﻴﺴﺘﻢ‬
‫‪6‬‬
‫ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻣﺎﺷﻴﻨﻲ ﻣﺠﺎﺯﻱ‬ ‫‪-‬‬

‫ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻭ ﺑﺨﺶ ﺑﻨﺪﻱ‬ ‫‪-‬‬

‫ﭘﺮﺩﺍﺯﺵﻣﻮﺍﺯﻱ‪ ،‬ﻣﺪﻳﺮﻳﺖ ﺑﺎﺭ ﻛﺎﺭﻱ ﻭ ﭘﻴﻜﺮﺑﻨﺪﻱ ﺑﺎ ﻗﺎﺑﻠﻴﺖ ﺩﺳﺘﺮﺳﻲ ﺑﺎﻻ ﺭﺍ ﻣﻌﻤﻮﻻ ﺑﺎ ﻧﺎﻡ‬

‫ﺧﻮﺷﻪﺑﻨﺪﻱ‪ 7‬ﻳﺎ ﻛﻼﺳﺘﺮ ﻣﻲ ﺷﻨﺎﺳﻨﺪ؛ ﺍﮔﺮ ﭼﻪ ﻫﺮ ﻳﻚ ﺳﺮﻭﻳﺲﻫﺎﻱ ﻣﺘﻔﺎﻭﺗﻲ ﺍﺭﺍﺋﻪ ﻣﻲﺩﻫﺪ‪.‬‬

‫ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﭘﺮﺩﺍﺯﺵ ﻳﻜﻲ ﺍﺯ ﺍﻳﻦ ﺳﻪ ﻛﺎﺭ ﺭﺍ ﺍﻧﺠﺎﻡ ﻣﻲ ﺩﻫﺪ‪:‬‬

‫‪ .1‬ﻛﭙﺴﻮﻟﻪ ﻛﺮﺩﻥ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﺑﻄﻮﺭﻱ ﻛﻪ ﺗﻌﺪﺍﺩ ﺯﻳﺎﺩﻱ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻣﻲ ﺗﻮﺍﻧﻨﺪ ﺑﺮﺭﻭﻱ ﻳﻚ‬

‫ﺳﻴﺴﺘﻢ ﺍﺟﺮﺍ ﺷﻮﻧﺪ‬

‫‪ .2‬ﻣﺘﺼﻞ ﻛﺮﺩﻥ ﭼﻨﺪ ﺳﻴﺴﺘﻢ ﺑﺮﺍﻱ ﺍﻳﻨﻜﻪ ﻳﻚ ﻛﺎﺭﺑﺮﺩ ﻭ ﻳﺎ ﺩﺍﺩﻩ ﺑﻴﻦ ﺁﻧﻬﺎ ﺗﻮﺯﻳﻊ ﺷﺪﻩ ﺗﺎ ﺑﺘﻮﺍﻥ ﺑﻪ‬

‫ﻛﻤﻚ ﭘﺮﺩﺍﺯﺵﻣﻮﺍﺯﻱ ﻛﺎﺭﺍﻳﻲ ﺭﺍ ﺑﺎﻻ ﺑﺮﺩ‬

‫‪ .3‬ﻣﺘﺼﻞ ﻛﺮﺩﻥ ﻛﺮﺩﻥ ﭼﻨﺪ ﺳﻴﺴﺘﻢ ﺗﺎ ﺩﺭ ﺻﻮﺭﺗﻲ ﺧﺮﺍﺑﻲ ﻳﻜﻲ ﺍﺯ ﺁﻧﻬﺎ ﺳﻴﺴﺘﻢ ﻣﺘﻮﻗﻒ ﻧﺸﺪﻩ ﻭ ﺑﻪ‬

‫‪Reliability 1‬‬
‫‪High Availability 2‬‬
‫‪parallel processing monitors 3‬‬
‫‪workload management monitors 4‬‬
‫‪high availability/fail over/disaster recovery monitors 5‬‬
‫‪virtual machine software 6‬‬
‫‪cluster 7‬‬

‫‪20‬‬
 ‫ﻛﻤﻚ ﺑﻘﻴﻪ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺘﺼﻞ ﺑﻪ ﻣﺠﻤﻮﻋﻪ‪ ،‬ﺑﻪ ﻛﺎﺭ ﺧﻮﺩ ﺍﺩﺍﻣﻪ ﺩﻫﺪ‪.‬‬

‫‪ 1-3-2-2‬ﻳﻚ ﺳﻴﺴﺘﻢ ﺑﺠﺎﻱ ﭼﻨﺪ ﺳﻴﺴﺘﻢ ﻭﭼﻨﺪ ﺳﻴﺴﺘﻢ ﺑﺠﺎﻱ ﻳﻚ ﺳﻴﺴﺘﻢ‪.‬‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺷﻜﻞ ‪ 5-2‬ﻧﺸﺎﻥ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪ ،‬ﺗﻔﺎﻭﺕ ﺯﻳﺎﺩﻱ ﺑﻴﻦ ﺍﻳﻨﻜﻪ ﻳﻚ ﺳﻴﺴﺘﻢ ﺍﺯ ﺩﻳﺪ ﺧﺎﺭﺟﻲ‬

‫ﭼﻨﺪ ﺳﻴﺴﺘﻢ ﺩﻳﺪﻩ ﺷﻮﺩ ﻳﺎ ﭼﻨﺪ ﺳﻴﺴﺘﻢ ﺍﺯ ﺩﻳﺪﻩ ﺑﺮﻭﻥ ﻳﻚ ﺳﻴﺴﺘﻢ ﺩﻳﺪﻩ ﺷﻮﻧﺪ ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪ .‬ﺩﺭ ﺍﺩﺍﻣﻪ ﻫﺮﻳﻚ‬

‫ﺍﺯ ﺍﻳﻦ ﺩﻭ ﺣﺎﻟﺖ ﺭﺍ ﺑﺮﺭﺳﻲ ﻣﻲﻛﻨﻴﻢ‪.‬‬

‫ﺷﻜﻞ ‪ . 5 2‬ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﭘﺮﺩﺍﺯﺵ‬

‫‪ 1-1-3-2-2‬ﭘﻴﻜﺮﺑﻨﺪﻱ ﻳﻚ ﺳﻴﺴﺘﻢ ﺑﻄﻮﺭﻱ ﻛﻪ ﺍﺯ ﺩﻳﺪ ﺧﺎﺭﺟﻲ ﭼﻨﺪ ﺳﻴﺴﺘﻢ ﺩﻳﺪﻩ ﺷﻮﺩ‬

‫ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻛﻞ ﭘﺸﺘﻪ ﻧﺮﻡﺍﻓﺰﺍﺭ ﺭﺍ ﻛﻪ ﺳﻴﺴﺘﻢ ﺭﺍ ﻣﻲﺳﺎﺯﺩ ﺩﺭ ﺩﺍﺧﻞ ﻓﺎﻳﻞ ﻣﺎﺷﻴﻦﻣﺠﺎﺯﻱ‬

‫ﻛﭙﺴﻮﻟﻪ ﻣﻲﻛﻨﺪ‪.‬‬

‫‪21‬‬
 ‫ﻓﻮﻕ ﻧﺎﻇﺮ‪ 1‬ﻣﻲﺗﻮﺍﻧﺪ ﻳﻚ ﻳﺎ ﭼﻨﺪ ﻣﺎﺷﻴﻦﻣﺠﺎﺯﻱ ﺭﺍ ﺑﺮ ﺭﻭﻱ ﻳﻚ ﻣﺎﺷﻴﻦ ﻓﻴﺰﻳﻜﻲ ﺍﺟﺮﺍﻛﻨﺪ‪.‬‬

‫ﺷﻜﻞ ‪ 6-2‬ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺭﺍ ﺑﻪ ﺗﺼﻮﻳﺮ ﻣﻲ ﻛﺸﺪ‬

‫ﺷﻜﻞ ‪ . 6 2‬ﺳﺮﻭﺭ ﻣﺠﺎﺯﻱ ﺩﺭ ﺑﺮﺍﺑﺮ ﺳﺮﻭﺭ ﻓﻴﺰﻳﻜﻲ‬

‫ﺩﻭ ﻧﻮﻉ ﻓﻮﻕ ﻧﺎﻇﺮ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ‪:‬‬

‫ﻓﻮﻕﻧﺎﻇﺮ ﻧﻮﻉ‪ 21‬ﻛﻪ ﺑﺮ ﺭﻭﻱ ﺳﻴﺴﺘﻢ ﻓﻴﺰﻳﻜﻲ ﺍﺟﺮﺍ ﻣﻲﺷﻮﺩ ﻭ ﻓﻮﻕﻧﺎﻇﺮ ﻧﻮﻉ‪32‬ﻛﻪ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ‬

‫ﻣﻴﻬﻤﺎﻥ ﺭﺍ ﺑﻪ ﻋﻨﻮﺍﻥ ﻳﻚ ﭘﺮﻭﺳﺲ ﺩﺭ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻧﺼﺐﺷﺪﻩ ﺑﺮ ﺭﻭﻱ ﺳﺨﺖﺍﻓﺰﺍﺭ ﺍﺟﺮﺍ ﻣﻲﻛﻨﺪ؛ ﻛﻪ ﺍﻟﺒﺘﻪ ﻫﺮ‬

‫ﻛﺪﺍﻡ ﺍﺯ ﺍﻳﻦ ﭘﺮﻭﺳﺲﻫﺎ ﻛﻨﺘﺮﻝ ﻛﺎﻣﻞ ﺳﻴﺴﺘﻢ ﺧﻮﺩ ﺭﺍﺩﺍﺭﺩ‪ ،‬ﻛﻪ ﺗﻨﻬﺎ ﺑﺨﺸﻲ ﺍﺯ ﻣﻨﺎﺑﻊ ﺳﻴﺴﺘﻢ ﻓﻴﺰﻳﻜﻲ ﺍﺻﻠﻲ ﺭﺍ‬

‫ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺩﺍﺭﺩ‪.‬‬

‫ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻭ ﺑﺨﺶ ﺑﻨﺪﻱ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﻓﺮﺍﻫﻢ ﻣﻲﻛﻨﻨﺪ ﺗﺎ ﺗﻌﺪﺩ ﺯﻳﺎﺩﻱ ﻛﺎﺭﺑﺮﺩ ﺗﺤﺖ ﻳﻚ‬

‫ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻭ ﺑﻪ ﻃﻮﺭ ﻛﺎﻣﻼ ﺍﻳﺰﻭﻟﻪ ﺷﺪﻩ ﻭ ﻫﺮﻳﻚ ﺩﺭ ﻣﺤﻴﻂ ﻣﺤﺎﻓﻈﺖﺷﺪﻩ ﺧﻮﺩ ﺍﺟﺮﺍ ﺷﻮﻧﺪ‪ .‬ﻫﺮ ﻳﻚ ﺍﺯ ﺍﻳﻦ‬

‫ﻛﺎﺭﺑﺮﺩﻫﺎ ﺑﺮ ﺭﻭﻱ ﺳﻴﺴﺘﻢ ﺧﻮﺩ ﺍﺟﺮﺍ ﺷﺪﻩ ﻭ ﻣﻨﺎﺑﻊ ﺧﻮﺩ ﺭﺍ ﻣﺪﻳﺮﻳﺖ ﻣﻲﻛﻨﺪ‪.‬‬

‫‪Hypervisor 1‬‬
‫‪Type one Hypervisor 2‬‬
‫‪Type two Hypervisor 3‬‬

‫‪22‬‬
 ‫ﻓﻮﻕ ﻧﺎﻇﺮ‬

‫ﻓﻮﻕ ﻧﺎﻇﺮ ﭘﻠﺘﻔﺮﻡ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺍﺳﺖ ﻛﻪ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﺑﻪ ﺷﻤﺎ ﻣﻲﺩﻫﺪ ﺗﺎ ﺑﺘﻮﺍﻧﻴﺪ ﭼﻨﺪﻳﻦ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ‬

‫ﺭﺍ ﺑﺮ ﺭﻭﻱ ﻳﻚ ﺳﻴﺴﺘﻢ ﻓﻴﺰﻳﻜﻲ ﻭﺍﺣﺪ ﻛﻪ ﺁﻥ ﺭﺍ ﻣﻴﺰﺑﺎﻥ‪ 1‬ﻣﻲ ﺧﻮﺍﻧﻨﺪ ﺍﺟﺮﺍ ﻛﻨﻴﺪ‪ .‬ﻋﻤﻠﻜﺮﺩ ﺍﺻﻠﻲ ﻓﻮﻕ ﻧﺎﻇﺮ ﺍﻳﻦ‬

‫ﺍﺳﺖ ﻛﻪ ﺑﺮﺍﻱ ﻫﺮ ﻳﻚ ﺍﺯ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻳﻚ ﻣﺤﻴﻂ ﺍﻳﺰﻭﻟﻪ ﺷﺪﻩ ﻣﺤﻴﺎ ﻛﻨﺪ ﻭ ﻫﻤﭽﻨﻴﻦ ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ‬

‫ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞﻫﺎﻱ ﺍﺟﺮﺍ ﺷﺪﻩ ﺑﺮ ﺭﻭﻱ ﻣﺎﺷﻴﻦﻫﺎﻱﻣﺠﺎﺯﻱ ﻭ ﺍﺭﺗﺒﺎﻁ ﺁﻧﻬﺎ ﺑﺎ ﻣﺎﺷﻴﻦ ﻣﻴﺰﺑﺎﻥ ﺭﺍ ﻣﺪﻳﺮﻳﺖ ﻧﻤﺎﻳﺪ‪.‬‬

‫ﺍﺻﻄﻼﺡ ﻓﻮﻕ ﻧﺎﻇﺮ ﺑﻪ ﺳﺎﻝ ‪ 1972‬ﺑﺮ ﻣﻲﮔﺮﺩﺩ؛ ﻫﻨﮕﺎﻣﻲ ﻛﻪ‪ IBM‬ﺑﺮﺍﻱ ﻛﻨﺘﺮﻝ ﻣﻴﻨﻔﺮﻳﻢ‪ system/ 370 ،‬ﺭﺍ‬

‫ﺑﺮﺍﻱ ﭘﺸﺘﻴﺒﺎﻧﻲ ﺍﺯ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺑﺮﻭﺯﺭﺳﺎﻧﻲ ﻛﺮﺩ‪.‬‬

‫ﻓﻮﻕ ﻧﺎﻇﺮ ﺭﺍ ﺑﻪ ﺩﻭ ﻃﺮﻳﻖ ﻣﻲﺗﻮﺍﻥ ﺩﺳﺘﻪ ﺑﻨﺪﻱ ﻛﺮﺩ‪:‬‬

‫ﺍﻭﻝ ﺍﺯ ﻧﻈﺮ ﺍﺟﺮﺍ ﺑﺮ ﺭﻭﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﻛﻪ ﺑﻪ ﺩﻭ ﺩﺳﺘﻪ ﻧﻮﻉ‪ 12‬ﻭ ﻧﻮﻉ‪ 23‬ﻃﺒﻘﻪ ﺑﻨﺪﻱ ﻣﻲﺷﻮﺩ‪.‬‬

‫ﺩﻭﻡ ﺍﺯ ﻧﻈﺮ ﻃﺮﺍﺣﻲ ﻛﻪ ﺑﻪ ﺩﻭ ﮔﺮﻭﻩ ﻳﻜﭙﺎﺭﭼﻪ‪ 4‬ﻭ ﺭﻳﺰﻫﺴﺘﻪ‪ 5‬ﺩﺳﺘﻪ ﺑﻨﺪﻱ ﻣﻲﺷﻮﻧﺪ‪.‬‬

‫ﻓﻮﻕ ﻧﺎﻇﺮ ﻧﻮﻉ‪1‬‬

‫ﻓﻮﻕ ﻧﺎﻇﺮ ﻧﻮﻉ ‪ 1‬ﺑﺮ ﺭﻭﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﺍﺟﺮﺍ ﺷﺪﻩ ﻭ ﻋﻤﻠﻜﺮﺩ ﺁﻥ ﺷﺒﻴﻪ ﺑﺮﻧﺎﻣﻪ ﻛﻨﺘﺮﻝ ﺍﺳﺖ‪ .‬ﺳﻴﺴﺘﻢ‬

‫ﻋﺎﻣﻞﻫﺎﻱ ﻣﻴﻬﻤﺎﻥ‪ 6‬ﻫﻢ ﺑﺮ ﺭﻭﻱ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻛﻪ ﺑﺮ ﺭﻭﻱ ﻻﻳﻪ ﻓﻮﻕﻧﺎﻇﺮ ﻗﺮﺍﺭ ﺩﺍﺭﻧﺪ ﺍﺟﺮﺍ ﻣﻲﺷﻮﻧﺪ ‪.‬‬

‫ﺷﻜﻞ ‪ 2-1‬ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺭﺍ ﺑﻪ ﺗﺼﻮﻳﺮ ﻛﺸﻴﺪﻩ ﺍﺳﺖ‪.‬‬

‫‪Host 1‬‬
‫‪Type 1 2‬‬
‫‪Type 2 3‬‬
‫‪Monolithic 4‬‬
‫‪Microkernel 5‬‬
‫‪Guest OS 6‬‬

‫‪23‬‬
 ‫ﺷﻜﻞ ‪ . 7 2‬ﻓﻮﻕﻧﺎﻇﺮ ﻧﻮﻉ‪1‬‬

‫ﺍﺯ ﺁﻧﺠﺎﻳﻲ ﻛﻪ ﻓﻮﻕ ﻧﺎﻇﺮ ﻧﻮﻉ ‪ 1‬ﻣﺴﺘﻘﻴﻤﺎ ﺑﺮ ﺭﻭﻱ ﺳﺨﺖﺍﻓﺰﺍﺭ ﺍﺟﺮﺍ ﻣﻲﺷﻮﻧﺪ‪ ،‬ﻣﻌﻤﻮﻻ ﺩﺍﺭﺍﻱ ﻛﺎﺭﺍﻳﻲ ﻭ‬

‫ﺑﻬﺮﻭﺭﻱ ﺑﻬﺘﺮ‪ ،‬ﺩﺳﺘﺮﺳﻲ ﺑﺎﻻﺗﺮ ﻭ ﺍﻣﻨﻴﺖ ﺑﻴﺸﺘﺮﻱ ﻧﺴﺒﺖ ﺩﻳﮕﺮ ﻓﻮﻕ ﻧﺎﻇﺮﻫﺎ ﺩﺍﺭﻧﺪ‪ .‬ﺑﻌﻀﻲ ﺍﺯ ﻣﺤﺼﻮﻻﺕ ﻣﺠﺎﺯﻱ‬

‫ﺳﺎﺯﻱ ﻧﻮﻉ ﻳﻚ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ‬

‫‪Microsoft Hyper-V‬‬
‫‪Citrix Xen Server‬‬
‫‪VMware ESX Server‬‬

‫ﻓﻮ ﻕ ﻧﺎﻇﺮ ﻧﻮﻉ ‪2‬‬

‫ﻓﻮﻕ ﻧﺎﻇﺮ ﻧﻮﻉ ‪ 2‬ﺑﺮ ﺭﻭﻱ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﻧﺼﺐ ﺷﺪﻩ ﺑﺮ ﺭﻭﻱ ﻛﺎﻣﭙﻴﻮﺗﺮ ﻣﻴﺰﺑﺎﻥ‪ ،‬ﺍﺟﺮﺍ ﻣﻲﺷﻮﺩ‪ .‬ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ‬

‫ﻫﺎﻱ ﻣﻴﻬﻤﺎﻥ ﻫﻢ ﺑﺮ ﺭﻭﻱ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺧﺘﻪ ﺷﺪﻩ ﺑﺮﺭﻭﻱ ﻓﻮﻕ ﻧﺎﻇﺮ ﻧﺼﺐ ﻭ ﺍﺟﺮﺍ ﻣﻲﺷﻮﻧﺪ ﻛﻪ ﺍﻳﻦ‬

‫ﻣﺴﺌﻠﻪ ﺩﺭ ﺷﻜﻞ ‪ 8-2‬ﻧﺸﺎﻥ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬

‫‪24‬‬
 ‫ﺷﻜﻞ ‪ . 8 2‬ﻓﻮﻕﻧﺎﻇﺮ ﻧﻮﻉ‪2‬‬

‫ﺑﺎ ﻣﻘﺎﻳﺴﻪ ﺍﻱ ﺑﻴﻦ ﺩﻭ ﺷﻜﻞ ‪ 7-2‬ﻭ ‪ 8-2‬ﻣﺘﻮﺟﻪ ﺧﻮﺍﻫﻴﺪ ﺷﺪﻛﻪ ﺩﺭ ﻓﻮﻕ ﻧﺎﻇﺮ ﻧﻮﻉ ‪ 2‬ﻳﻚ ﻻﻳﻪ ﺍﺿﺎﻓﻲ ﺑﻴﻦ‬

‫ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﻫﺎﻱ ﻣﻴﻬﻤﺎﻥ ﻭ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ﺍﻳﻦ ﻻﻳﻪ ﺑﺎﺭ ﺍﺿﺎﻓﻲ ﺭﺍ ﺑﻪ ﺳﻴﺴﺘﻢ ﺗﺤﻤﻴﻞ ﻣﻲﻛﻨﺪ‬

‫ﻛﻪ ﺑﺎﻋﺚ ﺍﻓﺖ ﻛﺎﺭﺍﻳﻲ ﺍﻳﻦ ﺳﻴﺴﺘﻢ ﺑﻪ ﻧﺴﺒﺖ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺩﺍﺭﺍﻱ ﻓﻮﻕ ﻧﺎﻇﺮ ﻧﻮﻉ‪ 1‬ﻣﻲﺷﻮﺩ‪ .‬ﺍﻳﻦ ﻣﺴﺌﻠﻪ )ﺍﻓﺖ‬

‫ﻛﺎﺭﺍﻳﻲ ﺩﺭ ﻓﻮﻕ ﻧﺎﻇﺮ ﻧﻮﻉ‪ (2‬ﺑﺎﻋﺚ ﺍﻳﺠﺎﺩ ﻣﺤﺪﻭﺩﻳﺖ ﺑﺮ ﺗﻌﺪﺍﺩ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﻴﻬﻤﺎﻥ ﺑﺮ ﺭﻭﻱ ﻓﻮﻕ ﻧﺎﻇﺮ ﻧﻮﻉ ‪2‬‬

‫ﻣﻲﺷﻮﺩ‪.‬‬

‫ﭼﻨﺪ ﻧﻤﻮﻧﻪ ﺍﺯ ﻓﻮﻕ ﻧﺎﻇﺮﻫﺎﻱ ﻧﻮﻉ ‪ 2‬ﺑﻪ ﻗﺮﺍﺭ ﺯﻳﺮ ﻫﺴﺘﻨﺪ ‪.‬‬

‫‪Microsoft virtual server‬‬

‫‪VMware server‬‬
‫‪Oracle virtual box‬‬
‫ﺳﻴﺴﺘﻢ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺭﻭﻣﻴﺰﻱ‪ 1‬ﻣﺎﻳﻜﺮﻭﺳﺎﻓﺖ ﻣﻮﺳﻮﻡ ﺑﻪ ‪ virtual pc‬ﻧﻴﺰ ﺍﺯ ﻣﻌﻤﺎﺭﻱ ﻓﻮﻕﻧﺎﻇﺮ ﻧﻮﻉ ‪2‬‬

‫‪Desktop 1‬‬

‫‪25‬‬
 ‫ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﻛﻨﺪ‪.‬‬

‫ﻓﻮﻕ ﻧﺎﻇﺮ ﻳﻜﭙﺎﺭﭼﻪ‬

‫‪1‬‬
‫ﻃﺮﺍﺣﻲ ﻓﻮﻕ ﻧﺎﻇﺮ ﻳﻜﭙﺎﺭﭼﻪ ﻃﻮﺭﻱ ﺍﺳﺖ ﻛﻪ ﺷﺎﻣﻞ ﺭﺍﻩﺍﻧﺪﺍﺯﻫﺎﻱ ﺳﺨﺖﺍﻓﺰﺍﺭﻱ ﺍﺻﻄﻼﺣﺎ –‪hyperviso‬‬

‫‪ aware‬ﺑﻮﺩﻩ ﻭ ﺍﻳﻦ ﺭﺍﻩﺍﻧﺪﺍﺯﻫﺎ ﺗﻮﺳﻂ ﻓﻮﻕﻧﺎﻇﺮ ﻣﺪﻳﺮﻳﺖ ﻣﻲﺷﻮﻧﺪ‪ .‬ﺷﻜﻞ ‪ 9-2‬ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺭﺍ ﺑﻪ ﺗﺼﻮﻳﺮ‬

‫ﻣﻲﻛﺸﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 9 2‬ﻓﻮﻕ ﻧﺎﻇﺮ ﻳﻜﭙﺎﺭﭼﻪ‬

‫ﺍﻳﻦ ﻃﺮﺍﺣﻲ ﻣﺰﺍﻳﺎ ﻭ ﻣﻌﺎﻳﺒﻲ ﺩﺍﺭﺩ ﻛﻪ ﺍﺯ ﺁﻥ ﺟﻤﻠﻪ ﺍﻳﻨﻜﻪ ﺍﻳﻦ ﻧﻮﻉ ﺍﺯ ﻓﻮﻕﻧﺎﻇﺮﻫﺎ ﻧﻴﺎﺯﻱ ﺑﻪ ﻗﺴﻤﺖ ﻛﻨﺘﺮﻝ‬

‫‪Driver 1‬‬

‫‪26‬‬
‫ﻛﻨﻨﺪﻩ ﻭ ﻳﺎ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﻭﺍﻟﺪ‪ 1‬ﻧﺪﺍﺭﺩ ﭼﺮﺍ ﻛﻪ ﺳﻴﺴﺘﻢﻋﺎﻣﻞﻫﺎﻱ ﻣﻴﻬﻤﺎﻥ ﻣﺴﺘﻘﻴﻤﺎ ﻭ ﺍﺯ ﻃﺮﻳﻖ ﺭﺍﻩﺍﻧﺪﺍﺯﻫﺎﻱ‬

‫‪ hyperviso–aware‬ﻣﻮﺟﻮﺩ ﺩﺭ ﻓﻮﻕﻧﺎﻇﺮ ﺑﺎ ﺳﺨﺖﺍﻓﺰﺍﺭ ﺩﺭ ﺍﺭﺗﺒﺎﻁ ﻫﺴﺘﻨﺪ‪ .‬ﻭ ﺍﻳﻦ ﻳﻜﻲ ﺍﺯ ﻣﺰﻳﺖ ﻫﺎﻱ ﺍﻳﻦ ﻧﻮﻉ‬

‫ﻣﻌﻤﺎﺭﻱ ﺍﺳﺖ‪ .‬ﺍﺯ ﻃﺮﻑ ﺩﻳﮕﺮ ﺍﻳﻦ ﻣﺴﺌﻠﻪ ﻛﻪ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻫﺎﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﺑﺎﻳﺴﺘﻲ ﺑﺮﺍﻱ ﺍﻳﻦ ﻓﻮﻕ ﻧﺎﻇﺮﻫﺎ‬

‫ﺗﻮﺳﻌﻪ ﺩﺍﺩﻩ ﺷﻮﻧﺪ ﻣﺸﻜﻞ ﺑﺰﺭﮔﻲ ﺧﻮﺍﻫﻨﺪ ﺑﻮﺩ‪.‬‬

‫ﭼﺮﺍ ﻛﻪ ﺍﻧﻮﺍﻉ ﻣﺨﺘﻠﻔﻲ ﺍﺯ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻫﺎ ﺍﺯ ﺳﺎﺯﻧﺪﮔﺎﻥ ﻣﺨﺘﻠﻒ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ‪ .‬ﻧﺘﻴﺠﻪ ﺍﻳﻨﻜﻪ ﺳﺎﺯﻧﺪﮔﺎﻥ ﺍﻳﻦ ﻧﻮﻉ‬

‫ﺍﺯ ﻓﻮﻕ ﻧﺎﻇﺮﻫﺎ ﺑﺎﻳﺴﺘﻲ ﺍﺭﺗﺒﺎﻁ ﺑﺴﻴﺎﺭ ﻧﺰﺩﻳﻜﻲ ﺑﺎ ﺳﺎﺯﻧﺪﮔﺎﻥ ﺳﺨﺖﺍﻓﺰﺍﺭ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ ﺗﺎ ﻧﺴﺨﻪ ‪Hypervisor-‬‬

‫‪ aware‬ﺭﺍﻩﺍﻧﺪﺍﺯﻫﺎﻱ ﺳﺨﺖﺍﻓﺰﺍﺭﻫﺎ ﺭﺍ ﺗﻬﻴﻪ ﻛﻨﻨﺪ‪ .‬ﻭ ﺍﻳﻦ ﻳﻌﻨﻲ ﺍﻳﻨﻜﻪ ﺳﺎﺯﻧﺪﮔﺎﻥ ﺍﻳﻦ ﻧﻮﻉ ﺍﺯ ﭘﻠﺘﻔﺮﻡﻫﺎ ﺑﺴﻴﺎﺭ‬

‫ﻭﺍﺑﺴﺘﻪ ﺑﻪ ﺗﻮﻟﻴﺪﻛﻨﻨﺪﮔﺎﻥ ﺳﺨﺖﺍﻓﺰﺍﺭ ﻫﺴﺘﻨﺪ‪ .‬ﻫﻤﭽﻨﻴﻦ ﺍﻳﻦ ﻣﺴﺌﻠﻪ ﺑﺎﻋﺚ ﻣﻲﺷﻮﺩ ﺗﺎ ﺍﻳﻦ ﻧﻮﻉ ﻓﻮﻕﻧﺎﻇﺮﻫﺎ‬

‫ﺩﺍﺭﺍﻱ ﻣﺤﺪﻭﺩﻳﺖ ﺑﻴﺸﺘﺮﻱ ﺑﺮﺍﻱ ﭘﺸﺘﻴﺒﺎﻧﻲ ﺍﺯ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻫﺎ ﻣﺨﺘﻠﻒ ﻣﻲﺑﺎﺷﻨﺪ‪ .‬ﻓﻮﻕﻧﺎﻇﺮ ‪ VMware ESX‬ﺍﺯ‬

‫ﺍﻳﻦ ﻣﻌﻤﺎﺭﻱ ﺑﻬﺮﻩ ﻣﻲﺑﺮﺩ‪.‬‬

‫ﻓﻮﻕ ﻧﺎﻇﺮ ﺭﻳﺰ ﻫﺴﺘﻨﺪ‬

‫ﻓﻮﻕﻧﺎﻇﺮﻫﺎﻱ ﺭﻳﺰﻫﺴﺘﻪ ﻧﻴﺎﺯﻱ ﺑﻪ ﺭﺍﻩﺍﻧﺪﺍﺯﻫﺎﻱ ﺳﺨﺖﺍﻓﺰﺍﺭﻱ ‪ Hypervisor-aware‬ﻧﺪﺍﺭﻧﺪ؛ ﭼﺮﺍ ﻛﻪ ﺩﺍﺭﺍﻱ‬

‫ﺳﻴﺴﺘﻢ ﻋﺎﻣﻠﻲ ﻫﺴﺘﻨﺪ ﻛﻪ ﺷﺒﻴﻪ ﺑﻪ ﺑﺨﺶ ﺭﻳﺸﻪ ﻳﺎ ﻭﺍﻟﺪ ﻋﻤﻞ ﻣﻲﻛﻨﺪ‪ .‬ﺑﺨﺸﻲ ﻭﺍﻟﺪ ﻣﺤﻴﻂ ﺍﺟﺮﺍﻳﻲ ﻛﻪ ﺭﺍﻩ‬

‫ﺍﻧﺪﺍﺯﻫﺎﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ﺑﺎ ﺳﺨﺖﺍﻓﺰﺍﺭﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮ ﻣﻴﺰﺑﺎﻥ ﻻﺯﻡ ﺩﺍﺭﻧﺪ ﺭﺍﻓﺮﺍﻫﻢ ﻣﻲﻛﻨﺪ‪ .‬ﺍﺻﻄﻼﺡ‬

‫"ﺑﺨﺶ‪ "2‬ﺭﺍ ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﻣﻌﺎﺩﻝ ﺑﺎ ﻣﻔﻬﻮﻡ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺑﻪ ﻛﺎﺭ ﺑﺮﻳﺪ‪.‬‬

‫ﺩﺭ ﭘﻠﺘﻔﺮﻡﻫﺎﻱ ﺑﺎ ﻓﻮﻕﻧﺎﻇﺮ ﺭﻳﺰ ﻫﺴﺘﻨﺪ‪ ،‬ﺑﺎﻳﺴﺘﻲ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻫﺎﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﺑﺮ ﺭﻭﻱ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻛﻪ ﺩﺭ‬

‫ﺣﺎﻝ ﺍﺟﺮﺍ ﺑﺮ ﺭﻭﻱ ﺑﺨﺶ ﻭﺍﻟﺪ ﺍﺳﺖ ﻧﺼﺐ ﺷﺪﻩ ﻭ ﻧﻴﺎﺯﻱ ﺑﻪ ﻧﺼﺐ ﺍﻳﻦ ﺭﺍﻩﺍﻧﺪﺍﺯﻫﺎ ﺑﺮ ﺭﻭﻱ ﺗﻚ ﺗﻚ‬

‫ﺳﻴﺴﺘﻢﻋﺎﻣﻞﻫﺎﻱ ﻣﻴﻬﻤﺎﻥ ﻧﻴﺴﺖ؛ ﭼﺮﺍ ﻛﻪ ﻫﺮ ﮔﺎﻩ ﺳﻴﺴﺘﻢﻋﺎﻣﻞﻫﺎﻱ ﻣﻴﻬﻤﺎﻥ ﻧﻴﺎﺯﻱ ﺑﻪ ﺍﺭﺗﺒﺎﻁ ﺑﺎ ﺳﺨﺖ‬

‫ﺍﻓﺰﺍﺭﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮ ﻣﻴﺰﺑﺎﻥ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ ﺍﺯ ﻃﺮﻳﻖ ﺑﺨﺶ ﻭﺍﻟﺪ ﺑﺴﺎﺩﮔﻲ ﺍﻧﺠﺎﻡ ﻣﻲﺩﻫﻨﺪ‪ .‬ﺑﻪ ﻋﺒﺎﺭﺕ ﺩﻳﮕﺮ ﺩﺭ‬

‫ﻃﺮﺍﺣﻲ ﺭﻳﺰﻫﺴﺘﻨﺪ‪ ،‬ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﻣﻴﻬﻤﺎﻥ ﺩﺳﺘﺮﺳﻲ ﻣﺴﺘﻘﻴﻤﻲ ﻧﺪﺍﺭﻧﺪ ﺑﻠﻜﻪ ﺍﺯ ﻃﺮﻳﻖ ﺑﺨﺶ ﻭﺍﻟﺪ ﺑﺎ‬

‫‪Parent 1‬‬
‫‪Partition 2‬‬

‫‪27‬‬
 ‫ﺳﺨﺖﺍﻓﺰﺍﺭ ﺍﺭﺗﺒﺎﻁ ﺑﺮﻗﺮﺍﺭ ﻣﻲﻛﻨﻨﺪ‪ .‬ﺷﻜﻞ ‪ 10-2‬ﻃﺮﺍﺣﻲ ﺭﻳﺰ ﻫﺴﺘﻪ ﺭﺍ ﻧﻤﺎﻳﺶ ﻣﻲﺩﻫﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 10 2‬ﻓﻮﻕﻧﺎﻇﺮ ﺭﻳﺰﻫﺴﺘﻪ‬

‫ﺍﺯ ﺁﻧﺠﺎﻳﻲ ﻛﻪ ﻣﻌﻤﺎﺭﻱ ﺭﻳﺰ ﻫﺴﺘﻪ ﻧﻴﺎﺯﻱ ﺑﻪ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ‪ Hypervisor-aware‬ﻧﺪﺍﺭﺩ‪ ،‬ﺗﻌﺪﺍﺩ‬

‫ﺑﺴﻴﺎﺭ ﺑﻴﺸﺘﺮﻱ ﺍﺯ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻫﺎ ﺭﺍ ﻣﻲﺗﻮﺍﻧﺪ ﺑﻜﺎﺭ ﮔﻴﺮﺩ‪ .‬ﻭ ﺍﻟﺒﺘﻪ ﺍﻳﺮﺍﺩ ﺍﻳﻦ ﻣﻌﻤﺎﺭﻱ ﻫﻢ ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﻧﻴﺎﺯ ﺑﻪ‬

‫ﺑﺨﺶ ﻭﺍﻟﺪ ﺩﺍﺭﺩ‪.‬‬

‫ﻓﻮﻕ ﻧﺎﻇﺮ ‪ Microsoft Hyper-V‬ﺍﺯ ﻣﻌﻤﺎﺭﻱ ﺭﻳﺰ ﻫﺴﺘﻨﺪ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﻛﻨﺪ ﻛﻪ ﺍﺯ ﻭﻳﻨﺪﻭﺯ ﺳﺮﻭﺭ‪2008‬‬

‫ﺑﻌﻨﻮﺍﻥ ﺑﺨﺶ ﻭﺍﻟﺪ ﺑﻬﺮﻩ ﻣﻲﺑﺮﺩ‪.‬‬

‫‪ 2-1-3-2-2‬ﭘﻴﻜﺮﺑﻨﺪﻱ ﭼﻨﺪﺳﻴﺴﺘﻢ ﺑﻄﻮﺭﻱ ﻛﻪ ﺍﺯ ﺩﻳﺪ ﺧﺎﺭﺟﻲ ﻳﻚ ﺳﻴﺴﺘﻢ ﺩﻳﺪﻩ ﺷﻮﻧﺪ‬

‫ﻧﺎﻇﺮ ﭘﺮﺩﺍﺯﺵ ﻣﻮﺍﺯﻱ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﻗﺮﺍﺭ ﻣﻲﺩﻫﺪ ﺗﺎ ﭼﻨﺪ ﺳﻴﺴﺘﻢ ﻳﻚ ﻛﺎﺭﺑﺮﺩ ﺭﺍ ﺍﺟﺮﺍ ﻛﻨﺪ )ﻫﺮ‬

‫ﺳﻴﺴﺘﻢ ﺑﺨﺸﻲ ﺍﺯ ﻛﺎﺭﺑﺮﺩ ﻣﻮﺭﺩ ﻧﻈﺮ ﺍﺟﺮﺍ ﻣﻲﻛﻨﺪ( ﺗﺎ ﺑﺘﻮﺍﻥ ﺯﻣﺎﻥ ﭘﺮﺩﺍﺯﺵ ﺭﺍ ﻛﻢ ﻛﺮﺩ‪ .‬ﺑﺪﻳﻦ ﺗﺮﺗﻴﺐ ﻛﺎﺭﺑﺮﺩ ﺑﻪ‬

‫ﭼﻨﺪﻳﻦ ﺑﺨﺶ ﺗﻘﺴﻴﻢ ﻣﻲ ﺷﻮﺩ ﻭ ﺑﻪ ﻫﺮ ﺳﻴﺴﺘﻢ ﻳﻚ ﺑﺨﺸﻲ ﺍﺯ ﺁﻥ ﺩﺍﺩﻩ ﻣﻲﺷﻮﺩ‪ .‬ﻫﺮ ﮔﺎﻩ ﺳﻴﺴﺘﻢ ﻣﺪ ﻧﻈﺮ‬

‫ﺑﺨﺶ ﻣﺤﻮﻝ ﺷﺪﻩ ﺭﺍ ﭘﺮﺩﺍﺯﺵ ﻛﻨﺪ‪ ،‬ﻧﺎﻇﺮ ﭘﺮﺩﺍﺯﺵ ﻣﻮﺍﺯﻱ‪ ،‬ﺑﺨﺶ ﺩﻳﮕﺮﻱ ﺭﺍ ﺑﺮﺍﻱ ﭘﺮﺩﺍﺯﺵ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺁﻥ‬

‫‪28‬‬
 ‫ﺳﻴﺴﺘﻢ ﻗﺮﺍﺭ ﻣﻲﺩﻫﺪ‪.‬‬

‫ﻧﺎﻇﺮﻣﺪﻳﺮﻳﺖ ﺑﺎﺭ ﻛﺎﺭﻱ )ﮔﺎﻫﻲ ﺁﻥ ﺭﺍ ﻧﺎﻇﺮ ﺗﻨﻈﻴﻢ ﺑﺎﺭ‪ 1‬ﻫﻢ ﻣﻲﺧﻮﺍﻧﻨﺪ( ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﺍﻳﺠﺎﺩ ﻣﻲﻛﻨﺪ ﺗﺎ ﭼﻨﺪ‬

‫ﻧﺴﺨﻪ ﺍﺯ ﻳﻚ ﻛﺎﺭﺑﺮﺩ ﺑﻄﻮﺭ ﻫﻤﺰﻣﺎﻥ ﺑﻪ ﺭﻭﻱ ﺗﻌﺪﺍﺩ ﺯﻳﺎﺩﻱ ﺳﻴﺴﺘﻢ ﺍﺟﺮﺍ ﺷﻮﻧﺪ‪ .‬ﻫﺮ ﮔﺎﻩ ﺩﺭﺧﻮﺍﺳﺘﻲ ﺑﺮﺍﻱ ﺁﻥ‬

‫ﻛﺎﺭﺑﺮﺩ ﻭﺟﻮﺩ ﺩﺍﺷﺖ ﻧﺎﻇﺮ ﻣﺪﻳﺮﻳﺖ ﺑﺎﺭ ﻛﺎﺭﻱ ﺩﺭﺧﻮﺍﺳﺖ ﺭﺍ ﺑﻪ ﺳﻴﺴﺘﻤﻲ ﻛﻪ ﺑﺎﺭ ﻛﺎﺭﻱ ﭘﺎﺋﻴﻦﺗﺮﻱ ﺩﺍﺭﺩ ﺍﺭﺟﺎﻉ‬

‫ﻣﻲﺩﻫﺪ‪.‬‬

‫ﻧﺎﻇﺮ ﺩﺳﺘﺮﺳﻲﻣﺴﺘﻤﺮ‪ /‬ﺑﺎﺯﮔﺸﺖ ﺍﺯ ﺧﻄﺎ‪ /‬ﺑﺎﺯﻳﺎﺑﻲ ﺳﻴﺴﺘﻢ‪ /‬ﻫﻢ ﺷﺮﺍﻳﻄﻲ ﺭﺍ ﺍﻳﺠﺎﺩ ﻣﻲﻛﻨﺪ ﺗﺎ ﺍﻓﺮﺍﺩﻱ ﻛﻪ ﺍﺯ‬

‫ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﭘﺮﺩﺍﺯﺷﻲ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﻛﻨﺪ ﺍﺯ ﺧﺮﺍﺑﻲ ﺩﺭ ﻛﺎﺭﺑﺮﺩ‪ ،‬ﺳﻴﺴﺘﻢ‪ ،‬ﻣﻮﻟﻔﻪﻫﺎﻱ ﺳﻴﺴﺘﻢ ﻣﺤﺎﻓﻈﺖ ﺷﻮﻧﺪ‪.‬‬

‫ﻧﺎﻇﺮ ﺧﺮﺍﺑﻲ ﺭﺍ ﺷﻨﺎﺳﺎﻳﻲ ﻛﺮﺩﻩ ﻭ ﻛﺎﺭﺑﺮﺩ ﺭﺍ ﺩﻭﺑﺎﺭﻩ ﺑﺮ ﺭﻭﻱ ﻳﻚ ﺳﻴﺴﺘﻢ ﺳﺎﻟﻢ ﺍﺟﺮﺍ ﻣﻲﻛﻨﺪ‪.‬‬

‫ﺩﺭ ﺣﺎﻝ ﺣﺎﺿﺮ ﺗﻌﺪﺍﺩ ﺯﻳﺎﺩﻱ ﺷﺮﻛﺖ ﺑﺰﺭگ ﭘﺸﺘﻴﺒﺎﻥ ﺍﻳﻦ ﺗﻜﻨﻮﻟﻮژﻱ ﻫﺴﺘﻨﺪ ﻭ ﺑﻪ ﺭﻭﺵﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺁﻥ ﺭﺍ‬

‫ﺍﺭﺍﺋﻪ ﻣﻲﺩﻫﻨﺪ‪ .‬ﺳﻴﺘﺮﻳﻜﺲ ﻛﻪ ﺩﺭ ﺍﻛﺜﺮ ﺯﻣﻴﻨﻪﻫﺎﻱ ﻣﺠﺎﺯﺳﺎﺯﻱ ﻭﺍﺭﺩ ﺷﺪﻩ ﺍﺳﺖ‪ xen sourse ،‬ﺭﺍ ﺍﺭﺍﺋﻪ ﺩﺍﺩﻩ‬

‫ﺍﺳﺖ‪ .‬ﺩﺭ ﺑﺨﺸﻲ ﻓﻮﻕﻧﺎﻇﺮ ﻫﻢ ‪ xen server‬ﺭﺍ ﻣﻌﺮﻓﻲﻛﺮﺩ‪ .‬ﻫﻤﭽﻨﻴﻦ ﺍﻳﻦ ﺷﺮﻛﺖ ﻧﺮﻡﺍﻓﺰﺍﺭﻫﺎﻳﻲ ﺭﺍ ﻫﻢ ﺑﺮﺍﻱ‬

‫ﻣﺪﻳﺮﻳﺖ ﺑﺎﺭ ﻛﺎﺭﻱ ﺍﺭﺍﺋﻪ ﻛﺮﺩﻩ ﺍﺳﺖ‪.‬‬

‫ﻣﺎﻳﻜﺮﻭﺳﺎﻓﺖ ﻫﻢ ﻛﻪ ﺩﺭ ﻫﻤﻪ ﺯﻣﻴﻨﻪﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ ﻭﺍﺭﺩ ﺷﺪﻩ ﺍﺳﺖ ﺩﺭ ﺳﺎﻝ ‪ Connectix 2003‬ﺭﺍ‬

‫ﺑﻜﺎﺭﮔﺮﻓﺖ ﻣﺤﺼﻮﻝ ﺷﺮﻛﺖ ﺑﻌﺪﻫﺎ ﺑﻪ ‪ hyper-V‬ﺗﻐﻴﻴﺮ ﻧﺎﻡ ﺩﺍﺩ ﻭ ﺍﻟﺒﺘﻪ ﺩﺭ ﻃﻮﻝ ﭼﻨﺪ ﺳﺎﻝ ﺑﺴﻴﺎﺭ ﭘﻴﺸﺮﻓﺖ‬

‫ﻛﺮﺩ‪ .‬ﻣﺎﻳﻜﺮﻭﺳﺎﻓﺖ ﻫﻤﭽﻨﻴﻦ ﺩﺭ ﺯﻣﻴﻨﻪﻫﺎﻱ ﭘﺮﺩﺍﺯﺵﻣﻮﺍﺯﻱ‪ ،‬ﻣﺪﻳﺮﻳﺖ ﺑﺎﺭ ﻛﺎﺭﻱ‪ ،‬ﺑﺎﺯﮔﺸﺖ ﺍﺯ ﺧﻄﺎ‪ ،‬ﺑﺎﺯﻳﺎﺑﻲ‬

‫ﺳﻴﺴﺘﻢ ﻧﻴﺰ ﺳﻴﺴﺘﻢﻫﺎ ﻭ ﻧﺮﻡﺍﻓﺰﺍﺭﻫﺎﻳﻲ ﺭﺍ ﺍﺭﺍﺋﻪ ﺩﺍﺩﻩ ﺍﺳﺖ‪.‬‬

‫‪ VMware‬ﻫﻢ ﻛﻪ ﺍﺯ ﭘﻴﺸﺘﺎﺯﻳﻦ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺍﺳﺖ ‪ ESX‬ﺭﺍ ﺑﻪ ﻋﻨﻮﺍﻥ ﻳﻚ ﻓﻮﻕﻧﺎﻇﺮ ﺍﺭﺍﺋﻪ‬

‫ﻛﺮﺩ‪.‬‬
‫‪2‬‬
‫ﺍﻳﻦ ﺷﺮﻛﺖ ﻫﻤﭽﻨﻴﻦ ﺳﻴﺴﺘﻢ ﺍﻧﺘﻘﺎﻝ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺑﻴﻦ ﺳﺮﻭﺭﻫﺎ ﺭﺍ ﺗﻮﺳﻌﻪ ﺩﺍﺩ‪VMware .‬‬

‫ﻣ ﺤﺼﻮﻻﺗﻲ ﻗﺪﺭﺗﻤﻨﺪﻱ ﺭﺍ ﻫﻢ ﺩﺭ ﺭﺍﺑﻄﻪ ﺑﺎ ﺩﺳﺘﺮﺳﻲﻣﺴﺘﻤﺮ‪ ،‬ﺑﺎﺯﮔﺸﺖ ﺍﺯ ﺧﻄﺎ ﻭ ﺑﺎﺯﻳﺎﺑﻲﺳﻴﺴﺘﻢ ﻣﻌﺮﻓﻲ ﻛﺮﺩﻩ‬

‫ﺍﺳﺖ‪.‬‬

‫‪load balancing monitors 1‬‬

‫‪Migration 2‬‬

‫‪29‬‬
 ‫‪1‬‬
‫‪ 4-2-2‬ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺷﺒﻜﻪ‬

‫ﺗﻜﻨﻮﻟﻮژﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻭ ﺳﺨﺖﺍﻓﺰﺍﺭﻱ ﻛﻪ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﺍﻳﺠﺎﺩ ﻣﻲﻛﻨﺪ ﺗﺎ ﺩﻳﺪﻱ ﺍﺯ ﺷﺒﻜﻪ ﺍﻳﺠﺎﺩ ﻛﺮﺩ ﻛﻪ ﺑﺎ‬

‫ﻭﺍﻗﻌﻴﺖ ﻭ ﺩﻳﺪ ﻓﻴﺰﻳﻜﻲ ﻣﺘﻔﺎﻭﺕ ﺑﺎﺷﺪ‪ .‬ﻣﺜﻼ ﺑﻪ ﻳﻚ ﻛﺎﻣﭙﻴﻮﺗﺮ ﺷﺨﺼﻲ ﺍﺟﺎﺯﻩ ﺩﺍﺩﻩ ﺷﻮﺩ ﺗﺎ ﺗﻨﻬﺎ‪ ،‬ﺳﻴﺴﺘﻢﻫﺎﻳﻲ ﺭﺍ‬

‫ﺑﺒﻴﻨﺪ ﻛﻪ ﺑﻪ ﺍﻭ ﺍﺟﺎﺯﻩ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ؛ ﻭ ﻳﺎ ﻣﺜﻼ ﻛﺎﺭﻱ ﻛﺮﺩ ﺗﺎ ﭼﻨﺪﻳﻦ ﻟﻴﻨﻚ ﺩﺭ ﺩﺍﺧﻞ ﺷﺒﻜﻪ ﻳﻚ ﻟﻴﻨﻚ ﺩﻳﺪﻩ‬

‫ﺷﻮﻧﺪ ﻛﻪ ﻣﺰﻳﺖ ﺁﻥ ﺑﺎﻻ ﺑﺮﺩﻥ ﻛﺎﺭﺍﻳﻲ ﻭ ﺍﻓﺰﺍﻳﺶ ﺍﻃﻤﻴﻨﺎﻥ ﺩﺭ ﺷﺒﻜﻪ ﺍﺳﺖ‪.‬‬

‫ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺷﺒﻜﻪ ﺍﺷﺎﺭﻩ ﺩﺍﺭﺩ ﺑﻪ ﺍﺑﺰﺍﺭﻱ ﻛﻪ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﻣﻲﺩﻫﺪ ﺗﺎ ﺑﺘﻮﺍﻥ ﺩﻳﺪﻱ ﺳﺎﺧﺘﮕﻲ ﻭ ﻣﺼﻨﻮﻋﻲ‬

‫ﺍﺯ ﺷﺒﻜﻪ ﺍﻳﺠﺎﺩ ﻛﺮﺩ‪ .‬ﻭ ﻳﺎ ﺑﻪ ﻋﺒﺎﺭﺕ ﻣﻲﺗﻮﺍﻥ ﺷﺒﻜﻪ ﻓﻴﺰﻳﻜﻲ ﺭﺍ ﺍﺯ ﺩﻳﺪ ﻛﺎﻣﭙﻴﻮﺗﺮ ﻭ ﺳﺮﻭﺭﻫﺎ ﻣﺨﻔﻲ ﻛﺮﺩ‪ .‬ﺍﻳﻦ‬

‫ﻣﺴﺌﻠﻪ ﺩﺭ ﺷﻜﻞ ‪ 11-2‬ﻧﺸﺎﻥ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬

‫ﺷﻜﻞ ‪ . 11 2‬ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺷﺒﻜﻪ‬

‫ﺍﺣﺘﻤﺎﻻ ﺷﻤﺎ ﻫﻢ ﻣﺘﻮﺟﻪ ﺷﺪﻩﺍﻳﺪ‪ ،‬ﺗﻘﺮﻳﺒﺎ ﺗﻤﺎﻡ ﻣﻮﺍﺭﺩﻱ ﻛﻪ ﺗﺤﺖ ﻋﻨﻮﺍﻥ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺷﺒﻜﻪ ﺷﻨﺎﺧﺘﻪ‬

‫‪Network Virtualization 1‬‬

‫‪30‬‬
‫ﻣﻲﺷﻮﻧﺪ ﻫﻤﺎﻥ ﺳﺮﻭﻳﺲ ﻫﺎ ﻭ ﺍﻣﻜﺎﻧﺎﺕ ﺭﺍﻳﺞ ﺷﺒﻜﻪ ﺍﺳﺖ‪ .‬ﻣﺜﻼ ﺳﺮﻭﻳﺲ ‪ V-LAN ، NAT‬ﻳﺎ ﻫﻤﻮﻥ ‪LAN‬‬

‫ﻣﺠﺎﺯﻱ ﻭ ﻳﺎ ﻟﻴﺴﺖﻫﺎﻱ ﺩﺳﺖﻳﺎﺑﻲ‪ 1‬ﺩﺭ ﻣﺴﻴﺮ ﻳﺎﺏﻫﺎ ﻭ ﺳﻮﺋﻴﭻﻫﺎﻱ ﻻﻳﻪ ﺳﻪ؛ ﻭ ﺑﺴﻴﺎﺭﻱ ﺩﻳﮕﺮ ﺍﺯ ﺗﻜﻨﻮﻟﻮژﻱﻫﺎﻱ‬

‫ﺷﺒﻜﻪ ﺍﺯ ﺍﻳﻦ ﺩﺳﺖ ﻫﺴﺘﻨﺪ‪.‬‬

‫ﺍﺯ ﻛﺎﺭﺑﺮﺩﻫﺎﻱ ﺗﻜﻨﻮﻟﻮژﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺷﺒﻜﻪ ﻣﻲﺗﻮﺍﻥ ﺑﻪ ﺑﺎﻻ ﺑﺮﺩﻥ ﻛﺎﺭﺍﻳﻲ ﺷﺒﻜﻪ‪ ،‬ﺑﻬﺒﻮﺩ ﻗﺎﺑﻠﻴﺖ‬

‫ﺩﺳﺘﺮﺳﻲ ﻭ ﺍﻓﺰﺍﻳﺶ ﺍﻣﻨﻴﺖ ﺷﺒﻜﻪ ﺍﺷﺎﺭﻩ ﻛﺮﺩ‪ .‬ﺍﺯ ﺁﻧﺠﺎﻳﻲ ﻛﻪ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺷﺒﻜﻪ ﺍﺭﺗﺒﺎﻁ ﭼﻨﺪﺍﻧﻲ ﺑﺎ ﻣﻮﺿﻮﻉ‬

‫ﺍﻳﻦ ﻧﻮﺷﺘﻪ ﻧﺪﺍﺭﺩ‪ ،‬ﺑﻪ ﺟﻬﺖ ﺟﻠﻮﮔﻴﺮﻱ ﺍﺯ ﺍﻃﻨﺎﺏ‪ ،‬ﺍﺯ ﺗﻮﺿﻴﺢ ﺑﻴﺸﺘﺮ ﺩﺭ ﺍﻳﻦ ﺯﻣﻴﻨﻪ ﺧﻮﺩﺩﺍﺭﻱ ﻛﺮﺩﻩ ﻭ ﺑﺎ ﻣﻌﺮﻓﻲ‬

‫ﭼﻨﺪ ﺷﺮﻛﺖ ﺑﺮﺗﺮ ﻓﻌﺎﻝ ﺩﺭ ﺍﻳﻦ ﺯﻣﻴﻨﻪ ﺑﻪ ﻣﻄﺎﻟﺐ ﺍﻳﻦ ﺑﺨﺶ ﺧﺎﺗﻤﻪ ﻣﻲﺩﻫﻴﻢ‪.‬‬

‫ﺷﺮﻛﺖ ﺳﻴﺴﻜﻮ ﻛﻪ ﻳﻜﻲ ﺍﺯ ﺑﺰﺭﮔﺘﺮﻳﻦ ﺷﺮﻛﺖ ﻫﺎﻱ ﻓﻌﺎﻝ ﺩﺭ ﺯﻣﻴﻨﻪ ﺗﺠﻬﻴﺰﺍﺕ ﺷﺒﻜﻪ ﺍﺳﺖ ﺗﻌﺪﺍﺩ ﺯﻳﺎﺩﻱ‬

‫ﺳﺮﻭﺭ ﺷﺒﻜﻪ ﻛﻪ ﺩﺭ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺷﺒﻜﻪ ﻋﻤﻞ ﻣﻲﻛﻨﻨﺪ ﺍﺭﺍﻳﻪ ﻛﺮﺩﻩ ﺍﺳﺖ‪.‬‬

‫ﺷﺮﻛﺖ ‪ HP‬ﻫﻢ ﺗﻮﺍﺑﻊ‪ 2‬ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺭﺍ ﺑﻌﻨﻮﺍﻥ ﺑﺨﺸﻲ ﺍﺯ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﺳﺮﻭﺭ ﭼﻨﺪﻣﻨﻈﻮﺭﻩ ﺧﻮﺩ ﺍﺭﺍﺋﻪ‬

‫ﻣﻲﺩﻫﺪ‪.‬‬

‫ﺷﺮﻛﺖ ‪ IBM‬ﻫﻢ ﻛﻪ ﻳﻜﻲ ﺍﺯ ﻗﺪﻳﻤﻲ ﺗﺮﻳﻦ ﺷﺮﻛﺖﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ ﺍﺳﺖ ﻧﻴﺰ ﻣﺎﻧﻨﺪ ‪ HP‬ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺭﺍ‬

‫ﺑﻌﻨﻮﺍﻥ ﺑﺨﺸﻲ ﺍﺯ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﺳﺮﻭﺭ ﭼﻨﺪ ﻣﻨﻈﻮﺭﻩ ﺧﻮﺩ ﻋﺮﺿﻪ ﻛﺮﺩﻩ ﺍﺳﺖ‪.‬‬

‫ﺷﺮﻛﺖ ‪ Junper Systems‬ﻧﻴﺰ ﺗﻌﺪﺍﺩ ﺯﻳﺎﺩﻱ ﺳﺮﻭﺭﻫﺎﻱ ﺷﺒﻜﻪ ﻛﻪ ﻛﺎﺭ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺷﺒﻜﻪ ﺍﻧﺠﺎﻡ ﻣﻲﺩﻫﻨﺪ‬

‫ﺍﺭﺍﺋﻪ ﻣﻲﻛﻨﺪ‪.‬‬

‫‪3‬‬
‫‪ 5-2-2‬ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺩﺍﺩﻩ‬

‫ﺗﻜﻨﻮﻟﻮژﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻭ ﺳﺨﺖﺍﻓﺰﺍﺭﻱ ﻛﻪ ﺑﺎﻋﺚ ﻣﻲﺷﻮﺩ ﺗﺎ ﺟﺰﺋﻴﺎﺕ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺍﺯ ﻗﺒﻴﻞ ﻣﺤﻞ‬

‫ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻭ ﻳﺎ ﺗﻜﻨﻮﻟﻮژﻱ ﺑﻜﺎﺭ ﺭﻓﺘﻪ ﺩﺭ ﺳﻴﺴﺘﻢ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺩﺍﺩﻩﻫﺎ ﺍﺯ ﻛﺎﺭﺑﺮﺩﻫﺎ ﻣﺨﻔﻲ ﺑﻤﺎﻧﺪ‪ .‬ﺍﻳﻦ‬

‫‪Access Lists 1‬‬

‫‪Functions 2‬‬
‫‪Storage Virtualization 3‬‬

‫‪31‬‬
‫ﺗﻜﻨﻮﻟﻮژﻱ ﺍﺟﺎﺯﻩ ﻣﻲﺩﻫﺪ ﺗﺎ ﺗﻌﺪﺍﺩ ﺯﻳﺎﺩﻱ ﺳﻴﺴﺘﻢ ﻳﻚ ﻭﺍﺣﺪ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺭﺍ ﺑﻴﻦ ﺧﻮﺩ ﺍﺻﻄﻼﺣﺎ ‪ share‬ﻛﻨﻨ ﺪ‬

‫ﺑﺪﻭﻥ ﺍﻳﻨﻜﻪ ﻫﺮ ﻳﻚ ﺍﺯ ﺩﻳﮕﺮﺍﻥ ﺍﻃﻼﻋﺎﺗﻲ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬

‫ﺍﻳﻦ ﺗﻜﻨﻮﻟﻮژﻱ ﻫﻤﭽﻨﻴﻦ ﺍﺟﺎﺯﻩ ﻣﻴﺪﻫﺪ ﺗﺎ ﺍﺯ ﻳﻚ ﺑﺴﺘﻪ ﺩﺭ ﺣﺎﻝ ﺍﺟﺮﺍ ﺍﺻﻄﻼﺣﺎ‪ snapshot‬ﮔﺮﻓﺘﻪ ﺷﻮﺩ ﺗﺎ‬

‫ﺑﺘﻮﺍﻥ ﺍﺯ ﺍﻳﻦ ﺳﻴﺴﺘﻢ ﻳﻚ ﻧﺴﺨﻪ ﭘﺸﺘﻴﺒﺎﻥ‪ 1‬ﺗﻬﻴﻪ ﻛﺮﺩ ﺑﺪﻭﻥ ﺍﻳﻨﻜﻪ ﺑﺮﺍﻱ ﻛﺎﺭﺑﺮﺩﻫﺎﻱ ﻭ ﺗﺮﺍﻛﻨﺸﻬﺎﻱ ﺩﺭ ﺣﺎﻝ‬

‫ﺍﺟﺮﺍ ﻣﺸﻜﻞ ﻭ ﻣﺮﺍﻗﺐ ﺍﻳﺠﺎﺩ ﺷﻮﺩ‪.‬‬

‫ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺳﻴﺴﺘﻢ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺍﻏﻠﺐ ﺗﻮﺳﻂ ﺳﺮﻭﺭﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ‪ 2‬ﭘﺸﺘﻴﺒﺎﻧﻲ ﻣﻲﺷﻮﺩ‪ .‬ﻛﻼﻳﻨﺖﻫﺎ‬

‫ﻭ ﺳﺮﻭﺭﻫﺎ ﻧﻴﺎﺯﻱ ﻧﺪﺍﺭﻧﺪ ﺑﺪﺍﻧﻨﺪ ﻓﺎﻳﻞﻫﺎﻳﻲ ﻛﻪ ﺩﺭ ﺣﺎﻝ ﭘﺮﺩﺍﺯﺵ ﺁﻧﻬﺎ ﻫﺴﺘﻨﺪ ﺩﺭ ﻛﺠﺎ ﺫﺧﻴﺮﻩ ﺷﺪﻩﺍﻧﺪ‪ .‬ﻫﻤﭽﻨﻴﻦ‬

‫ﻧﻴﺎﺯﻱ ﻫﻢ ﻧﺪﺍﺭﻧﺪ ﺗﺎ ﺑﺪﺍﻧﻨﺪ ﭼﻪ ﻧﻮﻉ ﺍﺯ ﺫﺧﻴﺮﻩﺳﺎﺯﻫﺎ‪ ،‬ﺩﺍﺩﻩﻫﺎ ﻭ ﻛﺎﺭﺑﺮﺩﻫﺎ ﺭﺍ ﺫﺧﻴﺮﻩ ﻛﺮﺩﻩﺍﻧﺪ‪ .‬ﻣﺜﻼ ﺩﺳﺘﮕﺎﻩﻫﺎﻱ‬

‫ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻣﻲﺗﻮﺍﻧﻨﺪ ﺩﻳﺴﻚ ﺳﺨﺖ ﺑﺎﺷﻨﺪ ﻳﺎ ‪ SSD‬ﻭ ﻳﺎ ﻫﺮ ﺗﻜﻨﻮﻟﻮژﻱ ﺩﻳﮕﺮ‪.‬‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺷﻜﻞ ‪ 12-2‬ﻧﺸﺎﻥ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪ ،‬ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻳﻚ ﺩﻳﺪ ﻣﺼﻨﻮﻋﻲ ﺍﺯ‬

‫ﺷﺒﻜﻪ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺍﻳﺠﺎﺩ ﻣﻲﻛﻨﺪ ﻛﻪ ﺟﺰﺋﻴﺎﺕ ﺷﺒﻜﻪ ﻓﻴﺰﻳﻜﻲ ﺭﺍ ﺍﺯ ﻛﻼﻳﻨﺖﻫﺎ ﻭ ﺳﺮﻭﺭﻫﺎ ﻣﺨﻔﻲ ﻣﻲﻛﻨﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 12 2‬ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺩﺭ ﺳﻴﺴﺘﻢﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ‬

‫‪Back Up 1‬‬
‫‪Storage Server 2‬‬

‫‪32‬‬
 ‫ﺍﻳﻦ ﺳﻴﺴﺘﻢ ﺗﻮﺍﺑﻊ ﺯﻳﺮ ﺭﺍ ﻓﺮﺍﻫﻢ ﻣﻲﻛﻨﺪ‪:‬‬
‫‪1‬‬
‫‪ -‬ﺍﻳﺠﺎﺩ ﺳﻴﺴﺘﻢ ﻓﺎﻳﻞ ﺗﻮﺯﻳﻊ ﺷﺪﻩ‬

‫ﺳﻴﺴﺘﻢ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺭﺍﻩ ﺩﻭﺭ ﻃﻮﺭﻱ ﺳﺎﺧﺘﻪ ﺷﺪﻩ ﻛﻪ ﺍﺯ ﺩﻳﺪ ﻛﻼﻳﻨﺖ ﺑﻪ ﻧﻈﺮ ﺑﺮﺳﺪ ﻭﺳﻴﻠﻪ ﺫﺧﻴﺮﻩﺳﺎﺯ‬

‫ﻣﺴﺘﻘﻴﻤﺎ ﺑﻪ ﻛﺎﻣﭙﻴﻮﺗﺮ ﻣﺘﺼﻞ ﺍﺳﺖ‪.‬‬

‫‪ -‬ﺍﻳﺠﺎﺩ ﺩﺭﺍﻳﻮﻫﺎﻱ ﺑﺎ ﺍﻧﺪﺍﺯﻩ ﻏﻴﺮﻭﺍﻗﻌﻲ ﻭ ﺩﻟﺨﻮﺍﻩ‬

‫ﺩﺭ ﺍﻳﻦ ﺳﻴﺴﺘﻢ ﻣﻲﺗﻮﺍﻥ ﭼﻨﺪﻳﻦ ﺍﺑﺰﺍﺭ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺭﺍ ﺑﻪ ﻳﻜﺪﻳﮕﺮ ﻣﺘﺼﻞ ﻛﺮﺩﻩ ﺗﺎ ﺍﺯ ﺩﻳﺪ ﺧﺎﺭﺟﻲ ﻃﻮﺭﻱ ﺑﻪ‬

‫ﻧﻈﺮ ﺑﺮﺳﺪ ﻛﻪ ﻳﻚ ﻭﺍﺣﺪ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺍﺳﺖ‪.‬‬

‫‪ -‬ﺍﻳﺠﺎﺩ ﺁﺭﺍﻳﻪ ﻫﺎﻱ ﺍﺯ ﺍﺑﺰﺍﺭﻫﺎﻱ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ‬

‫ﺩﺍﺩﻩ ﻫﺎ ﻭ ﻛﺎﺭﺑﺮﺩﻫﺎ ﻣﻲﺗﻮﺍﻧﻨﺪ ﺑﺮ ﺭﻭﻱ ﭼﻨﺪﻳﻦ ﻭﺍﺣﺪ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺗﻮﺯﻳﻊ ﺷﻮﻧﺪ ﺗﺎ ﺑﺪﻳﻦﻃﺮﻳﻖ ﻛﺎﺭﺍﻳﻲ‬

‫ﺳﻴﺴﺘﻢ ﺍﻓﺰﺍﻳﺶ ﭘﻴﺪﺍ ﻛﻨﻨﺪ‪ .‬ﺍﻳﻦ ﺳﻴﺴﺘﻢ ﻫﻤﭽﻨﻴﻦ ﻣﻲ÷ﺗﻮﺍﻧﺪ ﻗﺎﺑﻠﻴﺖ ﺍﻃﻤﻴﻨﺎﻥ ﺳﻴﺴﺘﻢ ﺭﺍ ﻫﻢ ﺍﻓﺰﺍﻳﺶ ﺩﻫﺪ؛‬

‫ﺑﺪﻳﻦ ﺻﻮﺭﺕ ﻛﻪ ﻳﻚ ﺩﺍﺩﻩ ﻭﺍﺣﺪ ﺑﺮ ﺭﻭﻱ ﭼﻨﺪﻳﻦ ﻭﺍﺣﺪ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻭ ﻳﺎ ﺳﺮﻭﺭ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻗﺮﺍﺭ ﻣﻲﮔﻴﺮﺩ ‪.‬‬

‫ﺍﮔﺮ ﻳﻜﻲ ﺍﺯ ﻭﺍﺣﺪﻫﺎ ﺧﺮﺍﺏ ﺷﻮﺩ ﺩﺍﺩﻩﻫﺎ ﺍﺯ ﻭﺍﺣﺪ ﺩﻳﮕﺮ ﻗﺎﺑﻞ ﺑﺎﺯﻳﺎﺑﻲ ﺍﺳﺖ‪.‬‬

‫‪ -‬ﺍﻣﻜﺎﻥ ﻣﺪﻳﺮﻳﺖ ﺑﻴﺸﺘﺮ ﺑﺮ ﻓﻀﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ‬

‫ﺍﺑﺰﺍﺭﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻣﻲﺗﻮﺍﻧﻨﺪ ﺑﻪ ﭼﻨﺪ ﻓﺎﻳﻞﺳﻴﺴﺘﻢ ﺑﺨﺶﺑﻨﺪﻱ ﺷﻮﻧﺪ ﺗﺎ ﺑﺘﻮﺍﻥ ﺍﺯ ﺍﺑﺰﺍﺭﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ‬

‫ﺑﻬﺘﺮ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ‪.‬‬

‫‪ -‬ﺍﻳﺠﺎﺩ ﺳﺎﺯﻭﻛﺎﺭﻱ ﺑﺮﺍﻱ ‪ Share‬ﻛﺮﺩﻥ ﻳﻚ ﺍﺑﺰﺍﺭ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ﺑﻴﻦ ﭼﻨﺪ ﺳﻴﺴﺘﻢ ﻧﺎﺳﺎﺯﮔﺎﺭ‬

‫ﻣﻴﻨﻔﺮﻳﻢﻫﺎ‪ ،‬ﻟﻴﻨﻮﻛﺲ‪ ،‬ﻳﻮﻧﻴﻜﺲ‪ ،‬ﻭﻳﻨﺪﻭﺯ ﻭ ﺩﻳﮕﺮ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞﻫﺎ ﻫﺮ ﻳﻚ ﺍﺯ ﻣﻜﺎﻧﻴﺴﻢ ﻣﺘﻔﺎﻭﺗﻲ ﺑﺮﺍﻱ‬

‫ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻭ ﺑﺎﺯﻳﺎﺑﻲ ﺩﺍﺩﻩﻫﺎ ﻭﻛﺎﺭﺑﺮﺩﻫﺎ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﻛﻨﻨﺪ‪ .‬ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﻭ ﻓﺮﺍﻫﻢ‬

‫ﻣﻲﻛﻨﺪ ﺗﺎ ﻫﻤﻪ ﺍﻳﻦ ﺳﻴﺴﺘﻢﻋﺎﻣﻞﻫﺎ ﻳﻚ ﻭﺍﺣﺪ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻭ ﻓﺎﻳﻞﻫﺎﻱ ﺁﻥ ﺭﺍ ﺑﻴﻦ ﺧﻮﺩ ‪ share‬ﻛﻨﻨﺪ‪.‬‬

‫ﺳﺮﻭﺭﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺗﻌﺪﺍﺩ ﺯﻳﺎﺩﻱ ﺩﺳﺘﮕﺎﻩ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺭﺍ ﻣﺪﻳﺮﻳﺖ ﻣﻲﻛﻨﻨﺪ ﻭ ﺍﻳﻦ ﺳﻴﺴﺘﻢ ﺍﺟﺎﺯﻩ‬

‫‪Distributed 1‬‬

‫‪33‬‬
‫ﻣﻲﺩﻫﺪ ﺗﻌﺪﺍﺩ ﺯﻳﺎﺩﻱ ﺳﻴﺴﺘﻢ ﻫﻤﻪ ﻣﻨﻈﻮﺭﻩ‪ 1‬ﺑﻪ ﻳﻚ ﺫﺧﻴﺮﻩ ﺳﺎﺯ ﺩﺳﺘﺮﺳﻲ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ‪ .‬ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﺳﺮﻭﺭ‬

‫ﺫﺧﻴﺮﻩﺳﺎﺯﻱ‪ ،‬ﺍﻃﻼﻋﺎﺗﻲ ﺩﺍﺭﺩ ﻛﻪ ﻣﻲ ﺩﺍﻧﺪ ﻛﺪﺍﻡ ﺳﺮﻭﺭ ﻫﻤﻪ ﻣﻨﻈﻮﺭﻩ‪ ،‬ﺑﻪ ﻛﺪﺍﻡ ﻭﺍﺣﺪ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻭ ﻛﺪﺍﻡ‬

‫ﻓﺎﻳﻞﺳﻴﺴﺘﻢ ﺍﺟﺎﺯﻩ ﺩﺳﺘﺮﺳﻲ ﺩﺍﺭﺩ‪ .‬ﺍﮔﺮ ﺍﻳﻦ ﺳﺮﻭﺭ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ‪ ،‬ﺍﺯ ﻃﺮﻳﻖ ﻳﻚ ﺷﺒﻜﻪ ﺫﺧﻴﺮﻩ ﺩﺍﺩﻩ‬

‫ﺧﺎﺹﻣﻨﻈﻮﺭﻩ ﺑﻪ ﻳﻚ ﺳﻴﺴﺘﻢ ﻫﻤﻪﻣﻨﻈﻮﺭﻩ ﻣﺘﺼﻞ ﺑﺎﺷﺪ‪ ،‬ﺍﻳﻦ ﭘﻴﻜﺮﺑﻨﺪﻱ ﺭﺍ ﺷﺒﻜﻪ ﻧﺎﺣﻴﻪ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ‪ 2‬ﻭ ﻳﺎ ﺑﻪ‬

‫ﺍﺧﺘﺼﺎﺭ‪ SAN‬ﻣﻲﮔﻮﻳﻨﺪ‪ .‬ﺍﺑﺰﺍﺭﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻛﻪ ﺍﺯ ﻃﺮﻳﻖ ﺷﺒﻜﻪ ﺩﺳﺘﻴﺎﺑﻲ ﻣﻲﺷﻮﺩ ﺭﺍ ﺫﺧﻴﺮﻩﺳﺎﺯ ﺿﻤﻴﻤﻪ ﺑﻪ‬

‫ﺷﺒﻜﻪ‪ 3‬ﻭ ﻳﺎ ﺑﻪ ﺍﺧﺘﺼﺎﺭ ‪ NAS‬ﻣﻲﮔﻮﻳﻨﺪ؛ ﺧﻮﺍﻩ ﺩﺭ ﻳﻚ ﺷﺒﻜﻪ ‪ SAN‬ﺑﺎﺷﺪ‪ ،‬ﺧﻮﺍﻩ ﻳﻚ ﺷﺒﻜﻪ ‪ LAN‬ﻛﻪ ﺗﻮﺳﻂ‬

‫ﻳﻚ ﺳﻴﺴﺘﻢ ﻫﻤﻪ ﻣﻨﻈﻮﺭﻩ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﺷﻮﺩ‪.‬‬

‫ﺍﮔﺮ ﭼﻪ ﺷﺮﻛﺖ ﻫﺎﻱ ﺯﻳﺎﺩﻱ ﺩﺭ ﺯﻣﻴﻨﻪ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻓﻌﺎﻝ ﻫﺴﺘﻨﺪ‪ ،‬ﺩﺭ ﺯﻳﺮ ﭼﻨﺪ ﻣﻮﺭﺩ ﺍﺯ‬

‫ﻣﻬﻤﺘﺮﻳﻦ ﺑﺎﺯﻳﮕﺮﺍﻥ ﺍﻳﻦ ﻋﺮﺻﻪ ﺭﺍ ﺫﻛﺮ ﻣﻲﻛﻨﻢ ‪.‬‬

‫‪ EMC‬ﻛﺎﺭ ﺧﻮﺩ ﺭﺍ ﺑﺎ ﺳﺎﺧﺖ ﺩﺳﺘﮕﺎﻩﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻣﻴﻨﻔﺮﻳﻢﻫﺎ ﻭ ﻛﺎﻣﭙﻴﻮﺗﺮﻫﺎﻱ ﺷﺨﺼﻲ ﺁﻏﺎﺯ ﻛﺮﺩ ﻭﻟﻲ‬

‫ﺑﺎ ﮔﺬﺷﺖ ﺯﻣﺎﻥ ﺷﺮﻛﺖ ﺑﻪ ﺑﺎﺯﺍﺭ ﺳﺮﻭﺭﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺩﺍﺩﻩ ﻫﻢ ﻭﺍﺭﺩ ﺷﺪ ﻭ ﺩﺭ ﺣﺎﻝ ﺣﺎﺿﺮ ﺍﻧﻮﺍﻉ ﺳﻴﺴﺘﻢﻫﺎﻱ‬

‫ﺭﺍ ﺗﻮﻟﻴﺪ ﻣﻲﻛﻨﺪ‪.‬‬

‫‪4‬‬
‫‪ Hitachi‬ﺍﻧﻮﺍﻉ ﺍﺑﺰﺍﺭﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻭ ﺳﺮﻭﺭﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺭﺍ ﺑﺮﺍﻱ ﻣﻴﻨﻔﺮﻳﻢﻫﺎ‪ ،‬ﺳﻴﺴﺘﻢﻫﺎﻱ ﻣﺘﻮﺳﻂ‬

‫ﻭ ﺳﻴﺴﺘﻢﻫﺎﻱ ﺻﻨﻌﺘﻲ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﺗﻮﻟﻴﺪ ﻣﻲﻛﻨﻨﺪ‪.‬‬

‫‪ HP‬ﺳﺮﻭﺭﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺧﻮﺩﺭﺍ ﺑﺮﺍﻱ ﭘﺸﺘﻴﺒﺎﻧﻲ ﺍﺯ ﺳﻴﺴﺘﻢﻫﺎﻱ ﻣﺘﻮﺳﻂ ﻭ ﺳﻴﺴﺘﻢﻫﺎﻱ ﺻﻨﻌﺘﻲ ﺧﻮﺩ‬

‫ﺍﺭﺍﻳﻪ ﻣﻲﻛﻨﺪ‪.‬‬

‫‪ IBM‬ﺍﻧﻮﺍﻉ ﻣﻴﻨﻔﺮﻳﻢﻫﺎ‪ ،‬ﺳﻴﺴﺘﻢﻫﺎﻱ ﻣﺘﻮﺳﻂ ﻭ ﺻﻨﻌﺘﻲ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﺧﻮﺩ ﺭﺍ ﺭﺍﻫﻲ ﺑﺎﺯﺍﺭﻛﺮﺩﻩ‪ .‬ﺷﺮﻛﺖ‬

‫ﻫﻤﭽﻨﻴﻦ ﺳﺮﻭﺭﻫﺎﻱ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ﻛﻪ ﺗﻤﺎﻡ ﻧﻴﺎﺯﻫﺎﻱ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺧﻮﺩ ﺭﺍ ﺗﺎﻣﻴﻦ ﻣﻲﻛﻨﺪ ﻧﻴﺰ ﺗﻮﻟﻴﺪ ﻣﻲﻧﻤﺎﻳﺪ‪.‬‬

‫‪Multi Purpose 1‬‬

‫‪Storage Area Network 2‬‬
‫‪Network Attached Storage 3‬‬
‫‪midrange systems 4‬‬

‫‪34‬‬
 ‫‪ 6-2-2‬ﺍﻣﻨﻴﺖ ﺩﺭ ﺳﻴﺴﺘﻢﻫﺎﻱ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ‬

‫ﺗﻜﻨﻮﻟﻮژﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻛﻪ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺍﺟﺰﺍﻱ ﻣﺨﺘﻠﻒ ﺩﺭ ﻣﺤﻴﻂ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺭﺍ ﻛﻨﺘﺮﻝ ﻛﺮﺩﻩ ﻭ ﺍﺯ‬

‫ﺩﺳﺘﺮﺳﻲ ﻏﻴﺮﻣﺠﺎﺯ ﻭ ﺧﺮﺍﺑﻜﺎﺭﺍﻧﻪ ﺟﻠﻮﮔﻴﺮﻱ ﻣﻲﻛﻨﺪ‪.‬‬

‫ﺍﻣﻨﻴﺖ ﻣﺤﻴﻂ ﻣﺠﺎﺯﻱ ﺍﺷﺎﺭﻩ ﺑﻪ ﺍﺑﺰﺍﺭﻱ ﺩﺍﺭﺩ ﻛﻪ ﺑﺮﺍﻱ ﻛﻨﺘﺮﻝ ﺩﺳﺘﻴﺎﺑﻲ ﺑﻪ ﻻﻳﻪﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺗﻜﻨﻮﻟﻮژﻱ‬

‫ﻣﺠﺎﺯﻱ ﻻﺯﻡ ﺍﺳﺖ‪ .‬ﻧﻈﺮ ﺑﻪ ﺍﻳﻨﻜﻪ ﺍﻣﻨﻴﺖ‪ ،‬ﻣﻮﺿﻮﻉ ﺍﻳﻦ ﻧﻮﺷﺘﻪ ﻧﻴﺴﺖ ﺍﺯ ﺗﻮﺿﻴﺢ ﺑﻴﺸﺘﺮ ﺭﺍﺟﻊ ﺑﻪ ﺍﻣﻨﻴﺖ‬

‫ﺧﻮﺩﺩﺍﺭﻱ ﻣﻲﻛﻨﻴﻢ‪.‬‬

‫‪ 7-2-2‬ﻣﺪﻳﺮﻳﺖ ﻣﺤﻴﻂ ﻣﺠﺎﺯﻱ‬

‫ﺗﻜﻨﻮﻟﻮژﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻛﻪ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﻭ ﻓﺮﺍﻫﻢ ﻣﻲﺁﻭﺭﺩ ﻛﻪ ﭼﻨﺪﻳﻦ ﺳﻴﺴﺘﻢ ﻣﺠﺎﺯﻱ ﺭﺍ ﻣﺎﻧﻨﺪ ﻳﻚ ﺳﻴﺴﺘﻢ‬

‫ﻛﺎﻣﭙﻴﻮﺗﺮﻱ ﻣﻨﻔﺮﺩ ﻣﺪﻳﺮﻳﺖ ﻛﺮﺩ‪.‬‬

‫ﻣﺪﻳﺮﻳﺖ ﻣﺤﻴﻂ ﻣﺠﺎﺯﻱ ﺍﺷﺎﺭﻩ ﺑﻪ ﺍﺑﺰﺍﺭﻱ ﺩﺍﺭﺩ ﻛﻪ ﺑﻪ ﻛﻤﻚ ﺁﻥ ﻣﻲﺗﻮﺍﻥ ﻣﺤﻴﻂ ﻣﺠﺎﺯﻱ ﺭﺍ ﺍﻳﺠﺎﺩ‪ ،‬ﻣﺸﺎﻫﺪﻩ ﻭ‬

‫ﺁﻧﺎﻟﻴﺰ ‪ ،‬ﻛﻨﺘﺮﻝ ﺧﻮﺩﻛﺎﺭ ﻭ ﺑﻬﻴﻨﻪﺳﺎﺯﻱ ﻛﺮﺩ‪ .‬ﻫﺮ ﭼﻪ ﻣﺤﻴﻂ ﻣﺠﺎﺯﻱ ﭘﻴﭽﻴﺪﻩﺗﺮ ﺷﻮﺩ ﺍﻫﻤﻴﺖ ﺍﻳﻦ ﺑﺨﺶ ﻧﻴﺰ‬

‫ﺑﻴﺸﺘﺮ ﻣﻲﺷﻮﺩ‪.‬‬

‫ﺳﻴﺴﺘﻢ ﻣﺪﻳﺮﻳﺖ ﻣﺤﻴﻂ ﻣﺠﺎﺯﻱ ﺑﺎﻳﺴﺘﻲ ﺗﻮﺍﺑﻊ ﻭ ﻋﻤﻠﻜﺮﺩﻫﺎﻱ ﺯﻳﺮ ﺭﺍ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪:‬‬

‫ﺍﻳﺠﺎﺩ ﻣﺤﻴﻂ ﻣﺠﺎﺯﻱ ﻭﻣﻮﻟﻔﻪﻫﺎﻱ ﺁﻥ‬ ‫‪-‬‬

‫ﻧﻈﺎﺭﺕ ﺑﺮ ﻣﺤﻴﻂ ﻣﺠﺎﺯﻱ‬ ‫‪-‬‬

‫ﻛﻨﺘﺮﻝ ﻣﺤﻴﻂ ﻣﺠﺎﺯﻱ ﻭ ﻣﻮﻟﻔﻪ ﻫﺎ ﺁﻥ‬ ‫‪-‬‬

‫ﺁﻧﺎﻟﻴﺰ ﻭﻗﺎﻳﻊ ﺛﺒﺖ ﺷﺪﻩ ﺟﻬﺖ ﻳﺎﻓﺘﻦ ﻣﺸﻜﻼﺕ ﭘﻴﻜﺮﺑﻨﺪﻱ ‪ ،‬ﻛﺎﺭﺍﻳﻲ ﻭ ﻋﻤﻠﻜﺮﺩﻱ‬ ‫‪-‬‬

‫ﺑﻬﻴﻨﻪﺳﺎﺯﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻣﺤﻴﻂ ﻣﺠﺎﺯﻱ ﻭ ﻣﻮﻟﻔﻪﻫﺎ ﺁﻥ‬ ‫‪-‬‬

‫ﺧﻮﺩ ﻛﺎﺭﺳﺎﺯﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻣﺤﻴﻂ ﻣﺠﺎﺯﻱ ﻭﻣﻮﻟﻔﻪﻫﺎﻱ ﺁﻥ‬ ‫‪-‬‬

‫ﺷﺮﻛﺖ ﻫﺎﻱ ﺯﻳﺎﺩﻱ ﺩﺭ ﺯﻣﻴﻨﻪ ﻣﺪﻳﺮﻳﺖ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﻓﻌﺎﻝ ﻫﺴﺘﻨﺪ ﻛﻪ ﺍﺯ ﺁﻥ ﺟﻤﻠﻪ ﻣﻲﺗﻮﺍﻥ‬

‫‪35‬‬
 ‫ﺑﻪ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺍﺷﺎﺭﻩ ﻛﺮﺩ‪:‬‬

‫ﺷﺮﻛﺖ ‪ CA‬ﻛﻪ ﺩﺭ ﺍﻳﻦ ﺯﻣﻴﻨﻪ ﻳﻜﻲ ﺍﺯ ﻗﺪﻳﻤﻲ ﺗﺮﻳﻦﻫﺎ ﺍﺳﺖ‪.‬‬

‫ﺷﺮﻛﺖ ‪ HP‬ﻛﻪ ﻣﺤﺼﻮﻻﺕ ﺧﻮﺩ ﺭﺍ ﺩﺭ ﺍﻳﻦ ﺯﻣﻴﻨﻪ ﺳﺎﻟﻬﺎﻱ ﺯﻳﺎﺩﻱ ﺍﺳﺖ ﻛﻪ ﺍﺭﺍﺋﻪ ﻛﺮﺩﻩ‪.‬‬

‫‪ IBM Tivoli‬ﻫﻢ ﺳﺎﺑﻘﻪ ﻃﻮﻻﻧﻲ ﺩﺭ ﺯﻣﻴﻨﻪ ﻧﺮﻡﺍﻓﺰﺍﺭﻫﺎﻱ ﻣﺪﻳﺮﻳﺖ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺩﺍﺭﺩ ‪.‬‬

‫ﻭ ﺍﻟﺒﺘﻪ ﻣﺎﻳﻜﺮﻭﺳﺎﻓﺖ ﻭ ‪ VMware‬ﻫﻢ ﻣﺤﺼﻮﻻﺗﻲ ﺑﺮﺍﻱ ﻣﺪﻳﺮﻳﺖ ﺳﻴﺴﺘﻢﻫﺎﻱ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺧﻮﺩ ﺍﺭﺍﺋﻪ‬

‫ﻛﺮﺩﻩﺍﻧﺪ‪.‬‬

‫‪ 3-2‬ﭼﻨﺪ ﺍﺻﻄﻼﺡ – ﭼﻨﺪ ﺍﺷﺘﺒﺎﻩ‬

‫ﺑﺴﻴﺎﺭﻱ ﺍﻭﻗﺎﺕ ﻳﻚ ﺗﻜﻨﻮﻟﻮژﻱ ﺑﺎ ﻣﻮﺍﺭﺩ ﺍﺳﺘﻔﺎﺩﻩﻫﺎﻱ ﻣﻮﺭﺩﻱ ﺍﺯ ﺁﻥ ﺗﻜﻨﻮﻟﻮژﻱ ﺍﺷﺘﺒﺎﻩ ﮔﺮﻓﺘﻪ ﻣﻲﺷﻮﺩ‪ .‬ﻣﺜﻼ‬

‫ﺩﺭ ﺑﺤﺚ ﻣﺠﺎﺯﻱ ﺳ ﺎﺯﻱ ﻭﻗﺘﻲ ﺩﺭ ﻣﻮﺭﺩ ﺗﻜﻨﻮﻟﻮژﻱ ﻣﺎﺷﻴﻦﻣﺠﺎﺯﻱ ﻛﻪ ﻳﻜﻲ ﺍﺯ ﻣﻮﺍﺭﺩ ﭘﻨﺞﮔﺎﻧﻪ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ‬
‫‪2‬‬
‫ﭘﺮﺩﺍﺯﺵ ﺑﺤﺚ ﻣﻲﺷﻮﺩ‪ ،‬ﺑﺴﻴﺎﺭﻱ ﺍﻓﺮﺍﺩ )ﺣﺘﻲ ﻣﺘﺨﺼﺼﻴﻦ( ﺑﺎ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺳﺮﻭﺭ‪ 1‬ﻭ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺩﺳﻜﺘﺎپ‬

‫ﺍﺷﺘﺒﺎﻩ ﻣﻲﮔﻴﺮﻧﺪ‪ .‬ﺩﺭ ﺍﻳﻦ ﺑﺨﺶ ﺳﻌﻲ ﻣﻲﻛﻨﻴﻢ ﭼﻨﺪ ﻭﺍژﻩ ﻣﻌﻤﻮﻝ ﺩﺭ ﺑﺤﺚ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺭﺍ ﺗﻌﺮﻳﻒ ﻛﺮﺩﻩ ﻭ‬

‫ﻣﻮﺍﺩ ﺍﺷﺘﺒﺎﻩ ﺭﺍ ﺑﺮﻃﺮﻑ ﻛﻨﻴﻢ‪.‬‬

‫‪3‬‬
‫‪ 1-3-2‬ﻛﻼﺳﺘﺮ‬

‫ﺗﻜﻨﻮﻟﻮژﻱ ﻣﺘﻔﺎﻭﺗﻲ ﻭﺟﻮﺩ ﺩﺍﺭﻧﺪ ﻛﻪ ﺍﺯ ﻗﺪﺭﺕ ﭘﺮﺩﺍﺯﺵ ﭼﻨﺪﺳﻴﺴﺘﻢ ﺗﺤﺖ ﻣﺪﻳﺮﻳﺖ ﻳﻚ ﺳﻴﺴﺘﻢ ﺑﻬﺮﻩ‬

‫ﻣﻲﮔﻴﺮﻧﺪ‪ .‬ﺍﮔﺮ ﭼﻪ ﺗﻜﻨﻮﻟﻮژﻱﻫﺎﻱ ﻫﻤﻪ ﺁﻧﻬﺎ ﺑﻪ ﻋﻨﻮﺍﻥ ﻛﻼﺳﺘﺮ ﺷﻨﺎﺧﺘﻪ ﻣﻲﺷﻮﻧﺪ‪ .‬ﺩﺭ ﺍﺩﺍﻣﻪ ﻳﻚ ﺗﻌﺮﻳﻒ ﺟﺎﻣﻊ ﺍﺯ‬

‫ﻛﻼﺳﺘﻪ ﺍﺭﺍﺋﻪ ﻣﻲ ﺩﻫﻴﻢ‪.‬‬

‫‪Server Virtualization0 1‬‬

‫‪Desktop Virtualizatin 2‬‬
‫‪Cluster 3‬‬

‫‪36‬‬
‫ﻳﻚ ﻛﻼﺳﺘﺮ‪ ،‬ﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ﻛﺎﻣﭙﻴﻮﺗﺮﻫﺎﻱ ﺟﺪﺍ ﺍﺯ ﻫﻢ ﺍﺳﺖ )ﻣﻌﻤﻮﻻً ﻳﻜﺴﺎﻥ ﻳﺎ ﻣﺸﺎﺑﻪ ﺑﻪ ﻟﺤﺎﻅ ﻣﻌﻤﺎﺭﻱ‬

‫ﺳﺨﺖﺍﻓﺰﺍﺭﻱ ﻭ ﻇﺮﻓﻴﺖ ﻣﺤﺎﺳﺒﺎﺗﻲ( ﻛﻪ ﺍﺯ ﻃﺮﻳﻖ ﺷﺒﻜﻪ ﺍﺗﺼﺎﻟﻲ ﺑﺴﻴﺎﺭ ﭘﺮﺳﺮﻋﺖ ﺑﻪ ﻳﻜﺪﻳﮕﺮ ﻣﺘﺼﻞ ﺷﺪﻩﺍﻧﺪ‪.‬‬

‫ﺷﻜﻞ ‪ 13-2‬ﺗﺼﻮﻳﺮﻱ ﺍﺯ ﻳﻚ ﻛﻼﺳﺘﺮ ﺑﻪ ﺩﺳﺖ ﻣﻲﺩﻫﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 13 2‬ﻛﻼﺳﺘﺮ‬

‫ﻋﻤﻠﻜﺮﺩ ﻳﻚ ﻛﻼﺳﺘﺮ ﺭﺍ ﻣﻲ ﺗﻮﺍﻥ ﺑﺴﻴﺎﺭ ﻣﺸﺎﺑﻪ ﺑﺎ ﻳﻚ ﻣﺎﻟﺘﻲﭘﺮﻭﺳﺴﻮﺭ ﺩﺍﻧﺴﺖ ﺑﺎ ﺍﻳﻦ ﺗﻔﺎﻭﺕ ﻛﻪ ﻳﻚ ﻛﻼﺳﺘﺮ‬

‫ﻣﺰﺍﻳﺎﻱ ﺯﻳﺎﺩﻱ ﺩﺭ ﻣﻘﺎﻳﺴﻪ ﺑﺎ ﺍﺑﺮﺭﺍﻳﺎﻧﻪﻫﺎﻱ ﺳﻨﺘﻲ )ﻣﺎﻟﺘﻲﭘﺮﻭﺳﺴﻮﺭﻫﺎﻳﻲ ﻛﻪ ﺗﺎ ﺍﻭﺍﺧﺮ ‪ 1990‬ﺳﺎﺧﺘﻪ ﻣﻲﺷﺪﻧﺪ(‬

‫ﺩﺍﺭﺩ‪ .‬ﻫﺰﻳﻨﻪ ﺗﻬﻴﻪ ﻳﻚ ﻛﻼﺳﺘﺮ ﺑﺴﻴﺎﺭ ﻛﻤﺘﺮ ﺍﺯ ﻳﻚ ﺍﺑﺮ ﺭﺍﻳﺎﻧﻪ ﺳﻨﺘﻲ ﺑﺎ ﺗﻮﺍﻥ ﭘﺮﺩﺍﺯﺷﻲ ﻣﺸﺎﺑﻪ ﺍﺳﺖ‪.‬‬

‫ﺍﺑﺮﺭﺍﻳﺎﻧﻪﻫﺎﻱ ﺳﻨﺘﻲ‪ ،‬ﻣﻌﻤﻮﻻً ﻣﻌﻤﺎﺭﻱ ﻏﻴﺮﻣﺘﻐﻴﺮ‪ 1‬ﻭ ‪ Hard-Wired‬ﺩﺍﺷﺘﻨﺪ‪ ،‬ﺑﻨﺎﺑﺮﺍﻳﻦ ﻣﻌﻤﻮﻻً ﻣﻘﻴﺎﺳﭘﺬﻳﺮ‬

‫ﻧﺒﻮﺩﻧﺪ‪ ،‬ﺩﺭ ﺻﻮﺭﺗﻲ ﻛﻪ ﺍﻓﺰﻭﺩﻥ ﺑﻪ ﺗﻮﺍﻥ ﻣﺤﺎﺳﺒﺎﺗﻲ ﻳﻚ ﻛﻼﺳﺘﺮ ﺳﺎﺩﻩﺗﺮ ﺍﺳﺖ‪ .‬ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ ﺭﺷﺪ ﻗﺪﺭﺕ‬

‫ﭘﺮﺩﺍﺯﻧﺪﻩﻫﺎ ﻭ ﭘﻴﺪﺍﻳﺶ ﺷﺒﻜﻪﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ ﺳﺮﻳﻊ‪ ،‬ﺍﻛﺜﺮ ﺍﺑﺮﺭﺍﻳﺎﻧﻪﻫﺎﻱ ﺍﻣﺮﻭﺯﻱ ﺍﺯ ﻣﻌﻤﺎﺭﻱ ﻛﻼﺳﺘﺮ ﺍﺳﺘﻔﺎﺩﻩ‬

‫‪Fixed 1‬‬

‫‪37‬‬
‫ﻣﻲﻛﻨﻨﺪ ﻭ ﺍﺑﺮ ﺭﺍﻳﺎﻧﻪﻫﺎﻱ ﺳﻨﺘﻲ‪ ،‬ﺍﺯ ﻧﻈﺮ ﻧﺴﺒﺖ ﻛﺎﺭﺍﻳﻲ ﺑﻪ ﻗﻴﻤﺖ‪ ،‬ﻗﺎﺑﻞ ﻣﻘﺎﻳﺴﻪ ﺑﺎ ﺍﺑﺮﺭﺍﻳﺎﻧﻪﻫﺎﻱ ﻣﺪﺭﻥ ﺍﻣﺮﻭﺯﻱ‬

‫ﻧﻴﺴﺘﻨﺪ‪.‬‬

‫‪ 2-3-2‬ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺩﺳﻜﺘﺎپ‬

‫ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺩﺳﻜﺘﺎپ‪ ،‬ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﭼﻨﺪﻳﻦ ﺗﻜﻨﻮﻟﻮژﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺑﻪ ﻃﻮﺭ ﺟﺪﺍﮔﺎﻧﻪ ﻭﻳﺎ ﺑﺎ ﻫﻢ ﻣﻲﺑﺎﺷﺪ‬

‫ﻛﻪ ﺩﺭ ﺍﺩﺍﻣﻪ ﺑﻪ ﭼﻨﺪ ﻣﻮﺭﺩ ﺍﺯ ﺁﻥ ﺍﺷﺎﺭﻩ ﻣﻲﻛﻨﻴﻢ‪.‬‬

‫ﻫﺮ ﮔﺎﻩ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺩﺳﻜﺘﺎپ ﺩﺭ ﻣﻮﺭﺩ ﺩﺳﺘﺮﺳﻲ ﺍﺯ ﺭﺍﻩ ﺩﻭﺭ ﺑﻪ ﻳﻚ ﺳﻴﺴﺘﻢ ﻓﻴﺰﻳﻜﻲ ﻳﺎ ﻣﺠﺎﺯﻱ ﻣﺪﻧﻈﺮ‬
‫‪1‬‬
‫ﺑﺎﺷﺪ‪ ،‬ﺗﻜﻨﻮﻟﻮژﻱ ﻣﻮﺭﺩ ﺍﺳﺘﻔﺎﺩﻩ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺩﺳﺘﺮﺳﻲ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪ .‬ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ﺗﺼﻮﻳﺮ ﺭﺍﺑﻂﻛﺎﺭﺑﺮﻱ‬

‫ﻛﺎﺭﺑﺮﺩ ﺍﺯ ﻃﺮﻳﻖ ﺷﺒﻜﻪ ﻣﻨﺘﻘﻞ ﺷﺪﻩ ﻭ ﺑﻪ ﻛﺎﺭﺑﺮ ﻣﻘﺼﺪ ﻣﻲﺭﺳﺪ‪ .‬ﺩﺍﺩﻩﻫﺎﻱ ﻭﺭﻭﺩﻱ ﻛﺎﺭﺑﺮ ﻫﻢ ﺑﻪ ﻫﻤﻴﻦ ﻃﺮﻳﻖ ﺍﺯ‬

‫ﻃﺮﻳﻖ ﺷﺒﻜﻪ ﺑﻪ ﻛﺎﺭﺑﺮﺩ ﺩﺭ ﺣﺎﻝ ﺍﺟﺮﺍ ﺩﺭ ﻛﺎﻣﭙﻴﻮﺗﺮ ﻣﺒﺪﺍء ﻣﻨﺘﻘﻞ ﻣﻲﺷﻮﺩ‪ .‬ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺩﺭ ﺷﻜﻞ ‪ 14-2‬ﻧﺸﺎﻥ‬

‫ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪ .‬ﺷﺮﻛﺖﻫﺎﻱ ﻣﺜﻞ ﻣﺎﻳﻜﺮﻭﺳﺎﻓﺖ‪ VMware ،‬ﻭ ﺳﻴﺘﺮﻳﻜﺲ‪ ،‬ﻧﺮﻡﺍﻓﺰﺍﺭﻫﺎﻱ ﺳﻤﺖﻛﻼﻳﻨﺖ ﺑﺮﺍﻱ‬

‫ﻟﻮﺡ ﺭﺍﻳﺎﻧﻪﻫﺎ‪ ،2‬ﺗﻠﻔﻦﻫﺎﻱ ﻫﻮﺷﻤﻨﺪ‪ ،‬ﻟﺐ ﺗﺎپﻫﺎ ﻭ ‪PC‬ﻫﺎ ﺍﺭﺍﺋﻪ ﻛﺮﺩﻩﺍﻧﺪ ﻛﻪ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﺑﻪ ﻛﺎﺭﺑﺮﺍﻥ ﻣﻲﺩﻫﻨﺪ ﺗﺎ‬

‫ﺑﻪ ﺑﺮﻧﺎﻣﻪﻫﺎﻱ ﻛﺎﺭﺑﺮﺩﻱ ﻛﻪ ﺩﺭ ﻫﺮ ﺟﺎﻱ ﺍﺯ ﺷﺒﻜﻪ ﺩﺭ ﺣﺎﻝ ﺍﺟﺮﺍ ﺍﺳﺖ ﺩﺳﺘﺮﺳﻲ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ‪.‬‬

‫‪User Interface 1‬‬

‫‪Tablets 2‬‬

‫‪38‬‬
 ‫ﺷﻜﻞ ‪ . 14 2‬ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺩﺳﻜﺘﺎپ ﺍﺯ ﻃﺮﻳﻖ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺩﺳﺘﺮﺳﻲ‬

‫ﮔﺎﻫﻲ ﺍﻭﻗﺎﺕ ﺍﺻﻄﻼﺡ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺩﺳﻜﺘﺎپ ﺩﺭ ﻣﻮﺭﺩ ﻛﭙﺴﻮﻟﻪ ﻛﺮﺩﻥ ﻛﺎﺭﺑﺮﺩ ﺑﻪ ﻛﻤﻚ ﺗﻜﻨﻮﻟﻮژﻱ‬

‫ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﻛﺎﺭﺑﺮﺩ ﻭ ﺍﺭﺳﺎﻝ ﺁﻥ ﺭﺍ ﺑﻪ ﻛﻼﻳﻨﺖ ﻣﻮﺭﺩ ﻧﻈﺮ ﺟﻬﺖ ﺍﺟﺮﺍ ﺑﻪ ﻛﺎﺭ ﻣﻲﺭﻭﺩ؛ ﻛﻪ ﺍﻟﺒﺘﻪ ﺑﺎﻳﺴﺘﻲ‬

‫ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻣﻨﺎﺳﺐ ﺑﺮ ﺭﻭﻱ ﻛﻼﻳﻨﺖ ﻧﺼﺐ ﺷﺪﻩﺑﺎﺷﺪ‪ .‬ﻣﺜﻼ ﺑﺮﺍﻱ ﻛﺎﺭﺑﺮﺩﻫﺎﻱ ﻭﻳﻨﺪﻭﺯﻱ ﺑﺎﻳﺴﺘﻲ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ‬

‫ﻧﺼﺐ ﺷﺪﻩ ﺑﺮ ﺭﻭﻱ ﻛﻼﻳﻨﺖ ﻧﺴﺨﻪ ﻣﻨﺎﺳﺒﻲ ﺍﺯ ﻭﻳﻨﺪﻭﺯ ﺑﺎﺷﺪ‪ .‬ﺷﻜﻞ ‪ 15-2‬ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﻛﻨﻴﺪ‪.‬‬

‫‪39‬‬
 ‫ﺷﻜﻞ ‪ . 15 2‬ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺩﺳﻜﺘﺎپ ﺍﺯ ﻃﺮﻳﻖ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﻛﺎﺭﺑﺮﺩ‬

‫ﺩﺭ ﻣﻮﺍﻗﻌﻲ ﻫﻢ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺩﺳﻜﺘﺎپ ﺩﺭ ﻣﻮﺭﺩ ﻛﭙﺴﻮﻟﻪ ﻛﺮﺩﻥ ﻛﻞ ﭘﺸﺘﻪ ﻛﺎﺭﺑﺮﺩ ﻛﻪ ﺩﺭ ﺣﺎﻝ ﺍﺟﺮﺍ ﺑﺮ ﺭﻭﻱ‬

‫ﻛﻼﻳﻨﺖ ﺍﺳﺖ ﺑﻜﺎﺭﻣﻲﺭﻭﺩ‪ .‬ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ﻗﺎﺑﻠﻴﺖ ﺟﺎﺑﻪﺟﺎﻳﻲ ﺳﻴﺴﺘﻢ ﻛﻼﻳﻨﺖ ﻣﺠﺎﺯﻱ ﻛﭙﺴﻮﻟﻪ ﺷﺪﻩ ﺑﺴﻴﺎﺭ ﺑﺎﻻ‬

‫ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪ .‬ﺗﺼﻮﻳﺮ ‪ 16-2‬ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺭﺍ ﻧﺸﺎﻥ ﻣﻲﺩﻫﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 16 2‬ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺩﺳﻜﺘﺎپ ﺍﺯ ﻃﺮﻳﻖ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﭘﺮﺩﺍﺯﺵ‬

‫‪40‬‬
 ‫ﺩﺭ ﺯﻳﺮ ﺣﺎﻟﺖ ﻣﺨﺘﻠﻒ ﻣﻮﺭﺩ ﺍﺧﻴﺮ ﺁﻭﺭﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪:‬‬

‫ﻳﻚ ﻳﺎ ﭼﻨﺪ ﺳﻴﺴﺘﻢ ﻛﻼﻳﻨﺖ ﻣﺠﺎﺯﻱ ﺑﺮ ﺭﻭﻱ ﻳﻚ ﻛﻼﻳﻨﺖ ﻓﻴﺰﻳﻜﻲ ﻣﻨﻔﺮﺩ ﻣﻲﺗﻮﺍﻧﻨﺪ ﺍﺟﺮﺍ ﺷﻮﻧﺪ‪ .‬ﺩﺭ‬ ‫‪-‬‬

‫ﺍﻳﻦ ﺣﺎﻟﺖ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﻓﺮﺍﻫﻢ ﻣﻲﺷﻮﺩ ﺗﺎ ﺑﺮﻧﺎﻣﻪﻫﺎﻱ ﻧﺎﻫﻤﮕﻮﻥ ﻭ ﻧﺎﺳﺎﺯﮔﺎﺭ ﺑﺘﻮﺍﻧﻨﺪ ﺩﺭ ﻛﻨﺎﺭ ﻫﻢ ﺑﻄﻮﺭ ﻫﻤﺰﻣﺎﻥ‬

‫ﺍﺟﺮﺍ ﺷﻮﻧﺪ‪.‬‬
‫‪2‬‬
‫ﺳﻴﺴﺘﻢ ﻛﻼﻳﻨﺖ ﻣﺠﺎﺯﻱ ﻣﻲﺗﻮﺍﻧﺪ ﺑﺮ ﺭﻭﻱ ﺳﺮﻭﺭ ﺗﻴﻐﻪﺍﻱ‪ 1‬ﻣﺤﻠﻲ ﻭﻳﺎ ﻧﺼﺐ ﺷﺪﻩ ﺩﺭ ﺩﺍﺧﻞ ﻣﺮﻛﺰﺩﺍﺩﻩ‬ ‫‪-‬‬

‫ﺳﺎﺯﻣﺎﻥ‪ ،‬ﺍﺟﺮﺍ ﺷﻮﺩ‪ .‬ﺭﺍﺑﻂ ﻛﺎﺭﺑﺮﻱ ﻫﻢ ﻣﻴﺘﻮﺍﻧﺪ ﺍﺯ ﻃﺮﻳﻖ ﺷﺒﻜﻪ ﺑﺮ ﺭﻭﻱ ﻳﻚ ‪ PC‬ﻣﻌﻤﻮﻟﻲ‪ ،‬ﻟﺐ ﺗﺎپ‪ ،‬ﻟﻮﺡﺭﺍﻳﺎﻧﻪ ﻭ‬

‫ﻳﺎ ﻳﻚ ‪ thinclient‬ﺑﻪ ﻛﻤﻚ ﺗﻜﻨﻮﻟﻮژﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺩﺳﺘﺮﺳﻲ ‪ ،‬ﻗﺎﺑﻞ ﺩﺳﺘﻴﺎﺑﻲ ﺑﺎﺷﺪ‪.‬‬

‫ﺍﺯ ﺍﻭﻧﺠﺎﻳﻲ ﻛﻪ ﺷﺮﻛﺖ ﻫﺎ ﺑﺮﺍﻱ ﻫﻤﻪ ﺍﻳﻦ ﻣﻮﺍﺭﺩ ﻳﻚ ﺗﻌﺮﻳﻒ ﺑﻜﺎﺭ ﻣﻲ ﺑﺮﻧﺪ‪ ،‬ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺩﺳﻜﺘﺎﺏ ﻣﻲ‬

‫ﺗﻮﺍﻧﺪ ﻛﻤﻲ ﮔﻴﺞ ﻛﻨﻨﺪﻩ ﺑﺎﺷﺪ‪.‬‬

‫‪ 3-3-2‬ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺳﺮﻭﺭ‬

‫ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺳﺮﻭﺭ ﻫﻤﺎﻥ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺗﻜﻨﻮﻟﻮژﻱ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻭ ﻳﺎ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻭ‬

‫ﺑﺨﺶﺑﻨﺪﻱ‪ 3‬ﺑﺮﺍﻱ ﺭﺍﻩﺍﻧﺪﺍﺯﻱ ﭼﻨﺪﻳﻦ ﺳﺮﻭﺭ ﻣﺠﺎﺯﻱ ﺑﺎ ﺑﺎﺭ ﻛﺎﺭﻱ ﻣﺠﺰﺍ ﺑﺮ ﺭﻭﻱ ﻳﻚ ﺳﺮﻭﺭ ﻓﻴﺰﻳﻜﻲ ﺍﺳﺖ‪ .‬ﺷﻜﻞ‬

‫‪ 9-7‬ﺭﺍ ﺑﺒﻴﻨﻴﺪ‪ .‬ﺍﮔﺮ ﺗﻜﻨﻮﻟﻮژﻱ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻭ ﺑﺨﺶﺑﻨﺪﻱ ﺑﺮﺍﻱ ﺍﻳﻦ ﻛﺎﺭ ﺍﺳﺘﻔﺎﺩﻩ ﺷﻮﺩ ﺗﻤﺎﻡ ﺑﺎﺭ‬

‫ﻛﺎﺭﻱ ﺑﺎﻳﺴﺘﻲ ﺗﻮﺳﻂ ﻳﻚ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﻣﻨﻔﺮﺩ ﺍﻧﺠﺎﻡ ﺷﻮﺩ؛ ﻭ ﺍﮔﺮ ﺗﻜﻨﻮﻟﻮژﻱ ﻣﺎﺷﻴﻦﻣﺠﺎﺯﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺷﻮﺩ‪ ،‬ﻫﺮ‬

‫ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻳﻚ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﺭﺍ ﺍﺟﺮﺍ ﻣﻲﻛﻨﺪ‪ .‬ﺍﻳﻦ ﺳﻴﺴﺘﻢﻋﺎﻣﻞﻫﺎ ﻣﻲﺗﻮﺍﻧﻨﺪ ﻧﺴﺨﻪﻫﺎﻱ ﻣﺨﺘﻠﻒ ﻳﻚ‬

‫ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﺑﺎﺷﻨﺪ ﻭ ﻳﺎ ﺣﺘﻲ ﺳﻴﺴﺘﻢﻋﺎﻣﻞﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺍﺯ ﺷﺮﻛﺖﻫﺎﻱ ﻣﺨﺘﻠﻒ ﻣﺜﻞ ﻭﻳﻨﺪﻭﺯ‪ ،‬ﻟﻴﻨﻮﻛﺲ‪،‬‬

‫ﻳﻮﻧﻴﻜﺲ ﻭ ‪ . ...‬ﺍﻳﻦ ﺗﻜﻨﻮﻟﻮژﻱ ﺑﺎﻋﺚ ﺍﻓﺰﺍﻳﺶ ﺑﻬﺮﻩﻭﺭﻱ ﺳﻴﺴﺘﻢ )ﻛﺎﻫﺶ ﺍﻭﻗﺎﺕ ﺑﻴﻜﺎﺭﻱ ﺳﻴﺴﺘﻢ( ﻣﻲﺷﻮﺩ‪.‬‬

‫‪blade server 1‬‬

‫‪Data center 2‬‬
‫‪Partitioning 3‬‬

‫‪41‬‬
‫ﻓﺼﻞ ﺳﻮﻡ‬

‫ﻣﻌﺮﻓﻲ ﻣﺠﻤﻮﻋﻪ ‪VMware vSphere 5‬‬

‫‪ vSphere 5‬ﻧﺴﻞ ﭘﻨﺠﻢ ﺍﺯ ﺗﻜﻨﻮﻟﻮژﻱ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺷﺮﻛﺖ ‪ VMware‬ﺍﺳﺖ ﻛﻪ ﻗﺒﻼ ﺑﺎ ﻧﺎﻡ ‪VMware‬‬

‫‪ Infrastructure‬ﻋﺮﺿﻪ ﻣﻲﺷﺪ‪ .‬ﺍﻳﻦ ﻣﺠﻤﻮﻋﻪ ﻋﻈﻴﻢ ﻛﺎﻣﻠﺘﺮﻳﻦ ﺍﺑﺰﺍﺭ ﺑﺮﺍﻱ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﺳﻴﺴﺘﻢ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ‬

‫ﺳﺮﻭﺭ ﺑﺎ ﭘﺸﺘﻴﺒﺎﻧﻲ ﺍﺯ ﺍﻧﻮﺍﻉ ﺳﻴﺴﺘﻢﻋﺎﻣﻞﻫﺎﻱ ﻣﻴﻬﻤﺎﻥ ﻭ ﻫﻤﭽﻨﻴﻦ ﭘﺸﺘﻴﺒﺎﻧﻲ ﺍﺯ ﺍﻧﻮﺍﻉ ﺗﻜﻨﻮﻟﻮژﻱﻫﺎﻱ ﭘﺮﺩﺍﺯﺷﻲ‬

‫ﻭ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻣﻲﺑﺎﺷﺪ‪ vSphere .‬ﺍﺯ ﺍﺟﺰﺍﻱ ﻣﺨﺘﻠﻒ ﺑﺮﺍﻱ ﺍﻫﺪﺍﻑ ﻣﺨﺘﻠﻒ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﻛﻨﻨﺪ ﻛﻪ ﻃﻲ ﺍﻳﻦ‬

‫ﻓﺼﻞ ﺍﻳﻦ ﺍﺟﺰﺍ ﺭﺍ ﻣﻌﺮﻓﻲ ﻛﺮﺩﻩ ﻭﺩﺭ ﻓﺼﻮﻝ ﺁﺗﻲ ﻧﺤﻮﻩ ﺭﺍﻩﺍﻧﺪﺍﺯﻱ‪ ،‬ﭘﻴﻜﺮﺑﻨﺪﻱ ﻭ ﻛﺎﺭﻛﺮﺩ ﺑﻌﻀﻲ ﺍﺯ ﺍﻳﻦ ﻗﺴﻤﺖﻫﺎﺭﺍ‬

‫ﺧﻮﺍﻫﻴﻢ ﮔﻔﺖ‪.‬‬

‫ﻣﺠﻤﻮﻋﻪ ‪ WMware vSphere‬ﺍﺯ ﻣﻮﻟﻔﻪﻫﺎ ﻭ ﻛﺎﺭﺑﺮﺩﻫﺎﻱ ﺯﻳﺮ ﺗﺸﻜﻴﻞ ﺷﺪﻩ ﺍﺳﺖ‪:‬‬

‫‪ϑ VMware ESXi‬‬

‫‪ϑ VMware vCenter Server‬‬

‫‪ϑ vSphere Update Manager‬‬

‫‪ϑ VMware vSphere Client and vSphere Web Client‬‬

‫‪42‬‬
ϑ VMware vShield Zones

ϑ VMware vCenter Orchestrator

ϑ vSphere Virtual Symmetric Multi-Processing

ϑ vSphere vMotion and Storage vMotion

ϑ vSphere Distributed Resource Scheduler

ϑ vSphere Storage DRS

ϑ Storage I/O Control and Network I/O Control

ϑ Profile-Driven Storage

ϑ vSphere High Availability

ϑ vSphere Fault Tolerance

ϑ vSphere Storage APIs for Data Protection and VMware Data Recovery

‫ ﺭﺍ ﭘﻮﺷﺶ ﻧﻤﻲﺩﻫﺪ؛ ﺑﻠﻜﻪ ﺑﺴﻴﺎﺭﻱ ﺍﺯ‬VMware ‫ ﺗﻤﺎﻡ ﺍﺟﺰﺍﻱ ﺗﻜﻨﻮﻟﻮژﻱ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ‬،‫ﺍﻟﺒﺘﻪ ﺍﻳﻦ ﻣﺠﻤﻮﻋﻪ‬

‫ ﻛﻪ ﺩﺭ ﺯﻣﻴﻨﻪ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﻭ ﭘﺮﺩﺍﺯﺵ ﺍﺑﺮﻱ ﺍﺭﺍﺋﻪ ﺷﺪﻩﺍﻧﺪ ﺑﻄﻮﺭ ﺟﺪﺍﮔﺎﻧﻪ ﻭ ﺧﺎﺭﺝ‬WMware ‫ﺍﺑﺰﺍﺭﻫﺎﻱ ﺷﺮﻛﺖ‬

:‫ﺍﺯ ﺍﻳﻦ ﻣﺠﻤﻮﻋﻪ ﻓﺮﻭﺧﺘﻪ ﻣﻲﺷﻮﻧﺪ ﻛﻪ ﺑﺮﺧﻲ ﺍﺯ ﺁﻧﻬﺎ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ‬

• VMware vCloud Director

• VMware vCloud Request Manager
• VMware vCenter AppSpeed
• VMware vCenterSite Recovery Manager

.‫ ﺭﺍ ﺗﻮﺿﻴﺢ ﻣﻲﺩﻫﻴﻢ‬vSphere ‫ﺣﺎﻝ ﻫﺮ ﻳﻚ ﺍﺯ ﺍﺟﺰﺍﻱ ﻣﺠﻤﻮﻋﻪ‬

43
 ‫‪VMware ESXi 1-3‬‬

‫ﻫﺴﺘﻪ ﻣﺠﻤﻮﻋﻪ ‪ vSphere‬ﺭﺍ ﻓﻮﻕﻧﺎﻇﺮ ﺁﻥ ﺗﺸﻜﻴﻞ ﻣﻲﺩﻫﺪ‪ ESXi .‬ﻻﻳﻪ ﻓﻮﻕ ﻧﺎﻇﺮ ﻣﺠﻤﻮﻋﻪ ‪vSphere‬‬

‫ﺍﺳﺖ‪ .‬ﺍﻟﺒﺘﻪ ﺩﺭ ﻧﺴﺨﻪﻫﺎﻱ ﻗﺒﻠﻲ ‪ vSphere‬ﻫﻢ ‪ ESX‬ﻭ ﻫﻢ ‪ ESXi‬ﺑﻪ ﻋﻨﻮﺍﻥ ﻓﻮﻕﻧﺎﻇﺮ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﺷﺪ ﻭﻟﻲ ﺩﺭ‬

‫ﻧﺴﺨﻪ ‪ 5‬ﻓﻘﻂ ‪ ESXi‬ﺍﺭﺍﺋﻪ ﻣﻲﺷﻮﺩ‪.‬‬

‫ﻫﺮ ﭼﻨﺪ ﻫﺮ ﺩﻭ ﻓﻮﻕ ﻧﺎﻇﺮ ﺩﺍﺭﺍﻱ ﻣﻮﺗﻮﺭ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﻳﻜﺴﺎﻥ ﻭ ﻭﻳﮋﮔﻲﻫﺎﻱ ﺑﺮﺍﺑﺮ ﻫﺴﺘﻨﺪ؛ ﺩﺭ ﻧﺴﺨﻪ ‪ESX‬‬

‫ﻳﻚ ﻛﻨﺴﻮﻝ ﺳﺮﻭﻳﺴﻲ ﭘﺎﻳﻪ ﻟﻴﻨﻮﻛﺴﻲ ﻧﻴﺰ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ﻫﺮ ﻳﻚ ﺍﺯ ﻛﺎﺭﺑﺮﺍﻥ ﺑﻪ ﺁﻥ ﺩﺳﺘﺮﺳﻲ ﻣﺴﺘﻘﻴﻢ‬

‫ﺩﺍﺷﺘﻨﺪ‪.‬‬

‫ﻋﻠﻴﺮﻏﻢ ﺣﺬﻑ ﻛﻨﺴﻮﻝ ﺍﺯ ‪ ESXi‬ﺍﻳﻦ ﻓﻮﻕ ﻧﺎﻇﺮ ﺗﻤﺎﻡ ﻗﺎﺑﻠﻴﺖﻫﺎ ﻭ ﻭﻳﮋﮔﻲﻫﺎﻱ ‪ ESX‬ﺭﺍ ﭘﺸﺘﻴﺒﺎﻧﻲ ﻣﻲﻛﻨﺪ‪ .‬ﻭ‬

‫ﺩﻟﻴﻞ ﺍﻳﻦ ﺍﻣﺮ ﻫﻢ ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﻣﺒﻨﺎﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺩﺭ ‪ ESXi‬ﺭﺍ ‪ vmkernel‬ﺗﺸﻜﻴﻞ ﻣﻲﺩﻫﺪ ﻛﻪ ﺩﺭ ﺩﺍﺧﻞ‬

‫ﻛﻨﺴﻮﻝ ﺳﺮﻭﻳﺲ ﻗﺮﺍﺭ ﻧﺪﺍﺭﺩ‪ .‬ﻭﻇﻴﻔﻪ ‪vmkernel‬ﻣﺪﻳﺮﻳﺖ ﺩﺳﺘﺮﺳﻲ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺑﻪ ﺳﺨﺖﺍﻓﺰﺍﺭ ﺑﻪ‬

‫ﻛﻤﻚ ﺯﻣﺎﻥﺑﻨﺪﻱ ‪ ، CPU‬ﻣﺪﻳﺮﻳﺖ ﺣﺎﻓﻈﻪ ﻭ ﻣﺪﻳﺮﻳﺖ ﭘﺮﺩﺍﺯﺵ ﺩﺍﺩﻩ ﺳﻮﺋﻴﭻﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻣﻲﺑﺎﺷﺪ‪ .‬ﺷﻜﻞ ‪1-3‬‬

‫ﺳﺎﺧﺘﺎﺭ ‪ VMware ESXi‬ﺭﺍ ﻧﺸﺎﻥ ﻣﻲﺩﻫﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 1 3‬ﺳﺎﺧﺘﺎﺭ ‪ESXi‬‬

‫‪ ESXi‬ﺩﺍﺭﺍﻱ ﻗﺪﺭﺕ ﺑﺎﻻﻳﻲ ﺩﺭ ﺍﺭﺍﺋﻪ ﻣﻨﺎﺑﻊ ﺑﻪ ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻣﻲﺑﺎﺷﺪ ﺩﺭ ﺟﺪﻭﻝ ‪ 1-3‬ﺑﻪ ﺑﺮﺧﻲ ﺍﺯ‬

‫‪44‬‬
 ‫ﺍﻳﻦ ﻭﻳﮋﮔﻲﻫﺎ ﺍﺷﺎﺭﻩ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬

‫ﺟﺪﻭﻝ ‪ . 1 3‬ﻗﺎﺑﻠﻴﺖﻫﺎﻱ ‪ESXi‬‬

‫‪VMware vCenter Server 2-3‬‬

‫‪ vCenter Server‬ﻣﺎﻧﻨﺪ ‪ Active Directory‬ﺍﺑﺰﺍﺭﻳﺴﺖ ﺑﺮﺍﻱ ﻣﺪﻳﺮﻳﺖ ﻣﺘﻤﺮﻛﺰ ﺗﻤﺎﻡ ﻣﺎﺷﻴﻦﻫﺎﻱ ‪ESXi‬‬

‫ﻭ ﺗﻤﺎﻣﻲ ﻣﺘﻌﻠﻘﺎﺕ ﻭ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺧﺘﻪ ﺷﺪﻩ ﺑﺮ ﺭﻭﻱ ﺁﻧﻬﺎ‪ .‬ﻫﻤﭽﻨﻴﻦ ﺑﺮﺍﻱ ﻛﻤﻚ ﺑﻪ ﺗﻮﺳﻌﻪﭘﺬﻳﺮﻱ‬

‫ﻣﺤﻴﻂ ‪vCenter Server‬ﻳﻚ ﭘﺎﻳﮕﺎﻩ ﺩﺍﺩﻩ ‪ back-end‬ﺑﺮﺍﻱ ﻧﮕﻬﺪﺍﺭﻱ ﺍﻃﻼﻋﺎﺕ ﻣﺮﺑﻮﻁ ﺑﻪ ﻣﻴﺰﺑﺎﻥﻫﺎ ﻭ‬

‫ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺑﻜﺎﺭ ﻣﻲﮔﻴﺮﺩ‪ ,‬ﻛﻪ ﺍﻳﻦ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﻣﻲﺗﻮﺍﻧﺪ ‪ Microsof SQL‬ﻭ ﻳﺎ ‪ Orade‬ﺑﺎﺷﺪ‪ .‬ﺩﺭ‬

‫ﻧﺴﺨﻪ ﻫﺎﻱ ﻗﺒﻠﻲ ‪ , vCenter Server ، vSphere‬ﻓﻘﻂ ﻣﻲ ﺗﻮﺍﻧﺴﺖ ﺑﺮ ﺭﻭﻱ ﻭﻳﻨﺪﻭﺯ ﺍﺟﺮﺍ ﺷﻮﺩﻭﻟﻲ ﺩﺭ ﻧﺴﺨﻪ ‪5‬‬

‫ﻳﻚ ‪ 1appliance‬ﭘﺎﻳﻪ ﻟﻴﻨﻮﻛﺲ ﻫﻤﺮﺍﻩ ﺑﺎ ﻣﺠﻤﻮﻋﻪ ﺍﺭﺍﺋﻪ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬

‫ﺍﻟﺒﺘﻪ ﺑﺪﻭﻥ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ vCenter Server‬ﻫﻢ ﻣﻲﺗﻮﺍﻥ ﺳﺮﻭﺭﻫﺎﻱ ‪ ESXi‬ﺭﺍ ﺑﺼﻮﺭﺕ ﻣﻨﻔﺮﺩ ﻣﺪﻳﺮﻳﺖ ﻛﺮﺩ‬

‫‪ appliance 1‬ﺩﺭﻭﺍﻗﻊ ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﭘﻴﺶ ﺳﺎﺧﺘﻪ ﺍﻱ ﻫﺴﺘﻨﺪ ﻛﻪ ﺑﻪ ﺭﺍﺣﺘﻲ ﻣﻲ ﺗﻮﺍﻧﺪ ﺑﻪ ﻋﻨﻮﺍﻥ ﻳﻚ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺑﺮ ﺭﻭﻱ ﺳﺮﻭﺭﻫﺎﻱ ‪ESXi‬‬
‫ﺍﺟﺮﺍ ﻛﺮﺩ‪.‬‬

‫‪45‬‬
‫ﻭﻟﻲ ﺑﺮﺍﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻗﺎﺑﻠﻴﺘﻬﺎﻱ ﺑﺴﻴﺎﺭ ﺍﺭﺯﺷﻤﻨﺪ ﻣﺠﻤﻮﻋﻪ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ‪ VMware‬ﻧﻈﻴﺮ‪، vMotion ،‬‬

‫ﺯﻣﺎﻥﺑﻨﺪ ﻣﻨﺎﺑﻊ ﺗﻮﺯﻳﻊ ﺷﺪﻩ‪ ،1‬ﻗﺎﺑﻠﻴﺖ ﺩﺳﺘﺮﺳﻲ ﻣﺴﺘﻤﺮ‪ ،2‬ﺳﻴﺴﺘﻢ ﺗﺤﻤﻞ ﺧﻄﺎ‪ 3‬ﻭ ﺑﺴﻴﺎﺭﻱ ﺍﺯ ﻗﺎﺑﻠﻴﺖﻫﺎﻱ ﺩﻳﮕﺮ‬

‫ﻛﻪ ﺩﺭ ﻓﺼﻞﻫﺎﻱ ﺑﻌﺪﻱ ﻫﻤﮕﻲ ﺁﻧﻬﺎ ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩ ﺧﻮﺍﻫﻨﺪ ﺷﺪ‪ ،‬ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ vCenter‬ﻻﺯﻡ ﺍﺳﺖ‪.‬‬

‫‪vSphere Update Manager 3-3‬‬

‫‪4‬‬
‫‪ Update manager‬ﭘﻼﮔﻴﻨﻲ ﺍﺳﺖ ﺑﺮﺍﻱ ‪ vCenter Server‬ﻛﻪ ﺑﻪ ﻛﻤﻚ ﺁﻥ ﻣﻲﺗﻮﺍﻥ ﺳﺮﻭﺭﻫﺎﻱ ‪ESXi‬‬

‫ﻭ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺍﻧﺘﺨﺎﺏ ﺷﺪﻩ ﺭﺍ ﺑﺎ ﺁﺧﺮﻳﻦ ﺑﺮﻭﺯﻫﺎ‪ 5‬ﻭ ﻭﺻﻠﻪ‪ 6‬ﻛﺮﺩ‪ Update Manager .‬ﺗﻮﺍﺑﻊ ﺯﻳﺮ ﺭﺍ‬

‫ﻓﺮﺍﻫﻢ ﻣﻲﺁﻭﺭﺩ ‪:‬‬

‫‪ -‬ﺑﺮﺭﺳﻲ ﻭ ﺗﺸﺨﻴﺺ ﺳﻴﺴﺘﻢﻫﺎﻳﻲ ﻛﻪ ﻧﻴﺎﺯ ﺑﻪ ﺑﺮﻭﺯ ﺷﺪﻥ ﺩﺍﺭﻧﺪ‪.‬‬

‫‪ -‬ﻧﺼﺐ ﺧﻮﺩﻛﺎﺭ ﺑﺮﻭﺯﻫﺎ‬

‫ﻳﻜﭙﺎﺭﭼﮕﻲ ﻛﺎﻣﻞ ﺑﺎ ﺩﻳﮕﺮ ﻗﺎﺑﻠﻴﺖﻫﺎﻱ ‪ vSphere‬ﻣﺜﻞ ﺳﻴﺴﺘﻢ ﺯﻣﺎﻥﺑﻨﺪ ﻣﻨﺎﺑﻊ ﺗﻮﺯﻳﻊ ﺷﺪﻩ‬

‫‪vSphere Client and vSphere web Client 4-3‬‬

‫‪ vCenter Server‬ﻳﻚ ﭼﺎﺭﭼﻮﺏ ﻣﺪﻳﺮﻳﺘﻲ ﻣﺘﻤﺮﻛﺰ ﺑﺮﺍﻱ ﻣﺪﻳﺮﻳﺖ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ ESXi‬ﺍﻳﺠﺎﺩ ﻣﻲﻛﻨﺪ ﻭﻟﻲ‬

‫ﺍﻣﻜﺎﻥ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺧﻮﺩ ‪ vCenter Server‬ﺍﺯ ﻃﺮﻳﻖ ‪ vSphere Client‬ﺧﻮﺍﻫﺪ ﺑﻮﺩ؛ ﻳﻌﻨﻲ ﺗﻤﺎﻡ ﺩﺳﺘﺮﺳﻲ ﻫﺎ‬

‫‪ ،‬ﭘﻴﻜﺮﺑﻨﺪﻱﻫﺎ ﻭ ‪ . . .‬ﺍﺯ ﻃﺮﻳﻖ ‪ vSphere Client‬ﺍﻧﺠﺎﻡ ﻣﻲﺷﻮﺩ‪ .‬ﺍﻟﺒﺘﻪ ﺳﻴﺴﺘﻤﻲ ﻛﻪ ‪ vCenter Server‬ﺑﺮ‬

‫ﺭﻭﻱ ﺁﻥ ﻧﺼﺐ ﺷﺪﻩ ﺍﺳﺖ ﻧﻴﺰ ﺧﻮﺩ ﻣﻲ ﺗﻮﺍﻧﺪ ﻣﻴﺰﺑﺎﻥ ‪ vSpher Client‬ﻧﻴﺰ ﺑﺎﺷﺪ‪ .‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻗﺒﻼ ﻧﻴﺰ ﮔﻔﺘﻪ‬

‫‪Distributed Resource Scheduler 1‬‬

‫‪High Availability 2‬‬
‫‪Fault Tolerance 3‬‬
‫‪Plug in 4‬‬
‫‪Up dates 5‬‬
‫‪Patch 6‬‬

‫‪46‬‬
‫ﺷﺪ ﺑﺪﻭﻥ ﺍﺗﺼﺎﻝ ‪ vSphere Cilent‬ﺑﻪ ‪ vCenter Server‬ﻭ ﻓﻘﻂ ﺑﺎ ﺍﺗﺼﺎﻝ ﺑﻪ ‪ ESXi‬ﺑﻪ ﻃﻮﺭ ﻣﻨﻔﺮﺩ ﻭ ﺑﻪ‬

‫ﻛﻤﻚ ‪ vSphere Client‬ﻣﻲﺗﻮﺍﻥ ‪ ESXi‬ﻫﺎ ﺭﺍ ﻣﺪﻳﺮﻳﺖ ﻛﺮﺩ‪ .‬ﺷﻜﻞ ‪ 1‬ﺭﺍ ﻧﮕﺎﻩ ﻛﻨﻴﺪ‪.‬‬

‫‪ vSphere web Client‬ﻳﻚ ﺳﻴﺴﺘﻢ ﻣﺪﻳﺮﻳﺖ ‪ ESXi‬ﻫﺎ ﺭﺍ ﺍﺯ ﻃﺮﻳﻖ ﻭﺏ ﺑﺮﻭﺯﺭ‪ 1‬ﻭ ﺍﻟﺒﺘﻪ ﺗﻨﻬﺎ ﺍﺯ ﻃﺮﻳﻖ‬

‫‪ vCenter Server‬ﺍﻳﺠﺎﺩ ﻣﻲﻛﻨﺪ‪ .‬ﺍﻟﺒﺘﻪ ﺗﻤﺎﻡ ﻭﻳﮋﮔﻲﻫﺎﻱ ﻣﺠﻤﻮﻋﻪ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺷﺮﻛﺖ ‪ VMware‬ﺍﺯ ﻃﺮﻳﻖ‬

‫‪ vSphere weab Client‬ﺩﺭ ﺩﺳﺘﺮﺱ ﻧﺨﻮﺍﻫﺪ ﺑﻮﺩ‪.‬‬

‫‪VMware vShield Zones 5-3‬‬

‫ﻳﻚ ﺩﻳﻮﺍﺭ ﺁﺗﺶ‪ 2‬ﻣﺠﺎﺯﻱ ﺍﺳﺖ ﻛﻪ ﺑﻪ ﻛﻤﻚ ﺁﻥ ﻣﻲﺗﻮﺍﻥ ﺗﺮﺍﻓﻴﻚ ﺷﺒﻜﻪ ﺩﺭ ﺩﺍﺧﻞ ﺳﻮﺋﻴﭻﻫﺎﻱ ﺷﺒﻜﻪ‬

‫ﻣﺠﺎﺯﻱ ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﻭ ﻣﺪﻳﺮﻳﺖ ﻛﺮﺩ‪.‬‬

‫ﻫﻤﭽﻨﻴﻦ ﻣﻲﺗﻮﺍﻥ ﺑﻪ ﻛﻤﻚ ﺁﻥ ﺳﻴﺎﺳﺖﻫﺎﻱ ﺍﻣﻨﻴﺘﻲ ﺧﺎﺻﻲ ﺭﺍ ﺑﺮ ﺭﻭﻱ ﮔﺮﻭﻫﻲ ﺍﺯ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ‬

‫ﺍﻋﻤﺎﻝ ﻛﺮﺩ ﻛﻪ ﺣﺘﻲ ﺩﺭ ﺻﻮﺭﺕ ﺍﻧﺘﻘﺎﻝ ﻳﻚ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺑﻪ ﻣﻴﺰﺑﺎﻥ ﺩﻳﮕﺮ ﺍﺯ ﻃﺮﻳﻖ ‪ DRS‬ﻭ ‪ vMotion‬ﺍﻳﻦ‬

‫ﺳﻴﺎﺳﺖﻫﺎ ﺣﻔﻆ ﺷﻮﻧﺪ‪.‬‬

‫‪VMware vCenter Orchestrator 6-3‬‬

‫‪vCenter Orchestrator‬ﻳﻚ ﻣﻮﺗﻮﺭ ﺧﻮﺩﻛﺎﺭ ﺳﺎﺯ ﺟﺮﻳﺎﻥ ﻛﺎﺭﻱ ﺍﺳﺖ ﻛﻪ ﺑﺎ ‪ vCenter Server‬ﺑﻪ ﻃﻮﺭ‬

‫ﺍﺗﻮﻣﺎﺗﻴﻚ ﻧﺼﺐ ﻣﻲﺷﻮﺩ‪ .‬ﺑﻪ ﻛﻤﻚ ﺍﻳﻦ ﺍﺑﺰﺍﺭ ﻣﻲﺗﻮﺍﻥ ﺑﺴﻴﺎﺭﻱ ﺍﺯ ﺍﻋﻤﺎﻝ ‪ vCenter Server‬ﺭﺍ ﺑﺼﻮﺭﺕ ﺧﻮﺩﻛﺎﺭ‬

‫ﺩﺭﺁﻭﺭﺩ ﻛﻪ ﺍﻳﻦ ﻛﺎﺭﻫﺎ ﻣﻲ ﺗﻮﺍﻧﻨﺪ ﺳﺎﺩﻩ ﻭ ﻳﺎ ﺑﺴﻴﺎﺭ ﭘﻴﭽﻴﺪﻩ ﺑﺎﺷﻨﺪ‪.‬‬

‫ﺗﻜﻨﻮﻟﻮژﻱ ﻫﺎﻱ ﺑﻜﺎﺭ ﺭﻓﺘﻪ ﺩﺭ ﻣﺠﻤﻮﻋﻪ ‪vSphere‬‬

‫ﺩﺭ ﺍﻳﻦ ﻗﺴﻤﺖ ﻧﮕﺎﻫﻲ ﺩﻗﻴﻘﺘﺮ ﺑﻪ ﺑﻌﻀﻲ ﺍﺯ ﺗﻜﻨﻮﻟﻮژﻱ ﻫﺎ ﻭ ﺍﻃﻼﻋﺎﺕ ﻣﻮﺟﻮﺩ ﺩﺭ ﻣﺠﻤﻮﻋﻪ ‪VMware‬‬

‫‪Web Browser 1‬‬

‫‪Fire wall 2‬‬

‫‪47‬‬
 ‫‪ vSphere‬ﻣﻲ ﺍﻧﺪﺍﺯﻳﻢ‬

‫‪1‬‬
‫‪ 7-3‬ﭼﻨﺪ ﭘﺮﺩﺍﺯﺷﻲ ﻣﺘﻘﺎﺭﻥ ﻣﺠﺎﺯﻱ‬

‫ﺍﻳﻦ ﺗﻜﻨﻮﻟﻮژﻱ ﺑﻪ ﻣﺪﻳﺮﺍﻥ ﺷﺒﻜﻪ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﻣﻲﺩﻫﺪ ﺗﺎ ﺑﺘﻮﺍﻧﻨﺪ ﻣﺎﺷﻴﻦﻫﺎﻳﻲ ﻣﺠﺎﺯﻱ ﺑﺎ ﭼﻨﺪ ﭘﺮﺩﺍﺯﻧﺪﻩ‬

‫ﻣﺠﺎﺯﻱ ﺍﻳﺠﺎﺩ ﻛﻨﻨﺪ‪ .‬ﺷﻜﻞ ‪ 2-3‬ﺗﻔﺎﻭﺕ ﺑﻴﻦ ﭼﻨﺪﭘﺮﺩﺍﺯﻧﺪﻩﺍﻱ ﺩﺭ ﻣﻴﺰﺑﺎﻥﻫﺎﻱ ‪ ESXi‬ﻭﭼﻨﺪﭘﺮﺩﺍﺯﻧﺪﻩ ﻣﺠﺎﺯﻱ ﺭﺍ‬

‫ﻧﺸﺎﻥ ﻣﻲﺩﻫﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 2 3‬ﭼﻨﺪ ﭘﺮﺩﺍﺯﺷﻲ ﻣﺘﻘﺎﺭﻥ ﻣﺠﺎﺯﻱ‬

‫ﺑﺪﻳﻦ ﻃﺮﻳﻖ ﻛﺎﺭﺑﺮﺩﻫﺎﻳﻲ ﻛﻪ ﺑﺮﺍﻱ ﺍﺟﺮﺍ ﺷﺪﻥ ﻧﻴﺎﺯ ﺑﻪ ﭼﻨﺪﭘﺮﺩﺍﺯﻧﺪﻩ ﺩﺍﺭﻧﺪ ﻣﻲ ﺗﻮﺍﻧﻨﺪ ﺩﺭ ﺍﻳﻦ ﻣﺎﺷﻴﻦﻫﺎﻱ‬

‫ﻣﺠﺎﺯﻱ ﺍﺟﺮﺍ ﺷﻮﻧﺪ‪ .‬ﺩﺭ ‪ vSphere 5‬ﺍﻳﻦ ﻗﺎﺑﻠﻴﺖ ﺑﺎ ﺍﺿﺎﻓﻪ ﺷﺪﻥ ﺍﻣﻜﺎﻥ ﺍﻳﺠﺎﺩ ﭘﺮﺩﺍﺯﻧﺪﻩﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻳﺎﭼﻨﺪ‬

‫ﻫﺴﺘﻨﻪ ﻣﺠﺎﺯﻱ ﺗﻮﺳﻌﻪ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬

‫‪Virtual Symmetric Multi Processing 1‬‬

‫‪48‬‬
 ‫‪vSphere vMotion and vSphere Storage vMotion 8-3‬‬

‫‪ vMotion‬ﻛﻪ ‪ live migration‬ﻧﻴﺰ ﺧﻮﺍﻧﺪﻩ ﻣﻲ ﺷﻮﺩ ﻭﻳﮋﮔﻲ ﺩﺭ ‪ ESXi , vCenter Server‬ﺍﺳﺖ ﻛﻪ ﺍﺟﺎﺯﻩ‬

‫ﻣﻲﺩﻫﺪ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺩﺭ ﺣﺎﻝ ﺍﺟﺮﺍ ﺍﺯ ﻳﻚ ﻣﻴﺰﺑﺎﻥ ﻓﻴﺰﻳﻜﻲ ﺑﻪ ﻣﻴﺰﺑﺎﻥ ﺩﻳﮕﺮ ﻣﻨﺘﻘﻞ ﺷﻮﻧﺪ ﺑﺪﻭﻥ ﺣﺘﻲ‬

‫ﻟﺤﻈﻪ ﺍﻱ ﺧﺎﻣﻮﺵ ﺷﺪﻥ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻭ ﻗﻄﻊ ﺷﺪﻥ ﺍﺗﺼﺎﻝ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺑﻪ ﺷﺒﻜﻪ ‪.‬‬

‫‪ vMotion‬ﻣﺤﺘﻮﻳﺎﺕ ﺩﺭ ﺣﺎﻝ ﺍﺟﺮﺍ ﺭﺍ ﺍﺯ ﻳﻚ ﺳﻴﺴﺘﻢ ﺑﻪ ﺳﻴﺴﺘﻢ ﺩﻳﮕﺮ ﻣﻨﺘﻘﻞ ﻣﻲﻛﻨﺪ ﺍﻣﺎ ﻣﺤﺘﻮﻳﺎﺕ‬

‫ﺳﻴﺴﺘﻢ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ﺩﺳﺖ ﻧﺎﺧﻮﺭﺩﻩ ﺩﺭ ﺟﺎﻱ ﺧﻮﺩ ﺑﺎﻗﻲ ﻣﻲﻣﺎﻧﻨﺪ‪ Storage vMotion .‬ﺍﻣﻜﺎﻧﻲ ﺍﺳﺖ ﺑﺮﺍﻱ‬

‫ﺍﻧﺘﻘﺎﻝ ﻣﺤﺘﻮﻳﺎﺕ ﺩﻳﺴﻚ ﻣﺠﺎﺯﻱ ﻳﻚ ﺳﻴﺴﺘﻢ ﻣﺠﺎﺯﻱ ﺩﺭ ﺧﺎﻣﻮﺵ ﻭﻳﺎ ﺩﺭ ﺣﺎﻝ ﺍﺟﺮﺍ ﺍﺯ ﻳﻚ ﻭﺍﺣﺪ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ‬

‫ﺑﻪ ﻳﻚ ﻭﺍﺣﺪ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ﺩﻳﮕﺮ ﺑﺪﻭﻥ ﺟﺎﺑﻪ ﺟﺎﻳﻲ ﻣﺎﺷﻴﻦ ﭘﺮﺩﺍﺯﺵ‪ .‬ﻳﻌﻨﻲ ﻣﺤﻞ ﺍﺟﺮﺍﻱ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺗﻐﻴﻴﺮ‬

‫ﻧﻤﻲﻛﻨﺪ‪ ،‬ﻭ ﺍﻳﻦ ﺩﺭ ﺣﺎﻟﻲ ﺍﺗﻔﺎﻕ ﻣﻲﺍﻓﺘﺪ ﻛﻪ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺭﻭﺷﻦ ﺑﻮﺩﻩ ﻭ ﻃﻲ ﺯﻣﺎﻥ ﺍﻧﺘﻘﺎﻝ ﻭﺍﺣﺪ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ‬

‫ﺧﻠﻠﻲ ﺩﺭ ﻛﺎﺭ ﺁﻥ ﺍﻳﺠﺎﺩ ﻧﻤﻲﺷﻮﺩ‪.‬‬

‫‪1‬‬
‫‪ 9-3‬ﺳﻴﺴﺘﻢ ﺯﻣﺎﻧﺒﻨﺪ ﻣﻨﺎﺑﻊ ﺗﻮﺯﻳﻊ ﺷﺪﻩ‬

‫‪ vMotion‬ﻳﻚ ﻋﻤﻞ ﺩﺳﺘﻲ‪ 2‬ﺍﺳﺖ ﻳﻌﻨﻲ ﻣﺪﻳﺮ ﺳﻴﺴﺘﻢ ﺑﺎﻳﺪ ﺑﻄﻮﺭ ﺩﺳﺘﻲ ﻋﻤﻞ ‪ vMotin‬ﺭﺍ ﺍﻧﺠﺎﻡ ﺩﻫﺪ‪.‬‬

‫ﺍﮔﺮﺑﺨﻮﺍﻫﻴﻢ ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ ﻧﻴﺎﺯ ﻣﺜﻼ ﺑﺮﺍﻱ ﺗﻨﻈﻴﻢ ﺑﺎﺭ ﻣﻴﺰﺑﺎﻥ ﻫﺎﻱ ‪ ESXi‬ﻋﻤﻞ ‪ vMotion‬ﺑﻄﻮﺭ ﺧﻮﺩﻛﺎﺭ ﺍﻧﺠﺎﻡ‬

‫ﺷﻮﺩ‪ ،‬ﺍﻳﻨﺠﺎﺳﺖ ﻛﻪ ﭘﺎﻱ ﺯﻣﺎﻥﺑﻨﺪ ﻣﻨﺎﺑﻊ ﺗﻮﺯﻳﻊ ﺷﺪﻩ ﻭ ﻳﺎ ﺑﻪ ﺍﺧﺘﺼﺎﺭ ‪ DRS‬ﻭﺳﻂ ﻣﻲﺁﻳﺪ‪.‬‬

‫ﻗﺒﻞ ﺍﺯ ﺍﺩﺍﻣﻪ ﺑﺤﺚ ﺩﺭ ﺣﺪ ﭼﻨﺪ ﺧﻂ ﺩﺭ ﻣﻮﺭﺩ ﻛﻼﺳﺘﺮ ﺩﺭ ‪ vSphere‬ﺗﻮﺿﻴﺢ ﺩﻫﻴﻢ ‪.‬‬

‫ﺩﺭ ﻓﺼﻞ ﻗﺒﻠﻲ ﺑﺎ ﻣﻔﻬﻮﻡ ﻛﻼﺳﺘﺮ ﺁﺷﻨﺎ ﺷﺪﻳﺪ ﻧﻴﺎﺯﻱ ﺑﻪ ﺗﻜﺮﺍﺭ ﺩﻭﺑﺎﺭﻩ ﻧﻴﺴﺖ‪ .‬ﺩﺭ ﻣﺠﻤﻮﻋﻪ ‪، vSphere‬‬

‫‪Distributed Resource Scheduler 1‬‬

‫‪Manual 2‬‬

‫‪49‬‬
‫ﻛﻼﺳﺘﺮ ‪ ،‬ﻣﺠﻤﻮﻋﻪﺍﻱ ﺍﺯ ﻣﻴﺰﺑﺎﻥﻫﺎﻱ ‪ ESXi‬ﺍﺳﺖ ﻛﻪ ﻣﻨﺎﺑﻊ ﺧﻮﺩ ﺭﺍ ﺩﺭ ﻳﻚ ﺍﺳﺘﺨﺮ ﻣﻨﺎﺑﻊ‪ 1‬ﺑﻪ ﺍﺷﺘﺮﺍﻙ‬

‫ﻣﻲﮔﺬﺍﺭﻧﺪ‪ .‬ﺑﻪ ﻋﺒﺎﺭﺕ ﺩﻳﮕﺮ ﻛﻼﺳﺘﺮ ‪ ،ESXi‬ﻳﻚ ﺗﺠﻤﻴﻊ ﺿﻤﻨﻲ ﺗﻮﺍﻥ ﭘﺮﺩﺍﺯﺷﻲ ﻭ ﺣﺠﻢ ﺣﺎﻓﻈﻪﻫﺎﻱ ﺗﻤﺎﻡ‬

‫ﻣﻴﺰﺑﺎﻥﻫﺎﻱ ﻋﻀﻮ ﻛﻼﺳﺘﺮ ﺍﺳﺖ‪.‬‬

‫ﺣﺎﻝ ﺑﺮﻣﻲﮔﺮﺩﻳﻢ ﺑﻪ ﻣﻮﺿﻮﻉ ‪ . DRS‬ﺍﻫﺪﺍﻑ ﻭ ﻭﻇﺎﻳﻒ ‪ DRS‬ﺩﺭ ﺩﻭ ﺑﻨﺪ ﺧﻼﺻﻪ ﻣﻲﺷﻮﺩ‪:‬‬

‫ﺩﺭ ﻫﻨﮕﺎﻡ ﺷﺮﻭﻉ)ﺭﻭﺷﻦ ﺷﺪﻥ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ(‪ DRS ،‬ﺳﻌﻲ ﻣﻲﻛﻨﺪ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺭﺍ ﺩﺭ‬ ‫‪-‬‬

‫ﻣﻴﺰﺑﺎﻧﻲ ﺍﺟﺮﺍ ﻛﻨﺪ ﻛﻪ ﺩﺍﺭﺍﻱ ﺑﺎﺭ ﭘﺮﺩﺍﺯﺷﻲ ﻛﻤﺘﺮﻱ ﺑﺎﺷﺪ‪.‬‬

‫ﻫﻨﮕﺎﻣﻲ ﻛﻪ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺩﺭ ﺣﺎﻝ ﺍﺟﺮﺍ ﺍﺳﺖ‪ DRS ،‬ﻣﺪﺍﻡ )ﻫﺮ ‪ 5‬ﺩﻗﻴﻘﻪ ﻳﻜﺒﺎﺭ( ﺩﺭ ﺣﺎﻝ ﺟﺴﺘﺠﻮ ﻭ‬ ‫‪-‬‬

‫ﺍﻧﺪﺍﺯﻩﮔﻴﺮﻱ ﺍﺳﺖ ﺗﺎ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺭﺍ ﺑﻪ ﻣﻴﺰﺑﺎﻧﻲ ﺍﻧﺘﻘﺎﻝ ﺩﻫﺪ ﻛﻪ ﺑﺮﺍﻱ ﻣﻨﺎﺑﻊ ﻣﻮﺭﺩ ﻧﻴﺎﺯﺷﺎﻥ‪ ،‬ﻛﻤﺘﺮﻳﻦ‬

‫ﺭﻗﺎﺑﺖ ﻭﺟﻮﺩ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬

‫ﻣﻮﺭﺩ ﺍﻭﻝ ﻛﻪ ﻣﻌﻤﻮﻻ ‪ Intelligent Placement‬ﻧﻴﺰ ﺧﻮﺍﻧﺪﻩ ﻣﻲﺷﻮﺩ ﺍﺷﺎﺭﻩ ﺑﻪ ﺍﻳﻦ ﻣﻔﻬﻮﻡ ﺩﺍﺭﺩ ﻛﻪ ﺩﺭ‬

‫ﻫﻨﮕﺎﻡ ﺭﻭﺷﻦﺷﺪﻥ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻛﻪ ﺩﺭ ﺩﺍﺧﻞ ﻳﻚ ﻛﻼﺳﺘﺮ ﻗﺮﺍﺭ ﺩﺍﺭﺩ‪ ،‬ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺑﺮﺍﻱ ﺍﺟﺮﺍ ﺑﻪ ﻣﻴﺰﺑﺎﻧﻲ‬

‫ﻣﻨﺘﻘﻞ ﻣﻲﺷﻮﺩ ﻛﻪ ﺍﺯ ﻟﺤﺎﻅ ﻣﻨﺎﺑﻊ ﺁﺯﺍﺩ ﻣﻮﺟﻮﺩ ﺑﻬﺘﺮﻳﻦ ﺑﺎﺷﺪ‪ .‬ﺑﻨﺪ ﺩﻭﻡ ﻫﻢ ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺭﺍ ﺑﻴﺎﻥ ﻣﻲﻛﻨﺪﻛﻪ‬

‫ﺣﺘﻲ ﻭﻗﺘﻲ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺭﻭﺷﻦ ﻫﻢ ﻫﺴﺘﻨﺪ‪ DRS ،‬ﺩﺍﺋﻤﺎ ﺳﻌﻲ ﻣﻲﻛﻨﺪ ﺑﻬﺘﺮﻳﻦ ﻣﻴﺰﺑﺎﻥ ‪ ESXi‬ﺭﺍ ﺍﺯ‬

‫ﻧﻈﺮ ﻣﻨﺎﺑﻊ ﺁﺯﺍﺭ ﻣﻮﺟﻮﺩ ﻛﻪ ﺩﺍﺧﻞ ﻫﻤﺎﻥ ﻛﻼﺳﺘﺮ ﻗﺮﺍﺭ ﺩﺍﺭﺩ‪ ،‬ﺑﺮﺍﻱ ﺍﻧﺘﻘﺎﻝ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺍﻧﺘﺨﺎﺏ ﻛﻨﺪ‪.‬‬

‫ﻣﺜﻞ ﻭﻗﺘﻲ ﺩﺭ ﻫﻨﮕﺎﻡ ﺭﻭﺷﻦ ﺑﻮﺩﻥ ﭼﻨﺪﻳﻦ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻋﻀﻮ ﻛﻼﺳﺘﺮ ﺍﮔﺮ ﻳﻚ ﻳﺎ ﭼﻨﺪ ﺗﺎ ﺍﺯ ﻣﺎﺷﻴﻦﻫﺎﻱ‬

‫ﻣﺠﺎﺯﻱ ﺑﺎﺭ ﭘﺮﺩﺍﺯﺵ ﺑﺎﻻﻳﻲ ﺭﺍ ﺑﻪ ﺳﻴﺴﺘﻢ ﺗﺤﻤﻴﻞ ﻛﻨﻨﺪ‪ DRS ،‬ﺑﻪ ﻃﻮﺭ ﺧﻮﺩﻛﺎﺭ ﻳﻚ ﻳﺎ ﭼﻨﺪ ﺗﺎ ﺍﺯ ﺁﻧﻬﺎ ﺭﺍ ﺑﻪ‬

‫‪ESXi‬ﻫﺎﻱ ﻋﻀﻮ ﻫﻤﺎﻥ ﻛﻼﺳﺘﺮ ﻛﻪ ﻣﻨﺎﺑﻊ ﭘﺮﺩﺍﺯﺷﻲ ﺁﺯﺍﺩ ﺑﻴﺸﺘﺮﻱ ﺩﺍﺭﻧﺪ ﻣﻨﺘﻘﻞ ﻣﻲﻛﻨﺪ‪.‬‬

‫‪vSphere Storage DRS 10-3‬‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ‪ DRS‬ﺑﺎﺭ ﭘﺮﺩﺍﺯﺵ ﺑﺮ ﺭﻭﻱ ‪ESXi‬ﻫﺎ ﺭﺍ ﺗﻨﻈﻴﻢ ﻣﻲﻛﻨﺪ‪ Storage DRS ،‬ﺑﺎ ﺟﺎ ﺑﺠﺎﻳﻲ ﻣﺎﺷﻴﻦ‬

‫‪Resource Pool 1‬‬

‫‪50‬‬
‫ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺑﺎﺭ ﺗﺮﺍﻓﻴﻜﻲ ﺑﺮ ﺭﻭﻱ ﺳﺮﻭﺭﻫﺎﻱ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ﺭﺍ ﻣﺘﻌﺎﺩﻝ ﻣﻲﻛﻨﺪ‪ .‬ﺍﻟﺒﺘﻪ ﻣﺎﻧﻨﺪ ‪Storage ، DRS‬‬

‫‪ DRS‬ﻫﻢ ﺩﺭ ﺩﺍﺧﻞ ﻳﻚ ﻛﻼﺳﺘﺮ ﻋﻤﻞ ﻣﻲﻛﻨﺪ‪ .‬ﻫﻤﺎﻧﮕﻮﻧﻪ ﻛﻪ ‪ DRS‬ﺍﺯ ﺗﻜﻨﻮﻟﻮژﻱ ‪ vMotion‬ﺑﺮﺍﻱ ﻣﺘﻌﺎﺩﻝ‬

‫ﻛﺮﺩ‪-‬ﻥ ﺳﻴﺴﺘﻢ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﻛﻨﺪ‪ Storage DRS .‬ﻫﻢ ﺍﺯ ‪ Storage vMotion‬ﺑﻬﺮﻩ ﻣﻲﮔﻴﺮﺩ‪.‬‬

‫‪ 11-3‬ﺳﻴﺴﺘﻢ ﻛﻨﺘﺮﻝ ﻭﺭﻭﺩﻱ ﺧﺮﻭﺟﻲ ﺷﺒﻜﻪ‪ 1‬ﻭ ﻛﻨﺘﺮﻝ ﻭﺭﻭﺩﻱ‬

‫‪2‬‬
‫ﺧﺮﻭﺟﻲ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ‬

‫‪ vSphere‬ﻛﻨﺘﺮﻝ ﺑﺴﻴﺎﺭ ﺯﻳﺎﺩﻱ ﺑﺮ ﺭﻭﻱ ﺗﺨﺼﻴﺺ ﻣﻨﺎﺑﻊ ﭘﺮﺩﺍﺯﺷﻲ ﻫﻤﭽﻨﻴﻦ ﺣﺎﻓﻈﻪﻫﺎﻱ ﺍﺻﻠﻲ ﺑﻪ‬

‫ﺧﺮﻭﺟﻲ ﺷﺒﻜﻪ ﻭ‬ ‫ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺩﺍﺭﺩ‪ .‬ﻗﺎﺑﻠﻴﺘﻲ ﻣﺸﺎﺑﻪ ﻧﻴﺰ ﺩﺭ ﺍﺧﺘﺼﺎﺹ ﺩﺍﺩﻥ ﺗﺮﺍﻓﻴﻚ ﻭﺭﻭﺩﻱ‬

‫ﺳﻴﺴﺘﻢﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺑﻪ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪.‬‬

‫ﺳﻴﺴﺘﻢ ﻛﻨﺘﺮﻝ ﻭﺭﻭﺩﻱ‪-‬ﺧﺮﻭﺟﻲ ﺫﺧﻴﺮﻩﺳﺎﺯﻫﺎ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﺑﻪ ﻣﺪﻳﺮﺍﻥ ﻣﻲﺩﻫﺪ ﺗﺎ ﺑﻪ ﻫﺮ ﻳﻚ ﺍﺯ‬

‫ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻳﻚ ﺍﻭﻟﻮﻳﺖ ﺩﺭ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﻣﻨﺎﺑﻊ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺍﺧﺘﺼﺎﺹ ﺩﻫﺪﻧﺪ ﺗﺎ ﺩﺭ ﺻﻮﺭﺕ ﺭﻗﺎﺑﺖ‬

‫ﺑﻴﻦ ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺩﺭ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺫﺧﻴﺮﻩﺳﺎﺯﻫﺎ‪ ،‬ﺍﻳﻦ ﺍﻭﻟﻮﻳﺖﻫﺎ ﺍﻋﻤﺎﻝ ﺷﻮﻧﺪ‪ .‬ﺍﻳﻦ ﻗﺎﺑﻠﻴﺖ ﺩﺭ‬

‫‪ vSphere5‬ﻓﻘﻂ ﺩﺭ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻫﺎﻳﻲ ﺑﺎ ﺳﻴﺴﺘﻢ ﻓﺎﻳﻞ ‪ NFS , VMFS‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪.‬‬

‫ﺳﻴﺴﺘﻢ ﻛﻨﺘﺮﻝ ﻭﺭﻭﺩﻱ‪-‬ﺧﺮﻭﺟﻲ ﺷﺒﻜﻪ ﻫﻢ ﻗﺎﺑﻠﻴﺘﻲ ﻣﺸﺎﺑﻪ ﺍﺳﺖ؛ ﻭﻟﻲ ﺩﺭ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﻛﺎﺭﺕﻫﺎﻱ ﺷﺒﻜﻪ‬

‫ﻓﻴﺰﻳﻜﻲ‪ .‬ﺍﻳﻦ ﺳﻴﺴﺘﻢ ﺑﻪ ﻣﺪﻳﺮﺍﻥ ﺷﺒﻜﻪ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﻣﻲﺩﻫﺪ ﺗﺎ ﺑﺎ ﺍﺧﺘﺼﺎﺹ ﺩﺍﺩﻥ ﺍﻭﻟﻮﻳﺘﻲ ﺑﻪ ﻣﺎﺷﻴﻦﻫﺎﻱ‬

‫ﻣﺠﺎﺯﻱ ﺩﺳﺘﺮﺳﻲ ﺁﻧﻬﺎ ﺑﻪ ﺗﺮﺍﻓﻴﻚ ﻭ ﭘﻬﻨﺎﻱ ﺑﺎﻧﺪ ﺭﺍ ﻣﺪﻳﺮﻳﺖ ﻛﻨﻨﺪ‪.‬‬

‫‪ 12-3‬ﻗﺎﺑﻠﻴﺖ ﺩﺳﺘﺮﺳﻲ ﻣﺴﺘﻤﺮ‪(HA) 3‬‬

‫ﻧﮕﺮﺍﻧﻲ ﻛﻪ ﻣﻤﻜﻦ ﺍﺳﺖ ﭘﻴﺶ ﺑﻴﺎﻳﺪ ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﺍﮔﺮ ﭼﻨﺪﻳﻦ ﺳﺮﻭﺭ ﺑﺮ ﺭﻭﻱ ﻳﻚ ﺳﺮﻭﺭ ﻓﻴﺰﻳﻜﻲ ﺍﺟﺮﺍ ﺷﻮﻧﺪ‬

‫‪Network I/O control 1‬‬

‫‪Storage I/O control 2‬‬
‫‪High Availability 3‬‬

‫‪51‬‬
‫ﺩﺭ ﺻﻮﺭﺕ ﺧﺮﺍﺏ ﺷﺪﻥ ﺳﺮﻭﺭ ﻓﻴﺰﻳﻜﻲ ﺗﻤﺎﻡ ﺳﺮﻭﺭﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺍﺯﻛﺎﺭ ﺧﻮﺍﻫﺪ ﺍﻓﺘﺎﺩ‪ .‬ﺩﺳﺘﺮﺳﻲ ﻣﺴﺘﻤﺮ ﭘﺎﺳﺨﻲ‬

‫ﺑﻪ ﺍﻳﻦ ﻣﺸﻜﻞ ﺍﺳﺖ‪ .‬ﻋﻤﻠﻜﺮﺩ ﺍﻳﻦ ﺗﻜﻨﻮﻟﻮژﻱ ﺑﺪﻳﻦﺻﻮﺭﺕ ﺍﺳﺖ ﻛﻪ ﺍﺑﺘﺪﺍ ﺩﻭ ﻳﺎ ﭼﻨﺪ ﺳﺮﻭﺭ ﻓﻴﺰﻳﻜﻲ ﺩﺭ ﻗﺎﻟﺐ‬

‫ﻳﻚ ﻛﻼﺳﺘﺮ ﻗﺮﺍﺭ ﻣﻲﮔﻴﺮﻧﺪ‪ .‬ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺑﺮ ﺭﻭﻱ ﺳﺮﻭﺭﻫﺎﻱ ﻓﻴﺰﻳﻜﻲ ﻛﻼﺳﺘﺮ ﺗﻮﺯﻳﻊ ﻣﻲﺷﻮﻧﺪ‪ .‬ﺍﮔﺮ ﻳﻜﻲ‬

‫ﺍﺯ ﺳﺮﻭﺭﻫﺎ ﺧﺮﺍﺏ ﺷﻮﺩ‪ ،‬ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺭﻭﻱ ﺁﻥ ﺳﺮﻭﺭ ﺑﻪ ﺳﺮﻭﺭﻫﺎﻱ ﺩﻳﮕﺮ ﻋﻀﻮ ﺁﻥ ﻛﻼﺳﺘﺮ ﻣﻨﺘﻘﻞ‬

‫ﻣﻲﺷﻮﻧﺪ‪ .‬ﺩﺭ ﺍﻳﻦ ﺑﻴﻦ ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺍﺟﺮﺍ ﺷﺪﻩ ﺑﻪ ﺭﻭﻱ ﺳﺮﻭﺭ ﺧﺮﺍﺏ ﺷﺪﻩ ﻗﺒﻞ ﺍﺯ ﺍﻧﺘﻘﺎﻝ ﺭﻳﺴﺖ‬

‫ﻣﻲﺷﻮﻧﺪ‪ .‬ﺗﻤﺎﻡ ﺍﻳﻦ ﺍﻋﻤﺎﻝ ﺑﻄﻮﺭ ﻛﺎﻣﻼ ﺍﺗﻮﻣﺎﺗﻴﻚ ﺍﻧﺠﺎﻡ ﻣﻲﺷﻮﻧﺪ‪ .‬ﺷﻜﻞ ‪ 3-3‬ﺍﻳﻦ ﻣﺴﺌﻠﻪ ﺭﺍ ﺑﻪ ﺗﺼﻮﻳﺮ ﻛﺸﻴﺪﻩ‬

‫ﺍﺳﺖ‪.‬‬

‫ﺷﻜﻞ ‪ . 3 3‬ﻗﺎﺑﻠﻴﺖ ﺩﺳﺘﺮﺳﻲ ﻣﺴﺘﻤﺮ‪ .‬ﺩﺭ ﺣﻴﻦ ﺍﻧﺘﻘﺎﻝ‪ ،‬ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺭﻳﺴﺖ ﻣﻲﺷﻮﻧﺪ‬

‫‪ 13-3‬ﺳﻴﺴﺘﻢ ﺗﺤﻤﻞ ﺧﻄﺎ‪(FT) 1‬‬

‫ﺍﮔﺮ ﺩﺭ ﻳﻚ ﻛﻼﺳﺘﺮ ﻛﻪ ‪ HA‬ﺩﺭ ﺁﻥ ﻓﻌﺎﻝ ﺍﺳﺖ ﻳﻜﻲ ﺍﺯ ﺳﺮﻭﺭﻫﺎﻱ ﻓﻴﺰﻳﻜﻲ ﺑﻪ ﻫﺮ ﺩﻟﻴﻠﻲ ﺍﺯ ﻛﺎﺭ ﺑﻴﻔﺘﺪ‬

‫‪Fault Tolerance 1‬‬

‫‪52‬‬
‫ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺁﻥ‪ ،‬ﻗﺒﻞ ﺍﺯ ﺍﻧﺘﻘﺎﻝ ﺑﻪ ﺳﺮﻭﺭ ﻓﻴﺰﻳﻜﻲ ﺩﻭﻡ ﺭﻳﺴﺖ ﺷﺪﻩ ﻭ ﺑﺮﺍﻱ ﻣﺪﺕ ﻛﻮﺗﺎﻫﻲ ﻛﻪ ﻣﻤﻜﻦ‬

‫ﺍﺳﺖ ﺗﺎ ‪ 3‬ﺩﻗﻴﻘﻪ ﻃﻮﻝ ﺑﻜﺸﺪ ﺧﺎﺭﺝ ﺍﺯ ﺳﺮﻭﻳﺲ ﺧﻮﺍﻫﻨﺪ ﺑﻮﺩ ﻭ ﻗﺎﻋﺪﺗﺎ ﺗﻤﺎﻡ ﺩﺍﺩﻩﻫﺎﻱ ﺫﺧﻴﺮﻩ ﻧﺸﺪﻩ ﺩﺍﺧﻞ‬

‫ﺣﺎﻓﻈﻪ ﺭﻡ ﻧﻴﺰ ﺍﺯﺑﻴﻦ ﺧﻮﺍﻫﺪ ﺭﻓﺖ‪ FT .‬ﺗﻜﻨﻮﻟﻮژﻱ ﺍﺳﺖ ﻛﻪ ﺣﺘﻲ ﺍﻳﻦ ﻣﺴﺌﻠﻪ ﺭﺍ ﻧﻴﺰ ﺣﻞ ﻛﺮﺩﻩ ﺍﺳﺖ‪ .‬ﻋﻤﻠﻜﺮﺩ‬

‫ﺍﻳﻦ ﺗﻜﻨﻮﻟﻮژﻱ ﺑﺪﻳﻦﺻﻮﺭﺕ ﺍﺳﺖ ﻛﻪ ﺩﺭ ﻛﻼﺳﺘﺮﻫﺎﻳﻲ ﻛﻪ ‪ FT‬ﻓﻌﺎﻝ ﺍﺳﺖ ﻳﻚ ﻛﭙﻲ ﺍﺯ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺩﺭ‬

‫ﺣﺎﻝ ﺍﺟﺮﺍ‪ ،‬ﺑﺮ ﺭﻭﻱ ﻳﻚ ﺳﺮﻭﺭ ﺩﻭﻣﻲ ﻧﻴﺰ ﺍﺟﺮﺍ ﻣﻲﺷﻮﺩ‪ .‬ﻫﺮﮔﺎﻩ ﻳﻚ ﺳﺮﻭﺭ ﻓﻴﺰﻳﻜﻲ ﺧﺎﻣﻮﺵ ﺷﻮﺩ‪ ،‬ﻣﺎﺷﻴﻦﻫﺎﻱ‬

‫ﻣﺠﺎﺯﻱ ﻛﻪ ﺁﻳﻨﻪﻭﺍﺭ ﺑﺮ ﺭﻭﻱ ﺳﺮﻭﺭ ﺩﻭﻡ ﺍﺟﺮﺍ ﻣﻲﺷﺪﻧﺪ‪ ،‬ﺑﻼﻓﺎﺻﻠﻪ ﺑﺪﻭﻥ ﻛﻮﭼﻜﺘﺮﻳﻦ ﻭﻗﻔﻪﺍﻱ ﺟﺎﻳﮕﺰﻳﻦ ﻣﻲﺷﻮﻧﺪ؛‬

‫ﻭ ﻛﺎﺭﺑﺮ ﻧﻬﺎﻳﻲ ﻣﺘﻮﺟﻪ ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﻧﺨﻮﺍﻫﺪ ﺷﺪ‪.‬‬

‫ﺑﻌﺪ ﺍﺯ ﺟﺎﻳﮕﺰﻳﻨﻲ ﻳﻚ ﻛﭙﻲ ﺍﺯ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺑﺮ ﺭﻭﻱ ﺳﺮﻭﺭ ﺳﻮﻡ ﺍﻳﺠﺎﺩ ﺧﻮﺍﻫﺪ ﺷﺪ‪ .‬ﺗﻤﺎﻣﻲ ﺍﻳﻦ ﺍﻋﻤﺎﻝ‬

‫ﺑﻄﻮﺭ ﺍﺗﻮﻣﺎﺗﻴﻚ ﺗﻮﺳﻂ ‪ vSphere‬ﺍﻧﺠﺎﻡ ﻣﻲﺷﻮﺩ‪ .‬ﺷﻜﻞ ‪ 4-3‬ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺭﺍ ﺑﻪ ﺗﺼﻮﻳﺮ ﻛﺸﻴﺪﻩ ﺍﺳﺖ‪.‬‬

‫ﺷﻜﻞ ‪ . 4 3‬ﺳﻴﺴﺘﻢ ﺗﺤﻤﻞ ﺧﻄﺎ‪ .‬ﺩﺭ ﺣﻴﻦ ﺍﻧﺘﻘﺎﻝ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺑﺪﻭﻥ ﻭﻗﻔﻪ ﺑﻪ ﻛﺎﺭ ﺧﻮﺩ ﺍﺩﺍﻣﻪ ﺧﻮﺍﻫﻨﺪ ﺩﺍﺩ‬

‫ﺍﮔﺮﻫﺮ ﺩﻭ ﺳﺮﻭﺭ ﺍﺻﻠﻲ ﻭ ﺳﺮﻭﺭ ﺁﻳﻨﻪﺍﻱ ﺧﺮﺍﺏ ﺷﻮﻧﺪ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ‪ ،‬ﺭﻳﺴﺘﺎﺭﺕ ﺷﺪﻩ ﻭ ﻳﻚ ﻛﭙﻲ ﺍﺯ ﺁﻥ ﺑﺮ‬

‫ﺭﻭﻱ ﻳﻚ ﺳﺮﻭﺭ ﺩﺭ ﺩﺳﺘﺮﺱ‪ ،‬ﺩﻭﺑﺎﺭﻩ ﺍﺟﺮﺍ ﺧﻮﺍﻫﺪ ﺷﺪ‪.‬‬

‫‪53‬‬
 ‫‪vSphere Storage API for data protection and 14-3‬‬
‫‪VMware data recovery‬‬
‫ﻳﻚ ﻗﺴﻤﺖ ﻣﻬﻢ ﺍﺯ ﻫﺮ ﺷﺒﻜﻪﺍﻱ ‪-‬ﻧﻪ ﻓﻘﻂ ﻳﻚ ﺯﻳﺮ ﺳﺎﺧﺘﺎﺭ ﻣﺠﺎﺯﻱﺷﺪﻩ‪ -‬ﺍﺳﺘﺮﺍﺗﮋﻱ ﭘﺸﺘﻴﺒﺎﻥﮔﻴﺮﻱ ﺍﺳﺖ ‪.‬‬

‫ﺑﺪﻳﻦ ﻣﻨﻈﻮﺭ ‪ VMware vSphere‬ﺩﻭﻣﻮﻟﻔﻪ ﻛﻠﻴﺪﻱ ﺩﺭﺍﺧﺘﻴﺎﺭ ﻗﺮﺍﺭ ﻣﻲﺩﻫﺪ‪ :‬ﻳﻜﻲ ‪vSphere Storage APIs‬‬

‫‪ for Data Protection‬ﻭ ﻳﺎﺑﻪ ﺍﺧﺘﺼﺎﺭ ‪ VADP‬ﻭ ﺩﻳﮕﺮﻱ ‪ VMware Data Recovery‬ﻳﺎ ‪VADP . VDR‬‬

‫ﻳﻚ ‪ API‬ﺍﺳﺖ ﻛﻪ ﺍﻣﻜﺎﻧﺎﺕ ﻻﺯﻡ ﺑﺮﺍﻱ ﺳﻴﺴﺘﻢﻫﺎﻱ ﭘﺸﺘﻴﺒﺎﻥﮔﻴﺮﻱ ﺭﺍ ﻓﺮﺍﻫﻢ ﻣﻲﻛﻨﺪ‪.‬‬

‫ﺍﻳﻦ ‪ API‬ﺍﺯ ﺍﻧﻮﺍﻉ ﺳﻴﺴﺘﻢﻫﺎﻱ ﭘﺸﺘﻴﺒﺎﻥﮔﻴﺮﻱ ﺍﺯ ﺟﻤﻠﻪ ﭘﺸﺘﻴﺒﺎﻥﮔﻴﺮﻱ ﺳﻄﺢ ﻓﺎﻳﻞ‪ ،1‬ﭘﺸﺘﻴﺒﺎﻥﮔﻴﺮﻱ‬

‫ﺍﻓﺰﺍﻳﺸﻲ‪ ، 2‬ﭘﺸﺘﻴﺒﺎﻥ ﮔﻴﺮﻱ ﺗﻔﺎﺿﻠﻲ‪ ،3‬ﭘﺸﺘﻴﺒﺎﻥ ﮔﻴﺮﻱ ﺍﻳﻤﺞ ﮔﻴﺮﻱ ﻛﺎﻣﻞ‪ 4‬ﻭ ‪...‬‬

‫‪ VADP‬ﻣﺎﻧﻨﺪ ﻳﻚ ﻓﺮﻳﻢﻭﺭﻙ ﻛﺎﺭ ﻣﻲﻛﻨﺪ ﻛﻪ ﺍﻣﻜﺎﻥ ﭘﺸﺘﻴﺒﺎﻥﮔﻴﺮﻱ ﺭﺍ ﻓﺮﺍﻫﻢ ﻣﻲﻛﻨﺪ‪ .‬ﺩﺭ ﻭﺍﻗﻊ ﺷﻤﺎ ﺗﻨﻬﺎ‬

‫ﺑﻪ ﻭﺳﻴﻠﻪ ‪ VADP‬ﻧﻤﻲﺗﻮﺍﻧﻴﺪ ﺍﺯ ﻣﺤﻴﻂ ﻣﺠﺎﺯﻱ ﺧﻮﺩ ﻧﺴﺨﻪ ﭘﺸﺘﻴﺒﺎﻥ ﺗﻬﻴﻪ ﻛﻨﻴﺪ‪ .‬ﺑﻠﻜﻪ ﺷﻤﺎ ﺑﻪ ﻳﻚ ﻛﺎﺭﺑﺮﺩ ﻛﻪ‬

‫ﺍﺯ ﻗﺎﺑﻠﻴﺖ ‪ VADP‬ﭘﺸﺘﻴﺒﺎﻧﻲ ﻣﻲﻛﻨﺪ ﻧﻴﺎﺯ ﺧﻮﺍﻫﻴﺪ ﺩﺍﺷﺖ‪.‬‬

‫ﺗﻌﺪﺍﺩ ﺯﻳﺎﺩﻱ ﻛﺎﺭﺑﺮﺩ ﻛﻪ ﻣﻲ ﺗﻮﺍﻧﺪ ﺑﺎ ‪ VADP‬ﻛﺎﺭ ﻛﻨﺪ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ‪ VMware‬ﺑﺪﻳﻦ ﻣﻨﻈﻮﺭ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬

‫ﭘﺸﺘﻴﺒﺎﻥﮔﻴﺮﻱ ﺧﻮﺩ ﺭﺍ ﺑﺎ ﻧﺎﻡ ‪ (VDR)VMware Data Recovery‬ﺭﺍ ﺍﺭﺍﺋﻪ ﻛﺮﺩﻩ ﺍﺳﺖ ﻛﻪ ﺑﺮﺍﻱ ﻣﺤﻴﻂﻫﺎﻱ‬

‫ﻣﺠﺎﺯﻱ ﻛﻮﭼﻚ ﺗﻬﻴﻪ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬

‫‪ 15-3‬ﻣﻘﺎﻳﺴﻪ ‪Xenserver , Hyper–V , VMware‬‬

‫ﺷﺎﻳﺪ ﻣﻘﺎﻳﺴﻪ ﺑﻴﻦ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﻛﺎﺭ ﺩﺭﺳﺘﻲ ﻧﺒﺎﺷﺪ؛ ﭼﺮﺍ ﻛﻪ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺩﺭ ﺭﻭﺵ‬

‫ﻭ ﺍﻫﺪﺍﻑ ﻣﺘﻔﺎﻭﺕ ﻫﺴﺘﻨﺪ‪ .‬ﻭﻟﻲ ﺩﺭ ﺍﻳﻨﺠﺎ ﻣﺎ ﺑﺮﺍﻱ ﺩﺍﺩﻥ ﻳﻚ ﺩﻳﺪ ﻛﻠﻲ ﻭ ﺩﺭﻙ ﺑﻬﺘﺮ ﻣﻮﺿﻮﻉ ﻳﻚ ﻣﻘﺎﻳﺴﻪ ﺍﺭﺍﺋﻪ‬

‫ﻣﻲﻛﻨﻴﻢ‪ .‬ﺑﺮﺍﻱ ﺍﺭﺍﺋﻪ ﻳﻚ ﻣﻘﺎﻳﺴﻪ ﺑﻬﺘﺮ ﻣﺎ ﻓﻘﻂ ﭘﻠﺘﻔﺮﻡ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﻧﻮﻉ ﻳﻚ ﺭﺍ ﺑﺮﺭﺳﻲ ﻣﻲﻛﻨﻴﻢ‪.‬‬

‫‪File level 1‬‬

‫‪incremental 2‬‬
‫‪differential 3‬‬
‫‪full image 4‬‬

‫‪54‬‬
‫ﻧﻜﺘﻪ ﺍﻭﻝ ﺩﺭ ﻣﻘﺎﻳﺴﻪ ﺍﻳﻦ ﻳﻠﺘﻔﺮﻡ ﻫﺎﻱﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ‪ :‬ﻫﻢ ‪ Microsoft Hyper-V‬ﻭ ﻫﻢ ‪Citrix‬‬

‫‪ Xenserver‬ﺗﻤﺎﻡ ﻋﻤﻠﻴﺎﺕ ﻭﺭﻭﺩﻱ ﺧﺮﻭﺟﻲ ﺧﻮﺩ ﺭﺍ ﺍﺯ ﻃﺮﻳﻖ ﺑﺎﺭﺗﻴﺸﻦ ﻭﺍﻟﺪ ﺍﻧﺠﺎﻡ ﻣﻲﺩﻫﺪ‪ .‬ﻳﻌﻨﻲ ﻫﻤﺎﻥ‬

‫‪ .dom0‬ﺍﻳﻦ ﺭﻭﺵ ﺍﻣﻜﺎﻥ ﺳﺎﺯﮔﺎﺭﻱ ﺑﻴﺸﺘﺮﻱ ﺑﺎ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﺭﺍ ﻓﺮﺍﻫﻢ ﻣﻲﻛﻨﺪ‪ .‬ﺩﺭ ﭘﺎﺭﺗﻴﺸﻦ ﻭﺍﻟﺪ ﻳﻚ‬

‫ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻫﻤﻪﻣﻨﻈﻮﺭﻩ ﻗﺮﺍﺭ ﻣﻲﮔﻴﺮﺩ ﻛﻪ ﺗﻤﺎﻡ ﻋﻤﻠﻴﺎﺕ ﻭﺭﻭﺩﻱ ﺧﺮﻭﺟﻲ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺭﺍ ﺍﻧﺠﺎﻡ‬

‫ﻣﻲﺩﻫﺪ‪ .‬ﻧﺴﺨﻪﻫﺎﻱ ﻗﺒﻠﻲ ‪ Hyper-V‬ﺍﺯ ‪ Server 2003‬ﻭ ﻧﺴﺨﻪ ﺟﺪﻳﺪﺗﺮ ﺍﻳﻦ ﻓﻮﻕ ﻧﺎﻇﺮ ﺍﺯ ‪Server 2008 R2‬‬

‫ﺑﺪﻳﻦ ﻣﻨﻈﻮﺭ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﻛﻨﺪ‪ .‬ﺩﺭ ﻣﻮﺭﺩ ‪ Xenserver‬ﻫﻢ ﻛﺎﺭ ﺑﻪ ﻫﻤﻴﻦ ﺷﻜﻞ ﺍﺳﺖ ﺑﺎ ﺍﻳﻦ ﺗﻔﺎﻭﺕ ﻛﻪ ﺩﺭ‬

‫ﭘﺎﺭﺗﻴﺸﻦ ﻭﺍﻟﺪ ﻳﻚ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻫﻤﻪ ﻣﻨﻈﻮﺭﻩ ﻟﻴﻨﻮﻛﺴﻲ ﻗﺮﺍﺭ ﺩﺍﺭﺩ‪.‬‬

‫ﺍﻣﺎ ﺩﺭ ‪ ESXi‬ﻣﺪﻳﺮﻳﺖ ﻭﺭﻭﺩﻱ‪-‬ﺧﺮﻭﺟﻲ ﺑﻄﻮﺭ ﻛﺎﻣﻞ ﺗﻮﺳﻂ ﻓﻮﻕﻧﺎﻇﺮ ﺍﻧﺠﺎﻡ ﻣﻲﺷﻮﺩ‪ .‬ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺑﺎﻋﺚ‬

‫ﻛﺎﻫﺶ ﺳﺮﺑﺎﺭ ﻭ ﺑﺎﻻ ﺭﻓﺘﻦ ﺑﻬﺮﻩﻭﺭﻱ ﻣﻲﺷﻮﺩ؛ ﻭ ﺍﺯ ﻃﺮﻑ ﺩﻳﮕﺮ ﻣﺠﻤﻮﻋﻪ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻫﺎﻳﻲ ﻛﻪ ﭘﺸﺘﻴﺒﺎﻧﻲ‬

‫ﻣﻲﺷﻮﺩ ﺑﺎﻟﻄﺒﻊ ﻛﻤﺘﺮ ﺧﻮﺍﻫﺪﺑﻮﺩ‪.‬‬

‫ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺗﺤﺖ ﻋﻨﻮﺍﻥ ﺩﺳﺘﻪ ﺑﻨﺪﻱ ﻓﻮﻕ ﻧﺎﻇﺮ ﺑﻪ )ﻓﻮﻕ ﻧﺎﻇﺮ ﻳﻜﭙﺎﺭﭼﻪ ﻭ ﺭﻳﺰ ﻫﺴﺘﻨﺪ( ﺩﺭ ﻓﺼﻞ ﺩﻭﻡ ﻣﻮﺭﺩ‬

‫ﺑﺮﺭﺳﻲ ﻗﺮﺍﺭ ﮔﺮﻓﺘﻪ ﺍﺳﺖ‪ .‬ﻧﻜﺘﻪ ﺩﻭﻡ ﺍﻳﻨﻜﻪ ﻫﺮ ﻳﻚ ﺍﺯ ﻳﻠﺘﻔﺮﻡ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﻣﺰﺍﻳﺎ ﻣﻌﺎﻳﺖ ﻭ ﻛﺎﺭﺑﺮﺩﻫﺎﻱ‬

‫ﺧﻮﺩ ﺭﺍ ﺩﺍﺭﻧﺪ‪.‬‬

‫ﻣﺜﻼ ﺑﺮﺍﻱ ﺩﻳﺘﺎﺳﻨﺘﺮﻫﺎﻱ ﺑﺰﺭگ ‪ vSphere‬ﻣﻨﺎﺳﺐﺗﺮ ﺍﺳﺖ ﻭﻟﻲ ﺑﺮﺍﻱ ﺩﻳﺘﺎﺳﻨﺘﺮﻫﺎﻱ ﻛﻮﭼﻜﺘﺮ ﺷﺎﻳﺪ‬

‫‪ Microsoft hyper-V , Citrix Xenserver‬ﻣﻨﺎﺳﺒﺘﺮ ﺑﺎﺷﺪ‪ .‬ﻭ ﻳﺎ ﻣﺜﻼ ﺷﻤﺎ ﺑﻌﻨﻮﺍﻥ ﻣﺪﻳﺮ ‪ IT‬ﺳﺎﺯﻣﺎﻥ ﻧﻴﺎﺯﻱ ﺑﻪ‬

‫‪ DRS , FT‬ﻭ ﻳﺎ ‪ Storage vMotion‬ﻧﺪﺍﺭﻳﺪ ﻣﻨﺎﺳﺐ ﺗﺮ ﺍﺳﺖ ﺗﺎ ﺍﺯ ‪ Xenserver , Hyper-V‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﻴﺪ‪.‬‬

‫‪55‬‬
‫ﻓﺼﻞ ﭼﻬﺎﺭﻡ‬

‫ﻧﺼﺐ ﻭ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﻣﺠﻤﻮﻋﻪ‬

‫‪WMware vSphere 5‬‬

‫ﻗﺒﻞ ﺍﺯ ﺷﺮﻭﻉ ﻓﺼﻞ ﺟﺪﻳﺪ ﺍﺟﺎﺯﻩ ﺩﻫﻴﺪ ﻣﺮﻭﺭ ﻣﺨﺘﺼﺮﻱ ﺍﺯ ﻓﺼﻮﻝ ﮔﺬﺷﺘﻪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﻢ‪.‬‬

‫ﺩﺭ ﻓﺼﻞ ﺍﻭﻝ ﺩﺭ ﻣﻮﺭﺩ ﺳﻴﺴﺘﻢﻫﺎﻱ ﭘﺮﺩﺍﺯﺵ ﺍﺑﺮﻱ ﺻﺤﺒﺖ ﻛﺮﺩﻳﻢ ﻭ ﺩﻳﺪﻳﻢ ﻛﻪ ﺍﻳﻦ ﺳﻴﺴﺘﻢ ﻫﺎ ﺳﻪ ﻧﻮﻉ‬

‫ﺳﺮﻭﻳﺲ ﻣﺨﺘﻠﻒ ﺍﺭﺍﺋﻪ ﻣﻲﺩﻫﻨﺪ‪ .‬ﺍﻭﻝ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺑﻪ ﻋﻨﻮﺍﻥ ﺳﺮﻭﻳﺲ ﻛﻪ ﻳﻚ ﺭﺍﺑﻂ ﻛﺎﺭﺑﺮﻱ ﺍﺯ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻣﻮﺭﺩ ﻧﻈﺮ‬

‫ﻛﺎﺭﺑﺮﺩ ﺭﺍ ﺍﺧﺘﻴﺎﺭ ﺍﻭ ﻗﺮﺍﺭ ﻣﻲﺩﻫﺪ‪ .‬ﺩﻭﻡ ﺳﻜﻮ ﺑﻌﻨﻮﺍﻥ ﺳﺮﻭﻳﺲ ﺍﺳﺖ ﻛﻪ ﻳﻚ ﻣﺤﻴﻂ ﺗﻮﺳﻌﻪ ﺭﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﻛﺎﺭﺑﺮ‬

‫ﻗﺮﺍﺭ ﻣﻲﺩﻫﻨﺪ‪.‬‬

‫ﻣﻮﺭﺩ ﺳﻮﻡ ﺯﻳﺮ ﺳﺎﺧﺘﺎﺭ ﺑﻪ ﻋﻨﻮﺍﻥ ﺳﺮﻭﻳﺲ ﺍﺳﺖ ﻛﻪ ﺩﺭ ﺁﻥ ﻳﻚ ﺯﻳﺮ ﺳﺎﺧﺘﺎﺭ ﻛﻪ ﻗﺒﻼ ﻣﻲ ﺗﻮﺍﻧﺪ ﻳﻚ ﺳﺮﻭﺭ‬

‫ﻓﻴﺰﻳﻜﻲ ﺑﺎﺷﺪ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﻛﺎﺭﺑﺮ ﻗﺮﺍﺭ ﻣﻴﮕﻴﺮﺩ‪ .‬ﺣﺎﻝ ﺍﮔﺮﺕ ﻋﺪﺍﺩﻱ ﺳﺮﻭﺭ ﻗﻮﻱ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺷﺮﻛﺖ ﺍﺭﺍﺋﻪ ﺩﻫﻨﺪﻩ‬

‫ﺧﺪﻣﺎﺕ ﺍﺑﺮﻱ ﺑﺎﺷﺪ ﻭ ﺗﻌﺪﺍﺩ ﺑﻴﺸﺘﺮﻱ ﻛﺎﺭﺑﺮ ﻛﻪ ﻧﻴﺎﺯﻱ ﺑﻪ ﺳﺮﻭﺭﻫﺎﻱ ﻗﻮﻱ ﻫﻢ ﻧﺪﺍﺷﺘﻪ ﺑﺎﺷﺪ ﺗﻌﺪﺍﺩﻱ ﺍﺯ ﻣﺸﺘﺮﻱ‬

‫‪56‬‬
‫ﻫﺎ ﻛﻪ ﺳﺮﻭﺭﻫﺎ ﺭﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺩﺍﺭﻧﺪ ﻣﻨﺎﺑﻊ ﺭﺍﻫﻮﺭ ﻣﻲ ﺩﻫﻨﺪ ﻭ ﻣﺎﺑﻘﻲ ﻣﺸﺘﺮﻱ ﻫﺎ ﻧﻤﻴﺘﻮﺍﻧﻨﺪ ﺳﺮﻭﻳﺲ ﺑﮕﻴﺮﻧﺪ‪ .‬ﺭﺍﻩ‬

‫ﺣﻞ ﺍﻳﻦ ﻣﺴﺌﻠﻪ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺍﺳﺖ ﻛﻪ ﻣﺎﺩﺭ ﺍﻳﻦ ﻓﺼﻞ ﻭ ﻓﺼﻮﻝ ﺁﺗﻲ ﻳﻚ ﻳﻠﺘﻔﺮﻡ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺭﺍ ﺑﻄﻮﺭﻛﺎﻣﻞ‬

‫ﭘﻴﺎﺩﻩ ﻣﻲﻛﻨﻴﻢ‪.‬‬

‫ﺩﺭ ﻓﺼﻞ ﺩﻭﻡ ﺍﻧﻮﺍﻉ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺭﺍ ﺑﺎ ﺍﺭﺍﺋﻪ ﻳﻚ ﻣﺪﻝ ﻛﺎﻣﻞ ﻣﻌﺮﻓﻲ ﻛﺮﺩﻳﻢ ﻭ ﺩﺭ ﺍﻳﻦ ﺑﻴﻦ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ‬

‫ﭘﺮﺩﺍﺯﺵ ﻛﻪ ﻣﺠﺎﺯﻱ ﺳﺮﻭﺭ ﺍﺯ ﻣﻬﻤﺘﺮﻳﻦ ﻣﻮﺿﻮﻋﺎﺕ ﺍﻳﻦ ﻗﺴﻢ ﺍﺯ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺍﺳﺖ ﺭﺍ ﺑﻄﻮﺭﻣﺨﺘﺼﺮ ﺑﺮﺭﺳﻲ‬

‫ﻛﺮﺩﻳﻢ ‪.‬‬

‫ﺩﺭ ﻓﺼﻞ ﺳﻮﻡ ﻳﻚ ﭘﻠﺘﻔﺮﻡ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺳﺮﻭﺭ ﺑﺎ ﻋﻨﻮﺍﻥ ‪ ،vSphere5‬ﺳﺎﺧﺖ ﺷﺮﻛﺖ ‪ VMware‬ﺭﺍ ﻣﻌﺮﻓﻲ‬

‫ﻛﺮﺩﻳﻢ‪ .‬ﻗﺎﺑﻠﻴﺖﻫﺎ‪ ،‬ﻣﺰﺍﻳﺎ‪ ،‬ﻣﻌﺎﻳﺖ ﻭ ﻣﻮﻟﻔﻪﻫﺎﻱ ﺗﺸﻜﻴﻞ ﺩﻫﻨﺪﻩ ﺍﻳﻦ ﻣﺠﻤﻮﻋﻪ ﺭﺍ ﻣﻌﺮﻓﻲ ﻛﺮﺩﻳﻢ؛ ﻭ ﺩﺭ ﺍﻧﺘﻬﺎ ﻫﻢ‬

‫ﻣﻘﺎﻳﺴﻪﺍﻱ ﻛﻮﺗﺎﻩ ﺑﻴﻦ ‪ vSphere‬ﻭ ﺳﺎﻳﺮ ﭘﻠﺘﻔﺮﻡﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ﺩﺍﺷﺘﻴﻢ‪.‬‬

‫ﺩﺭ ﺍﻳﻦ ﻓﺼﻞ ﻭ ﻓﺼﻮﻝ ﺑﺎﻗﻲ ﻣﺎﻧﺪﻩ ﻫﻢ ﻧﺤﻮﻩ ﺭﺍﻩﺍﻧﺪﺍﺯﻱ ﭘﻠﺘﻔﺮﻡ ﻣﺠﺎﺯﻱ‪ vSphere‬ﺭﺍ ﺧﻮﺍﻫﻴﻢ ﮔﻔﺖ‪.‬‬

‫ﺳﺎﺧﺘﺎﺭ ﻛﻠﻲ ﻣﺠﻤﻮﻋﻪ ‪ vSphere‬ﻭ ﻣﻮﻟﻔﻪ ﻫﺎﻱ ﺍﺳﺎﺳﻲ ﺗﺸﻜﻴﻞ ﺩﻫﻨﺪﻩ ﺁﻥ ﻭ ﺳﺎﺧﺘﺎﺭ ﻛﻠﻲ ﺍﻳﻦ ﻣﺠﻤﻮﻋﻪ ﺩﺭ‬

‫ﺷﻜﻞ ‪ 1-4‬ﻗﺎﺑﻞ ﻣﺸﺎﻫﺪﻩ ﺍﺳﺖ‪.‬‬

‫ﺷﻜﻞ ‪ . 1 4‬ﺳﺎﺧﺘﺎﺭ ﻛﻠﻲ ﻣﺠﻤﻮﻋﻪ ‪vSphere‬‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﻓﺼﻞ ﻗﺒﻞ ﻧﻴﺰ ﺍﺷﺎﺭﻩ ﺷﺪ ﺑﺮ ﺭﻭﻱ ﻣﻴﺰﺑﺎﻥﻫﺎ )ﺳﺮﻭﺭﻫﺎﻱ ﻓﻴﺰﻳﻜﻲ( ‪ ESXi‬ﻧﺼﺐ ﻣﻲﺷﻮﺩ ‪.‬‬

‫‪57‬‬
‫ﻳﻚ ﺳﺮﻭﺭ ﺗﺤﺖ ﻋﻨﻮﺍﻥ ‪ vCenter Server‬ﻧﻘﺶ ﻣﺪﻳﺮﻳﺖ ﻣﺠﻤﻮﻋﻪ ﺭﺍ ﺑﺮ ﻋﻬﺪﻩ ﺩﺍﺭﺩ‪ .‬ﺍﺑﺰﺍﺭﻫﺎﻱ ﻣﺪﻳﺮﻳﺘﻲ ﻛﻪ‬

‫ﺗﻮﺳﻂ ‪ vCenter Server‬ﺍﺭﺍﺋﻪ ﻣﻲﺷﻮﺩ‪ ،‬ﺗﻮﺳﻂ ‪ vSphere cilent‬ﺩﺭ ﺩﺳﺘﺮﺱ ﺧﻮﺍﻫﺪﺑﻮﺩ‪ .‬ﺍﻟﺒﺘﻪ ﺗﻮﺳﻂ‬

‫‪ vSphere Client‬ﻭ ﺣﺘﻲ ﺑﺪﻭﻥ ﻛﻤﻚ ‪ vCenter Server‬ﻭ ﻣﺴﺘﻘﻴﻤﺎ ﻣﻲﺗﻮﺍﻥ ﺑﻪ ‪ ESXi‬ﻫﺎ ﻣﺘﺼﻞ ﺷﺪ ﻭ ﻫﺮ‬

‫ﻳﻚ ﺍﺯ ﺁﻧﻬﺎ ﺭﺍ ﺑﻄﻮﺭ ﻣﺠﺰﺍ ﻣﺪﻳﺮﻳﺖ ﻭ ﺑﺮﻧﺎﻣﻪﺭﻳﺰﻱ ﻛﺮﺩ‪ .‬ﻛﺎﻣﻼ ﻭﺍﺿﺢ ﺍﺳﺖ ﻛﻪ ﺩﺭ ﺍﻳﻦ ﺻﻮﺭﺕ ﺑﺴﻴﺎﺭﻱ ﺍﺯ‬

‫ﺍﺑﺰﺍﺭﻫﺎﻱ ﻣﺪﻳﺮﻳﺘﻲ ﺩﺭ ﺩﺳﺘﺮﺱ ﻧﺨﻮﺍﻫﺪ ﺑﻮﺩ ‪.‬‬

‫‪ 1-4‬ﻧﺼﺐ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﻭ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ‪ESXi‬‬

‫ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ ﺗﻮﺿﻴﺤﺎﺕ ﺍﺭﺍﺋﻪ ﺷﺪﻩ ﺍﻭﻟﻴﻦ ﻣﺮﺣﻠﻪ ﺩﺭ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﺍﻳﻦ ﻣﺠﻤﻮﻋﻪ ﻧﺼﺐ ‪ ESXi‬ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪ .‬ﻳﻚ‬

‫ﻧﻜﺘﻪ ﻣﻬﻢ ﻛﻪ ﻗﺒﻞ ﺍﺯ ﺷﺮﻭﻉ ﻧﺼﺐ ‪ESXi‬ﻫﺎ ﺑﺎﻳﺴﺘﻲ ﺑﻪ ﺁﻥ ﺍﺷﺎﺭﻩ ﻛﻨﻴﻢ ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ‪ :‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﻓﺼﻞ‬

‫ﻗﺒﻞ ﻧﻴﺰ ﺑﻪ ﺁﻥ ﺍﺷﺎﺭﻩ ﺷﺪ ﻓﻮﻕ ﻧﺎﻇﺮ ‪ ESXi‬ﺍﺯ ﻧﻮﻉ ﻳﻜﭙﺎﺭﭼﻪ ﺑﻮﺩﻩ ﻛﻪ ﺑﺎﻳﺴﺘﻲ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻫﺎﻱ ﺳﺨﺖﺍﻓﺰﺍﺭﻫﺎﻳﻲ ﻛﻪ‬

‫ﺑﺎ ﺁﻧﻬﺎ ﻛﺎﺭ ﻣﻲﻛﻨﺪ ﺭﺍﺩﺭ ﺧﻮﺩ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪ .‬ﺑﻨﺎﺑﺮﺍﻳﻦ ‪ ESXi‬ﺑﺮ ﺭﻭﻱ ﻫﺮ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﻧﻤﻲ ﺗﻮﺍﻧﺪ ﻧﺼﺐ ﻭ ﺍﺟﺮﺍ‬

‫ﺷﻮﺩ‪ .‬ﺍﻟﺒﺘﻪ ﺍﻳﻦ ﻣﺴﺌﻠﻪ ﻧﮕﺮﺍﻧﻲ ﻋﻤﺪﻩ ﺍﻱ ﻧﻴﺴﺖ‪ ،‬ﭼﺮﺍ ﻛﻪ ﺍﻛﺜﺮ ﺳﺮﻭﺭﻫﺎ ﺑﺎ ﻗﻄﻌﺎﺕ ﺩﺍﺧﻠﻲ ﺁﻧﻬﺎ ﺗﻮﺳﻂ ‪ESXi‬ﻫﺎ‬

‫ﭘﺸﺘﻴﺒﺎﻧﻲ ﻣﻲﺷﻮﻧﺪ‪ .‬ﭘﺲ ﻻﺯﻡﺍﺳﺖ ﻗﺒﻞ ﺍﺯ ﺧﺮﻳﺪ ﺳﺮﻭﺭﻫﺎ ﻭ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻫﺎﻱ ﻣﻮﺭﺩ ﻧﻴﺎﺯ‪ ،‬ﺳﺮﻱ ﺑﻪ ﺳﺎﻳﺖ‬

‫‪ VMware‬ﺑﺰﻧﻴﺪ ﺗﺎ ﻟﻴﺴﺖ ﻗﻄﻌﺎﺕ ﻭ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻫﺎﻱ ﺳﺎﺯﮔﺎﺭ ﺑﺎ ‪ ESXi‬ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﻛﻨﻴﺪ‪.‬‬

‫‪ 1-1-4‬ﻧﺼﺐ ‪ESXi‬‬

‫‪ ESXi‬ﺑﻪ ﺳﻪ ﻃﺮﻳﻖ ﻗﺎﺑﻞ ﻧﺼﺐ ﺍﺳﺖ‪:‬‬

‫‪ Interactive Installation‬ﻳﺎ ﻧﺼﺐ ﺗﻌﺎﻣﻠﻲ ‪ Unattended Installtien ،‬ﻳﺎ ﻧﺼﺐ ﺧﻮﺩﻛﺎﺭ ﻭ ﻣﻮﺭﺩ ﺁﺧﺮ ﻛﻪ‬

‫ﺩﺭ ﻭﺍﻗﻊ ﺑﺎﺭﮔﺬﺍﺭﻱ ‪ ESXi‬ﺩﺍﺧﻞ ﺭﻡ ﺳﻴﺴﺘﻢ ﻓﻴﺰﻳﻜﻲ ﺩﺭ ﻗﺎﻟﺐ ﻳﻚ ‪ imag‬ﺑﻮﺩﻩ ﻭ ﻧﺼﺐ ﺩﺭ ﻛﺎﺭ ﻧﻴﺴﺖ ﻭ ﺍﻳﻦ‬

‫ﺭﻭﺵ ﺭﺍ ‪ Stateless Provisioning‬ﻣﻲ ﻧﺎﻣﻨﺪ‪.‬‬

‫‪58‬‬
 ‫ﺩﺭ ﺍﻳﻦ ﻧﻮﺷﺘﻪ ﺑﻪ ﺟﻬﺖ ﺍﺧﺘﺼﺎﺭ ﻣﺎ ﻓﻘﻂ ﺭﻭﺵ ﺍﻭﻝ‪ ،‬ﻳﻌﻨﻲ ﻧﺼﺐ ﺗﻌﺎﻣﻠﻲ ﺭﺍ ﺑﺮﺭﺳﻲ ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩ‪.‬‬

‫ﺑﺮﺍﻱ ﻧﺼﺐ ‪ ESXi‬ﺍﺑﺘﺪﺍ ‪ CD‬ﺣﺎﻭﻱ ﻓﺎﻳﻞ ﻧﺼﺐ ﺭﺍ ﺩﺭ ﺩﺍﺧﻞ ﺳﺮﻭﺭ ﻗﺮﺍﺭ ﺩﻫﻴﺪ‪ .‬ﺳﻴﺴﺘﻢ ﺭﺍ ﺭﻭﺷﻦ ﻧﻤﻮﺩﻩ ﻭ‬

‫‪ boot‬ﺳﻴﺴﺘﻢ ﺭﺍ ‪ CD-ROM‬ﻗﺮﺍﺭ ﺩﻫﻴﺪ ﻭ ﺍﺯ ﻃﺮﻳﻖ ‪ ، CD-ROM‬ﺑﻮﺕ ﺷﻮﻳﺪ‪.‬‬

‫ﺍﻭﻟﻴﻦ ﻣﻮﺭﺩﻱ ﻛﻪ ﺑﺎ ﺁﻥ ﻣﻮﺍﺟﻪ ﺧﻮﺍﻫﻴﺪ ﺷﺪ‪ .‬ﺗﺼﻮﻳﺮﻱ ﺷﺒﻴﻪ ﺑﻪ ﺷﻜﻞ ‪ 2-4‬ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪ .‬ﺑﺮﺍﻱ ﺍﺩﺍﻣﻪ ﮔﺰﻳﻨﻪ‬

‫ﺍﻭﻝ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ﻭ ﺍﻳﻨﺘﺮ ﺭﺍ ﺑﻔﺸﺎﺭﻳﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 2 4‬ﺻﻔﺤﻪ ﺷﺮﻭﻉ ﻧﺼﺐ ‪ESXi‬‬

‫ﭘﺲ ﺍﺯ ﻣﺪﺗﻲ ﺑﺎ ﺻﻔﺤﻪ ﺧﻮﺵﺁﻣﺪﮔﻮﻳﻲ ﻣﻮﺍﺟﻪ ﺧﻮﺍﻫﺪ ﺷﺪ‪ .‬ﺑﺎ ﺯﺩﻥ ﺍﻳﻨﺘﺮ ﺍﺩﺍﻣﻪ ﺩﻫﻴﺪ‪.‬‬

‫ﺳﭙﺲ ﺑﻪ ﻣﻮﺍﻓﻘﺖﻧﺎﻣﻪ ﺧﻮﺍﻫﻴﺪ ﺭﺳﻴﺪ ﻛﻪ ﺑﺮﺍﻱ ﺗﺎﺋﻴﺪ ﻭ ﺍﺩﺍﻣﻪ ‪ F11‬ﺭﺍ ﺑﺰﻧﻴﺪ‪.‬‬

‫ﺩﺭ ﺍﺩﺍﻣﻪ ﻫﺎﺭﺩﺩﻳﺴﻚﻫﺎﻱ ﺩﺭ ﺩﺳﺘﺮﺱ ﺑﺮﺍﻱ ﺍﻧﺘﺨﺎﺏ ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﺧﻮﺍﻫﻨﺪ ﺷﺪ‪ .‬ﺍﮔﺮ ﺗﻨﻬﺎ ﺩﻳﺴﻚ ﻣﺤﻠﻲ‬

‫ﺩﺍﺧﻞ ﺳﻴﺴﺘﻢ ﻣﻮﺟﻮﺩ ﺑﺎﺷﺪ ﺗﺼﻮﻳﺮﻱ ﺷﺒﻴﻪ ﺷﻜﻞ ‪ 3-4‬ﻭ ﺍﮔﺮ ﻋﻼﻭﻩ ﺑﺮ ﺩﻳﺴﻚﻫﺎﻱ ﻣﺤﻠﻲ ﺩﻳﺴﻚﻫﺎﻱ ﺭﻳﻤﻮﺕ‬

‫ﺩﺭ ﺩﺳﺘﺮﺱ ﺑﺎﺷﺪ‪ ،‬ﺗﺼﻮﻳﺮﻱ ﺷﺒﻴﻪ ﺑﻪ ﺷﻜﻞ ‪ 4-4‬ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﺧﻮﺍﻫﺪﺷﺪ‪.‬‬

‫‪59‬‬
 ‫ﺷﻜﻞ ‪ . 3 4‬ﺍﻧﺘﺨﺎﺏ ﺩﻳﺴﻚ ﺑﺮﺍﻱ ﻧﺼﺐ ‪ESXi‬‬

‫ﭘﺲ ﺍﺯ ﺍﻧﺘﺨﺎﺏ ﺩﻳﺴﻚ ﻣﻮﺭﺩ ﻧﻈﺮ ﺑﺮﺍﻱ ﻧﺼﺐ ‪ ،ESXi‬ﺑﺎ ﺯﺩﻥ ‪ Enter‬ﺑﻪ ﻣﺮﺣﻠﻪ ﺑﻌﺪ ﺑﺮﻭﻳﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 4 4‬ﺍﻧﺘﺨﺎﺏ ﺩﻳﺴﻚ ﺑﺮﺍﻱ ﻧﺼﺐ ‪ESXi‬‬

‫ﺩﺭ ﻣﺮﺣﻠﻪ ﺑﻌﺪ ﺍﮔﺮ ﺑﺮ ﺭﻭﻱ ﺩﻳﺴﻚ ﺍﻧﺘﺨﺎﺏ ﺷﺪﻩ ﺍﺯ ﻗﺒﻞ ‪ ESXi‬ﻧﺼﺐ ﺑﻮﺩﻩ ﺑﺎﺷﺪ‪ ،‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺷﻜﻞ‬

‫‪ 5-4‬ﻧﺸﺎﻥ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪ ،‬ﺳﻪ ﺍﻣﻜﺎﻥ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺷﻤﺎ ﻗﺮﺍﺭ ﺧﻮﺍﻫﺪ ﮔﺮﻓﺖ‪:‬‬

‫ﺍﻭﻝ ‪ Upgrade ESXi , preserve VMFS datastore‬ﻛﻪ ﻧﺴﺨﻪ ﻣﻮﺟﻮﺩ ﺭﺍ ﺑﻪ ‪ ESXi5‬ﺍﺭﺗﻘﺎ ﻣﻲﺩﻫﺪ ﻭ‬

‫ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻗﺒﻠﻲ ﻛﻪ ﺑﺮ ﺭﻭﻱ ﺩﻳﺴﻚ ﻗﺮﺍﺭ ﺩﺍﺭﻧﺪ ﺣﻔﻆ ﺧﻮﺍﻫﻨﺪ ﺷﺪ‪.‬‬

‫ﺩﻭﻡ ‪ Install ESXi , preserve VMFS datastore‬ﻛﻪ ﻧﺴﺨﻪ ﻗﺒﻠﻲ ﺭﺍ ﭘﺎﻙ ﻛﺮﺩﻩ ﻭ ﻧﺴﺨﻪ ﺟﺪﻳﺪ ﺭﺍ‬

‫ﺟﺎﻳﮕﺰﻳﻦ ﺁﻥ ﻣﻲﻛﻨﺪﻭﻟﻲ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻛﻤﺎﻛﺎﻥ ﺑﺎﻗﻲ ﺧﻮﺍﻫﻨﺪ ﻣﺎﻧﺪ‪.‬‬

‫ﺳﻮﻡ ‪ Install ESXi , overwrite VMFS dalastore‬ﻛﻪ ﻛﻠﻴﻪ ﺍﻃﻼﻋﺎﺕ ﻣﻮﺟﻮﺩ ﺑﺮ ﺩﻳﺴﻚ ﻭﺣﺘﻲ‬

‫ﻓﺎﻳﻠﻬﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺭﺍ ﭘﺎﻙ ﺧﻮﺍﻫﺪ ﻛﺮﺩ ﻭ ‪ ESXi‬ﺭﺍ ﻧﺼﺐ ﻣﻲﻛﻨﺪ‪.‬‬

‫‪60‬‬
 ‫ﺷﻜﻞ ‪ . 5 4‬ﺍﻧﺘﺨﺎﺏ ﻧﺤﻮﻩ ﺗﺨﺼﻴﺺ ﺩﻳﺴﻚ ﺳﺨﺖ ﺑﺮﺍﻱ ﻧﺼﺐ ‪ESXi‬‬

‫ﺣﺎﻝ ﻣﻮﺭﺩ ﻣﻨﺎﺳﺐ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ﻭ ‪ Enter‬ﺭﺍ ﺑﻔﺸﺎﺭﻳﺪ ﺗﺎ ﺑﻪ ﻣﺮﺣﻠﻪ ﺑﻌﺪ ﺑﺮﻭﻳﺪ‪.‬‬

‫ﺯﺑﺎﻥ ﻛﻴﺒﺮﺩ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ‪ Enter‬ﺭﺍ ﺑﺰﻧﻴﺪ‪.‬‬

‫ﺩﺭ ﺍﻳﻦﻣﺮﺣﻠﻪ ﻫﻢ ﭘﺴﻮﺭﺩ ﺩﻟﺨﻮﺍﻩ ﻭ ﺍﻟﺒﺘﻪ ﺑﺎ ﻃﻮﻝ ﺣﺪﺍﻗﻞ ‪ 7‬ﻛﺎﺭﺍﻛﺘﺮ ﻭﺍﺭﺩ ﻛﺮﺩﻩ ﻭ ﺑﺎ ﺯﺩﻥ ﺍﻳﻨﺘﺮ ﺍﺯ ﺍﻳﻦ‬

‫ﻣﺮﺣﻠﻪ ﺧﺎﺭﺝ ﺷﻮﻳﺪ ﺩﺭ ﺍﻧﺘﻬﺎ ﺑﺎ ﺯﺩﻥ ﺍﻳﻨﺘﺮ ﺳﻴﺴﺘﻢ ﺭﺍ ﻭﻳﺴﺘﺎﺭﺕ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫‪ 2-1-4‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺍﻭﻟﻴﻪ ‪ESXi‬‬

‫ﭘﺲ ﺍﺯ ﻧﺼﺐ ‪ ESXi‬ﺑﺎ ﺻﻔﺤﻪﺍﻱ ﻣﺸﺎﺑﻪ ﺷﻜﻞ ‪ 6-4‬ﻣﻮﺍﺟﻪ ﺧﻮﺍﻫﻴﺪ ﺷﺪ‪ .‬ﺑﺎ ﺯﺩﻥ ﻛﻠﻴﺪ ‪ F2‬ﻭﺍﺭﺩ ﺗﻨﻈﻴﻤﺎﺕ‬

‫ﺍﻭﻟﻴﻪ ﻭ ﺍﺳﺎﺳﻲ ‪ ESXi server‬ﻣﻲﺷﻮﻳﺪ‪ .‬ﺍﺑﺘﺪﺍ ﺟﻬﺖ ﻭﺭﻭﺩ ﻧﺎﻡ ﻛﺎﺭﺑﺮﻱ ﻭ ﭘﺴﻮﺭﺩ ﺳﻴﺴﺘﻢ ﺭﺍ ﻭﺍﺭﺩ ﻛﻨﻴﺪ‪.‬ﺩﺭ ﺍﻳﻨﺠﺎ‬

‫ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﺑﺎ ﻛﺎﺭﺑﺮ ‪ root‬ﻭ ﭘﺴﻮﺭﺩﻱ ﻛﻪ ﺩﺭ ﻫﻨﮕﺎﻡ ﻧﺼﺐ ﻭﺍﺭﺩ ﻛﺮﺩﻳﺪ ﺑﻪ ﺳﻴﺴﺘﻢ ‪ login‬ﻛﻨﻴﺪ‪.‬‬

‫‪61‬‬
 ‫ﺷﻜﻞ ‪ . 6 4‬ﺍﻭﻟﻴﻦ ﺗﺼﻮﻳﺮ ‪ ESXi‬ﭘﺲ ﺍﺯ ﻧﺼﺐ‬

‫ﺩﺭ ﺑﺨﺶ ‪ configure password‬ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﺭﻣﺰ ﻭﺭﻭﺩ ﺧﻮﺩ ﺭﺍ ﺗﻐﻴﻴﺮ ﺩﻫﻴﺪ‪.‬‬

‫ﺩﺭ ﺑﺨﺶ ‪ configure management network‬ﻣﻲﺗﻮﺍﻧﻴﺪ ﺗﻨﻈﻴﻤﺎﺕ ﺷﺒﻜﻪ ﺳﻴﺴﺘﻢ ﺍﺯ ﺟﻤﻠﻪ ﺍﻧﺘﺨﺎﺏ ‪، IP‬‬

‫ﺗﻨﻈﻴﻢ ‪ DNS‬ﻭ ‪ ...‬ﺭﺍ ﺍﻧﺠﺎﻡ ﺩﺍﺩ‪.‬‬

‫ﺩﺭ ﺑﺨﺶ ‪ test management network‬ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﺑﻪ ﻛﻤﻚ ﺳﺮﻭﻳﺲ ‪ ping‬ﺍﺯ ﺍﺗﺼﺎﻻﺕ ﺑﻴﻦ ﺳﻴﺴﺘﻢﻫﺎﻱ‬

‫ﻣﺘﺼﻞ ﺑﻪ ﺷﺒﻜﻪ ﺍﻃﻤﻴﻨﺎﻥ ﺣﺎﺻﻞ ﻛﻨﻴﺪ‪.‬‬

‫ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ restor network setting‬ﻣﻲﺗﻮﺍﻥ ﺗﻨﻈﻴﻤﺎﺕ ﺷﺒﻜﻪ ﺭﺍ ﺑﻪ ﺣﺎﻟﺖ ﺍﻭﻟﻴﻪ ﭘﺲ ﺍﺯ ﻧﺼﺐ ﺩﺭﺁﻭﺭﺩ‪.‬‬

‫ﺯﺑﺎﻥ ﺻﻔﺤﻪ ﻛﻠﻴﺪ ﺭﺍ ﻣﻲﺗﻮﺍﻥ ﺩﺭ ﺑﺨﺶ ‪ configure keyboard‬ﺗﻐﻴﻴﺮ ﺩﺍﺩ‪.‬‬

‫ﺩﺭﺑﺨﺶ ‪ trouble shooting‬ﻣﻲﺗﻮﺍﻧﻴﺪ ﺗﻨﻈﻴﻤﺎﺕ ﻣﺮﺑﻮﻁ ﺑﻪ ﻋﻴﺐ ﻳﺎﺑﻲ‪ ،‬ﺍﺯ ﺟﻤﻠﻪ ﻓﻌﺎﻝ ﻭﻏﻴﺮ ﻓﻌﺎﻝ ﻛﺮﺩﻥ‬

‫ﻭﺍﺳﻂ ﻓﺮﻣﺎﻥ ﻭ ‪ ...‬ﺭﺍ ﺍﻧﺠﺎﻡ ﺩﻫﻴﺪ‪.‬‬

 ‫ﺩﺭ ﺑﺨﺶ ‪ viewsystem logs‬ﻣﻲﺗﻮﺍﻧﻴﺪ ﺍﺗﻔﺎﻗﺎﺕ‪ 1‬ﺛﺒﺖ ﺷﺪﻩ‪ 2‬ﺳﻴﺴﺘﻢ ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﻛﻨﻴﺪ‪.‬‬

‫ﻭ ﺩﺭ ﻧﻬﺎﻳﺖ ﺗﻮﺳﻂ ‪ reset system configuration‬ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﺗﻨﻈﻴﻤﺎﺕ ﻛﻞ ‪ ESXi‬ﺭﺍ ﺑﻪ ﺣﺎﻟﺖ ﺍﻭﻟﻴﻪ ﭘﺲ‬

‫ﺍﺯ ﻧﺼﺐ ﺑﺎﺯﮔﺮﺩﺍﻧﻴﺪ‪.‬‬

‫ﻫﻤﭽﻨﻴﻦ ﺑﻮﺳﻴﻠﻪ ﻛﻠﻴﺪ ‪ F12‬ﻣﻲﺗﻮﺍﻧﻴﺪ ﺳﻴﺴﺘﻢ ﺭﺍ ﺭﻳﺴﺘﺎﺭﺕ ﻭ ﻳﺎ ﺧﺎﻣﻮﺵ ﻛﻨﻴﺪ‪.‬‬

‫‪ 2-4‬ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ‪vCenter Server‬‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻗﺒﻼ ﻫﻢ ﺍﺷﺎﺭﻩ ﺷﺪ ﺑﺮﺍﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ESXi‬ﻫﺎ ﻭ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺑﺮ ﺭﻭﻱ ﺁﻧﻬﺎ ﻭ‬

‫ﻫﻤﭽﻨﻴﻦ ﺑﻬﺮﻩﺑﺮﺩﺍﺭﻱ ﺍﺯ ﺗﻤﺎﻣﻲ ﺍﻣﻜﺎﻧﺎﺕ ‪ vSphere‬ﺑﺎﻳﺴﺘﻲ ﺁﻧﻬﺎ ﺭﺍ ﺗﺤﺖ ﻣﺪﻳﺮﻳﺖ ‪ vCenter Server‬ﺩﺭﺁﻭﺭﺩ ‪.‬‬

‫ﺩﺭ ﺍﻳﻦ ﻗﺴﻤﺖ ‪ vCenter Server‬ﺭﺍ ﻧﺼﺐ ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩ؛ ﻭ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺁﻥ ﺭﺍ ﺑﻪ ﻓﺼﻮﻝ ﺍﺗﻲ ﻣﻮﻛﻮﻝ ﻣﻲﻛﻨﻴﻢ ‪.‬‬

‫ﻭ ﺍﻟﺒﺘﻪ ﻗﺒﻞ ﺍﺯ ﻧﺼﺐ ﻛﻤﻲ ﺩﺭ ﻣﻮﺭﺩ ﺁﻥ ﺗﻮﺿﻴﺤﺎﺗﻲ ﺍﺭﺍﺋﻪ ﺧﻮﺍﻫﻴﻢ ﺩﺍﺩ‪.‬‬

‫‪ 1-2-4‬ﺳﺎﺧﺘﺎﺭ ﻭ ﺳﺮﻭﻳﺲ ﻫﺎﻱ ‪vCenter Server‬‬

‫ﻫﻤﺎﻧﻄﻮﺭﻛﻪ ﻗﺒﻼ ﻫﻢ ﮔﻔﺘﻪ ﺷﺪ ‪vCenter Server‬ﺭﺍ ﻳﻚ ﻛﺎﺭﺑﺮﺩ ﺗﺤﺖ ﻭﻳﻨﺪﻭﺯ ﺑﻮﺩﻩ ﻛﻪ ﻭﻇﻴﻔﻪ ﻣﺪﻳﺮﻳﺖ‬

‫ﻣﻴﺰﺑﺎﻧﻬﺎ ‪ ESXi‬ﻭﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺳﺎﺧﺘﻪ ﺷﺪﻩ ﺑﺮ ﺭﻭﻱ ﺁﻧﻬﺎ ﺭﺍ ﺑﺮ ﻋﻬﺪﻩ ﺩﺍﺭﺩ‪ .‬ﺍﻟﺒﺘﻪ ﻳﻚ‪ appliance‬ﭘﺎﻳﻪ‬

‫ﻟﻴﻨﻮﻛﺴﻲ )‪ (Suse-linux‬ﻫﻤﺮﺍﻩ ﻣﺠﻤﻮﻋﻪ‪ vSphere‬ﺍﺭﺍﺋﻪ ﻣﻲﺷﻮﺩ ﻛﻪ ﻣﺤﺪﻭﺩﻳﺖﻫﺎﻳﻲ ﻧﺴﺒﺖ ﺑﻪ ‪vCenter‬‬

‫‪ Server‬ﻭﻳﻨﺪﻭﺯﻱ ﺩﺍﺭﺩ‪.‬‬

‫ﺑﻪ ﻃﻮﺭ ﻛﻠﻲ ﻭﻇﺎﻳﻒ ﺍﺻﻠﻲ ‪vCenter Server‬ﺭﺍ ﻣﻲﺗﻮﺍﻥ ﺍﻳﻨﮕﻮﻧﻪ ﺧﻼﺻﻪ ﻛﺮﺩ‪.‬‬

‫ﻣﺪﻳﺮﻳﺖ ﻣﻨﺎﺑﻊ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ ESXi‬ﻭ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ‬ ‫‪-‬‬

‫‪1‬‬
‫ﻣﺪﻳﺮﻳﺖ ﻗﺎﻟﺐﻫﺎﻱ ﺁﻣﺎﺩﻩ‬ ‫‪-‬‬

‫‪event 1‬‬
‫‪logged 2‬‬

‫‪63‬‬
 ‫‪2‬‬
‫ﺗﻮﺳﻌﻪ ﻭ ﺁﻣﺎﺩﻩ ﺳﺎﺯﻱ ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻣﺠﺎﺯﻱ‬ ‫‪-‬‬

‫ﻣﺪﻳﺮﻳﺖ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ‬ ‫‪-‬‬

‫‪3‬‬
‫ﺯﻣﺎﻧﺒﻨﺪﻱ ﻭﻇﺎﻳﻒ‬ ‫‪-‬‬
‫‪5‬‬
‫ﺁﻣﺎﺭﮔﻴﺮﻱ‪ 4‬ﻭ ﺛﺒﺖ ﻭﻗﺎﻳﻊ‬ ‫‪-‬‬

‫ﺁﻻﺭﻡﻫﺎ ﻭ ﻣﺪﻳﺮﻳﺖ ﺭﻭﻳﺪﺍﺩﻫﺎ‬ ‫‪-‬‬

‫ﻣﺪﻳﺮﻳﺖ ﻣﻴﺰﺑﺎﻥﻫﺎﻱ ‪ESXi‬‬ ‫‪-‬‬

‫ﻣﻮﺍﺭﺩ ﺑﺎﻻ ﺑﺼﻮﺭﺕ ﻧﻤﻮﺩﺍﺭﻱ ﺩﺭ ﺷﻜﻞ ‪ 7-4‬ﻧﺸﺎﻥ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﻧﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 7 4‬ﺳﺮﻭﻳﺲﻫﺎﻱ ‪vCenter Server‬‬

‫ﻳﻚ ﺳﺮﻭﻳﺲ ﻣﻬﻢ ﻛﻪ ﺩﺭ ﺷﻜﻞ ﺑﺎﻻ ﺑﻪ ﺁﻥ ﺍﺷﺎﺭﻩ ﻧﺸﺪ ﻣﺪﻳﺮﻳﺖ ﻣﺘﻤﺮﻛﺰ ﺣﺴﺎﺏ ﻫﺎﻱ ﻛﺎﺭﺑﺮﺩﻱ ﺍﺳﺖ‪.‬‬

‫‪templates 1‬‬
‫‪VM Deployment 2‬‬
‫‪Task scheduler 3‬‬
‫‪Statistics 4‬‬
‫‪Logging 5‬‬

‫‪64‬‬
 ‫ﺑﺮﺍﻱ ﺩﺭﻙ ﺍﻫﻤﻴﺖ ﺍﻳﻦ ﺳﺮﻭﻳﺲ ﺑﻪ ﻣﺜﺎﻝ ﺯﻳﺮ ﺗﻮﺟﻪ ﻛﻨﻴﺪ‪.‬‬

‫ﻓﺮﺽ ﻛﻨﻴﺪ ﺻﺪﻫﺎ ﻣﻴﺰﺑﺎﻥ ‪ ESXi‬ﺗﺤﺖ ﻣﺪﻳﺮﻳﺖ ﻳﻚ ‪ vCenter‬ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﺪ‪ .‬ﺍﮔﺮ ﭼﻨﺪﻳﻦ ﻣﺪﻳﺮ ﻗﺼﺪ‬

‫ﻣﺪﻳﺮﻳﺖ ﺍﻳﻦ ﻣﺠﻤﻮﻋﻪ ﺭﺍ ﺩﺍﺷﺘﻪ ﻭﻫﺮ ﻳﻚ ﺣﺴﺎﺏ ﻛﺎﺭﺑﺮﻱ ﺧﻮﺩ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ‪ ،‬ﻻﺯﻡ ﺍﺳﺖ ﺑﻄﻮﺭﺟﺪﺍﮔﺎﻧﻪ ﺑﻪ ﻫﺮ‬

‫ﻳﻚ ﺍﺯ ﺍﻳﻦ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ ESXi‬ﻭﺍﺭﺩ ﺷﺪﻩ ﻭ ﻳﻚ ﻛﺎﺭﺑﺮ ﺟﺪﻳﺪ ﺍﻳﺠﺎﺩ ﻛﻨﻴﺪ؛ ﻭ ﻳﺎ ﻣﺜﻼ ﺑﺮﺍﻱ ﺗﻐﻴﻴﺮ ﻛﻠﻤﻪ ﻋﺒﻮﺭ‬

‫ﻫﺮﻛﺎﺭﺑﺮ ﺑﺎﻳﺴﺘﻲ ﺍﻳﻦ ﺳﻨﺎﺭﻳﻮ ﺗﻜﺮﺍﺭ ﺷﻮﺩ‪.‬‬

‫ﻭﻟﻲ ‪ vCenter Server‬ﺍﻳﻦ ﻣﺸﻜﻞ ﺭﺍ ﺣﻞ ﻛﺮﺩﻩ ﺑﺪﻳﻦ ﺗﺮﺗﻴﺐ ﻛﻪ ﻛﺎﻓﻲ ﺍﺳﺖ ﺗﻨﻬﺎ ﻳﻜﺒﺎﺭ ﻣﻴﺰﺑﺎﻥﻫﺎﻱ‬

‫‪ ESXi‬ﺭﺍ ﻋﻀﻮ ‪ vCenter‬ﻛﺮﺩﻩ ﻭ ﺩﺭ ﺳﺮﻭﺭ ﻭﻳﻨﺪﻭﺯﻱ ‪ vCenter Server‬ﻛﺎﺭﺑﺮﻫﺎ ﻭ ﮔﺮﻭﻫﺎﻱ ﻻﺯﻡ ﺭﺍ ﺍﻳﺠﺎﺩ‬

‫ﻛﺮﺩﻩ ﻭ ﻫﺮ ﻣﺪﻳﺮ ﺑﻪ ﻛﻤﻚ ‪ vSphere Client‬ﺑﺎ ﻧﺎﻡ ﻛﺎﺭﺑﺮﻱ ﺧﻮﺩ ﺩﺭ ‪ ،vCenter Server‬ﺑﻪ ﺳﻴﺴﺘﻢ ﻭﺍﺭﺩ ﺷﺪﻩ‬

‫ﻭ ﻭﻇﺎﻳﻒ ﺧﻮﺩ ﺭﺍ ﺍﻧﺠﺎﻡ ﺩﻫﺪ‪ .‬ﺍﮔﺮ ﺍﺯ ‪ applianee‬ﻟﻴﻨﻮﻛﺴﻲ ﺑﻌﻨﻮﺍﻥ ‪ vCenter Server‬ﺍﺳﺘﻔﺎﺩﻩ ﺷﻮﺩ ﻭﻇﻴﻔﻪ‬

‫ﺗﺼﺪﻳﻖ ﻫﻮﻳﺖ ﺑﻪ ﻋﻬﺪﻩ ﺳﻴﺴﺘﻢ ﺍﻛﺘﻴﻮ ﺩﺍﻳﺮﻛﺘﻮﺭﻱ ﻛﻪ ‪ vCenter Server‬ﻋﻀﻮ ﺁﻥ ﺍﺳﺖ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪.‬‬

‫ﻋﻼﻭﻩ ﺑﺮ ﺳﺮﻭﻳﺲﻫﺎﻱ ﮔﻔﺘﻪ ﺷﺪﻩ ‪ vCenter Server‬ﻳﻚ ‪ API‬ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺑﺮﻧﺎﻣﻪﻧﻮﻳﺴﺎﻥ ﻗﺮﺍﺭ ﻣﻲﺩﻫﺪ ﺗﺎ‬

‫ﺷﺮﻛﺖﻫﺎﻱ ﺛﺎﻟﺚ ﻫﻢ ﺑﺘﻮﺍﻧﻨﺪ ﺑﺮﺍﻱ ‪ vCenter Server‬ﺑﺮﻧﺎﻣﻪﻧﻮﻳﺴﻲ ﻛﻨﻨﺪ‪ ،‬ﻭ ﺍﻳﻦ ﻛﻤﻚ ﺑﺴﻴﺎﺭ ﺑﺰﺭﮔﻲ ﺑﺮﺍﻱ‬

‫ﺗﻮﺳﻌﻪ ﺳﻴﺴﺘﻢﻫﺎﻱ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪.‬‬

‫ﻫﻤﭽﻨﻴﻦ ‪ vCenter Server‬ﺩﺍﺭﺍﻱ ﻳﻚ ﺣﺎﻟﺖ ‪ link-mode‬ﺍﺳﺖ ﻛﻪ ﺑﺮﺍﻱ ﻣﺤﻴﻂ ﻫﺎﻱ ﺑﺰﺭﮔﺘﺮ ﺩﺭ ﻧﻈﺮ‬

‫ﮔﺮﻓﺘﻪ ﺷﺪﻩ ﺍﺳﺖ ﺑﻄﻮﺭﻳﻜﻪ ﭼﻨﺪﻳﻦ ﺳﺮﻭﺭ ‪ vCenter‬ﻣﻲﺗﻮﺍﻧﻨﺪ ﺗﺤﺖ ﻣﺪﻳﺮﻳﺖ ﻳﻚ ‪ Active Directory‬ﻛﻨﺘﺮﻝ‬

‫ﻳﻚ ﺩﻳﺘﺎ ﺳﻨﺘﺮ ﺭﺍ ﺑﺮ ﻋﻬﺪﻩ ﺑﮕﻴﺮﻧﺪ‪.‬‬

‫‪ 2-2-4‬ﻧﻴﺎﺯﻣﻨﺪﻱﻫﺎﻱ ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﻭ ﺳﺨﺖﺍﻓﺰﺍﺭﻱ ‪vCenter Server‬‬

‫ﻗﺒﻞ ﺍﺯ ﻫﺮ ﭼﻴﺰ ﻻﺯﻡ ﺍﺳﺖ ﺑﺪﺍﻧﻴﻢ ﭼﻪ ﻣﻮﺍﺭﺩﻱ ﺑﺮﺍﻱ ﻧﺼﺐ ‪ vCenter Server‬ﻧﻴﺎﺯ ﺍﺳﺖ‪ .‬ﻣﺜﻼ ﺑﺮ ﺭﻭﻱ ﭼﻪ‬

‫ﭘﻠﺘﻔﺮﻡ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﺍﺟﺮﺍ ﻣﻲﺷﻮﺩ‪ ،‬ﺑﺮ ﺭﻭﻱ ﭼﻪ ﻭﺭژﻥ ﻫﺎﻳﻲ ﺍﺯ ﻭﻳﻨﺪﻭﺯ ﻗﺎﺑﻞ ﻧﺼﺐ ﺍﺳﺖ‪ ،‬ﺍﺯ ﭼﻪ ﺑﺎﻧﻚ‬

‫ﺍﻃﻼﻋﺎﺗﻲ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﻛﻨﺪ ﻭ‪ . ...‬ﭘﺎﺳﺦ ﺍﻳﻦ ﺳﻮﺍﻻﺕ ﺑﺴﺘﻪ ﺑﻪ ﻣﺤﻴﻂ ﻋﻤﻠﻴﺎﺗﻲ ﻭ ﺍﻧﺪﺍﺯﻩ ﺩﻳﺘﺎﺳﻨﺘﺮ ﻣﺘﻔﺎﻭﺕ‬

‫‪65‬‬
 ‫ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪.‬‬

‫ﺣﺪﺍﻗﻞ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﻻﺯﻡ ﺑﺮﺍﻱ ‪ vCenter Server‬ﺑﻪ ﻗﺮﺍﺭ ﺯﻳﺮ ﺍﺳﺖ‪:‬‬

‫ﺩﻭ ﭘﺮﺩﺍﺯﻧﺪﻩ ‪ 64‬ﺑﻴﺖ ﻭ ﻳﺎ ﻳﻚ ﭘﺮﺩﺍﺯﻧﺪﻩ ﺩﻭ ﻫﺴﺘﻪ ﺍﻱ ‪ 64‬ﺑﻴﺘﻲ ﺑﺎ ﻓﺮﻛﺎﻧﺲ ﻛﺎﺭﻱ ‪ 2‬ﮔﻴﮕﺎﻫﺮﻧﺰ‬ ‫‪-‬‬

‫‪ 3‬ﮔﻴﮕﺎ ﺑﺎﻳﺖ ﺭﻡ‬ ‫‪-‬‬

‫‪ 3‬ﮔﻴﮕﺎ ﺑﺎﻳﺖ ﻓﻀﺎﻱ ﺧﺎﻟﻲ ﺑﺮ ﺭﻭﻱ ﻫﺎﺭﺩ ﺩﻳﺴﻚ‬ ‫‪-‬‬

‫ﻳﻚ ﻛﺎﺭﺕ ﺷﺒﻜﻪ ﺍﺗﺮﻧﺖ )ﺑﻬﺘﺮ ﺍﺳﺖ ﮔﻴﮕﺎﺑﻴﺖ ﺑﺎﺷﺪ(‬ ‫‪-‬‬

‫ﺑﺮﺍﻱ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﻫﻢ ﻳﻜﻲ ﺍﺯ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﻻﺯﻡ ﺍﺳﺖ‪:‬‬

‫ﻭﻳﻨﺪﻭﺯ ﺳﺮﻭﺭ ‪ ، 2003‬ﻭﻳﻨﺪﻭﺯ ﺳﺮﻭﺭ ‪ 2003 R2‬ﻭﻳﻨﺪﻭﺯ ﺳﺮﻭﺭ ‪ 2008‬ﻭ ﻭﻳﻨﺪﻭﺯ ﺳﺮﻭﺭ ‪ . 2008 R2‬ﻻﺯﻡ ﺑﻪ‬

‫ﺫﻛﺮ ﺍﺳﺖ ﻛﻪ ‪ vCenter Server‬ﻓﻘﻂ ﺑﺮ ﺭﻭﻱ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﻫﺎﻱ ‪ 64‬ﺑﻴﺘﻲ ﺍﺟﺮﺍ ﻣﻲﺷﻮﺩ ‪.‬‬

‫ﻣﻮﺍﺭﺩ ﮔﻔﺘﻪ ﺷﺪﻩ ﺩﺭ ﺑﺎﻻ‪ ،‬ﺣﺪﺍﻗﻞ ﺭﺍ ﺩﺭ ﻧﻈﺮ ﮔﺮﻓﺘﻪ ﺍﺳﺖ‪ .‬ﻗﺎﻋﺪﺗﺎ ﺑﺮﺍﻱ ﺩﻳﺘﺎﺳﻨﺘﺮﻫﺎﻱ ﺑﺰﺭﮔﺘﺮ ﺳﻴﺴﺘﻢ‬

‫ﻗﻮﻱﺗﺮﻱ ﻻﺯﻡ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪ .‬ﻫﻤﭽﻨﻴﻦ ﻣﻮﺍﺭﺩ ﺑﺎﻻ ﺑﺎ ﺍﻳﻦ ﭘﻴﺶ ﻓﺮﺽ ﺩﺭ ﻧﻈﺮ ﮔﺮﻓﺘﻪ ﺷﺪﻩ ﺍﻧﺪ ﻛﻪ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ‬

‫ﺑﺮ ﺭﻭﻱ ﺳﺮﻭﺭ ﺩﻳﮕﺮﻱ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﺷﺪﻩ ﺍﺳﺖ؛ ﺍﮔﺮ ﭼﻪ ﺑﺎ ﺗﻬﻴﻪ ﻛﺮﺩﻥ ﻳﻚ ﺳﺮﻭﺭ ﻗﻮﻱ ﺗﺮ ﻣﻲ ﺗﻮﺍﻥ ‪vCenter‬‬

‫‪ Server‬ﻭ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﺭﺍ ﺩﺭ ﻛﻨﺎﺭ ﻫﻢ ﻭ ﺑﺮ ﺭﻭﻱ ﻳﻚ ﺳﺮﻭﺭ ﻧﺼﺐ ﻛﺮﺩ‪ .‬ﺍﻟﺒﺘﻪ ﺍﻳﻦ ﻛﺎﺭ ﺍﺻﻼ ﺗﻮﺻﻴﻪ ﻧﻤﻲﺷﻮﺩ‬

‫ﭼﺮﺍ ﻛﻪ ﺩﺭ ﺻﻮﺭﺕ ﺧﺮﺍﺑﻲ ﺳﺮﻭﺭ‪ ،‬ﺩﻭ ﻧﻘﻄﻪ ﺍﺯ ﺷﺒﻜﻪ ﻣﺎ ﺩﭼﺎﺭ ﻣﺸﻜﻞ ﺧﻮﺍﻫﺪ ﺷﺪ ﻳﻜﻲ ﺳﺮﻭﺭ ‪ vCenter‬ﻭ‬

‫ﺩﻳﮕﺮﻱ ﺳﺮﻭﺭ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ‪.‬‬

‫ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﺩﺭ ﺍﻳﻨﺠﺎ ﻭﻇﻴﻔﻪ ﻧﮕﻬﺪﺍﺭﻱ ﺍﻃﻼﻋﺎﺕ ﻣﻴﺰﺑﺎﻥ ﻫﺎﻱ ‪ ESXi‬ﻭ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺍﺯ ﺟﻤﻠﻪ‬

‫ﺍﻃﻼﻋﺎﺕ ﭘﻴﻜﺮﺑﻨﺪﻱ‪ ،‬ﻣﺠﻮﺯﻫﺎ‪ ،‬ﺁﻣﺎﺭﻫﺎ ﻭ ﺩﻳﮕﺮ ﺍﻃﻼﻋﺎﺕ ﺭﺍ ﺑﺮ ﻋﻬﺪﻩ ﺩﺍﺭﺩ‪.‬‬

‫ﺍﮔﺮ ﺑﺨﻮﺍﻫﻴﻢ ﺳﺮﻭﺭ ‪ vCenter‬ﻭ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﻳﻜﻲ ﺑﺎﺷﺪ ﻳﻌﻨﻲ ﻫﺮ ﺩﻭ ﺑﺮ ﺭﻭﻱ ﻳﻚ ﺳﺮﻭﺭ ﺍﺟﺮﺍ ﺷﻮﻧﺪ‪ ،‬ﺣﺪﺍﻗﻞ‬

‫ﺳﺨﺖﺍﻓﺰﺍﺭ ﻻﺯﻡ ﺑﻪ ﻗﺮﺍﺭ ﺯﻳﺮ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪:‬‬

‫ﻳﻚ ﭘﺮﺩﺍﺯﻧﺪﻩ ﺩﻭ ﻫﺴﺘﻪ ﻭ ‪ 4‬ﮔﻴﮕﺎﺑﺎﻳﺖ ﺭﻡ ﺑﺮﺍﻱ ﻳﻚ ﻣﺠﻤﻮﻋﻪ ﺑﺎ ‪ 50‬ﻣﻴﺰﺑﺎﻥ ‪ ESXi‬ﻭ ‪ 500‬ﻣﺎﺷﻴﻦ‬

‫ﻣﺠﺎﺯﻱ‪ .‬ﺍﮔﺮ ﺩﻳﻨﺎﺳﻨﺘﺮ ﺷﻤﺎ ﺩﺍﺭﺍﻱ ‪ 300‬ﻣﻴﺰﺑﺎﻥ ‪ ESXi‬ﻭ ‪ 3000‬ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺍﺳﺖ‪ ،‬ﺍﻱ ﺑﺎ ‪ 4‬ﻫﺴﺘﻪ‬

‫‪66‬‬
‫ﭘﺮﺩﺍﺯﻧﺪﻩ ﻭ ﻣﻘﺪﺍﺭ ‪ 8‬ﮔﻴﮕﺎﺑﺎﻳﺖ ﺭﻡ ﻻﺯﻡ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪ .‬ﺑﺮﺍﻱ ﻳﻚ ﺩﻳﻨﺎﺳﻨﺘﺮ ﺑﺎ ‪ 1000‬ﻣﻴﺰﺑﺎﻥ ‪ ESXi‬ﻭ ‪10000‬‬

‫ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ‪ 8‬ﻫﺴﺘﻪ ﭘﺮﺩﺍﺯﻧﺪﻩ ﻧﻴﺎﺯ ﺍﺳﺖ‪ .‬ﻣﻘﺪﺍﺭ ﺣﺪﺍﻗﻞ ﺭﻡ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ﻫﻢ ﺑﺮﺍﺑﺮ ﺑﺎ ‪ 16‬ﮔﻴﮕﺎﺑﺎﻳﺖ ﺧﻮﺍﻫﺪ‬

‫ﺑﻮﺩ‪ .‬ﻣﻴﺰﺍﻥ ﻓﻀﺎﻱ ﺁﺯﺍﺩ ﺑﺮ ﺭﻭﻱ ﺩﻳﺴﻚ ﻧﻴﺰ ﻣﺘﻨﺎﺳﺐ ﺑﺎ ﺗﻌﺪﺍﺩ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ ESXi‬ﻭ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺍﻓﺰﺍﻳﺶ‬

‫ﺧﻮﺍﻫﺪ ﻳﺎﻓﺖ‪.‬‬

‫ﺍﺯ ﺁﻧﺠﺎﻳﻲ ﻛﻪ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﺍﻫﻤﻴﺖ ﻓﻮﻕ ﺍﻟﻌﺎﺩﻩﺍﻱ ﺑﺮﺍﻱ ‪ vCenter Server‬ﺩﺍﺭﺩ‪ ،‬ﺗﻨﻬﺎﺍﺯ ﺑﺎﻧﻚﻫﺎﻱ‬

‫ﺍﻃﻼﻋﺎﺗﻲ ﺍﻳﻨﺘﺮﭘﺮﺍﻳﺰ ﭘﺸﺘﻴﺒﺎﻧﻲ ﻣﻲﻛﻨﺪ‪ .‬ﺩﺭ ﺣﺎﻝ ﺣﺎﺿﺮ ﺑﺎﻧﻚ ﻫﺎﻱ ﺍﻃﻼﻋﺎﺗﻲ ﺯﻳﺮ ﻣﻲﺗﻮﺍﻧﻨﺪ ﺑﺮﺍﻱ ‪vCenter‬‬

‫‪ Server‬ﺍﺳﺘﻔﺎﺩﻩ ﺷﻮﻧﺪ‪:‬‬

‫‪ϑ‬‬ ‫)‪IBM DB2 9.5 (fix pack 5 required; fix pack 7 recommended‬‬
‫‪ϑ‬‬ ‫)‪IBM DB2 9.7 (fix pack 2 required; fix pack 3a recommended‬‬
‫‪ϑ‬‬ ‫)‪Microsoft SQL Server 2008 R2 Express (bundled with vCenter Server‬‬
‫‪ϑ‬‬ ‫)‪Microsoft SQL Server 2005 (32-bit or 64-bit; SP3 is required, and SP4 is recommended‬‬
‫‪ϑ‬‬ ‫)‪Microsoft SQL Server 2008 (32-bit or 64-bit; SP1 is required, and SP2 is recommended‬‬
‫‪ϑ‬‬ ‫‪Microsoft SQL Server 2008 R2‬‬
‫‪ϑ‬‬ ‫)‪Oracle 10g R2 (10.2.0.4 required‬‬
‫‪ϑ‬‬ ‫)‪Oracle 11g R1 (11.1.0.7 required‬‬
‫‪ϑ‬‬ ‫)‪Oracle 11g R2 (11.2.0.1 with patch 5 required‬‬
‫ﺗﻮﺟﻪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﺪ ﻛﻪ ﻣﻤﻜﻦ ﺍﺳﺖ ﺑﺎﻧﻚﻫﺎﻱ ﺍﻃﻼﻋﺎﺗﻲ ﺫﻛﺮ ﺷﺪﻩ ﺗﻮﺳﻂ ﻣﻮﻟﻔﻪﻫﺎﻱ ﺩﻳﮕﺮ ‪ vSphere‬ﻧﻈﻴﺮ‬

‫‪ vSpher Update Manager‬ﭘﺸﺘﻴﺒﺎﻧﻲ ﻧﺸﻮﻧﺪ ﻛﻪ ﺑﺮﺍﻱ ﺍﻃﻼﻋﺎﺕ ﺑﻴﺸﺘﺮ ﺩﺭ ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﻣﻲﺗﻮﺍﻧﻴﺪ ﺑﻪ ﺳﺎﻳﺖ‬

‫‪ VMware‬ﻣﺮﺍﺟﻌﻪ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫ﻳﻚ ﻧﻜﺘﻪ ﻣﻬﻢ ﻛﻪ ﺩﺭ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺑﺎﻧﻚ ﻫﺎﻱ ﺍﻃﻼﻋﺎﺗﻲ ﺣﺎﺋﺰ ﺍﻫﻤﻴﺖ ﺍﺳﺖ ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﻧﻮﻉ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ‬

‫ﻣﻴﺘﻮﺍﻧﺪ ﺩﺭ ﺗﻌﺪﺍﺩ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ ESXi‬ﻭ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻣﺤﺪﻭﺩﻳﺖ ﺍﻳﺠﺎﺩ ﻛﻨﺪ ﭼﺮﺍ ﻛﻪ ﺷﺮﻛﺖ ‪VMware‬‬

‫ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ SQL server 2008 Express‬ﺭﺍ ﺑﺮﺍﻱ ﺩﻳﻨﺎ ﺳﻨﺘﺮﻫﺎﻱ ﺑﺎ ‪ 5‬ﻣﻴﺰﺑﺎﻥ ‪ ESXi‬ﻭ ‪ 50‬ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻭ‬

‫ﺑﻴﺸﺘﺮ ﺍﺻﻼ ﺗﻮﺻﻴﻪ ﻧﻤﻲﻛﻨﺪ‪.‬‬

‫ﺑﻨﺎﺑﺮﺍﻳﻦ ﭘﺲ ﺍﺯﺗﻬﻴﻪ ﻣﺎﻳﺤﺘﺎﺝ ﺳﺨﺖﺍﻓﺰﺍﺭﻱ ﺩﻭﻣﻴﻦ ﻣﺴﺌﻠﻪ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﺍﺳﺖ‪.‬‬

‫‪67‬‬
 ‫‪ 3-2-4‬ﺁﻣﺎﺩ ﺳﺎﺯﻱ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﮔﻔﺘﻪ ﺷﺪ ﻻﺯﻡ ﺍﺳﺖ ﻗﺒﻞ ﺍﺯ ﻧﺼﺐ ‪ vCenter Server‬ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﺭﺍ ﺁﻣﺎﺩﻩﺳﺎﺯﻱ ﻛﻨﻴﻢ‪.‬‬

‫ﺍﮔﺮ ﺩﻳﺘﺎﺳﻨﺘﺮ ﺷﻤﺎ ﻛﻮﭼﻚ ﺑﻮﺩﻩ ﺑﻄﻮﺭﻱ ﻛﻪ ﺗﻌﺪﺍﺩ ﻣﻴﺰﺑﺎﻥ ‪ ESXi‬ﻛﻤﺘﺮ ﺍﺯ ‪ 5‬ﻭ ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻛﻤﺘﺮ‬

‫ﺍﺯ ‪ 50‬ﺑﻮﺩﻩ ﻭ ﻫﻤﭽﻨﻴﻦ ﻧﻴﺎﺯﻱ ﺑﻪ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﻛﻪ ﺑﺮ ﺭﻭﻱ ﺳﺮﻭﺭﻱ ﻏﻴﺮ ﺍﺯ ﺳﺮﻭﺭ ‪ vCenter‬ﻭﺟﻮﺩ‬

‫ﺩﺍﺭﺩ ﻧﺪﺍﺭﻳﺪ ﻣﻲﺗﻮﺍﻧﻴﺪ ﺍﺯ ﺍﻳﻦ ﺑﺨﺶ ﻋﺒﻮﺭ ﻛﻨﻴﺪ‪ .‬ﺍﻣﺎ ﺗﻮﺻﻴﻪ ﻣﻲ ﺷﻮﺩ ﺣﺪﺍﻗﻞ ﺑﺮﺍﻱ ﺍﻓﺰﺍﻳﺶ ﺁﮔﺎﻫﻲ ﺧﻮﺩ ﺩﺭ ﻣﻮﺭﺩ‬

‫ﭼﮕﻮﻧﮕﻲ ﻛﺎﺭ ﺑﺎ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﺭﻳﻤﻮﺕ ﺍﻳﻦ ﻗﺴﻤﺖ ﺭﺍ ﻣﻄﺎﻟﻌﻪ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫ﻗﺪﻡ ﺍﻭﻝ ﺍﻳﺠﺎﺩ ﭘﺎﻳﮕﺎﻩ ﺩﺍﺩﻩ‪ ،‬ﻳﺎ ﻫﻤﺎﻥ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﺍﺳﺖ‪ .‬ﺑﻪ ﺳﺮﻭﺭﻱ ﻛﻪ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﺭﺍ ﺑﺮ ﺭﻭﻱ ﺁﻥ‬

‫ﻧﺼﺐ ﻛﺮﺩﻩﺍﻳﺪ ‪ login‬ﻛﻨﻴﺪ‪ .‬ﺍﺯ ﻣﺴﻴﺮ‬

‫‪start > All programs > Microsoft SQL Server 2008 R2 > SQL Server management st‬‬
‫ﺑﻪ ‪ SQL‬ﻭﺍﺭﺩ ﺷﻮﻳﺪ‪ .‬ﺑﻌﺪ ﺍﺯ ‪ login‬ﻛﺮﺩﻥ ﺑﻪ ﺑﺨﺸﻲ ﻣﺪﻳﺮﻳﺖ ﭘﺎﻳﮕﺎﻩ ﻭﺍﺭﺩ ﺧﻮﺍﻫﻴﺪ ﺷﺪ‪.‬‬

‫ﺍﺑﺘﺪﺍ ﻻﺯﻡ ﺍﺳﺖ ﺗﺎ ﺑﺮﺍﻱ ﺍﺗﺼﺎﻝ ﺑﻪ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﻳﻚ ﻧﺎﻡ ﻛﺎﺭﺑﺮﻱ ﺍﻳﺠﺎﺩ ﺷﻮﺩ‪ .‬ﮔﺮ ﭼﻪ ﻛﺎﺭﺑﺮ ‪ sa‬ﺑﻪ ﻃﻮﺭ‬

‫ﭘﻴﺶﻓﺮﺽ ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪ .‬ﺑﺪﻳﻦ ﻣﻨﻈﻮﺭ‪ :‬ﺳﻤﺖ ﭼﭗ ﺻﻔﺤﻪ‪ ،‬ﺩﺭ ﺑﺨﺶ ‪ object explorer‬ﺑﺮ ﺭﻭﻱ ﻋﻼﻣﺖ ﺑﻌﻼﻭﻩ‬

‫ﻛﻨﺎﺭ ‪ security‬ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪.‬‬

‫ﺣﺎﻝ ﺑﺮ ﺭﻭﻱ ﺑﻌﻼﻭﻩ ﻛﻨﺎﺭ‪ logins‬ﻧﻴﺰ ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪ .‬ﺑﺮ ﺭﻭﻱ ‪ logins‬ﻛﻠﻴﻚ ﺭﺍﺳﺖ ﻛﺮﺩﻩ‪ ،‬ﺍﺑﺘﺪﺍ ‪ new‬ﻭ ﺑﻌﺪ‬

‫…‪ login‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ .‬ﺩﺭ ﻗﺴﻤﺖ ‪ login name‬ﻧﺎﻣﻲ ﺑﺮﺍﻱ ﻛﺎﺭﺑﺮ ﺟﺪﻳﺪ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪SQLserver .‬‬

‫‪ authentication‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ﻭ ﭘﺴﻮﺭﺩﻱ ﻧﻴﺰ ﺑﺮﺍﻱ ﻛﺎﺭﺑﺮ ﺟﺪﻳﺪ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪.‬ﺗﻴﻚ ﮔﺰﻳﻨﻪ ‪enforce‬‬

‫‪ password policy‬ﺭﺍ ﺑﺮﺩﺍﺭﻳﺪ‪ .‬ﺳﻤﺖ ﭼﭗ ‪ ،‬ﺑﺎﻻﻱ ﻫﻤﻴﻦ ﺻﻔﺤﻪ ﺑﺮ ﺭﻭﻱ ‪ server roles‬ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪.‬‬

‫ﮔﺰﻳﻨﻪﻫﺎﻱ ‪ sysadmin , public‬ﺭﺍ ﺗﻴﻚ ﺑﺰﻧﻴﺪ ‪.‬ﺑﺎ ﺯﺩﻥ ‪ ok‬ﺻﻔﺤﻪ ﺭﺍﺑﺒﻨﺪﻳﺪ‪.‬‬

‫ﺩﺭ ﺑﺨﺶ ‪ object explorer‬ﺑﺮﺭﻭﻱ ‪ Databases‬ﻛﻠﻴﻚ ﺭﺍﺳﺖ ﻛﺮﺩﻩ ‪ new Databases‬ﺭﺍ ﺑﺮﮔﺰﻳﻨﻴﺪ‪ .‬ﺩﺭ‬

‫ﺗﻜﺴﺖﺑﺎﻛﺲ ‪ Databases name‬ﻳﻚ ﻧﺎﻡ ﺑﺮﺍﻱ ﭘﺎﻳﮕﺎﻩﺩﺍﺩﻩ ﺧﻮﺩ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ owner .‬ﺁﻥ ﺭﺍ ﺑﻪ ﻛﺎﺭﺑﺮﻱ‬

‫‪68‬‬
 ‫ﺍﺧﺘﺼﺎﺹ ﺩﻫﻴﺪﻛﻪ ﻗﺼﺪ ﺩﺍﺭﻳﺪ ﺑﻮﺳﻴﻠﻪ ﺁﻥ ﺑﻪ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﻣﺘﺼﻞ ﺷﻮﻳﺪ‪ .‬ﺑﺎ ﺯﺩﻥ ‪ ok‬ﺻﻔﺤﻪ ﺭﺍﺑﺒﻨﺪﻳﺪ‪.‬‬

‫ﺣﺎﻝ ﺍﺯ ﺑﺮﻧﺎﻣﻪ ﻣﺪﻳﺮﻳﺖ ﭘﺎﻳﮕﺎﻩ ﺩﺍﺩﻩ ﺧﺎﺭﺝ ﺷﻮﻳﺪ‪.‬‬

‫ﻗﺒﻞ ﺍﺯ ﺍﺩﺍﻣﻪ ﻣﻄﻤﺌﻦ ﺷﻮﻳﺪ ﺳﺮﻭﻳﺲ ‪ SQLagent‬ﺩﺭ ﺣﺎﻟﺖ ﺍﺟﺮﺍ ﺑﺎﺷﺪ‪ .‬ﺑﺪﻳﻦﻣﻨﻈﻮﺭ ﭘﺲ ﺍﺯ ﻭﺍﺭﺩ ﺷﺪﻥ ﺑﻪ‬

‫ﺳﺮﻭﺭ ﭘﺎﻳﮕﺎﻩﺩﺍﺩﻩ‪ ،‬ﺍﺯ ﻣﺴﻴﺮ ‪ ، start > administrative tools > services‬ﺑﻪ ﺑﺨﺶ ﺳﺮﻭﻳﺲﻫﺎ ﻭﺍﺭﺩ ﺷﻮﻳﺪ ﻭ‬

‫‪ SQL Server agent‬ﺭﺍ ﺍﺟﺮﺍ ﻛﺮﺩﻩ ﻭﺩﺭﺣﺎﻟﺖ ‪ Automatic‬ﻗﺮﺍﺭ ﺩﻫﻴﺪ‪.‬‬

‫ﺑﻪ ﺳﺮﻭﺭ ‪ vCenter Server‬ﻭﺍﺭﺩ ﺷﻮﻳﺪ‪ .‬ﺑﺮﺍﻱ ﺍﺗﺼﺎﻝ ﺑﻪ ﭘﺎﻳﮕﺎﻩ ﺩﺍﺩﻩ ﻻﺯﻡ ﺍﺳﺖ ﻳﻚ ‪ ODBC DSN‬ﺍﻳﺠﺎﺩ‬

‫ﻛﻨﻴﺪ‪ .‬ﺑﺪﻳﻦ ﻣﻨﻈﻮﺭ ﺍﺯ ﻣﺴﻴﺮ‪:‬‬

‫‪start > administrative tools > Datasource‬‬

‫ﺑﻪ ‪ ODBC Datasource Administrator‬ﻭﺍﺭﺩ ﺷﻮﻳﺪ‪ .‬ﺩﺭ ﺳﺮﺑﺮگ ‪ System DSN‬ﺑﺮ ﺭﻭﻱ ‪ Add‬ﻛﻠﻴﻚ‬

‫ﻛﻨﻴﺪ‪ .‬ﭘﺲ ﺍﺯ ﺍﻧﺘﺨﺎﺏ ﺩﺭﺍﻳﻮﺭ ‪ SQL Server native client‬ﺑﺮ ﺭﻭﻱ ‪ finish‬ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪.‬‬

‫ﺍﮔﺮ ‪ native client‬ﻭﺟﻮﺩ ﻧﺪﺍﺭﺩ ﺑﺎﻳﺴﺘﻲ ﻗﺒﻞ ﺍﺯ ﺍﺩﺍﻣﻪ ﻛﺎﺭ ﺁﻥ ﺭﺍﻧﺼﺐ ﻛﻨﻴﺪ‪ native client .‬ﺭﺍﻣﻲﺗﻮﺍﻧﻴﺪ ﺍﺯ‬

‫ﺳﺎﻳﺖ ﻣﺎﻳﻜﺮﻭﺳﺎﻓﺖ ﺩﺍﻧﻠﻮﺩ ﻛﻨﻴﺪ ﻭ ﻳﺎ ﺩﺍﺧﻞ ‪ DVD‬ﺣﺎﻭﻱ ‪ SQL‬ﺁﻥ ﺭﺍ ﺑﻴﺎﺑﻴﺪ‪ .‬ﺍﮔﺮ ﻧﺘﻮﺍﻧﺴﺘﻴﺪ ﺑﻄﻮﺭﻣﺠﺰﺍ ﺁﻥ ﺭﺍ‬

‫‪client tools‬‬ ‫ﺩﺍﺧﻞ ‪ DVD‬ﺑﻴﺎﺑﻴﺪ‪ ،‬ﻧﺼﺐ ‪ SQL‬ﺭﺍ ﺁﻏﺎﺯ ﻛﻨﻴﺪ ﻭﻟﻲ ﻫﻨﮕﺎﻡ ﺍﻧﺘﺨﺎﺏ ﻣﻮﻟﻔﻪﻫﺎ‪ ،‬ﺗﻨﻬﺎ‬

‫‪ connectivity‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ .‬ﺍﻟﺒﺘﻪ ﺑﻌﺪ ﺍﺯ ﭘﺎﻳﺎﻥ ﻧﺼﺐ ﻣﻲﺗﻮﺍﻧﻴﺪ ﺗﻤﺎﻡ ﻣﻮﻟﻔﻪﻫﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ‪ SQL‬ﺑﺠﺰ‬

‫‪ native client‬ﺭﺍ ﺍﺯﻃﺮﻳﻖ ‪ programs and features‬ﺣﺬﻑ ﻛﻨﻴﺪ‪.‬‬

‫ﻫﻤﭽﻨﻴﻦ ﻗﺒﻞ ﺍﺯ ﺍﺩﺍﻣﻪ ﻛﺎﺭ‪ ،‬ﺩﻳﻮﺍﺭ ﺁﺗﺶ ﺳﺮﻭﺭﻱ ﻛﻪ ‪ SQL‬ﺩﺭ ﺁﻥ ﺍﺟﺮﺍ ﻣﻲﺷﻮﺩ ﺭﺍ ﻧﻴﺰ ﺧﺎﻣﻮﺵ ﻛﻨﻴﺪ‪ .‬ﺑﻌﺪ‬

‫ﺍﺯ ﻧﺼﺐ ‪ native client‬ﻓﺮﺍﻳﻨﺪ ﺍﻳﺠﺎﺩ ‪ ODBC DSN‬ﺭﺍ ﺩﻭﺑﺎﺭﻩ ﺗﻜﺮﺍﺭ ﻛﻨﻴﺪ‪.‬‬

‫ﺑﻌﺪ ﺍﺯ ﺍﻧﺘﺨﺎﺏ ‪ SQL Server native client‬ﻭ ﺯﺩﻥ ﺩﻛﻤﻪ ‪ finish‬ﺻﻔﺤﻪ ﺟﺪﻳﺪﻱ ﺑﺎﺯ ﻣﻲﺷﻮﺩ‪ .‬ﺩﺭ ﺍﻳﻦ‬

‫ﺻﻔﺤﻪ ﺩﺭ ﻗﺴﻤﺖ ‪ name‬ﻧﺎﻣﻲ ﺩﻟﺨﻮﺍﻩ ﺑﺮﺍﻱ ﺍﻳﻦ ‪ DSN‬ﻭﺍﺭﺩ ﻧﻤﺎﺋﻴﺪ‪ .‬ﺩﺭ ﺑﺨﺶ ‪ server‬ﻧﺎﻡ ﻭ ﻳﺎ ‪ IP‬ﺳﺮﻭﺭ ﺑﺎﻧﻚ‬

‫ﺍﻃﻼﻋﺎﺗﻲ ﺭﺍ ﻭﺍﺭﺩ ﻛﻨﻴﺪ‪ .‬ﺗﻮﺟﻪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﺪ ﺍﮔﺮ ﺳﺮﻭﺭ ‪ DNS‬ﻧﺪﺍﺭﻳﺪ ﺗﻨﻬﺎ ‪ IP‬ﻣﻲ ﺗﻮﺍﻥ ﻭﺍﺭﺩ ﻛﺮﺩ‪ .‬ﺑﺎ ﺯﺩﻥ ‪next‬‬

‫ﺑﻪ ﺻﻔﺤﻪ ﺑﻌﺪ ﺑﺮﻭﻳﺪ‪ with SQL Server Authentication .‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ ﻭ ﻧﺎﻡ ﻛﺎﺭﺑﺮﻱ ﻛﻪ ﺩﺭ ﻣﺮﺣﻠﻪ ﻗﺒﻞ‬

‫ﺩﺭ ﺑﺨﺶ ﻣﺪﻳﺮﻳﺖ ‪ SQL‬ﺍﻳﺠﺎﺩ ﻛﺮﺩﻳﺪ ﺭﺍ ﺑﻪ ﻫﻤﺮﺍﻩ ﺭﻣﺰ ﻋﺒﻮﺭ ﺁﻥ ﺭﺍ ﻭﺍﺭﺩ ﻛﻨﻴﺪ‪ .‬ﺑﺮﺍﻱ ﺍﻃﻤﻴﻨﺎﻥ ﺍﺯ ﺍﺗﺼﺎﻝ ﺗﻴﻚ‬

‫‪69‬‬
 ‫ﮔﺰﻳﻨﻪ ﭘﺎﻳﻴﻦ ﺻﻔﺤﻪ ﺭﺍ ﺑﺰﻧﻴﺪ‪ ،‬ﺳﭙﺲ ﺑﺮﺭﻭﻱ ‪ next‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫ﺗﻴﻚ ﮔﺰﻳﻨﻪ ‪ change the default databases‬ﺭﺍ ﺑﺰﻧﻴﺪ ﻭﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﻛﻪ ﺩﺭ ﺑﺨﺶ ﻣﺪﻳﺮﻳﺖ ‪SQL‬‬

‫ﺍﻳﺠﺎﺩ ﻛﺮﺩﻳﺪ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ Next .‬ﺭﺍ ﺑﺰﻧﻴﺪ ﺻﻔﺤﻪ ﺟﺪﻳﺪ ﺭﺍ ﺑﺪﻭﻥ ﺗﻐﻴﻴﺮ ﺭﻫﺎ ﻛﻨﻴﺪ‪ .‬ﭘﺲ ﺍﺯ ﺯﺩﻥ ‪finish‬‬

‫ﻣﻲﺗﻮﺍﻧﻴﺪ ﺑﺎ ﺯﺩﻥ ‪ test Datasource‬ﺍﺯ ﺻﺤﺖ ﻛﺎﺭﻛﺮﺩ‪ DSN‬ﻣﻄﻤﺌﻦ ﺷﻮﻳﺪ‪.‬‬

‫‪ ODBCDSN‬ﺳﺎﺧﺘﻪ ﺷﺪ‪ .‬ﻣﻲﺗﻮﺍﻧﻴﻢ ﻧﺼﺐ ‪ vCenter Server‬ﺭﺍ ﺁﻏﺎﺯ ﻛﻨﻴﻢ‪.‬‬

‫‪ 4-2-4‬ﻧﺼﺐ ‪vCenter Server‬‬

‫ﺑﺪﻳﻦ ﻣﻨﻈﻮﺭ ‪:‬‬

‫‪ .1‬ﺍﺑﺘﺪﺍ ﺭﺳﺎﻧﻪ ﺣﺎﻭﻱ ﻓﺎﻳﻞ ﻧﺼﺐ ‪ vCenter‬ﺭﺍ ﺩﺍﺧﻞ ﺩﺭﺍﻳﻮ ﻗﺮﺍﺭ ﺩﻫﻴﺪ ﭘﺲ ﺍﺯ ﺍﺟﺮﺍ ﺷﺪﻥ ﺍﺗﻮﺭﺍﻥ ﺑﺎ‬

‫ﺗﺼﻮﻳﺮﻱ ﻣﺸﺎﺑﻪ ﺑﻪ ﺷﻜﻞ ‪ 8-4‬ﻣﻮﺍﺟﻪ ﺧﻮﺍﻫﻴﺪ ﺷﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 8 4‬ﺍﺗﻮﺭﺍﻥ ﺭﺳﺎﻧﻪ ﺣﺎﻭﻱ ‪vCenter Server‬‬

‫‪70‬‬
 ‫‪ .2‬ﺍﺯ ﺳﻤﺖ ﭼﭗ ‪ ،‬ﺑﺎﻻﻱ ﺍﺗﻮﺭﺍﻥ ‪vCenter Server‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻭ ﭘﺲ ﺍﺯ ﺁﻥ ﺑﺮ ﺭﻭﻱ ‪ install‬ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪.‬‬

‫‪ .3‬ﭘﺲ ﺍﺯ ﺍﻧﺘﺨﺎﺏ ﺯﺑﺎﻥ ﻣﻮﺭﺩ ﻧﻈﺮ ﺑﺮ ﺭﻭﻱ ‪ ok‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫‪ .4‬ﺑﺮ ﺭﻭﻱ ‪ next‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫‪ .5‬ﺑﺎﺭ ﺩﻳﮕﺮ ﺑﺮ ﺭﻭﻱ ‪ next‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫‪ .6‬ﭘﺲ ﺍﺯ ﺍﻧﺘﺨﺎﺏ ﮔﺰﻳﻨﻪ ‪ agree‬ﻛﻪ ﺑﻪ ﻣﻌﻨﺎﻱ ﻗﺒﻮﻝ ﻣﻮﺍﻓﻘﺖ ﻧﺎﻣﻪ ﺍﺳﺖ‪ ،‬ﺑﺮ ﺭﻭﻱ ‪ next‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫‪ .7‬ﺩﺭ ﺍﻳﻦ ﺻﻔﺤﻪ ﻧﻴﺰ ﭘﺲ ﺍﺯ ﭘﺮ ﻛﺮﺩﻥ ﻣﻮﺍﺭﺩ ﺧﻮﺍﺳﺘﻪ ﺷﺪﻩ‪ ،‬ﺑﺮ ﺭﻭﻱ ‪ next‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫‪ .8‬ﺩﺭ ﺍﻳﻦ ﺻﻔﺤﻪ ﺑﺎﻳﺴﺘﻲ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﺧﻮﺩ ﺭﺍﺍﻧﺘﺨﺎﺏ ﻧﻤﺎﺋﻴﺪ‪ .‬ﻫﻤﺎﻧﻄﻮﺭﻛﻪ ﻗﺒﻼ ﺍﺷﺎﺭﻩ ﺷﺪ ﺩﺭ ﺻﻮﺭﺕ‬

‫ﻛﻮﭼﻚ ﺑﻮﺩﻥ ﺩﻳﺘﺎﺳﻨﺘﺮ ﺷﻤﺎ ﻭ ﻳﺎ ﻧﺪﺍﺷﺘﻦ ﺳﺮﻭﺭ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ‪ ،‬ﺑﺎ ﺍﻧﺘﺨﺎﺏ ﮔﺰﻳﻨﻪ ﺍﻭﻝ ﻳﻚ ﻧﺴﺨﻪ ‪SQL‬‬

‫‪ Server 2008 express‬ﻛﻪ ﺩﺭ ﺩﺍﺧﻞ ﺭﺳﺎﻧﻪ ‪ vCenter‬ﻗﺮﺍﺭ ﺩﺍﺭﺩ ﺭﺍ ﻧﺼﺐ ﻧﻤﺎﺋﻴﺪ ﻛﻪ ﺩﺭ ﺍﻳﻦﺻﻮﺭﺕ ﺷﻤﺎ ﻧﻴﺎﺯ‬

‫ﺑﻪ ﻫﻴﭻﮔﻮﻧﻪ ﺗﻨﻈﻴﻤﺎﺗﻲ ﺑﺮﺍﻱ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﺧﻮﺩ ﻧﺪﺍﺭﻳﺪ‪ .‬ﺩﺭ ﻏﻴﺮ ﺍﻳﻦ ﺻﻮﺭﺕ ﮔﺰﻳﻨﻪ ﺩﻭﻡ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ ﻭ ﺍﺯ‬

‫ﻟﻴﺴﺖ ﻣﻮﺟﻮﺩ ‪ DSN‬ﻛﻪ ﺩﺭ ﺑﺨﺶ ﻗﺒﻠﻲ ﺳﺎﺧﺘﻴﺪ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫ﻧﺎﻡ ﺳﺮﻭﺭ ﺭﺍﻭﺍﺭﺩ ﻛﻨﻴﺪ‪ .‬ﺍﮔﺮ ﺳﻴﺴﺘﻢ ﻋﻀﻮ ﺩﺍﻣﻨﻪ ﺍﺳﺖ ﻧﺎﻡ ﻛﺎﻣﻞ ﺑﻪﻫﻤﺮﺍﻩ ﻧﺎﻡ ﺩﺍﻣﻨﻪ ﺭﺍ ﻭﺍﺭﺩ ﻛﻨﻴﺪ‪ .‬ﻣﺜﻼ ﺍﮔﺮ‬

‫ﻧﺎﻡ ﺳﺮﻭﺭ ‪ server1‬ﻭ ﻧﺎﻡ ﺩﺍﻣﻨﻪ ‪ mydomain.com‬ﺍﺳﺖ؛ ﺩﺭ ﺍﻳﻦ ﻗﺴﻤﺖ ‪ serverl.mydomain.com‬ﺭﺍ ﻭﺍﺭﺩ‬

‫ﻛﻨﻴﺪ‪.‬‬

‫‪ .9‬ﺍﮔﺮ ﮔﺰﻳﻨﻪ ﺩﻭﻡ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ﺑﺎﺷﻴﺪ‪ ،‬ﻳﻌﻨﻲ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﺟﺪﺍﮔﺎﻧﻪ‪ ،‬ﺩﺭ ﺍﻳﻦ ﺻﻮﺭﺕ ﭘﺲ ﺍﺯ ﺯﺩﻥ‬

‫‪ next‬ﺍﺯ ﺷﻤﺎ ﻧﺎﻡ ﻛﺎﺭﺑﺮﻱ ﻭ ﺭﻣﺰ ﻭﺭﻭﺩﻱ ﻛﻪ ﺩﺭ ‪ SQL‬ﺍﻳﺠﺎﺩ ﻛﺮﺩﻳﻢ ﺧﻮﺍﺳﺘﻪ ﺧﻮﺍﻫﺪ ﺷﺪ‪ .‬ﺍﻟﺒﺘﻪ ﺍﮔﺮ ﺍﺯ‬

‫‪ domain controller‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩﻩ ﺑﺎﺷﻴﺪ ﻣﻲﺗﻮﺍﻧﻴﺪ ‪ windows authentication‬ﻧﻴﺰ ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﻴﺪ‪.‬‬

‫ﺗﻴﻚ ﮔﺰﻳﻨﻪ ‪ use system account‬ﺭﺍ ﺑﺰﻧﻴﺪ ﻭ ﻳﺎ ﻧﺎﻡ ﻛﺎﺭﺑﺮﻱ ﺍﺯ ﺳﻴﺴﺘﻢ ﻳﺎ ﺩﺍﻣﻨﻪ ﺭﺍ ﻭﺍﺭﺩ ﻛﻨﻴﺪ ﻛﻪ‬

‫ﻣﻲﺧﻮﺍﻫﻴﺪ ﺑﺮﺍﻱ ﻭﺭﻭﺩ ﺑﻪ ‪ vCenter‬ﺍﺯ ﺁﻥ ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﻴﺪ‪ .‬ﺩﺭ ﻏﻴﺮ ﺍﻳﻦ ﺻﻮﺭﺕ‪ ،‬ﻳﻌﻨﻲ ﺍﻧﺘﺨﺎﺏ ﮔﺰﻳﻨﻪ ﻧﺼﺐ‬

‫‪ SQL server 2008 express‬ﺍﻳﻦ ﻣﺮﺣﻠﻪ ﻧﻤﺎﻳﺎﻥ ﻧﺨﻮﺍﻫﺪ ﺷﺪ‪.‬‬

‫‪ .10‬ﺩﺭ ﺍﻳﻦ ﻣﺮﺣﻠﻪ ﻣﺴﻴﺮﻱ ﻛﻪ ‪ vCenter‬ﺩﺭ ﺁﻥ ﻧﺼﺐ ﻣﻲﺷﻮﺩ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ ﻭ ﺑﺮ ﺭﻭﻱ ‪ next‬ﻛﻠﻴﻚ‬

‫‪71‬‬
 ‫ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫‪ .11‬ﺩﺭ ﺍﻳﻦ ﻗﺴﻤﺖ ﻫﻢ ﮔﺰﻳﻨﻪ ﺍﻭﻝ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ﻭ ﺑﺮﺭﻭﻱ ‪ next‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪ .‬ﺩﺭ ﻣﻮﺭﺩ ﮔﺰﻳﻨﻪ ﺩﻭﻡ ﺩﺭ‬

‫ﺍﺩﺍﻣﻪ ﺻﺤﺒﺖ ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩ‪.‬‬

‫‪ .12‬ﺩﺭ ﺍﻳﻨﺠﺎ ﺷﻤﺎﺭﻩ ﭘﻮﺭﺕ ﻫﺎﻳﻲ ﻛﻪ ‪ vCenter‬ﻧﻴﺎﺯ ﺩﺍﺭﺩ ﻣﺸﺎﻫﺪﻩ ﻣﻲﻛﻨﻴﺪ‪ .‬ﺗﻮﺻﻴﻪ ﻣﻲﺷﻮﺩ ﻫﻴﭻ ﻳﻚ ﺍﺯ‬

‫ﺷﻤﺎﺭﻩﻫﺎ ﺭﺍ ﺗﻐﻴﻴﺮ ﻧﺪﻫﻴﺪ‪ .‬ﺍﻣﺎ ﺍﮔﺮ ﻧﺎﭼﺎﺭ ﺑﻪ ﺗﻐﻴﻴﺮ ﺍﻳﻦ ﺷﻤﺎﺭﻩ ﭘﻮﺭﺕ ﻫﺎ ﺷﺪﻳﺪ‪ ،‬ﻣﺜﻼ ﭘﻮﺭﺕ ﻫﺎ ﻗﺒﻼ ﺗﻮﺳﻂ ﺑﺮﻧﺎﻣﻪ‬

‫ﻫﺎﻱ ﺩﻳﮕﺮ ﺍﻧﺘﻘﺎﻝ ﺷﺪﻩﺍﻧﺪ‪ ،‬ﺷﻤﺎﺭﻩ ﭘﻮﺭﺕ ﻫﺎﻱ ﺟﺪﻳﺪ ﺭﺍ ﺣﺘﻤﺎ ﻳﺎﺩﺩﺍﺷﺖ ﻛﺮﺩﻩ ﻭ ﺑﻪ ﭘﻴﻐﺎﻡ ﻫﺎﻳﻲ ﻛﻪ ﺑﺮﻧﺎﻣﻪﻱ‬

‫ﻧﺼﺐ‪ ،‬ﻣﻲﺩﻫﺪ ﺗﻮﺟﻪ ﻛﻨﻴﺪ‪.‬‬

‫‪ .13‬ﺩﺭ ﺻﻔﺤﻪ ﺑﻌﺪ ﻫﻢ ﺍﻣﻜﺎﻧﻲ ﺑﺮﺍﻱ ﺗﻐﻴﻴﺮ ﭘﻮﺭﺕ ﻫﺎﻳﻲ ‪ UDP , TCP‬ﻣﻮﺭﺩ ﻧﻴﺎﺯ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ﭘﻴﺸﻨﻬﺎﺩ‬

‫ﻣﻲ ﺷﻮﺩ ﺁﻧﻬﺎ ﺭﺍ ﻧﻴﺰ ﺑﺪﻭﻥ ﺗﻐﻴﻴﺮ ﺭﻫﺎ ﻛﺮﺩﻩ ﻭ ﺑﺮ ﺭﻭﻱ ‪ next‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫‪ .14‬ﺩﺭ ﺍﻳﻦ ﻣﺮﺣﻠﻪ ﻣﻲﺗﻮﺍﻧﻴﺪ ﺍﻧﺪﺍﺯﻩ ﺩﻳﺘﺎ ﺳﻨﺘﺮ ﻭ ﻣﺤﻴﻂ ﻋﻤﻠﻴﺎﺗﻲ ﺧﻮﺩ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ .‬ﺑﺮ ﺭﻭﻱ ‪next‬‬

‫ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫‪ install .15‬ﺭﺍ ﺯﺩﻩ ﻭ ﭘﺲ ﺍﺯ ﺍﻧﺠﺎﻡ ﻧﺼﺐ ﺑﺮ ﺭﻭﻱ ‪ finish‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫ﺩﺭ ﺍﻳﻨﺠﺎ ﻧﺼﺐ ‪ vCenter Server‬ﻧﻴﺰ ﺑﻪ ﭘﺎﻳﺎﻥ ﺭﺳﻴﺪ‪.‬‬

‫‪ 5-2-4‬ﻧﺼﺐ ‪ vCenter Server‬ﺩﺭ ﺣﺎﻟﺖ ‪linked mode‬‬

‫ﭼﻨﺎﻧﭽﻪ ﺩﻳﺘﺎﺳﻨﺘﺮ ﺷﻤﺎ ﺑﺴﻴﺎﺭ ﺑﺰﺭگ ﺑﺎﺷﺪ‪ 1‬ﻛﻪ ﻳﻚ ‪ vCenter Server‬ﺑﺮﺍﻱ ﻣﺪﻳﺮﻳﺖ ﺁﻥ ﻛﺎﻓﻲ ﻧﺒﺎﺷﺪ ﻭ ﻳﺎ‬

‫ﻣﺤﺪﻭﺩﻳﺖﻫﺎﻱ ﺩﻳﮕﺮ ﻣﺜﻞ ﻣﺤﺪﻭﺩﻳﺖﻫﺎﻱ ﺟﻐﺮﺍﻓﻴﺎﻳﻲ ﻣﺎﻧﻊ ﺍﺯ ﻣﺪﻳﺮﻳﺖ ﺩﻳﺘﺎ ﺳﻨﺘﺮ ﺗﻮﺳﻂ ﻓﻘﻂ ﻳﻚ ‪vCenter‬‬

‫ﻣﻲﺷﻮﺩ‪ ،‬ﻻﺯﻡ ﺍﺳﺖ ﭼﻨﺪﻳﻦ ‪ vCenter‬ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﻢ‪.‬‬

‫ﺩﺭ ‪ vSphere‬ﺍﻣﻜﺎﻧﻲ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ﺑﺘﻮﺍﻥ ﭼﻨﺪﻳﻦ ‪ vCenter Server‬ﺭﺍ ﺑﺎ ﻭﺭﻭﺩ ﺑﻪ ﻳﻜﻲ ﺍﺯ ﺁﻧﻬﺎ ﻣﺪﻳﺮﻳﺖ‬

‫ﻛﺮﺩ ﻛﻪ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ‪ linked-mode‬ﻣﻲﻧﺎﻣﻨﺪ‪ .‬ﺑﺮﺍﻱ ﻧﺼﺐ ‪ vCenter‬ﺩﺭ ﺍﻳﻦ ﻣﻮﺭﺩ ﻣﺮﺍﺣﻞ ﻧﺼﺐ ‪ vCenter‬ﺭﺍ‬

‫‪ 1‬ﻳﻚ ‪ vCenter Server‬ﻣﻲﺗﻮﺍﻧﺪ ﺗﺎ ‪ 1000‬ﻣﻴﺰﺑﺎﻥ ‪ ESXi‬ﻭ ﻳﺎ ‪ 10000‬ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺭﺍ ﺗﺤﺖ ﻣﺪﻳﺮﻳﺖ ﺧﻮﺩ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‬

‫‪72‬‬
‫ﺗﺎ ﻣﺮﺣﻠﻪ ‪ 10‬ﻣﺎﻧﻨﺪ ﺣﺎﻟﺖ ﻋﺎﺩﻱ ﺍﺩﺍﻣﻪ ﺩﻫﻴﺪ ﻭﻟﻲ ﺩﺭ ﻣﺮﺣﻠﻪ ‪ 11‬ﮔﺰﻳﻨﻪ ﺩﻭﻡ ﻳﻌﻨﻲ ‪ linked-mode‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ‬

‫ﻛﻨﻴﺪ‪.‬‬

‫ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ﺩﺭ ﻣﺮﺣﻠﻪ ﺑﻌﺪ ﻧﺎﻡ ﺳﺮﻭﺭ ‪ vCenter Server‬ﻛﻪ ﻗﺒﻼ ﻧﺼﺐ ﻭ ﺭﺍﻩﺍﻧﺪﺍﺯﻱ ﺷﺪﻩ ﺍﺳﺖ ﺭﺍ ﻭﺍﺭﺩ‬

‫ﻛﻨﻴﺪ‪ .‬ﻣﺮﺍﺣﻞ ﺑﻌﺪﻱ ﻧﻴﺰ ﻣﺎﻧﻨﺪ ﺣﺎﻟﺖ ﻧﺼﺐ ﺳﺎﺩﻩ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪ .‬ﻳﻌﻨﻲ ﻣﺮﺍﺣﻞ ‪ 12‬ﻭ ﺑﻪ ﺑﻌﺪ‪ .‬ﺍﻟﺒﺘﻪ ﻳﻚ ‪vCenter‬‬

‫‪ Server‬ﻛﻪ ﺑﻪﺻﻮﺭﺕ ‪ Single‬ﻧﺼﺐ ﺷﺪﻩ ﺍﺳﺖ ﺭﺍ ﻧﻴﺰ ﻣﻲﺗﻮﺍﻥ ﭘﺲ ﺍﺯ ﻧﺼﺐ‪ ،‬ﺑﻪ ﻋﻀﻮﻳﺖ ﻳﻚ ‪linked-mode‬‬

‫‪ group‬ﺩﺭﺁﻭﺭﺩ‪ .‬ﺍﻳﻦ ﻛﺎﺭ ﺑﻮﺳﻴﻪ ﺍﺑﺰﺍﺭ ‪ vCenter Server linked mode configuration‬ﻛﻪ ﺑﺎ ‪vCenter‬‬

‫‪ Server‬ﻧﺼﺐ ﻣﻲﺷﻮﺩ‪ ،‬ﺍﻣﻜﺎﻥ ﭘﺬﻳﺮ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪.‬‬

‫ﺑﺮﺍﻱ ﻧﺼﺐ ‪ vCenter‬ﺩﺭﺣﺎﻟﺖ ‪ linked-mode‬ﺗﻮﺟﻪ ﺑﻪ ﻧﻜﺎﺕ ﺯﻳﺮ ﺿﺮﻭﺭﻱ ﺍﺳﺖ‪.‬‬

‫ﺗﻤﺎﻣﻲ ‪vCenter Server‬ﻫﺎﻱ ﻋﻀﻮ ﻳﻚ ﺩﺍﻣﻨﻪ ﺑﺎﺷﻨﺪ؛ ﻭ ﻳﺎ ﺍﮔﺮ ﻋﻀﻮ ﺩﺍﻣﻨﻪﻫﺎﻱ ﻣﺨﺘﻠﻒ ﻫﺴﺘﻨﺪ‪ ،‬ﺑﻴﻦ‬ ‫‪-‬‬

‫ﺩﺍﻣﻨﻪ ﻫﺎ ﺑﺎﻳﺴﺘﻲ ‪ two- way trust relationship‬ﺑﺮﻗﺮﺍﺭ ﺑﺎﺷﺪ‪.‬‬

‫ﺳﺮﻭﻳﺲ ‪ DNS‬ﺑﺎﻳﺴﺘﻲ ﻓﻌﺎﻝ ﺑﻮﺩﻩ ﻭ ﻧﺎﻡ ﺳﺮﻭﺭﻫﺎ ﺑﺎ ﻧﺎﻡ ‪DNS‬ﺷﺎﻥ ﻣﻄﺎﺑﻖ ﺑﺎﺷﺪ‪.‬‬ ‫‪-‬‬

‫ﺳﺮﻭﺭﻱ ﻛﻪ ‪ vCenter‬ﺍﺳﺖ ﻧﻤﻲﺗﻮﺍﻧﺪ ﻫﻤﺰﻣﺎﻥ ‪ Domain Controller‬ﻭ ﻳﺎ ‪Terminal Server‬‬ ‫‪-‬‬

‫ﺑﺎﺷﺪ‪.‬‬

‫‪ vCenter Server5‬ﺭﺍ ﻧﻤﻲﺗﻮﺍﻥ ﺑﺎ ﻧﺴﺨﻪﻫﺎﻱ ﻗﺒﻠﻲ ‪ vCenter‬ﺩﺭﺣﺎﻟﺖ ‪ linked-mode‬ﻗﺮﺍﺭ ﺩﺍﺩ‬ ‫‪-‬‬

‫ﻫﺮ ﻳﻚ ﺍﺯ ‪vCenter‬ﻫﺎ ﺑﺎﻳﺴﺘﻲ ﺑﺎﻧﻚ ﺍﻃﻼﻋﺎﺗﻲ ﺧﻮﺩ ﺭﺍ ﺑﻪﻃﻮﺭ ﻣﺠﺰﺍ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ )ﺍﻟﺰﺍﻣﺎ ﻧﻪ ﺳﺮﻭﺭﻫﺎﻱ‬ ‫‪-‬‬

‫ﺟﺪﺍﮔﺎﻧﻪ (‬

‫ﺩﺭ ﺿﻤﻦ ﻫﺮ ﻳﻚ ﺍﺯ ‪ vCenter‬ﺑﻄﻮﺭ ﺟﺪﺍﮔﺎﻧﻪ ﻣﺪﻳﺮﻳﺖ ﻣﻲ ﺷﻮﻧﺪ ﻳﻌﻨﻲ ﻣﺜﻼ ﻧﻤﻲﺗﻮﺍﻥ ﻋﻤﻞ‪ vMotion‬ﺭ ﺍ‬

‫ﺑﻴﻦ ﺩﻭ ﺳﺮﻭﺭ ﻛﻪ ﻋﻀﻮ ‪ vCenter‬ﻣﺨﺘﻠﻒ ﻫﺴﺘﻨﺪ ﺍﻧﺠﺎﻡ ﺩﺍﺩ‪.‬‬

‫‪ 3-4‬ﻧﺼﺐ ‪ vSphere Client‬ﺑﺮﺍﻱ ﻭﺭﻭﺩ ﺑﻪ ‪vCenter Server‬‬

‫ﺑﺮﺍﻱ ﻭﺭﻭﺩ ﺑﻪ ﺑﺨﺶ ﻣﺪﻳﺮﻳﺖ ‪ vCenter Server‬ﺑﻪ ﺩﻭ ﻃﺮﻳﻖ ﻣﻲﺗﻮﺍﻥ ﻋﻤﻞ ﻛﺮﺩ‪ .‬ﻳﻜﻲ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ‬

‫‪73‬‬
‫‪ vSphere Client‬ﻭ ﺩﻳﮕﺮﻱ ‪ vSphere web client‬ﻛﻪ ﺍﻭﻟﻲ ﻳﻚ ﻛﺎﺭﺑﺮﺩ ﻭﻳﻨﺪﻭﺯﻱ ﺍﺳﺖ ﻭ ﺩﻳﮕﺮﻱ ﻳﻚ‬

‫ﻛﺎﺭﺑﺮﺩ ﺗﺤﺖ ﻭﺏ ﻛﻪ ﻣﺎ ﺍﺯ ‪ vSphere Client‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﻛﻨﻴﻢ‪.‬‬

‫‪ Web Client , vSphere Client‬ﺩﺭ ﺩﺍﺧﻞ ﺭﺳﺎﻧﻪ ﺣﺎﻭﻱ ‪ vCenter Server‬ﻧﻴﺰ ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪ .‬ﺑﻪ ﺩﻟﻴﻞ‬

‫ﺳﺎﺩﮔﻲ ﻧﺼﺐ ‪ ،vSphere Client‬ﺍﺯ ﺗﻮﺿﻴﺢ ﺩﺍﺩﻥ ﺁﻥ ﺧﻮﺩﺩﺍﺭﻱ ﻣﻲﻛﻨﻴﻢ‪.‬‬

‫‪ vSphere Client‬ﻣﻲﺗﻮﺍﻧﺪ ﺑﺮ ﺭﻭﻱ ﺳﺮﻭﺭ ‪ vCenter‬ﻧﺼﺐ ﺷﻮﺩ ﻭ ﻳﺎ ﺑﺮ ﺭﻭﻱ ﻳﻚ ﺳﻴﺴﺘﻢ ﺩﻳﮕﺮ‪ .‬ﻧﻴﺎﺯ ﺑﻪ‬

‫ﺳﺨﺖﺍﻓﺰﺍﺭ ﺧﺎﺻﻲ ﻫﻢ ﻧﺪﺍﺭﺩ ﻭ ﺑﺮ ﺭﻭﻱ ﺗﻤﺎﻣﻲ ﻧﺴﺨﻪﻫﺎﻱ ﻭﻳﻨﺪﻭﺯ ‪ XP‬ﻭ ﺑﻪ ﺑﻌﺪ ﻗﺎﺑﻞ ﻧﺼﺐ ﻣﻲﺑﺎﺷﺪ‪.‬‬

‫ﭘﺲ ﺍﺯﻧﺼﺐ ‪ ،vSphere Client‬ﺁﻥ ﺭﺍ ﺍﺟﺮﺍ ﻛﻨﻴﺪ‪ .‬ﺩﺭ ﻗﺴﻤﺖ ‪ IP Address/name‬ﻧﺎﻡ ﻭ ﻳﺎ ﺁﺩﺭﺱ ‪IP‬‬

‫ﺳﺮﻭﺭ ‪ vCenter Server‬ﺭﺍ ﻭﺍﺭﺩ ﻛﻨﻴﺪ ﻭ ﺩﺭ ﻗﺴﻤﺖ ‪ password , username‬ﻧﺎﻡ ﻛﺎﺭﺑﺮﻱ ﻛﻪ ﺣﻖ ﺩﺳﺘﺮﺳﻲ‬

‫ﺑﻪ ‪ vCenter‬ﺭﺍ ﺩﺍﺭﺩ ﻭ ﻛﻠﻤﻪ ﻋﺒﻮﺭ ﺁﻥ ﺭﺍ ﻭﺍﺭﺩ ﻛﻨﻴﺪ‪ .‬ﺍﮔﺮ ﺑﺎ ﻛﺎﺭﺑﺮﻱ ﻛﻪ ﺣﻖ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ‪ vCenter‬ﺭﺍ ﺩﺍﺭﺩ ﺑﻪ‬

‫ﺳﻴﺴﺘﻢ ‪ login‬ﻛﺮﺩﻩ ﺑﺎﺷﻴﺪ)ﻣﺜﻞ ﺯﻣﺎﻧﻲ ﻛﻪ ‪ vSphere Client‬ﺑﺮ ﺭﻭﻱ ﺳﺮﻭﺭ ‪ vCenter‬ﻧﺼﺐ ﺷﺪﻩ ﺍﺳﺖ ( ﺑﺎ‬

‫ﺯﺩﻥ ﺗﻴﻚ ‪ Use Windows Authentication‬ﻧﻴﺎﺯﻱ ﺑﻪ ﻭﺍﺭﺩ ﻛﺮﺩﻥ ﻧﺎﻡ ﻛﺎﺭﺑﺮﻱ ﻭ ﻛﻠﻤﻪ ﻋﺒﻮﺭ ﻧﻴﺰ ﻧﺨﻮﺍﻫﺪ ﺑﻮﺩ ‪.‬‬

‫ﭘﺲ ﺍﺯ ﻭﺭﻭﺩ ﺑﻪ ﺳﻴﺴﺘﻢ ﺑﺮﺍﻱ ﺍﻭﻟﻴﻦ ﺑﺎﺭ‪ ،‬ﺍﮔﺮ ﺑﻪ ‪ login ، ESXi‬ﻛﺮﺩﻩ ﺑﺎﺷﻴﺪ ﺷﻜﻞ ‪ 9-4‬ﻭ ﺍﮔﺮ ﺑﻪ ‪vCenter‬‬

‫‪ login ، Server‬ﻛﺮﺩﻩ ﺑﺎﺷﻴﺪ ﺷﻜﻞ‪ 4-10‬ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﺧﻮﺍﻫﻴﺪ ﻛﺮﺩ‪.‬‬

‫ﺷﻜﻞ ‪ . 9 4‬ﺍﺗﺼﺎﻝ ﺑﻪ ‪ ESXi‬ﺑﻪﻛﻤﻚ ‪vSphere Client‬‬

‫‪74‬‬
 ‫ﺩﺭ ﻓﺼﻞﻫﺎﻱ ﺑﻌﺪ ﻧﺤﻮﻩ ﻛﺎﺭﺑﺎ ‪ vCenter Server‬ﻭ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺗﻮﺍﻧﺎﻳﻲﻫﺎﻱ ﺁﻥ ﺭﺍ ﺧﻮﺍﻫﻴﻢ ﺁﻣﻮﺧﺖ‪.‬‬

‫ﺷﻜﻞ ‪ . 10 4‬ﺍﺗﺼﺎﻝ ﺑﻪ ‪ vCenter Server‬ﺑﻪﻛﻤﻚ ‪vSphere Client‬‬

‫‪ 4-4‬ﻧﺼﺐ ‪vSphere Web Client‬‬

‫ﮔﺮ ﭼﻪ ‪ vSphere Client‬ﺗﻤﺎﻡ ﻗﺎﺑﻠﻴﺖ ‪ vCenter‬ﺭﺍ ﺩﺭ ﺩﺳﺘﺮﺱ ﻗﺮﺍﺭ ﻣﻲﺩﻫﺪ ﻭ ﻛﺎﻣﻠﺘﺮ ﻭ ﻗﻮﻱﺗﺮ ﺍﺯ ‪web‬‬

‫‪ client‬ﺍﺳﺖ‪ ،‬ﺍﻣﺎ ﮔﺎﻫﻲ ﻣﻤﻜﻦ ﺍﺳﺖ ﻣﺪﻳﺮ ﺳﺎﻳﺖ ﺩﺭ ﻣﺤﻠﻲ ﺑﺎﺷﺪ ﻛﻪ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ‪vSphere web client‬‬

‫ﻧﺪﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬

‫ﺩﺭ ﺍﻳﻦ ﻭﺿﻌﻴﺖ ﻣﻲﺗﻮﺍﻧﺪ ﺑﻪ ﻛﻤﻚ ﻳﻚ ‪ browser‬ﻣﺜﻞ ‪ IE‬ﻭ ﻳﺎ ﻓﺎﻳﺮﻓﺎﻛﺲ ﻛﻪ ﻣﺠﻬﺰ ﺑﻪ ‪adobe flash‬‬

‫‪ player‬ﻭ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻳﻚ ﺍﺗﺼﺎﻝ ﺍﻳﻨﺘﺮﻧﺖ ﺑﻪ ‪ vSphere web client‬ﻣﺘﺼﻞ ﺷﺪﻩ ﻭ ﺳﻴﺴﺘﻢ ﻣﺠﺎﺯﻱ ﺭﺍ ﺍﺯ ﺭﺍﻩ‬

‫ﺩﻭﺭ ﻣﺪﻳﺮﻳﺖ ﻛﻨﺪ‪ .‬ﺑﺪﻳﻦ ﻣﻨﻈﻮﺭ ﺍﺑﺘﺪﺍ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪ vSphere web client‬ﺭﺍ ﻧﺼﺐ ﻣﻲﻛﻨﻴﻢ‪ .‬ﻣﻲﺗﻮﺍﻥ ﺍﻳﻦ ﻧﺮﻡﺍﻓﺰﺍﺭ‬

‫ﺭﺍﺑﺮ ﺭﻭﻱ ﺳﺮﻭﺭ ‪ vCenter‬ﻧﻴﺰ ﻧﺼﺐ ﻛﺮﺩ‪ .‬ﺍﻳﻦ ﺑﺮﻧﺎﻣﻪ ﺩﺭ ﺭﺳﺎﻧﻪ ﺣﺎﻭﻱ ‪ vCenter‬ﻗﺮﺍﺭ ﺩﺍﺭﺩ ﻭ ﻓﺮﺍﻳﻨﺪ ﻧﺼﺐ ﺁﻥ‬

‫ﻧﻴﺰ ﺑﺴﻴﺎﺭ ﺳﺎﺩﻩ ﺍﺳﺖ ﻛﻪ ﺩﺭ ﺍﻳﻨﺠﺎ ﺩﺭ ﻣﻮﺭﺩ ﺁﻥ ﺻﺤﺒﺖ ﻧﻤﻲﻛﻨﻴﻢ‪.‬‬

‫ﭘﺲ ﺍﺯ ﻧﺼﺐ ‪ web client‬ﻻﺯﻡ ﺍﺳﺖ ﺗﺎ ‪ vCenter‬ﺭﺍ ﺩﺭ ‪ web client‬ﺛﺒﺖ ﻛﻨﻴﺪ‪ .‬ﺑﺪﻳﻦ ﻣﻨﻈﻮﺭ ﺑﻪ‬

‫ﺳﻴﺴﺘﻤﻲ ﻛﻪ ‪ vSphere web client‬ﺑﺮ ﺭﻭﻱ ﺁﻥ ﻧﺼﺐ ﺍﺳﺖ ‪ login‬ﻛﺮﺩﻩ ﭘﺲ ﺍﺯ ﺍﺟﺮﺍﻱ ‪ IE) browser‬ﻭ ﻳﺎ‬

‫‪75‬‬
 ‫ﻓﺎﻳﺮ ﻓﺎﻛﺲ( ﺁﺩﺭﺱ ﺳﺮﻭﺭ ‪ vSphere web client‬ﺭﺍ ﻭﺍﺭﺩ ﻛﻨﻴﺪ)ﻳﻌﻨﻲ ﻫﻤﻴﻦ ﺳﺮﻭﺭ(‬

‫ﺁﺩﺭﺱ ﺑﺼﻮﺭﺕ ﺯﻳﺮ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‬

‫ﻣﺜﻼﺍﮔﺮﺁﺩﺭﺱ ‪ IP‬ﺳﺮﻭﺭ ‪ 192.168.10.10 ، vSphere web client‬ﺍﺳﺖ ﺍﻳﻦ ﺁﺩﺭﺱ ﺑﺼﻮﺭﺕ ﺯﻳﺮ ﺧﻮﺍﻫﺪ‬

‫ﺑﻮﺩ‪:‬‬

‫‪https://192.160.10.10:9443/admin-app‬‬
‫ﭘﺲ ﺍﺯ ﻟﻮﺩ ﺷﺪﻥ ﺻﻔﺤﻪ ﺍﺯ ﺳﻤﺖ ﺭﺍﺳﺖ ﺑﺎﻻﻱ ﺻﻔﺤﻪ ‪ register vCenter Server‬ﺭﺍ ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪.‬‬

‫ﺩﺭ ﭘﻨﺠﺮﻩ ﺑﺎﺯ ﺷﺪﻩ ﻛﻪ ﺑﺼﻮﺭﺕ ﺷﻜﻞ ‪ 11-4‬ﺍﺳﺖ ﺍﻃﻼﻋﺎﺕ ﺧﻮﺍﺳﺘﻪ ﺷﺪﻩ ﺭﺍ ﺑﺼﻮﺭﺕ ﺯﻳﺮ ﻭﺍﺭﺩ ﻛﻨﻴﺪ‪.‬‬

‫ﺩﺭ ﻛﺎﺩﺭ ﺍﻭﻝ‪ IP‬ﺳﺮﻭﺭ‪ vCenter‬ﺭﺍ ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺷﻜﻞ ﻧﺸﺎﻥ ﺩﺍﺩﻩ ﺷﺪﻩ ﻭﺍﺭﺩ ﻛﻨﻴﺪ‪.‬‬

‫ﺩﺭ ﻛﺎﺩﺭﻫﺎﻱ ﺩﻭﻡ ﻭ ﺳﻮﻡ ﻧﺎﻡ ﻛﺎﺭﺑﺮﻱ ﻭﺭﻣﺰ ﻋﺒﻮﺭﻱ ﻛﻪ ﺣﻖ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺑﺨﺶ ﻣﺪﻳﺮﻳﺖ ‪ vCenter‬ﺭﺍ ﺩﺍﺭﻧﺪ‬

‫ﻭﺍﺭﺩ ﻛﻨﻴﺪ‪.‬ﺩﺭ ﻛﺎﺩﺭ ﺍﻧﺘﻬﺎﻳﻲ ﻫﻢ ﻧﺎﻡ ﺳﺮﻭﺭﻱ ﻛﻪ‪ vSphere web client‬ﺑﺮ ﺭﻭﻱ ﺁﻥ ﻧﺼﺐ ﺍﺳﺖ ﺭﺍ ﻭﺍﺭﺩ ﻛﻨﻴﺪ ﻭ‬

‫ﺩﻛﻤﻪ ‪ register‬ﺭﺍ ﺑﺰﻧﻴﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 11 4‬ﺍﻓﺰﻭﺩﻥ ﺳﺮﻭﺭﻫﺎﻱ ‪ vCenter‬ﺑﻪ ‪ vSphere web Cliebt‬ﺑﺮﺍﻱ ﻣﺪﻳﺮﻳﺖ‬

‫ﭘﺲ ﺍﺯﺛﺒﺖ ‪vCenter‬ﻫﺎ ﺍﺯ ﻫﺮ ﺳﻴﺴﺘﻤﻲ ﻭ ﺗﻨﻬﺎ ﺑﻪ ﻛﻤﻚ ﻳﻚ ‪ browser‬ﻣﻴﺘﻮﺍﻧﻴﺪ ﺑﻪ ﺳﺮﻭﺭ ‪webclient‬‬

‫ﺗﻮﺳﻂ ﺁﺩﺭﺱ ﺑﻪ ﺻﻮﺭﺕ ﺯﻳﺮ ﺑﻪ ﺑﺨﺶ ﻣﺪﻳﺮﻳﺖ ‪ webclient‬ﻭﺍﺭﺩ ﺷﻮﻳﺪ‪.‬‬

‫‪https://webclient-ipaddress/vSphere-client‬‬
‫ﻣﺜﻼ ﺍﮔﺮ‪ ip‬ﺳﺮﻭﺭ‪ 192.168.58.1 web client‬ﺍﺳﺖ ﺁﺩﺭﺱ ﺑﺼﻮﺭﺕ ﺯﻳﺮ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪.‬‬

‫‪https://192.168.58.1/vSphere-client‬‬
‫ﭘﺲ ﺍﺯﻟﻮﺩ ﺷﺪﻥ ﺩﺭ ﭘﺎﻳﻴﻦ ﺳﻤﺖ ﭼﭗ ﺻﻔﺤﻪ ﺑﺎ ﺍﻧﺘﺨﺎﺏ ‪ vCenter‬ﻭ ﻭﺍﺭﺩ ﻛﺮﺩﻥ ﻧﺎﻡ ﻛﺎﺭﺑﺮﻱ ﻭ ﺭﻣﺰ ﻋﺒﻮﺭ‬

‫ﺁﻥ ﺑﻪ ﺑﺨﺶ ﻣﺪﻳﺮﻳﺖ ﺁﻥ ﻭﺍﺭﺩ ﺷﻮﻳﺪ‪ .‬ﭘﺲ ﺍﺯ‪ ،login‬ﺑﺎﺻﻔﺤﻪﺍﻱ ﻣﺸﺎﺑﻪ ﺷﻜﻞ‪ 12-4‬ﻣﻮﺍﺟﻪ ﺧﻮﺍﻫﻴﺪ ﺷﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 12 4‬ﺑﺨﺶ ﻣﺪﻳﺮﻳﺖ ﺩﺭ ‪vSphere web Client‬‬

‫‪ vSphere web client‬ﻣﺤﺪﻭﺩﻳﺖﻫﺎﻳﻲ ﻫﻢ ﻧﺴﺒﺖ ﺑﻪ ‪ vSphere Client‬ﺩﺍﺭﺩ ﻛﻪ ﺍﺯ ﺁﻥ ﺟﻤﻠﻪ ﻣﻲﺗﻮﺍﻥ ﺑﻪ‬

‫ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺍﺷﺎﺭﻩ ﻛﺮﺩ‪:‬‬

‫ﺩﺭ ‪ web client‬ﺑﺮﺍﻱ ﺍﺿﺎﻓﻪ ﻛﺮﺩﻥ ‪vCenter‬ﻫﺎ ﺑﺮﺍﻱ ﻣﺪﻳﺮﻳﺖ ﺑﺎﻳﺪ ﺑﻪ ﺳﻴﺴﺘﻤﻲ ﻛﻪ ‪ web client‬ﺑﺮ‬ ‫‪-‬‬

‫ﺭﻭﻱ ﺁﻥ ﻧﺼﺐ ﺷﺪﻩ ‪ login‬ﻛﺮﺩ ‪.‬‬

‫ﺩﺭ ‪ web client‬ﻧﻤﻲﺗﻮﺍﻥ ‪ cluster‬ﺍﻳﺠﺎﺩ ﻛﺮﺩ‪.‬‬ ‫‪-‬‬

‫ﺩﺭ ‪ web client‬ﻧﻤﻲﺗﻮﺍﻥ ﻣﻴﺰﺑﺎﻥﻫﺎﻱ ‪ ESXi‬ﺭﺍ ﺍﺿﺎﻓﻪ ﻛﺮﺩ‪.‬‬ ‫‪-‬‬

‫ﻭ ﺑﺴﻴﺎﺭﻱ ﺍﺯ ﻣﻮﺍﺭﺩ ﺩﻳﮕﺮ ﻛﻪ ﺑﺎ ﻭﺍﺭﺩ ﺷﺪﻥ ﺑﻪ ‪ web client‬ﺁﻧﻬﺎ ﺭﺍ ﺧﻮﺍﻫﻴﺪ ﺩﻳﺪ‪.‬‬ ‫‪-‬‬

‫‪77‬‬
‫ﻓﺼﻞ ﭘﻨﺠﻢ‬

‫ﺩﺳﺘﮕﺎﻩﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺩﺍﺩﻩ‬

‫ﺳﻴﺴﺘﻢﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻳﻜﻲ ﺍﺯ ﻣﻬﻤﺘﺮﻳﻦ ﺑﺨﺶﻫﺎﻱ ﻫﺮ ﺳﻴﺴﺘﻢ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ ﺍﺳﺖ‪ .‬ﺩﺭ ﺍﻳﻦ ﺑﻴﻦ‬

‫ﺳﻴﺴﺘﻢﻫﺎﻱ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ﺍﺷﺘﺮﺍﻛﻲ ﺑﻪ ﺩﻟﻴﻞ ﺑﺎﻻ ﺑﺮﺩﻥ ﻛﺎﺭﺍﻳﻲ ﻭ ﺩﺳﺘﺮﺳﻲ ﺍﺯ ﺍﻫﻤﻴﺖ ﻭﻳﮋﻩ ﺍﻱ ﺑﺮﺧﻮﺭﺩﺍﺭﻧﺪ‪.‬‬

‫ﺑﻪ ﺩﻟﻴﻞ ﻭﺍﺑﺴﺘﮕﻲ ﺑﺴﻴﺎﺭﻱ ﺍﺯ ﻗﺎﺑﻠﻴﺖ ﻫﺎﻱ ﺍﺳﺎﺳﻲ ‪ vSphere‬ﺑﻪ ﺩﺳﺘﮕﺎﻩﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺍﺷﺘﺮﺍﻛﻲ ﺍﻳﻦ‬

‫ﺳﻴﺴﺘﻤﻬﺎ ﻳﻜﻲ ﺍﺯ ﺣﻴﺎﺗﻲﺗﺮﻳﻦ ﺍﺟﺰﺍﻱ ﭘﻠﺘﻔﺮﻡ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ ‪ VMware‬ﺍﺳﺖ‪.‬‬

‫ﺩﺭ ﺍﺩﺍﻣﻪ ﺍﻳﻦ ﻓﺼﻞ ﺍﺑﺘﺪﺍ ﺩﺭ ﻣﻮﺭﺩ ﺍﻧﻮﺍﻉ ﺳﻴﺴﺘﻢﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺻﺤﺒﺖ ﻣﻲﻛﻨﻴﻢ‪ .‬ﭘﺲ ﺍﺯ ﺁﻥ ﻳﻚ‬

‫‪ ISCSI‬ﺭﺍ ﺑﻪ ﻛﻤﻚ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ‪ openfiler‬ﺷﺒﻴﻪﺳﺎﺯﻱ ﻛﺮﺩﻩ ﻭﺩﺭ ﺍﻧﺘﻬﺎ ﺍﻳﻦ ‪ ISCSI SAN‬ﺭﺍ ﺩﺭ ﭘﻠﺘﻔﺮﻡ‬

‫ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺑﻜﺎﺭ ﺧﻮﺍﻫﻴﻢ ﮔﺮﻓﺖ‪.‬‬

‫‪78‬‬
 ‫‪ 1-5‬ﺍﻧﻮﺍﻉ ﺳﻴﺴﺘﻢﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ‬

‫ﺫﺧﻴﺮﻩ ﺳﺎﺯﻫﺎ ﺭﺍ ﺍﺯﻧﻈﺮ ﻧﻮﻉ ﺍﺗﺼﺎﻝ ﺑﻪ ﺳﺮﻭﺭ ﻣﻲﺗﻮﺍﻥ ﺑﻪ ﺩﻭ ﺩﺳﺘﻪ ﺗﻘﺴﻴﻢ ﻛﺮﺩ‪:‬‬

‫ﻧﻮﻉ ﺍﻭﻝ ﺫﺧﻴﺮﻩﺳﺎﺯﻫﺎ ﺑﺎ ﺍﺗﺼﺎﻝ ﻣﺴﺘﻘﻴﻢ ﺑﻪ ﺳﺮﻭﺭ ﻭ ﻧﻮﻉ ﺩﻭﻡ ﺳﻴﺴﺘﻢﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺍﺷﺘﺮﺍﻛﻲ ﻳﺎ ﻫﻤﺎﻥ‬

‫‪ Shared Storage‬ﻫﺎ ﻫﺴﺘﻨﺪ ﻛﻪ ﺩﺭ ﺍﺩﺍﻣﻪ ﻫﺮﻳﻚ ﺭﺍ ﺑﺮﺭﺳﻲ ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩ‪.‬‬

‫‪ 1-1-5‬ﺫﺧﻴﺮﻩﺳﺎﺯﻫﺎ ﺑﺎ ﺍﺗﺼﺎﻝ ﻣﺴﺘﻘﻴﻢ ﺑﻪ ﺳﺮﻭﺭ‬

‫ﺍﻳﻦ ﻧﻮﻉ ﺫﺧﻴﺮﻩﺳﺎﺯﻫﺎ‪ ،‬ﻫﻤﺎﻥ ﺩﻳﺴﻚﻫﺎﻱ ﻣﺤﻠﻲ ﻫﺴﺘﻨﺪ ﻛﻪ ﺍﺧﺘﺼﺎﺭﺍ ﺑﻪ ﺁﻧﻬﺎ ‪ 1DAS‬ﮔﻔﺘﻪ ﻣﻲﺷﻮﺩ‪ .‬ﺍﻳﻦ‬

‫ﻧﻮﻉ ﺫﺧﻴﺮﻩﺳﺎﺯﻱﻫﺎ ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺑﺎﺭﻫﺎ ﻧﻴﺰ ﺑﻪ ﺁﻥ ﺍﺷﺎﺭﻩ ﺷﺪ‪ ،‬ﺑﻪ ﺟﻬﺖ ﻋﺪﻡ ﭘﺸﺘﻴﺒﺎﻧﻲ ﺍﺯ ﺳﻴﺴﺘﻢﻫﺎﻱ ﭘﻴﺸﺮﻓﺘﻪ‬

‫‪ vSphere‬ﺩﺭ ﺍﻳﻦ ﻣﺠﻤﻮﻋﻪ ﻛﺎﺭﺑﺮﺩ ﻛﻤﻲ ﺩﺍﺭﻧﺪ‪ .‬ﺍﻟﺒﺘﻪ ﺍﻳﻦ ﻧﻮﻉ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻣﺰﺍﻳﺎﻳﻲ ﻧﻴﺰ ﺩﺍﺭﻧﺪ ﻛﻪ ﺍﺯ ﺟﻤﻠﻪ ﺁﻥ‬

‫ﻣﻲﺗﻮﺍﻥ ﺑﻪ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺍﺷﺎﺭﻩ ﻛﺮﺩ‪.‬‬

‫ﻧﺼﺐ ﻭ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﺁﺳﺎﻥ‬ ‫‪-‬‬

‫ﺍﺭﺯﺍﻧﻲ )ﻧﻴﺎﺯ ﺑﻪ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﻭ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺍﺿﺎﻓﻲ ﻧﺪﺍﺭﺩ‪ ،‬ﭼﺮﺍ ﻛﻪ ﺗﻤﺎﻣﻲ ﺑﺎﺭ ﭘﺸﺘﻴﺒﺎﻧﻲ ﻭ ﻣﺪﻳﺮﻳﺖ ﺁﻥ ﺑﻪ‬ ‫‪-‬‬

‫ﻋﻬﺪﻩ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﻭ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﺳﺮﻭﺭ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪(.‬‬

‫ﻋﺪﻡ ﻧﻴﺎﺯ ﺑﻪ ﺍﺗﺼﺎﻻﺕ ﺷﺒﻜﻪ ﺍﺿﺎﻓﻲ‬ ‫‪-‬‬

‫‪ 1-1-5‬ﺳﻴﺴﺘﻢﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺍﺷﺘﺮﺍﻛﻲ‬

‫ﻧﻮﻉ ﺩﻭﻡ ﺳﻴﺴﺘﻢﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﺍﺷﺘﺮﺍﻛﻲ ﻳﺎ ﻫﻤﺎﻥ ‪ Shared Storage‬ﻫﺎ ﻫﺴﺘﻨﺪ ﻛﻪ ﺍﻧﻮﺍﻉ ﻭ ﺍﻗﺴﺎﻡ‬

‫ﺯﻳﺎﺩﻱ ﺩﺍﺭﻧﺪ ﻛﻪ ﻫﺮ ﻳﻚ ﺩﺭ ﺳﻄﻮﺡ ﻣﺨﺘﻠﻒ ﺍﺯ ﺗﻜﻨﻮﻟﻮژﻱ ﻫﺎﻱ ﻣﺘﻔﺎﻭﺗﻲ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﻛﻨﺪ‪ .‬ﺫﺧﻴﺮﻩﺳﺎﺯﻫﺎﻱ‬

‫ﺍﺷﺘﺮﺍﻛﻲ ﺑﻪ ﺩﻭ ﺩﺳﺘﻪ ﺍﺻﻠﻲ ‪ NAS‬ﻭ ‪ SAN‬ﺗﻘﺴﻴﻢ ﻣﻲ ﺷﻮﻧﺪ ﻛﻪ ﺩﺭ ﺍﺩﺍﻣﻪ ﺗﻮﺿﻴﺢ ﻣﺨﺘﺼﺮﻱ ﺩﺭ ﻣﻮﺭﺩ ﻫﺮ ﻳﻚ‬

‫‪Direct Attached Storage 1‬‬

‫‪79‬‬
 ‫ﺍﺭﺍﺋﻪ ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩ‪.‬‬

‫‪ 1-1-1-5‬ﺫﺧﻴﺮﻩﺳﺎﺯﻫﺎﻱ ‪SAN1‬‬

‫ﻫﻤﺎﻥ ﻃﻮﺭ ﻛﻪ ﺍﺯ ﻧﺎﻡ ﺁﻥ ﻧﻴﺰ ﻓﻬﻤﻴﺪﻩ ﻣﻲﺷﻮﺩ‪ SAN ،‬ﻳﻚ ﺷﺒﻜﻪ ﺍﺳﺖ؛ ﺷﺒﻜﻪ ﺍﻱ ﺟﻬﺖ ﺍﻧﺘﻘﺎﻝ ﺍﻃﻼﻋﺎﺕ‬

‫ﺑﻴﻦ ﺳﺮﻭﺭﻫﺎ ﻭ ﺯﻳﺮﺷﺒﻜﻪ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ‪ .‬ﺍﺯ ﻧﻈﺮ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ‪ SAN‬ﻫﻤﺎﻧﻨﺪ ‪ DAS‬ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪ .‬ﻓﻀﺎﻱ ﻣﻮﺟﻮﺩ‬

‫ﺩﺭ ‪ SAN‬ﺑﺼﻮﺭﺕ ﺑﻠﻮﻙﻫﺎﻱ ﻣﻨﻄﻘﻲ ﺑﻪ ﻧﺎﻡ ‪) LUN‬ﻫﻤﺎﻧﻨﺪ ﭘﺎﺭﺗﻴﺸﻦﻫﺎﻱ ﻳﻚ ﺩﻳﺴﻚ ﻣﺤﻠﻲ( ﺩﺭ ﺍﺧﺘﻴﺎﺭ‬

‫ﺳﺮﻭﺭ ﻗﺮﺍﺭ ﻣﻲﮔﻴﺮﺩ‪ .‬ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﺑﺎ ﺍﻳﻦ ‪ LUN‬ﻫﻤﺎﻧﻨﺪ ﻳﻚ ﭘﺎﺭﺗﻴﺸﻦ ﻣﺤﻠﻲ ﺑﺮﺧﻮﺭﺩ ﻛﺮﺩﻩ ﻭ ﻓﺎﻳﻞ ﺳﻴﺴﺘﻢ‬

‫ﻣﻮﺭ ﺩ ﻧﻈﺮ ﺧﻮﺩ ﺭﺍ ﺑﺮ ﺭﻭﻱ ﺁﻥ ﺍﻋﻤﺎﻝ ﻣﻲﻛﻨﺪ‪ .‬ﺍﻟﺒﺘﻪ ﺑﺮﺍﻱ ﺍﻳﻨﻜﻪ ﭼﻨﺪﻳﻦ ﺳﺮﻭﺭ ﺑﺘﻮﺍﻧﺪ ﺑﻪ ﻳﻚ ‪ LUN‬ﺩﺳﺘﺮﺳﻲ‬

‫ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ ﺑﺎﻳﺴﺘﻲ ﺑﺎ ﻓﺎﻳﻞﺳﻴﺴﺘﻢﻫﺎﻱ ﺧﺎﺻﻲ ﻓﺮﻣﺖ ﺷﻮﻧﺪ‪.‬‬

‫ﻣﺜﻼ ﻭﻳﻨﺪﻭﺯ ‪ Server 2008 R2‬ﺑﺮﺍﻱ ﺍﻳﻦ ﻣﻨﻈﻮﺭ ﺍﺯ ﻓﺎﻳﻞ ﺳﻴﺴﺘﻢ ‪ CSV‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﻛﻨﺪ‪.‬‬

‫ﺑﺮﺍﻱ ﺍﺗﺼﺎﻝ ‪ SAN‬ﺑﻪ ﺳﺮﻭﺭ ﻋﻤﺪﺗﺎ ﺍﺯﺩﻭ ﺗﻜﻨﻮﻟﻮژﻱ ‪ ISCSI , FC‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﺷﻮﺩ‪ FC .‬ﻳﺎ ﺗﻜﻨﻮﻟﻮژﻱ‬

‫ﻓﻴﺒﺮﻧﻮﺭﻱ ﭘﻴﭽﻴﺪﻩﺗﺮ ﻭ ﭘﺮﻫﺰﻳﻨﻪ ﺗﺮ ﺍﺳﺖ ﻭ ﺍﻟﺒﺘﻪ ﺳﺮﻋﺖ ﺑﺴﻴﺎﺭ ﺑﺎﻻﻳﻲ ﻧﻴﺰ ﺩﺍﺭﺩ‪ .‬ﻫﻤﭽﻨﻴﻦ ﺍﻳﻦ ﺗﻜﻨﻮﻟﻮژﻱ ﻧﻴﺎﺯ ﺑﻪ‬

‫ﺳﻮﺋﻴﭻﻫﺎﻱ ﻓﻴﺒﺮﻧﻮﺭﻱ ﻧﻴﺰ ﺩﺍﺭﺩ ﻛﻪ ﻫﺰﻳﻨﻪ ﻧﺴﺒﺘﺎ ﺑﺎﻻﻳﻲ ﺭﺍ ﺑﻪ ﺳﻴﺴﺘﻢ ﺗﺤﻤﻴﻞ ﻣﻲﻛﻨﻨﺪ‪ .‬ﺍﺯ ﻣﺰﻳﺖﻫﺎﻱ ﺩﻳﮕﺮ‬

‫ﺍﻳﻦ ﺗﻜﻨﻮﻟﻮژﻱ ﺑﺠﺰ ﺳﺮﻋﺖ ﺑﺎﻻﻱ ﺁﻥ ﻓﺎﺻﻠﻪ ﺑﺴﻴﺎﺭ ﺑﺎﻻﻳﻲ ﺍﺳﺖ ﻛﻪ ﭘﺸﺘﻴﺒﺎﻧﻲ ﻣﻲﺷﻮﺩ )ﺗﺎ ‪ 10‬ﻛﻴﻠﻮﻣﺘﺮ(‬

‫‪ ، ISCSI‬ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﺍﻧﺘﻘﺎﻝ ﺑﻼﻙﻫﺎﻱ ‪ SCSI‬ﺩﺭ ﺷﺒﻜﻪ ﺍﺗﺮﻧﺖ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ TCP/IP‬ﺍﺳﺖ‪ .‬ﻭﻇﻴﻔﻪ ﺍﺗﺼﺎﻝ‬

‫ﺳﺮﻭﺭ ﺑﺎ ﺫﺧﻴﺮﻩﺳﺎﺯﻫﺎﻱ ‪ ISCSI‬ﺑﺮ ﻋﻬﺪﻩ ‪ ISCSI Initiator‬ﺍﺳﺖ ﻛﻪ ﺑﻪ ﻋﻨﻮﺍﻥ ﻳﻚ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺩﺭ ﺳﺮﻭﺭ ﺍﺟﺮﺍ‬

‫ﻣﻲ ﺷﻮﺩ‪ .‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﮔﻔﺘﻪ ﺷﺪ ‪ ISCS‬ﺑﺮﺍﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺍﺩﻩ ﺍﺯ ‪ TCP/IP‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﻛﻨﺪ؛ ﺑﻨﺎﺑﺮﺍﻳﻦ‪ ،‬ﺍﻳﻦ ﺷﺒﻜﻪ‬

‫ﻣﻲﺗﻮﺍﻧﺪ ﺩﺭ ﺑﺴﺘﺮ ﺍﻳﻨﺘﺮﻧﺖ ﻓﻌﺎﻟﻴﺖ ﻛﻨﺪ ﻭ ﺍﻳﻦ ﻳﻌﻨﻲ ﭘﺸﺘﻴﺒﺎﻧﻲ ﺍﺯ ﻓﺎﺻﻠﻪ ﻧﺎﻣﺤﺪﻭﺩ‪ .‬ﺍﻟﺒﺘﻪ ﺍﺯ ﻧﻈﺮ ﺳﺮﻋﺖ ﻧﺴﺒﺖ‬

‫ﺑﻪ ‪ FC‬ﻣﺤﺪﻭﺩﺗﺮ ﺍﺳﺖ‪.‬‬

‫‪Storage Area Network 1‬‬

‫‪80‬‬
 ‫‪ 2-1-1-5‬ﺫﺧﻴﺮﻩ ﺳﺎﺯﻫﺎﻱ ‪NAS1‬‬

‫‪NAS‬ﻫﺎ ﺩﺭ ﻭﺍﻗﻊ ﺳﺮﻭﺭﻫﺎﻳﻲ ﺑﺎ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻣﺨﺼﻮﺹ ﺍﺭﺍﺋﻪ ﺳﺮﻭﻳﺲ ﻓﺎﻳﻞ ﻫﺴﺘﻨﺪ‪ .‬ﻳﻌﻨﻲ ﻳﻚ ﺳﺮﻭﺭ ﺍﺭﺯﺍﻥ‬

‫ﻗﻴﻤﺖ ﻛﻪ ﺩﺍﺭﺍﻱ ﺗﻌﺪﺍﺩ ﺯﻳﺎﺩﻱ ﻫﺎﺭﺩ ﺩﻳﺴﻚ ‪ SATA‬ﻭ ﻳﺎ ‪ SCSI‬ﻭ ﻳﻚ ﻳﺎ ﭼﻨﺪ ﻛﺎﺭﺍﺕ ﺍﺗﺮﻧﺖ ﺑﺎﺷﺪ ﺭﺍ ﻣﻲﺗﻮﺍﻥ‬

‫ﺩﺭ ﻧﻘﺶ ﺳﺮﻭﺭ ‪ NAS‬ﺑﻜﺎﺭ ﮔﺮﻓﺖ‪ .‬ﺑﺪﻳﻦ ﺗﺮﺗﻴﺐ ﺩﻳﮕﺮ ﺳﺮﻭﺭﻫﺎﻱ ﻗﺪﺭﺗﻤﻨﺪ ﻭ ﮔﺮﺍﻥﻗﻴﻤﺖ ﻫﻤﻪﻣﻨﻈﻮﺭﻩ ﺩﺭﮔﻴﺮ‬

‫ﺳﺮﻭﻳﺲ ﻓﺎﻳﻞ ﻧﻤﻲﺷﻮﻧﺪ‪ .‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﮔﻔﺘﻪ ﺷﺪ‪ ،‬ﺑﺮﺍﻱ ﺍﺗﺼﺎﻝ ﺫﺧﻴﺮﻩﺳﺎﺯﻫﺎﻱ ‪ NAS‬ﺑﻪ ﺷﺒﻜﻪ ﻣﻲﺗﻮﺍﻥ ﺍﺯ‬

‫ﻛﺎﺭﺕ ﺷﺒﻜﻪ ﺍﺗﺮﻧﺖ ‪ 10G , GIG , 100,10‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ‪ .‬ﺳﺮﻭﺭﻫﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ‪ NAS‬ﺑﺮﺍﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺍﺩﻩ ﺍﺯ‬

‫‪ TCP/IP‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﻛﻨﺪ‪ .‬ﺑﻌﻼﻭﻩ ﺑﻪ ﻛﻤﻚ ﺳﺮﻭﺭ ‪ NAS‬ﻣﻲﺗﻮﺍﻥ ﺑﻄﻮﺭ ﻫﻤﺰﻣﺎﻥ ﺑﻪ ﺳﺮﻭﺭﻫﺎﻱ ﻭﻳﻨﺪﻭﺯﻱ ﻭ‬

‫ﻟﻴﻨﻮﻛﺴﻲ ﺳﺮﻭﻳﺲ ﺩﺍﺩ ﻭ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﭼﻨﺪ ﺍﻳﻨﺘﺮﻓﻴﺲ )ﻣﺠﺎﺯﻱ ﻳﺎ ﺣﻘﻴﻘﻲ( ﺑﻪ ﭼﻨﺪ ﺷﺒﻜﻪ ﻣﺘﺼﻞ ﺷﺪﻩ ﻭ ﺑﻪ‬

‫ﺳﺮﻭﺭﻫﺎﻱ ﻣﺘﺼﻞ ﺑﻪ ﺁﻧﻬﺎ ﺳﺮﻭﻳﺲ ﺩﺍﺩ‪ .‬ﻣﺸﻬﻮﺭﺗﺮﻳﻦ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ‪ NAS‬ﺩﺭ ﺣﺎﻝ ﺣﺎﺿﺮ ‪ FreeNAS‬ﻣﻲﺑﺎﺷﺪ‬

‫ﻛﻪ ﺭﺍﺑﻂ ﻛﺎﺭﺑﺮﻱ ﺁﻥ ﻛﻪ ﺍﺯ ﺍﺗﺼﺎﻝ ﺑﻪ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪ web-base‬ﺁﻥ ﻛﻪ ﺍﺯ ﻃﺮﻳﻖ ﻓﺎﻳﺮﻓﺎﻛﺲ ﺣﺎﺻﻞ ﺷﺪﻩ ﺍﺳﺖ ﺩﺭ‬

‫ﺷﻜﻞ ‪ 1-5‬ﻗﺎﺑﻞ ﻣﺸﺎﻫﺪﻩ ﺍﺳﺖ‪ .‬ﺍﻟﺒﺘﻪ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞﻫﺎﻱ ﺩﻳﮕﺮﻱ ﭼﻮﻥ ‪ Nexenta‬ﻭ ‪ NASLite‬ﻧﻴﺰ ﺑﺪﻳﻦ‬

‫ﻣﻨﻈﻮﺭ ﺍﺭﺍﺋﻪ ﺷﺪﻩﺍﻧﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 1 5‬ﺻﻔﺤﻪ ﻣﺪﻳﺮﻳﺖ ‪freeNAS‬‬

‫‪Network Attached Storage 1‬‬

‫‪81‬‬
 ‫‪ 2-5‬ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﻳﻚ ‪ISCSI SAN‬‬

‫ﺩﺭ ﺍﻳﻦ ﺑﺨﺶ ﻗﺼﺪ ﺩﺍﺭﻳﻢ ﺑﻪ ﻛﻤﻚ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ‪ open filer‬ﻳﻚ ‪ ISCSI SAN‬ﻧﺮﻡﺍﻓﺰﺍﺭﻱ ﺭﺍ ﺭﺍﻩﺍﻧﺪﺍﺯﻱ‬

‫ﺗﺎ ﺁﻥ ﺭﺍ ﺑﻪ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ ESXi‬ﻣﺘﺼﻞ ﻛﻨﻴﻢ‪.‬‬

‫ﺑﺪﻳﻦ ﻣﻨﻈﻮﺭ ﺍﺑﺘﺪﺍ ﻻﺯﻡ ﺍﺳﺖ ﺗﺎ ﺍﻳﻦ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﺭﺍ ﻧﺼﺐ ﻛﻨﻴﻢ‪.‬‬

‫‪ 1-2-5‬ﻧﺼﺐ ‪Open Filer‬‬

‫ﻗﺒﻞ ﺍﺯ ﺷﺮﻭﻉ ﻧﺼﺐ ﺗﻮﺟﻪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﺪ ﻛﻪ ﺍﻳﻦ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﺭﺍ ﻣﻲﺗﻮﺍﻧﻴﺪ ﺑﺼﻮﺭﺕ ﻣﺠﺎﺯﻱﺳﺎﺯﻱ ﺷﺪﻩ ﺑﺮ‬

‫ﺭﻭﻱ ﻳﻜﻲ ﺍﺯ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ ESXi‬ﻧﺼﺐ ﻛﻨﻴﺪ‪ .‬ﻳﻌﻨﻲ ﺑﺪﻭﻥ ﺍﻳﻨﻜﻪ ﻧﻴﺎﺯﻱ ﺑﻪ ﺳﺨﺖﺍﻓﺰﺍﺭ ﺍﺿﺎﻓﻲ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﺪ ﻳﻜﻲ‬

‫ﺍﺯ ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺍﺟﺮﺍ ﺷﺪﻩ ﺑﺮ ﺭﻭﻱ ﻳﻜﻲ ﺍﺯ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ‪ ESXi‬ﺭﺍ ﺑﻌﻨﻮﺍﻥ ﺫﺧﻴﺮﻩﺳﺎﺯ ‪ SAN‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﻴﺪ‪.‬‬

‫ﺍﮔﺮﭼﻨﻴﻦ ﻗﺼﺪﻱ ﺩﺍﺭﻳﺪ ﻭ ﻳﺎ ﺍﻳﻨﻜﻪ ﻗﺼﺪ ﺷﺒﻴﻪ ﺳﺎﺯﻱ ﺑﻪ ﻛﻤﻚ ‪ WMvare workstation‬ﺭﺍ ﺩﺍﺭﻳﺪ ﻫﻨﮕﺎﻡ‬

‫ﺍﻧﺘﺨﺎﺏ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻟﻴﻨﻮﻛﺴﻲ ‪ cent os‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻧﻤﺎﺋﻴﺪ‪ .‬ﺣﺎﻝ ﻓﺮﺍﻳﻨﺪ ﻧﺼﺐ ﺭﺍ ﺁﻏﺎﺯ ﻣﻲﻛﻨﻴﻢ‪.‬‬

‫ﭘﺲ ﺍﺯ ﺑﻮﺕ ﻛﺮﺩﻥ ﺳﻴﺴﺘﻢ ﺍﺯ ﻃﺮﻳﻖ ‪ CD‬ﺣﺎﻭﻱ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ‪ open filer‬ﺗﺼﻮﻳﺮﻱ ﻣﺸﺎﺑﻪ ﺑﺎ ﺷﻜﻞ ‪2-5‬‬

‫ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﺧﻮﺍﻫﻴﺪ ﻛﺮﺩ‪ .‬ﺑﺮﺍﻱ ﻧﺼﺐ ﺩﺭ ﺣﺎﻟﺖ ﮔﺮﺍﻓﻴﻜﻲ ﺍﻳﻨﺘﺮ ﺭﺍ ﺑﻔﺸﺎﺭﻳﺪ‪.‬‬

‫‪82‬‬
 ‫ﺷﻜﻞ ‪ . 2 5‬ﻧﺼﺐ ‪open filer‬‬

‫ﭘﺲ ﺍﺯ ﻟﻮﺩ ﻛﺎﻣﻞ ﺩﻛﻤﻪ ‪ next‬ﺭﺍ ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪ .‬ﺩﺭ ﺍﺩﺍﻣﻪ ﺑﺎ ﺍﻧﺘﺨﺎﺏ ﺯﺑﺎﻥ ﺻﻔﺤﻪﻛﻠﻴﺪ‪ next ،‬ﺭﺍ ﺑﺰﻧﻴﺪ ﭘﺲ‬

‫ﺍﺯﻟﻮﺩ ﻛﺎﻣﻞ ﺩﻛﻤﻪ ‪ next‬ﺭﺍﻛﻠﻴﻚ ﻛﻨﻴﺪ‪ .‬ﺩﺭ ﺍﺩﺍﻣﻪ ﺑﺎ ﺍﻧﺘﺨﺎﺏ ﺯﺑﺎﻥ ﺻﻔﺤﻪﻛﻠﻴﺪ ‪ next‬ﺭﺍ ﺑﺰﻧﻴﺪ ﺍﺣﺘﻤﺎﻻ ﺑﺎ ﺯﺩﻥ‬

‫‪ next‬ﺑﺎ ﭘﻴﻐﺎﻣﻲ ﺑﺎ ﺍﻳﻦ ﻣﻀﻤﻮﻥ ﺑﺮﺧﻮﺭﺩ ﺧﻮﺍﻫﻴﺪ ﻛﺮﺩ ﻛﻪ ﺍﻃﻼﻋﺎﺕ ﻣﻮﺟﻮﺩ ﺩﺭ ﻫﺎﺭﺩﺩﻳﺴﻚ ﺷﻤﺎ ﺑﻪ ﻃﻮﺭﻛﺎﻣﻞ‬

‫ﺍﺯ ﺑﻴﻦ ﺧﻮﺍﻫﺪ ﺭﻓﺖ‪ .‬ﺍﮔﺮ ﺍﻃﻼﻋﺎﺕ ﻣﻬﻤﻲ ﻧﺪﺍﺭﻳﺪ؛ ﺑﺎ ﺍﻧﺘﺨﺎﺏ ‪ yes‬ﻓﺮﺍﻳﻨﺪ ﻧﺼﺐ ﺭﺍ ﺍﺩﺍﻣﻪ ﺩﻫﻴﺪ‪ .‬ﺩﺭ ﺻﻔﺤﻪ ﺑﻌﺪ‬

‫ﻣﻲﺗﻮﺍﻧﻴﺪ ﭘﻴﻜﺮﺑﻨﺪﻱ ﻻﺯﻡ ﻫﺎﺭﺩﺩﻳﺴﻚ ﺭﺍ ﺑﺮﺍﻱ ﻧﺼﺐ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ ﻛﻪ ﻣﻲﺗﻮﺍﻧﻴﺪ ﺑﺪﻭﻥ ﻫﻴﭻ ﺗﻐﻴﻴﺮﻱ ﺩﺭ ﮔﺰﻳﻨﻪ‬

‫ﻫﺎﻱ ﭘﻴﺶ ﻓﺮﺽ ﺑﺎ ﺯﺩﻥ ‪ next‬ﺑﻪ ﻣﺮﺣﻠﻪ ﺑﻌﺪ ﺑﺮﻭﻳﺪ‪ .‬ﺩﺭ ﺍﺩﺍﻣﻪ ﺑﺎ ﺻﻔﺤﻪ ﻣﺮﺑﻮﻁ ﺑﻪ ﺗﻨﻈﻴﻤﺎﺕ ﺷﺒﻜﻪ ﻣﻮﺍﺟﻪ‬

‫ﺧﻮﺍﻫﻴﺪ ﺷﺪ ﻛﻪ ﻣﺸﺎﺑﻪ ﺷﻜﻞ ‪ 3-5‬ﺧﻮﺍﻫﺪ ﺑﻮﺩ ﺩﺭ ﺍﻳﻨﺠﺎ ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﺑﺎ ﻛﻠﻴﻚ ﺑﺮ ﺭﻭﻱ ‪ ، Edit‬ﺑﻪ ﺍﻳﻨﺘﺮﻓﻴﺲﻫﺎ ‪IP‬‬

‫ﺍﺳﺘﺎﻧﻴﻚ ﺍﺧﺘﺼﺎﺹ ﺩﻫﻴﺪ‪ .‬ﻣﺸﺎﺑﻪ ﺷﻜﻞ ‪. 4-5‬‬

‫‪83‬‬
 ‫ﺷﻜﻞ ‪ . 3 5‬ﺗﻨﻀﻴﻤﺎﺕ ﺷﺒﻜﻪ ‪open filer‬‬

‫ﺑﺎ ﻛﻠﻴﻚ ﺑﺮ ﺭﻭﻱ ‪ next‬ﺑﻪ ﺻﻔﺤﻪ ﺍﻧﺘﺨﺎﺏ ﻣﻨﻄﻘﻪ ﺯﻣﺎﻧﻲ ﻭﺍﺭﺩ ﻣﻲﺷﻮﻳﺪ ﻛﻪ ﭘﺲ ﺍﺯ ﺍﻧﺘﺨﺎﺏ ﺷﻬﺮ ﻣﻮﺭﺩ ﻧﻈﺮ‬

‫ﺑﺎ ﻛﻠﻴﻚ ﺑﺮ ﺭﻭﻱ ‪ next‬ﺑﻪ ﺻﻔﺤﻪ ﺑﻌﺪ ﺧﻮﺍﻫﻴﺪ ﺭﻓﺖ‪.‬‬

‫ﺷﻜﻞ ‪ . 4 5‬ﺍﺧﺘﺼﺎﺹ ‪ IP‬ﺑﻪ ﻛﺎﺭﺕ ﺷﺒﻜﻪ ﺩﺭ ‪open filer‬‬

‫‪84‬‬
‫ﺩﺭ ﺍﻳﻨﺠﺎ ﻧﻴﺰ ﺭﻣﺰ ﻋﺒﻮﺭ ﻛﺎﺭﺑﺮ ﺭﻳﺸﻪ ﻳﺎ ﻫﻤﺎﻥ ‪ root‬ﺭﺍ ﻭﺍﺭﺩ ﻛﺮﺩﻩ ﻭ ‪ next‬ﺭﺍ ﺑﻔﺸﺎﺭﻳﺪ‪ .‬ﺣﺎﻝ ﺑﺎ ﺯﺩﻥ ‪next‬‬

‫ﻓﺮﺍﻳﻨﺪ ﻧﺼﺐ ﺷﺮﻭﻉ ﺧﻮﺍﻫﺪ ﺷﺪ ﻛﻪ ﻣﻤﻜ ﻦ ﺍﺳﺖ ﭼﻨﺪﻳﻦ ﺩﻗﻴﻘﻪ ﺑﻪ ﻃﻮﻝ ﺍﻧﺠﺎﻣﺪ‪ .‬ﺩﺭ ﭘﺎﻳﺎﻥ ﻓﺮﺍﻳﻨﺪ ﻧﺼﺐ‪ ،‬ﺑﺎ‬

‫ﻛﻠﻴﻚ ﺑﺮ ﺭﻭﻱ ‪ reboot‬ﺳﻴﺴﺘﻢ ﺭﺍ ﺭﻳﺴﺘﺎﺭﺕ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫ﭘﺲ ﺍﺯ ﺭﻳﺴﺘﺎﺭﺕ ﺷﺪﻥ ﻭﻟﻮﺩ ﻛﺎﻣﻞ‪ openfiler‬ﺑﺎ ﺗﺼﻮﻳﺮﻱ ﺷﺒﻴﻪ ﺑﻪ ﺷﻜﻞ ‪ 5-5‬ﻣﻮﺍﺟﻪ ﺧﻮﺍﻫﻴﺪ ﺷﺪ‪.‬‬

‫ﺷﻜﻞ ‪ open filer . 5 5‬ﭘﺲ ﺍﺯ ﻧﺼﺐ‬

‫ﺩﺭ ﺍﻳﻨﺠﺎ ﻧﺼﺐ ‪ open filer‬ﺑﻪ ﭘﺎﻳﺎﻥ ﺭﺳﻴﺪ‪ .‬ﺣﺎﻝ ﻣﻲﺗﻮﺍﻧﻴﺪ ﺑﻪ ﻛﻤﻚ ﻳﻚ ‪) web broswser‬ﺑﻬﺘﺮ ﺍﺳﺖ ﺍﺯ‬

‫‪ firefox‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﻴﺪ( ﻭ ﻳﻚ ﺳﻴﺴﺘﻢ ﺩﻭﻣﻲ ﺑﻪ ‪ open filer‬ﻣﺘﺼﻞ ﺷﺪﻩ ﻭ ﺁﻥ ﺭﺍ ﻣﺪﻳﺮﻳﺖ ﻛﻨﻴﺪ‪.‬‬

‫‪ 2-2-5‬ﻣﺪﻳﺮﻳﺖ ‪Open Filer‬‬

‫ﺑﺮﺍﻱ ﻣﺪﻳﺮﻳﺖ ‪ ، open filer‬ﭘﺲ ﺍﺯ ﺍﺟﺮﺍﻱ ‪ ،web browser‬ﺁﺩﺭﺱ ‪ ip‬ﺳﻴﺴﺘﻢ ‪ open filer‬ﺭﺍ ﺑﺎ ﭘﻮﺭﺕ‬

‫‪ 446‬ﻭ ﭘﺮﻭﺗﻜﻞ ‪ https‬ﺩﺭ ﻧﻮﺍﺭ ﺁﺩﺭﺱ ﻭﺍﺭﺩ ﻛﺮﺩﻩ ﻭ ﺍﻳﻨﺘﺮ ﺭﺍ ﺑﻔﺸﺎﺭﻳﺪ‪ .‬ﻳﻌﻨﻲ ﺑﻪ ﺷﻜﻞ ‪ https://IP:446‬ﭘﺲ ﺍﺯ‬

‫ﻟﻮﺩ ﺷﺪﻥ ﺻﻔﺤﻪ‪ ،‬ﻛﻪ ﻣﺸﺎﺑﻪ ﺷﻜﻞ ‪ 6-5‬ﺍﺳﺖ ﺑﺎ ﻧﺎﻡ ﻛﺎﺭﺑﺮﻱ ”‪ “openfiler‬ﻭ ﺭﻣﺰ ﻋﺒﻮﺭ ”‪ “password‬ﺑﻪ‬

‫ﺳﻴﺴﺘﻢ ‪ login‬ﻛﻨﻴﺪ‪.‬‬

‫‪85‬‬
 ‫ﺷﻜﻞ ‪ . 6 5‬ﺻﻔﺤﻪ ‪ login‬ﺩﺭ ‪open filer‬‬

‫ﺩﺭﺍﺑﺘﺪﺍ ﺍﻭﻟﻴﻦ ﺻﻔﺤﻪﺍﻱ ﻛﻪ ﻣﻲﺑﻴﻨﻴﺪ ﻣﺸﺎﺑﻪ ﺷﻜﻞ ‪ 7-5‬ﺧﻮﺍﻫﺪ ﺑﻮﺩ ﻛﻪ ﻫﻤﺎﻥ ﺻﻔﺤﻪ ‪ status‬ﺍﺳﺖ ﻭ‬

‫ﺣﺎﻭﻱ ﺍﻃﻼﻋﺎﺗﻲ ﺩﺭ ﻣﻮﺭﺩ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﺳﻴﺴﺘﻢ ﻣﻲﺑﺎﺷﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 7 5‬ﺻﻔﺤﻪ ﻣﺪﻳﺮﻳﺖ ‪open filer‬‬

‫ﺑﺎ ﻭﺭﻭﺩ ﺑﻪ ﻣﺮﻛﺰ ﻣﺪﻳﺮﻳﺖ ﻣﺘﻮﺟﻪ ﺧﻮﺍﻫﻴﺪ ﺷﺪ ﻛﻪ ﻣ ﺮﻛﺰ ﻣﺪﻳﺮﻳﺖ‪ ،‬ﺩﺍﺭﺍﻱ ﺳﺮﺑﺮگﻫﺎﻱ‪ 1‬ﻣﺨﺘﻠﻒ ﺑﻮﺩﻩ ﻭ ﻫﺮ‬

‫ﻛﺪﺍﻡ ﺍﺯ ﺳﺮﺑﺮگﻫﺎ ﺩﺭ ﺳﻤﺖ ﺭﺍﺳﺖ ﺧﻮﺩ ﺍﺑﺰﺍﺭﻫﺎﻳﻲ ﺭﺍ ﺩﺭ ﺩﺳﺘﺮﺱ ﻗﺮﺍﺭ ﻣﻲﺩﻫﻨﺪ‪ .‬ﻣﺜﻼ ﺩﺭ ﺳﺮﺑﺮگ ‪system‬‬

‫‪tabs 1‬‬
‫ﻛﻪ ﺩﺭ ﺷﻜﻞ ‪ 8-5‬ﻗﺎﺑﻞ ﻣﺸﺎﻫﺪﻩ ﺍﺳﺖ‪ ،‬ﺑﺎ ﻛﻠﻴﻚ ﺑﺮ ﺭﻭﻱ ﻫﺮ ﻳﻚ ﺍﺯ ﺍﺑﺰﺍﺭﻫﺎ ﺩﺭ ﺳﻤﺖ ﺭﺍﺳﺖ ﺻﻔﺤﻪ ﻣﻲﺗﻮﺍﻧﻴﺪ‬

‫ﺗﻨﻈﻴﻤﺎﺗﻲ ﺍﺯ ﻗﺒﻴﻞ ﺗﻨﻈﻴﻢ ﺯﻣﺎﻥ‪ ،‬ﺗﻨﻈﻴﻤﺎﺕ ﻣﺮﺑﻮﻁ ﺑﻪ ﺷﺒﻜﻪ ﭘﺸﺘﻴﺒﺎﻥﮔﻴﺮﻱ‪ ،‬ﺑﺮﻭﺯ‪ 1‬ﻛﺮﺩﻥ ﺳﻴﺴﺘﻢ ﻭ ‪ ...‬ﺭﺍ‬

‫ﺍﻧﺠﺎﻡ ﺩﻫﻴﺪ‪ .‬ﺑﺎﻛﻠﻴﻚ ﺑﺮ ﺭﻭﻱ ﺳﺮﺑﺮگﻫﺎﻱ ﺩﻳﮕﺮ ﺑﻪ ﺗﻨﻈﻴﻤﺎﺕ ﺩﻳﮕﺮ ﻧﻴﺰ ﺩﺳﺘﺮﺳﻲ ﺧﻮﺍﻫﻴﺪ ﺩﺍﺷﺖ ﻛﻪ ﻣﺎﺩﺭ‬

‫ﺍﻳﻨﺠﺎ ﺑﻪ ﺑﻌﻀﻲ ﺍﺯ ﺁﻧﻬﺎ ﺍﺷﺎﺭﻩ ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩ‪.‬‬

‫ﺷﻜﻞ ‪ . 8 5‬ﺳﺮﺑﺮگ ‪ system‬ﺩﺭ ﺻﻔﺤﻪ ﻣﺪﻳﺮﻳﺖ ‪open filer‬‬

‫ﻫﺪﻑ ﻣﺎ ﺍﺯ ﺍﺳﺘﻔﺎﺩﻩ ‪ ، open filer‬ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﻳﻚ ‪ SAN storage‬ﺍﺳﺖ‪ .‬ﺑﺪﻳﻦ ﻣﻨﻈﻮﺭ ﻻﺯﻡ ﺍﺳﺖ ﻳﻚ‬

‫ﻓﺮﺍﻳﻨﺪ ﭼﻨﺪ ﻣﺮﺣﻠﻪﺍﻱ ﺻﻮﺭﺕ ﭘﺬﻳﺮ؛ ﻛﻪ ﻣﺎ ﺩﺭ ﺍﺩﺍﻣﻪ ﺗﻤﺎﻡ ﺍﻳﻦ ﻣﺮﺍﺣﻞ ﺭﺍ ﮔﺎﻡ ﺑﻪ ﮔﺎﻡ ﻃﻲ ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩ‪.‬‬

‫‪ .1‬ﺍﺑﺘﺪﺍ ﻻﺯﻡ ﺍﺳﺖ ﺑﺮ ﺭﻭﻱ ﺩﻳﺴﻚﻫﺎﻱ ﻣﺘﺼﻞ ﺑﻪ ﺳﻴﺴﺘﻢ ﭘﺎﺭﺗﻴﺸﻦﻫﺎﻳﻲ ﺳﺎﺧﺘﻪ ﺷﻮﺩ ﺑﺮﺍﻱ ﺍﻳﻦ ﻛﺎﺭ ﺑﺮ‬

‫ﺭﻭﻱ ﺳﺮﺑﺮگ ‪ volumes‬ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪ .‬ﺗﺼﻮﻳﺮﻱ ﻣﺸﺎﺑﻪ ﺷﻜﻞ ‪ 9-5‬ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﺧﻮﺍﻫﻴﺪ ﻛﺮﺩ‪ ) .‬ﺍﻟﺒﺘﻪ ﺍﮔﺮ ﺍﺯ ﻗﺒﻞ‬

‫ﭘﺎﺭﺗﻴﺸﻦ ﻧﺴﺎﺧﺘﻪ ﺑﺎﺷﻴﺪ(‬

‫‪Update 1‬‬

‫‪87‬‬
 ‫ﺷﻜﻞ ‪ . 9 5‬ﺳﺎﺧﺖ ﭘﺎﺭﺗﻴﺸﻦ ﺑﺮ ﺭﻭﻱ ﺩﻳﺴﻚ‬

‫‪ .2‬ﺑﺮﺍﻱ ﺍﻳﺠﺎﺩ ﭘﺎﺭﺗﻴﺸﻦ ﺟﺪﻳﺪ ﺑﺮ ﺭﻭﻱ ﻟﻴﻨﻚ ‪ create new physical volumes‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪ .‬ﭘﺲ‬

‫ﺍﺯﺁﻥ ﻫﺎﺭﺩ ﺩﻳﺴﻚﻫﺎﻱ ﻣﺘﺼﻞ ﺑﻪ ﺳﻴﺴﺘﻢ ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﺧﻮﺍﻫﻴﺪ ﻛﺮﺩ‪.‬‬

‫‪ .3‬ﺑﺮ ﺭﻭﻱ ﺩﻳﺴﻚ ﻣﻮﺭﺩ ﻧﻈﺮ ﺑﺮﺍﻱ ﺳﺎﺧﺖ ﭘﺎﺭﺗﻴﺸﻦ ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪ .‬ﺗﺼﻮﻳﺮﻱ ﻣﺸﺎﺑﻪ ﺑﻪ ﺷﻜﻞ ‪ 10-5‬ﺭﺍ‬

‫ﺧﻮﺍﻫﻴﺪ ﺩﻳﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 10 5‬ﺗﻨﻈﻴﻢ ﻭﻳﮋﮔﻲﻫﺎﻱ ﭘﺎﺭﺗﻴﺸﻦ‬

‫‪ .4‬ﺩﺭ ﭘﺎﺋﻴﻦ ﺻﻔﺤﻪ ﺁﭘﺸﻦﻫﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ﭘﺎﺭﺗﻴﺸﻦ ﺟﺪﻳﺪ ﻗﺎﺑﻞ ﺗﻨﻈﻴﻢ ﺍﺳﺖ‪ Mode .‬ﺭﺍ ‪ primary‬ﻭ‬

‫‪ type‬ﺭﺍ ‪ physical volume‬ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ .‬ﭘﺲ ﺍﺯ ﻭﺍﺭﺩ ﻛﺮﺩﻥ ﺳﻴﻠﻨﺪﺭ ﺷﺮﻉ ﻭ ﭘﺎﻳﺎﻥ ﺑﺮ ﺭﻭﻱ ‪ create‬ﻛﻠﻴﻚ‬

‫ﻛﻨﻴﺪ ﺗﺎ ﭘﺎﺭﺗﻴﺸﻦ ﻣﻮﺭﺩ ﻧﻈﺮ ﺳﺎﺧﺘﻪ ﺷﻮﺩ‪ .‬ﺍﮔﺮﭘﺎﺭﺗﻴﺸﻦ ﻣﻮﺭﺩ ﻧﻈﺮ ﺳﺎﺧﺘﻪ ﻧﺸﺪ‪ ،‬ﺗﻌﺪﺍﺩﻱ ﺍﺯ ﺳﻴﻠﻨﺪﺭﻫﺎ ﺭﺍ ﻧﺎﺩﻳﺪﻩ‬

‫ﺑﮕﻴﺮﻳﺪ)ﺑﺎ ﺍﻓﺰﺍﻳﺶ ﺷﻤﺎﺭﻩ ﺳﻴﻠﻨﺪﺭ ﺷﺮﻭﻉ ﻭ ﻛﺎﻫﺶ ﺷﻤﺎﺭﻩ ﺳﻴﻠﻨﺪﺭ ﺍﻧﺘﻬﺎ( ‪.‬‬

‫ﺍﻟﺒﺘﻪ ﺗﻮﺟﻪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﺪ ﻛﻪ ﻳﻚ ﻫﺎﺭﺩ ﺩﻳﺴﻚ ﻧﻤﻲﺗﻮﺍﻧﺪ ﺑﻴﺶ ﺍﺯ ﭼﻬﺎﺭ ﭘﺎﺭﺗﻴﺸﻦ ‪ primary‬ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬

‫ﺍﮔﺮ ﺑﻪ ﺑﻴﺶ ﺍﺯ ‪ 4‬ﭘﺎﺭﺗﻴﺸﻦ ﻧﻴﺎﺯ ﺩﺍﺭﻳﺪ ﺑﺎﻳﺪ ﺣﺪﺍﻛﺜﺮ ﺳﻪ ﭘﺎﺭﺗﻴﺸﻦ ‪ primary‬ﻭ ﻳﻚ ﭘﺎﺭﺗﻴﺸﻦ ‪primary-‬‬

‫‪ extended‬ﺍﻳﺠﺎﺩ ﻛﻨﻴﺪ ﻭ ﭘﺲ ﺍﺯ ﺁﻥ ﻣﺎ ﺑﻘﻲ ﭘﺎﺭﺗﻴﺸﻦ ﻫﺎ ﺭﺍ ﺩﺭ ‪ logical mode‬ﺳﺎﺧﺘﻪ ﻭ ﺯﻳﺮ ﻣﺠﻤﻮﻋﻪ‬

‫ﭘﺎﺭﺗﻴﺸﻦ ‪ primary- extended‬ﻗﺮﺍﺭ ﺩﻫﻴﺪ‪ .‬ﺍﺯ ﺁﻧﺠﺎﻳﻲ ﻛﻪ ﻛﻤﺘﺮ ﻧﻴﺎﺯ ﺑﻪ ﺍﻳﻦ ﻣﻮﺭﺩ ﭘﻴﺪﺍ ﻣﻲﺷﻮﺩ ﺍﺯ ﺗﻮﺿﻴﺢ‬

‫ﺑﻴﺸﺘﺮ ﺩﺭ ﺭﺍﺑﻄﻪ ﺑﺎ ﺁﻥ ﺧﻮﺩﺩﺍﺭﻱ ﻣﻲﻛﻨﻴﻢ ﻭ ﺫﻛﺮ ﺍﻳﻦ ﻧﻜﺘﻪ ﻫﻢ ﺻﺮﻓﺎ ﺟﻬﺖ ﺍﻃﻼﻉ ﺑﻮﺩ‪.‬‬

‫‪ .5‬ﺩﺭ ﻣﺮﺣﻠﻪ ﺑﻌﺪ ﻻﺯﻡ ﺍﺳﺖ ﺗﺎ ﻳﻚ ‪ volume group‬ﺍﻳﺠﺎﺩﺷﻮﺩ‪ .‬ﺑﺮﺍﻱ ﺍﻳﻦ ﻣﻨﻈﻮﺭ ﺍﺯ ﻫﻤﻴﻦ ﺳﺮﺑﺮگ‬

‫‪ ،volumes‬ﺍﺯ ﺳﻤﺖ ﺭﺍﺳﺖ ﺻﻔﺤﻪ ﺑﺮ ﺭﻭﻱ ‪ add volumes‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪ .‬ﺩﺭ ﺻﻔﺤﻪ ﺍﻱ ﻛﻪ ﺑﺎﺯ ﻣﻲﺷﻮﺩ ﻧﺎﻣﻲ‬

‫ﺑﺮﺍﻱ ‪ volume group‬ﻭﺍﺭﺩ ﻛﻨﻴﺪ ﻭ ﭘﺎﺭﺗﻴﺸﻦﻫﺎﻳﻲ ﻛﻪ ﻗﺼﺪ ﺩﺍﺭﻳﺪ ﺗﺎ ﺯﻳﺮ ﻣﺠﻤﻮﻋﻪ ﺍﻳﻦ ‪ volume group‬ﻗﺮﺍﺭ‬

‫ﺩﻫﻴﺪ ﺭﺍ ﺑﺎ ﭘﺮ ﻛﺮﺩﻥ ﭼﻚ ﺑﺎﻛﺲ ﻛﻨﺎﺭﺷﺎﻥ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ .‬ﻣﺠﻤﻮﻉ ﻓﻀﺎﻱ ﭘﺎﺭﺗﻴﺸﻦﻫﺎﻱ ﺍﻧﺘﺨﺎﺏ ﺷﺪﻩ‪ ،‬ﺣﺠﻢ‬

‫‪ volume group‬ﺭﺍ ﺗﺸﻜﻴﻞ ﻣﻲﺩﻫﺪ‪.‬‬

‫‪ .6‬ﺣﺎﻝ ﻻﺯﻡ ﺍﺳﺖ ‪volume‬ﻱ ﺭﺍ ﺳﺎﺧﺘﻪ ﻭ ﻓﺎﻳﻞﺳﻴﺴﺘﻤﻲ ﺭﺍ ﺑﻪ ﺁﻥ ﺍﺧﺘﺼﺎﺹ ﺩﻫﻴﻢ‪ .‬ﺑﺪﻳﻦﻣﻨﻈﻮﺭ ﺑﺮ‬

‫ﺭﻭﻱ ﺳﺮﺑﺮگ ‪ shares‬ﻛﻠﻴﻚ ﻛﺮﺩﻩ ﻭ ﺩﺭ ﺻﻔﺤﻪ ﻟﻮﺩ ﺷﺪﻩ ﺑﺮ ﺭﻭﻱ ﻟﻴﻨﻚ ‪create new filesystem volume‬‬

‫ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ ﻭ ﻳﺎ ﺍﻳﻨﻜﻪ ﻣﺴﺘﻘﻴﻤﺎ ﺍﺯ ﺳﺮﺑﺮگ ‪ ، volume‬ﺍﺯ ﺳﻤﺖ ﺭﺍﺳﺖ ﺑﺮ ﺭﻭﻱ ‪ add volume‬ﻛﻠﻴﻚ‬

‫ﻛﻨﻴﺪ‪.‬‬

‫‪ .7‬ﺩﺭ ﺻﻔﺤﻪ ﺑﺎﺯ ﺷﺪﻩ ﻛﻪ ﺷﺒﻴﻪ ﺑﻪ ﺷﻜﻞ ‪ 11-5‬ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪ ،‬ﺩﺭ ﻗﺴﻤﺖ ‪ name‬ﻧﺎﻣﻲ ﺩﻟﺨﻮﺍﻩ ﺭﺍ ﺑﺮﺍﻱ‬

‫‪ volume‬ﺟﺪﻳﺪ ﻭﺍﺭﺩ ﻧﻤﺎﺋﻴﺪ‪ ،‬ﭘﺲ ﺍﺯ ﻭﺍﺭﺩ ﻛﺮﺩﻥ ﺗﻮﺿﻴﺤﺎﺕ ﻭ ﺣﺠﻢ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ‪ block ،‬ﺭﺍ ﺑﻌﻨﻮﺍﻥ ‪file‬‬

‫‪ system‬ﺑﺮﮔﺰﻳﻨﻴﺪ‪ .‬ﺗﻮﺟﻪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﺪ ﻛﻪ ﺍﻳﻦ ‪ volume‬ﻫﺎ ﻫﻤﺎﻥ ‪ LUN‬ﻳﺎ ﻭﺍﺣﺪﻫﺎﻱ ﻣﻨﻄﻘﻲ ‪SAN‬‬

‫‪Storage‬ﻫﺎ ﻫﺴﺘﻨﺪ‪.‬‬

‫‪89‬‬
 ‫ﺷﻜﻞ ‪ . 11 5‬ﺳﺎﺧﺖ ‪Volume Group‬‬

‫‪ .8‬ﺑﺮﺍﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺍﻳﻦ ‪volume‬ﻫﺎ ﺩﺭ ﺳﺮﻭﺭﻫﺎﻱ ‪ ESXi‬ﻭ ﻳﺎ ﻫﺮ ﺳﺮﻭﺭ ﻭ ﺳﻴﺴﺘﻢ ﺩﻳﮕﺮ ﻣﻲﺑﺎﻳﺴﺖ ﻳﻚ‬

‫‪ iqn‬ﺑﻪ ﻫﺮ ﻳﻚ ﺍﺯ ﺁﻧﻬﺎ ﺍﺧﺘﺼﺎﺹ ﺩﺍﺩ ‪.‬ﺑﺮﺍﻱ ﺍﻳﻨﻜﺎﺭ ﺍﺯ ﺳﺮﺑﺮگ ‪ volume‬ﺍﺯ ﺳﻤﺖ ﺭﺍﺳﺖ ﺻﻔﺤﻪ ﺑﺮ ﺭﻭﻱ ‪target‬‬

‫‪ ISCSI‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪ .‬ﺻﻔﺤﻪ ﺍﻱ ﻣﺸﺎﺑﻪ ﺷﻜﻞ ‪ 12-5‬ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﺧﻮﺍﻫﻴﺪ ﻛﺮﺩ‪ .‬ﺍﻟﺒﺘﻪ ﺑﺎﻳﺴﺘﻲ ﻗﺒﻞ ﺍﺯ ﺍﻳﻦ ﻛﺎﺭ‬

‫ﺳﺮﻭﻳﺲ ‪ISCSI target‬ﻓﻌﺎﻝ ﺑﺎﺷﺪ ﻛﻪ ﺑﺮﺍﻱ ﻓﻌﺎﻝ ﺳﺎﺯﻱ ﺁﻥ ﺑﻪ ﺳﺮ ﺑﺮگ ‪ services‬ﺭﻓﺘﻪ ﻭ ﺳﺮﻭﻳﺲ ﻣﺬﻛﻮﺭ‬

‫ﻓﻌﺎﻝ ﻭ ﺍﺟﺮﺍ ﻛﻨﻴﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 12 5‬ﺳﺎﺧﺖ ‪iqn‬‬

‫‪90‬‬
‫‪ .9‬ﺑﺮﺍﻱ ﺍﻳﺠﺎﺩ ﻳﻚ ‪ iqn‬ﺑﺮ ﺭﻭﻱ ‪ add‬ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪ .‬ﭘﺲ ﺍﺯ ﺍﻳﺠﺎﺩ ‪ iqn‬ﺑﺎﻳﺪ ﺁﻥ ﺭﺍ ﺑﻪ ‪ volum‬ﻫﺎ ﻳﺎ ﻫﻤﺎﻥ‬

‫‪LUN‬ﻫﺎ ‪ map ،‬ﻧﻤﺎﺋﻴﺪ‪ .‬ﺑﺮﺍﻱ ﺍﻳﻦ ﻛﺎﺭ ﺑﻪ ﺳﺮﺑﺮگ ‪ LUN mapping‬ﺩﺭ ﻫﻤﻴﻦ ﺻﻔﺤﻪ ﺭﻓﺘﻪ ﻭ ‪ iqn‬ﺳﺎﺧﺘﻪ‬

‫ﺷﺪﻩ ﺭﺍ ﺑﻪ ‪ volume‬ﻣﻮﺭﺩ ﻧﻈﺮ ‪ map‬ﻧﻤﺎﺋﻴﺪ‪ .‬ﻣﻄﺎﺑﻖ ﺷﻜﻞ ‪ .13-5‬ﺍﮔﺮ ‪volume‬ﻫﺎﻱ ﺩﻳﮕﺮ ﻧﻴﺰ ﺩﺍﺭﻳﺪ ﺑﻪ‬

‫ﺳﺮﺑﺮگ ‪ target configuration‬ﺑﺎﺯﮔﺸﺘﻪ ﻭ ﭘﺲ ﺍﺯ ﺍﻳﺠﺎﺩ ‪ ، iqn‬ﺁﻥ ﺭﺍ ﺑﻪ ‪ volume‬ﻣﻮﺭﺩ ﻧﻈﺮ ‪ map‬ﻛﻨﻴﺪ‪.‬‬

‫ﺷﻜﻞ ‪ map . 13 5‬ﻛﺮﺩﻥ ‪volum‬ﻫﺎ ﺑﻪ ‪iqn‬‬

‫‪ .10‬ﻗﺒﻞ ﺍﺯ ﺍﺩﺍﻣﻪ ﺑﺎﻳﺴﺘﻲ ﺍﻣﻜﺎﻥ ﺩﺳﺘﺮﺳﻲ ﺳﺮﻭﺭﻫﺎﻱ ﺷﺒﻜﻪ ﺑﻪ ‪volum‬ﻫﺎ ﺭﺍ ﻓﺮﺍﻫﻢ ﻛﺮﺩ‪ .‬ﺑﺮﺍﻱ ﺍﻳﻦ ﻛﺎﺭ ﺑﻪ‬

‫ﺳﺮ ﺑﺮگ ‪ system‬ﺭﻓﺘﻪ ﻭ ﺩﺭ ﭘﺎﺋﻴﻦ ﺻﻔﺤﻪ ﻣﻄﺎﺑﻖ ﺷﻜﻞ ‪ 14-5‬ﺁﺩﺭﺱ ﺷﺒﻜﻪ ﻭ ﻣﺎﺳﻚ ﺁﻥ ﺭﺍﻭﺍﺭﺩ ﻛﻨﻴﺪ‪.‬‬

‫‪91‬‬
 ‫ﺷﻜﻞ ‪ . 14 5‬ﺗﻨﻈﻴﻢ ﺩﺳﺘﺮﺳﻲ ﺷﺒﻜﻪ ﺑﻪ ‪volume‬ﻫﺎ‬

‫‪ .11‬ﺩﺭ ﺁﺧﺮﻳﻦ ﻣﺮﺣﻠﻪ ﺑﺎﻳﺴﺘﻲ ﺍﻣﻜﺎﻥ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺳﺮﻭﺭﻫﺎﻱ ﺷﺒﻜﻪ ﺩﺭ ﻣﺮﺣﻠﻪ ﻗﺒﻞ ﻓﺮﺍﻫﻢ ﺷﺪ ﺭﺍ ﻓﻌﺎﻝ‬

‫ﻧﻤﺎﺋﻴﺪ‪ .‬ﺑﺮﺍﻱ ﺍﻳﻦ ﻛﺎﺭ ﺑﻪ ﺳﺮ ﺑﺮگ ‪ volume‬ﺑﺎﺯﮔﺸﺘﻪ ﻭ ﭘﺲ ﺍﺯ ﻛﻠﻴﻚ ﺑﺮ ﺭﻭﻱ ‪ ISCSI torget‬ﺑﻪ ‪network‬‬

‫‪ ACL‬ﺭﻓﺘﻪ ﻭ ﺍﻣﻜﺎﻥ ‪ access‬ﺭﺍ ‪ allow‬ﻛﺮﺩﻩ ﻭ ﺑﺮ ﺭﻭﻱ ‪ update‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪ .‬ﻻﺯﻡ ﺑﻪ ﺫﻛﺮ ﺍﺳﺖ ﻛﻪ‬

‫ﻣﻲﺗﻮﺍﻧﻴﺪ ﺍﺯ ﻫﻤﻴﻦ ﺻﻔﺤﻪ ﺩﺭ ﻗﺴﻤﺖ ‪ ، chap authentication‬ﺍﺯ ﭘﺮﻭﺗﻜﻞ ﺭﻣﺰ ﮔﺬﺍﺭﻱ ‪ chap‬ﻧﻴﺰ ﺍﺳﺘﻔﺎﺩﻩ‬

‫ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫ﺷﻜﻞ ‪ 15-5‬ﺗﺼﻮﻳﺮﻱ ﺍﺯ ﺍﻳﻦ ﻓﺮﺍﻳﻨﺪ ‪ 11‬ﻣﺮﺣﻠﻪﺍﻱ ﺑﺪﺳﺖ ﻣﻲﺩﻫﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 15 5‬ﻧﺤﻮﻩ ﺳﺎﺧﺘﻪ ﺷﺪﻥ ﻳﻚ ﺫﺧﻴﺮﻩﺳﺎﺯ ‪ ISCSI‬ﺑﻪﻛﻤﻚ ‪open filer‬‬

‫‪92‬‬
‫ﻛﺎﺭ ﻣﺎﺩﺭ ‪ open filer‬ﺗﻤﺎﻡ ﺍﺳﺖ‪ .‬ﺩﺭ ﺍﺩﺍﻣﻪ ﺑﺎﻳﺴﺘﻲ ‪ ESXi‬ﺭﺍ ﺑﺮﺍﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺍﻳﻦ ‪ ، ISCSI‬ﭘﻴﻜﺮﺑﻨﺪﻱ‬

‫ﻧﻤﺎﺋﻴﻢ‪.‬‬

‫ﺑﺮﺍﻱ ﺍﺗﺼﺎﻝ ‪ ISCSI‬ﺑﻪ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ ESXi‬ﺑﺪﻳﻦ ﺻﻮﺭﺕ ﻋﻤﻞ ﻣﻲﻛﻨﻴﻢ‪:‬‬

‫‪ .1‬ﺍﺑﺘﺪﺍ ‪ vCenter Server‬ﻭﺍﺭﺩ ﺷﻮﻳﺪ )‪ login‬ﻧﻤﺎﺋﻴﺪ(‪ .‬ﻧﺤﻮﻩ ﻭﺭﻭﺩ ﺑﻪ ‪ vCenter Server‬ﺩﺭ ﻓﺼﻞﻫﺎﻱ‬

‫ﮔﺬﺷﺘﻪ ﮔﻔﺘﻪ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬

‫ﺑﺮ ﺭﻭﻱ ﻣﻴﺰﺑﺎﻥ ‪ ESXi‬ﻣﻮﺭﺩ ﻧﻈﺮ ﻛﻠﻴﻚ ﻛﻨﻴﺪ )ﺑﺮﺍﻱ ﺍﻃﻼﻉ ﺍﺯ ﻧﺤﻮﻩ ﺍﺿﺎﻓﻪ ﻛﺮﺩﻥ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ESXi‬‬ ‫‪.2‬‬

‫ﺑﻪ ﺳﺮﻭﺭ ‪ vCenter‬ﺑﻪ ﻓﺼﻞ ﺷﺸﻢ ﻣﺮﺍﺟﻌﻪ ﻓﺮﻣﺎﺋﻴﺪ( ﻭﭘﺲ ﺍﺯﺁﻥ ﺑﻪ ﺳﺮﺑﺮگ ‪ configuration‬ﺑﺮﻭﻳﺪ ﻭﺍﺯ ﺳﻤﺖ‬

‫ﭼﭗ ﺻﻔﺤﻪ ﺑﺮ ﺭﻭﻱ ‪ storage adapters‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪ .‬ﺷﻜﻞ ‪ 16-5‬ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺭﺍ ﻧﺸﺎﻥ ﻣﻲﺩﻫﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 16 5‬ﭘﻴﻜﺮﺑﻨﺪﻱ ‪ ESXi‬ﺑﺮﺍﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺫﺧﻴﺮﻩﺳﺎﺯﻫﺎﻱ ‪ISCSI‬‬

‫‪ .3‬ﻣﻲﺑﺎﻳﺴﺖ ﻗﺒﻞ ﺍﺯ ﻫﺮﻛﺎﺭﻱ ﻳﻚ ﺁﺩﺍﭘﺘﻮﺭ ‪ ISCSI‬ﺑﺴﺎﺯﻳﺪ‪ .‬ﺑﺪﻳﻦﻣﻨﻈﻮﺭﺩﺭ ﺑﺎﻻﻱ ﺻﻔﺤﻪ ﺳﻤﺖ ﺭﺍﺳﺖ ﺑﺮ‬

‫ﺭﻭﻱ ‪ Add‬ﻛﻠﻴﻚ ﻛﺮﺩﻩ ﻭ ﺩﺭ ﭘﻴﻐﺎﻡ ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﺷﺪﻩ ﺑﺮ ﺭﻭﻱ ‪ ok‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫‪ .4‬ﭘﺲ ﺍﺯ ﺳﺎﺧﺖ ﺁﺩﺍﭘﺘﻮﺭ‪ ،‬ﺑﺮ ﺭﻭﻱ ﺁﻥ ﺭﺍﺳﺖ ﻛﻠﻴﻚ ﻛﺮﺩﻩ‪ properties ،‬ﺭﺍ ﺑﺮﮔﺰﻳﻨﻴﺪ‪.‬‬

‫‪ .5‬ﺍﺯ ﺳﺮﺑﺮگ ‪ dynamic discovery‬ﺑﺮ ﺭﻭﻱ ‪ Add‬ﻛﻠﻴﻚ ﻛﺮﺩﻩ ﺁﺩﺭﺱ ‪ IP‬ﺳﺮﻭﺭ‪ open filer‬ﺭﺍ ﻭﺍﺭﺩ‬

‫ﻧﻤﻮﺩﻩ ﻭ ﺷﻤﺎﺭﻩ ﭘﻮﺭﺕ ﺭﺍ ﺑﺪﻭﻥ ﺗﻐﻴﻴﺮ ﺭﻫﺎ ﻛﻨﻴﺪ‪ .‬ﺍﮔﺮﺩﺭ ﻣﻮﻗﻊ ﺳﺎﺧﺖ ‪ iqn‬ﺩﺭ ‪ chap ، open filer‬ﺭﺍ ﻓﻌﺎﻝ‬
‫ﻛﺮﺩﻩﺍﻳﺪ ﺩﺭ ﺍﻳﻦ ﺟﺎ ﻧﻴﺰ ﻗﺴﻤﺖ ﻣﺮﺑﻮﻁ ﺑﻪ ‪ chap‬ﺭﺍ ﺗﻨﻈﻴﻢ ﻛﻨﻴﺪ ﻭ ﺑﺎ ﺯﺩﻥ ‪ ok‬ﺻﻔﺤﻪ ‪ Add‬ﺭﺍ ﺑﺴﺘﻪ ﻭ ﭘﺲ‬

‫ﺍﺯﺁﻥ ﺑﺎ ﻛﻠﻴﻚ ﺑﺮ ﺭﻭﻱ ‪ close‬ﺧﺎﺭﺝ ﺷﻮﻳﺪ‪ .‬ﺑﻌﺪ ﺍﺯ ﺑﺴﺘﻪ ﺷﺪﻥ ﺻﻔﺤﻪ‪ ،‬ﺍﺯ ﺷﻤﺎ ﺩﺭ ﻣﻮﺭﺩ ‪ scan‬ﺩﻭﺑﺎﺭﻩ ﺁﺩﺍﭘﺘﻮﺭ‬

‫ﺳﻮﺍﻝ ﺧﻮﺍﻫﺪ ﺷﺪ ﻛﻪ ﺑﺮ ﺭﻭﻱ ‪ yes‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫ﭘﺲ ﺍﺯ ﭼﻨﺪﺛﺎﻧﻴﻪ ‪LUN‬ﻫﺎﻱ ﻣﻮﺟﻮﺩ ﺩﺭ ‪ open filer‬ﺩﺭﭘﺎﺋﻴﻦ ﺻﻔﺤﻪ ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﺧﻮﺍﻫﺪ ﺷﺪ‪.‬‬

‫‪ .6‬ﺩﺭ ﺍﺩﺍﻣﻪ ﻣﻲﺑﺎﻳﺴﺖ ﺑﺮﺍﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺍﻳﻦ ﺫﺧﻴﺮﻩﺳﺎﺯﻩ ﺁﻧﻬﺎ ﺭﺍ ﺑﺎﺳﻴﺴﺘﻢﻓﺎﻳﻞ ‪ VMFS‬ﻓﺮﻣﺖ ﻛﺮﺩ ‪.‬‬

‫ﺑﺮﺍﻱ ﺍﻳﻦ ﻛﺎﺭ ﺍﺯ ﺳﻤﺖ ﭼﭗ ﺻﻔﺤﻪ ﺑﺮ ﺭﻭﻱ ‪ storage‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ ﻭﺍﺯ ﺑﺎﻻﻱ ﺻﻔﺤﻪ‪ ،‬ﺳﻤﺖ ﺭﺍﺳﺖ ‪،‬‬

‫ﺑﺮ ﺭﻭﻱ ‪ Add storage‬ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪.‬‬

‫‪ .7‬ﺩﺭ ﻭﻳﺰﺍﺭﺩ ﺍﺟﺮﺍ ﺷﺪﻩ ﭘﺲ ﺍﺯ ﺍﻧﺘﺨﺎﺏ‪ Disk /LUN‬ﺑﺮ ﺭﻭﻱ ‪ next‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫‪ .8‬ﺩﺭ ﺍﻳﻦ ﻣﺮﺣﻠﻪ ‪ LUN‬ﻣﻮﺭﺩ ﻧﻈﺮ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ﻭ ﺑﺮ ﺭﻭﻱ ‪ next‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫‪.9‬ﺩﺭ ﺍﻳﻨﺠﺎ ﺳﻴﺴﺘﻢ ﻓﺎﻳﻞ ﻣﻨﺎﺳﺐ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ﻭ ‪ next‬ﺭﺍ ﺑﺰﻧﻴﺪ‪ .‬ﺑﻬﺘﺮ ﺍﺳﺖ ‪ VMFS-5‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ ‪.‬‬

‫ﺍﻟﺒﺘﻪ ﺍﮔﺮ ﺍﺯ ﻧﺴﺨﻪ ‪ ESXi‬ﺑﺠﺰ ﻧﺴﺨﻪ ‪ 5‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﻛﻨﻴﺪ ﺍﺯ ﺍﻳﻦ ﺳﻴﺴﺘﻢ ﻓﺎﻳﻞ ﭘﺸﺘﻴﺒﺎﻧﻲ ﻧﺨﻮﺍﻫﺪ ﺷﺪ ﻭ‬

‫ﺑﺎﻳﺘﺴﻲ ‪ vmfs-3‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫‪ .10‬ﭘﺲ ﺍﺯ ﻛﻠﻴﻚ ﺑﺮ ﺭﻭﻱ ‪ next‬ﻭ ‪ next‬ﻭ ﻭﺍﺭﺩ ﻛﺮﺩﻥ ﻧﺎﻡ ﺑﺮﺍﻱ ‪ datastor‬ﺑﺮ ﺭﻭﻱ ‪ next‬ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪.‬‬

‫‪ .11‬ﺩﺭ ﺍﺩﺍﻣﻪ ﺣﺠﻢ ﺩﻟﺨﻮﺍﻩ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ﺑﺮ ﺭﻭﻱ ‪ next‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ ﻭ ﺩﺭ ﺍﻧﺘﻬﺎ ‪ finish‬ﺭﺍ ﺑﺰﻧﻴﺪ‪.‬‬

‫ﺑﺎ ﺑﺴﺘﻪ ﺷﺪﻥ ﺻﻔﺤﻪ ﻭﻳﺰﺍﺭﺩ ﭘﺲ ﺍﺯﭼﻨﺪ ﺛﺎﻧﻴﻪ ‪ data store‬ﺑﻪ ﻟﻴﺴﺖ ﺍﺿﺎﻓﻪ ﺧﻮﺍﻫﺪ ﺷﺪ‪ .‬ﺗﻮﺟﻪ ﺩﺍﺷﺘﻪ‬

‫ﺑﺎﺷﻴﺪ ﻛﻪ ﻧﻴﺎﺯﻱ ﻧﻴﺴﺖ ﻛﻪ ﺍﻳﻦ ﻓﺮﺍﻳﻨﺪ ﺑﺮﺍﻱ ﻫﺮ ﻳﻚ ﺍﺯ ﻣﻴﺰﺑﺎﻥﻫﺎﻱ ‪ ESXi‬ﺗﻜﺮﺍﺭ ﺷﻮﺩ؛ ﺑﻠﻜﻪ ﺑﺎ ﺍﻓﺰﻭﺩﻥ ﻳﻚ‬

‫‪ data store‬ﺑﻪ ﻳﻚ ﺳﺮﻭﺭ ‪ ESXi‬ﻫﻤﻪ ﺳﺮﻭﺭﻫﺎﻱ ﻋﻀﻮ ﻛﻼﺳﺘﺮ‪ ،‬ﺑﻪ ﺁﻥ ‪ data store‬ﺩﺳﺘﺮﺳﻲ ﺧﻮﺍﻫﻨﺪ ﺩﺍﺷﺖ‪.‬‬

‫ﺩﺭ ﺍﻳﻨﺠﺎ ﺍﻳﻦ ﻓﺼﻞ ﺑﻪ ﭘﺎﻳﺎﻥ ﻣﻲﺭﺳﺪ‪ .‬ﺍﻟﺒﺘﻪ ﺩﻧﻴﺎﻱ ﺫﺧﻴﺮﻩﺳﺎﺯﻫﺎ‪ ،‬ﺩﻧﻴﺎﻱ ﺑﺴﻴﺎﺭ ﻭﺳﻴﻌﻲ ﺍﺳﺖ ﻛﻪ ﺧﻮﺩ‬

‫ﺑﻪﺗﻨﻬﺎﻳﻲ ﻧﻴﺎﺯ ﺑﻪ ﻳﻚ ﻛﺘﺎﺏ ﺟﺪﺍﮔﺎﻧﻪ ﺩﺍﺭﺩ‪.‬‬

‫‪94‬‬
‫ﻓﺼﻞ ‪6‬‬

‫ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﻭ ﻣﺪﻳﺮﻳﺖ ﺳﻴﺴﺘﻢ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ‬

‫ﻫﻤﻪ ﭼﻴﺰ ﺑﺮﺍﻱ ﺷﺮﻭﻉ ﺁﻣﺎﺩﻩ ﺍﺳﺖ ﺗﻤﺎﻡ ﺗﻮﺿﻴﺤﺎﺕ ﭘﻴﺸﻨﻴﺎﺯ ﺩﺭ ﻓﺼﻮﻝ ﮔﺬﺷﺘﻪ ﮔﻔﺘﻪ ﺷﺪ‪ .‬ﭘﺲ ﺑﺪﻭﻥ ﻫﻴﭻ‬

‫ﻣﻘﺪﻣﻪﺍﻱ ﭘﺲ ﻛﺎﺭ ﺍﺻﻠﻲ ﺭﺍ ﺁﻏﺎﺯ ﻣﻲﻛﻨﻴﻢ‪.‬‬

‫ﻛﺎﺭ ﺍﺻﻠﻲ ﻣﺎ ﺑﺎ ﻣﻴﺰﺑﺎﻥﻫﺎ ﻳﺎ ﻫﻤﺎﻥ ‪host‬ﻫﺎ ﻭ ﻛﻼﺳﺘﺮﻫﺎ ﺍﺳﺖ ﺑﻨﺎﺑﺮﺍﻳﻦ ﺑﺮ ﺭﻭﻱ ﺁﻳﻜﻮﻥ ‪hosts and clusters‬‬

‫ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ ﻭ ﻳﺎ ﻛﻠﻴﺪ ﺗﺮﻛﻴﺒﻲ ‪ ctrl+shift+h‬ﺭﺍ ﺑﻔﺸﺎﺭﻳﺪ‪.‬‬

‫‪ 1-6‬ﺍﻳﺠﺎﺩ ﺩﻳﺘﺎﺳﻨﺘﺮ ﻭ ﺍﺿﺎﻓﻪ ﻛﺮﺩﻥ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ ESXi‬ﺑﻪ ‪vCenter‬‬

‫ﺑﺮﺍﻱ ﺷﺮﻭﻉ ﻳﻚ ﺩﻳﺘﺎ ﺳﻨﺘﺮ ﺍﻳﺠﺎﺩ ﻣﻲ ﻛﻨﻴﻢ‪ .‬ﺑﺪﻳﻦ ﻣﻨﻈﻮﺭ ﺍﺯ ﺳﻤﺖ ﭼﭗ ﺻﻔﺤﻪ ﺑﺮ ﺭﻭﻱ ﻧﺎﻡ ﺳﺮﻭﺭ‬

‫‪ vCenter‬ﺭﺍﺳﺖ ﻛﻠﻴﻚ ﻛﺮﺩﻩ ﻭ ‪ new data vCenter‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ﻭ ﻧﺎﻣﻲ ﺑﺮﺍﻱ ﺁﻥ ﻭﺍﺭﺩ ﻛﻨﻴﺪ‪.‬‬

‫ﺩﺭ ﺍﺩﺍﻣﻪ ﺑﺎﻳﺴﺘﻲ ﻣﻴﺰﺑﺎﻥ ﻫﺎﻱ ‪ ESXi‬ﺭﺍ ﺑﻪ ‪ vCenter‬ﻣﺘﺼﻞ ﻧﻤﺎﺋﻴﺪ‪ .‬ﺑﺮﺍﻱ ﺍﻳﻦ ﻛﺎﺭ ﻣﺮﺍﺣﻞ ﺯﻳﺮ ﺭﺍ ﺍﻧﺠﺎﻡ‬

‫‪95‬‬
 ‫ﺩﻫﻴﺪ‪.‬‬

‫‪.1‬ﺑﺮ ﺭﻭﻱ ﺩﻳﺘﺎ ﺳﻨﺘﺮ ﺭﺍﺳﺖ ﻛﻠﻴﻚ ﻛﺮﺩﻩ ﻭ ﺑﺮﺭﻭﻱ ‪ Add Host‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪ .‬ﻭﻳﺰﺍﺭﺩﻱ ﺍﺟﺮﺍ ﺧﻮﺍﻫﺪ ﺷﺪ‪.‬‬

‫ﺷﻜﻞ ‪ 1-6‬ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺭﺍ ﻧﺸﺎﻥ ﻣﻲﺩﻫﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 1 6‬ﺍﺿﺎﻓﻪ ﻛﺮﺩﻥ ﻣﻴﺰﺑﺎﻥﻫﺎﻱ ‪ ESXi‬ﺑﻪ ‪vCenter‬‬

‫‪ .2‬ﺩﺭ ﺻﻔﺤﻪ ﺍﻭﻝ ﻭﻳﺰﺍﺭﺩ ﺍﺟﺮﺍ ﺷﺪ ﺩﺭ ﻗﺴﻤﺖ ‪ host‬ﻧﺎﻡ ﺳﺮﻭﺭ ‪ ESXi‬ﻭ ﻳﺎ ﺁﺩﺭﺱ ‪ IP‬ﺁﻥ ﺭﺍ ﻭﺍﺭﺩ ﻛﻨﻴﺪ‪ .‬ﺩﺭ‬

‫ﻗﺴﻤﺖ ‪ username‬ﻧﺎﻡ ﻛﺎﺭﺑﺮﻱ ‪ root‬ﻭ ﺩﺭ ﻗﺴﻤﺖ ‪ ، password‬ﭘﺴﻮﺭﺩ ﻛﺎﺭﺑﺮ ‪ root‬ﺭﺍ ﻭﺍﺭﺩ ﻧﻤﺎﺋﻴﺪ ﺑﺮ ﺭﻭﻱ‬

‫‪ next‬ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪.‬‬

‫‪ .3‬ﺍﻃﻼﻋﺎﺗﻲ ﺩﺭ ﻣﻮﺭﺩ ﺳﺮﻭﺭ ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﺧﻮﺍﻫﺪ ﺷﺪ‪ .‬ﺩﻭﺑﺎﺭﻩ ‪ next‬ﺭﺍﺑﺰﻧﻴﺪ‪.‬‬

‫‪ .4‬ﺩﺭ ﺍﻳﻦ ﻣﺮﺣﻠﻪ ﻣﻲﺗﻮﺍﻧﻴﺪ‪ license key‬ﺑﻪ ﺳﺮﻭﺭ ﺍﺧﺘﺼﺎﺹ ﺩﻫﻴﺪ‪ .‬ﻭ ‪ next‬ﺭﺍ ﺑﺰﻧﻴﺪ‪.‬‬

‫‪ .5‬ﺩﺭ ﺍﻳﻦ ﻗﺴﻤﺖ ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﺑﺎ ﻋﻼﻣﺖ ﺯﺩﻥ ﭼﻚ ﺑﺎﻛﺲ ‪ enable lockdown mode‬ﺍﻣﻜﺎﻥ ﻭﺍﺭﺩ ﺷﺪﻥ‬

‫ﺳﺮﻭﺭ ‪ ESXi‬ﺑﻪ ﻃﻮﺭ ﻣﺴﺘﻘﻴﻢ )ﺑﺪﻭﻥ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ (vCenter‬ﺍﺯ ﺭﺍﻩ ﺩﻭﺭ ﺭﺍ ﻏﻴﺮ ﻓﻌﺎﻝ ﻧﻤﺎﺋﻴﺪ ‪ .‬ﺑﺎ ﺯﺩﻥ ‪ next‬ﺑﻪ‬

‫‪96‬‬
 ‫ﻣﺮﺣﻠﻪ ﺑﻌﺪ ﺑﺮﻭﻳﺪ‪.‬‬

‫‪ .6‬ﺩﺭ ﺍﻳﻨﺠﺎ ﭘﺲ ﺍﺯﺍﻧﺘﺨﺎﺏ ﺩﻳﻨﺎﺳﻨﺘﺮ ﺑﺮﺍﻱ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺑﺮ ﺭﻭﻱ ‪ next‬ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪ ،‬ﻭ ﭘﺲ ﺍﺯ ﺁﻥ‬

‫‪ finish‬ﺭﺍ ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪ .‬ﭘﺲ ﺍﺯ ﻣﺪﺕ ﻛﻮﺗﺎﻫﻲ ﻣﻴﺰﺑﺎﻥ ﺍﺿﺎﻓﻪ ﺷﺪﻩ ﺩﺭ ﺳﻤﺖ ﭼﭗ ﺻﻔﺤﻪ ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﺧﻮﺍﻫﺪ‬

‫ﺷﺪ‪.‬‬

‫‪ 2-6‬ﺳﺎﺧﺖ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ‬

‫ﺩﻭﻣﻴﻦ ﻣﺴﺌﻠﻪ ﭘﺲ ﺍﺯ ﺍﺿﺎﻓﻪ ﻛﺮﺩﻥ ﻣﻴﺰﺑﺎﻧﻬﺎ‪ ،‬ﺍﻳﺠﺎﺩ ﻭ ﺭﺍﻩﺍﻧﺪﺍﺯﻱ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺍﺳﺖ‪.‬ﺑﺮﺍﻱ ﺍﻳﻦ ﻛﺎﺭ‪:‬‬

‫‪ .1‬ﺑﺮ ﺭﻭﻱ ﻛﻼﺳﺘﺮ ﻳﺎ ﻣﻴﺰﺑﺎﻥ ﻣﻮﺭﺩ ﻧﻈﺮ ﺭﺍﺳﺖﻛﻠﻴﻚ ﻛﺮﺩﻩ‪ New Virtual Machine ،‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪.‬‬

‫‪ .2‬ﻭﻳﺰﺍﺭﺩﻱ ﺍﺟﺮﺍ ﺧﻮﺍﻫﺪ ﺷﺪ‪ .‬ﺩﺭ ﺻـﻔﺤﻪ ﺍﻭﻝ ﺩﻭ ﮔﺰﻳﻨـﻪ ﺩﺭ ﺩﺳـﺘﺮﺱ ﺧﻮﺍﻫـﺪ ﺑـﻮﺩ‪ .‬ﺑـﺎ ﺍﻧﺘﺨـﺎﺏ ﮔﺰﻳﻨـﻪ‬

‫‪ Typical‬ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﻣﺠﺎﺯﻱ ﭘﻴﺶﻓﺮﺽ ﺑﻪ ﺳﻴﺴﺘﻢ ﺍﺧﺘﺼﺎﺹ ﺧﻮﺍﻫﺪ ﻳﺎﻓﺖ ﻛﻪ ﺍﻟﺒﺘﻪ ﭘﺲ ﺍﺯ ﺳـﺎﺧﺖ‬

‫ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻗﺎﺑﻞ ﺗﻐﻴﻴﺮ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪ .‬ﺍﻣﺎ ﺩﺭ ﮔﺰﻳﻨﻪ ‪ ،Custom‬ﺍﺧﺘﺼﺎﺹ ﺳﺨﺖﺍﻓﺰﺍﺭ‪ ،‬ﺩﺭ ﻃﻲ ﻭﻳﺰﺍﺭﺩ‬

‫ﺻﻮﺭﺕ ﺧﻮﺍﻫﺪ ﭘﺬﻳﺮﻓﺖ‪ Typical .‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ‪ Next‬ﺭﺍ ﺑﺰﻧﻴﺪ‪.‬‬

‫‪ .3‬ﭘﺲ ﺍﺯ ﺍﻧﺘﺨﺎﺏ ﺩﻳﺘﺎﺳﻨﺘﺮ ﺑﺮﺍﻱ ﻋﻀﻮﻳﺖ ﻣﺎﺷﻴﻦ ﻣﺠـﺎﺯﻱ ﻭ ﻭﺍﺭﺩﻛـﺮﺩﻥ ﻧـﺎﻣﻲ ﺩﻟﺨـﻮﺍﻩ ﺑـﺮﺍﻱ ﻣﺎﺷـﻴﻦ‬

‫ﻣﺠﺎﺯﻱ ‪ Next‬ﺭﺍ ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪.‬‬

‫‪ .4‬ﺩﺭ ﺍﻳﻦ ﻗﺴﻤﺖ‪ ،‬ﺫﺧﻴﺮﻩﺳﺎﺯ ﻣﻮﺭﺩﻧﻈﺮ ﺑـﺮﺍﻱ ﻧﮕﻬـﺪﺍﺭﻱ ﻣﺎﺷـﻴﻦ ﻣﺠـﺎﺯﻱ ﺭﺍ ﺍﻧﺘﺨـﺎﺏ ﻛﻨﻴـﺪ ﻭ ‪ Next‬ﺭﺍ‬

‫ﺑﺰﻧﻴﺪ‪.‬‬

‫‪ .5‬ﺩﺭ ﺍﻳﻨﺠﺎ ﻣﻲﺗﻮﺍﻧﻴﺪ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻣﻮﺭﺩ ﻧﻈﺮ ﺑﺮﺍﻱ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪.‬‬

‫‪ .6‬ﺩﺭ ﺍﻳﻦ ﺟﺎ ﻛﺎﺭﺕ ﺷﺒﻜﻪ‪ ،‬ﻧﻮﻉ ﺁﻥ ﻭ ﺷﺒﻜﻪ‪/‬ﺷﺒﻜﻪﻫﺎﻱ ﻣﺘﺼﻞ ﺑﻪ ﺁﻥ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ Next .‬ﺭﺍ ﺑﺰﻧﻴﺪ‪.‬‬

‫‪ .7‬ﺩﺭ ﺍﻳﻦ ﻣﺮﺣﻠﻪ ﻓﻀﺎﻱ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ﺑﺮﺍﻱ ﺍﺧﺘﺼﺎﺹ ﺑﻪ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ)ﺑﻪ ﻋﻨﻮﺍﻥ ﺩﻳﺴﻚ ﺳﺨﺖ ﻣﺠـﺎﺯﻱ(‬

‫ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ .‬ﺑﺮﺍﻱ ﺍﺧﺘﺼﺎﺹ ﻓﻀﺎ ﺑﻪ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺩﻭ ﺍﻧﺘﺨﺎﺏ ﻭﺟـﻮﺩ ﺩﺍﺭﺩ‪Thick Provision .‬‬

‫ﻭ ‪ .Thin Provision‬ﺍﮔﺮ ﺍﻭﻟﻲ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ ،‬ﻛﻞ ﻓﻀﺎﻱ ﺩﺭﺧﻮﺍﺳﺖ ﺷﺪﻩ ﺑﻪ ﻣﺤﺾ ﺳـﺎﺧﺘﻪ ﺷـﺪﻥ‬

‫‪97‬‬
‫ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ‪ ،‬ﺑﻪ ﺁﻥ ﺍﺧﺘﺼﺎﺹ ﺧﻮﺍﻫﺪ ﻳﺎﻓﺖ‪ .‬ﻳﻌﻨﻲ ﻛﻞ ﻓﻀﺎﻱ ﺩﺭﺧﻮﺍﺳﺖ ﺷﺪﻩ ﺍﺷﻐﺎﻝ ﺧﻮﺍﻫﺪ ﺷﺪ‪.‬‬

‫ﺍﻣﺎ ﺩﺭ ﺣﺎﻟﺖ ﺩﻭﻡ )‪ (Thin Provision‬ﻓﻀـﺎﻱ ﺩﺭﺧﻮﺍﺳـﺖ ﺷـﺪﻩ ﻓﻘـﻂ ﻧﺸـﺎﻧﮕﺮ ﻣﺤـﺪﻭﺩﻳﺖ ﻣﺎﺷـﻴﻦ‬

‫ﻣﺠﺎﺯﻱ ﺩﺭ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻓﻀﺎﻱ ﺩﺧﻴﺮﻩ ﺳﺎﺯﻱ ﺍﺳﺖ‪ .‬ﻳﻌﻨﻲ ﺗﺎ ﺯﻣـﺎﻧﻲ ﻛـﻪ ﻣﺎﺷـﻴﻦ ﻣﺠـﺎﺯﻱ ﺍﺯ ﺍﻳـﻦ ﻓﻀـﺎ‬

‫ﺍﺳﺘﻔﺎﺩﻩ ﻧﻜﻨﺪ )ﻓﺎﻳﻠﻲ ﺩﺭ ﺁﻥ ﻗﺮﺍﺭ ﻧﺪﻫﺪ( ﻓﻀﺎﻳﻲ ﺍﺷﻐﺎﻝ ﻧﺨﻮﺍﻫﺪ ﺷﺪ‪ .‬ﭘﺲ ﺍﺯ ﺗﻜﻤﻴﻞ ﺍﻳﻦ ﻗﺴـﻤﺖ‪ ،‬ﺑـﺮ‬

‫ﺭﻭﻱ ‪ Next‬ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪.‬‬

‫‪ .8‬ﺩﺭ ﺍﻳﻦ ﻗﺴﻤﺖ ﺧﻼﺻﻪﺍﻱ ﺍﺯ ﻣﺸﺨﺼﺎﺕ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﺧﻮﺍﻫﺪ ﺷـﺪ‪ .‬ﺩﺭ ﭘﺎﻳـﺎﻥ ﺑـﺮ ﺭﻭﻱ‬

‫‪ Finish‬ﻛﻠﻴﻚ ﻛﻨﻴﺪ ﺗﺎ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺳﺎﺧﺘﻪ ﺷﻮﺩ‪.‬‬

‫‪ 3-6‬ﺗﺨﺼﻴﺺ ﻣﻨﺎﺑﻊ ﺑﻪ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ‬

‫ﺩﺭ ﻫﻨﮕﺎﻡ ﺍﻳﺠﺎﺩ ﻭ ﭘﺲ ﺍﺯ ﺳﺎﺧﺖ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻣﻲﺗﻮﺍﻥ ﻣﻨﺎﺑﻊ ﺍﺧﺘﺼـﺎﺹ ﺩﺍﺩﻩ ﺷـﺪﻩ ﺑـﻪ ﻣﺎﺷـﻴﻦﻫـﺎﻱ‬

‫ﻣﺠﺎﺯﻱ‪ ،‬ﺍﺯ ﺟﻤﻠﻪ ﺣﺎﻓﻈﻪ‪ ،‬ﭘﺮﺩﺍﺯﻧﺪﻩ ‪ ،‬ﻛﺎﺭﺕ ﻫﺎﻱ ﺷﺒﻜﻪ ‪ ،‬ﺫﺧﻴﺮﻩﺳﺎﺯﻫﺎ ﻭ ‪ ....‬ﺭﺍ ﺍﻓﺰﺍﻳﺶ ﻭ ﻛﺎﻫﺶ ﺩﺍﺩ؛ ﻭ ﻳﺎ ﺣﺘﻲ‬

‫ﺩﺭ ﻫﻨﮕﺎﻡ ﺭﻭﺷﻦ ﺑﻮﺩﻥ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻫﻢ ﻣﻲﺗﻮﺍﻥ ﺑﻌﻀﻲ ﺍﺯ ﺁﻧﻬﺎ ﺭﺍ ﻭﻳﺮﺍﻳﺶ ﻛﺮﺩ ) ﺍﻓﺰﺍﻳﺶ ﻳـﺎ ﻛـﺎﻫﺶ ﺩﺍﺩ ( ‪.‬‬

‫ﺑﺮﺍﻱ ﺍﻳﻦ ﻛﺎﺭ ﺑﺮﺭﻭﻱ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻣﻮﺭﺩ ﻧﻈﺮ ﺭﺍﺳﺖ ﻛﻠﻴﻚ ﻛﺮﺩﻩ ‪ Edit setting‬ﺭﺍ ﺑﺮﮔﺰﻳﻨﻴﺪ‪ .‬ﻫﻤـﺎﻧﻄﻮﺭ ﻛـﻪ‬

‫ﺩﺭ ﺷﻜﻞ ‪ 2-6‬ﻧﻴﺰ ﻣﺸﺎﻫﺪﻩ ﻣﻲﻛﻨﻴﺪ ﺩﺍﺭﺍﻱ ﭼﻨﺪﻳﻦ ﺳﺮﺑﺮگ ﺍﺳﺖ ﻛﻪ ﺑﺘﺮﺗﻴﺐ ﺁﻧﻬﺎ ﺭﺍ ﺗﻮﺿﻴﺢ ﺧﻮﺍﻫﻴﻢ ﺩﺍﺩ‪.‬‬

‫‪98‬‬
 ‫ﺷﻜﻞ ‪ . 2 6‬ﺗﺨﺼﻴﺺ ﻣﻨﺎﺑﻊ ﺑﻪ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ‬

‫ﺳﺮﺑﺮگ ﺍﻭﻝ ﻛﻪ ‪ Hardware‬ﺍﺳﺖ ﻭ ﺩﺭ ﺁﻥ ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﻣﻨﺎﺑﻊ ﻓﻴﺰﻳﻜﻲ ﺍﺧﺘﺼﺎﺹ ﺩﺍﺩﻩ ﺷﺪﻩ ﺑﻪ ﻣﺎﺷﻴﻦ ﻣﺠـﺎﺯﻱ‬

‫ﺭﺍ ﺗﻐﻴﻴﺮ ﺗﻐﻴﻴﺮ ﺩﻫﻴﺪ ﻭ ﻳﺎ ﺣﺘﻲ ﻣﻲﺗﻮﺍﻧﻴﺪ ﺑﺎ ﻛﻠﻴﻚ ﺑﺮﺭﺭﻭﻱ ‪ ، Add‬ﺳﺨﺖﺍﻓﺰﺍﺭ ﻣﺠـﺎﺯﻱ ﺩﻳﮕـﺮﻱ ﺑـﻪ ﺳﻴﺴـﺘﻢ‬

‫ﺍﺿﺎﻓﻪ ﻛﻨﻴﺪ ) ﺷﻜﻞ ‪ . (3-6‬ﺩﺭ ﻋﻴﻦ ﺍﻫﻤﻴﺖ‪ ،‬ﻛﺎﺭﻛﺮﺩﻥ ﺑﺎ ﺍﻳﻦ ﻗﺴﻤﺖ ﺳﺎﺩﻩ ﺑﻮﺩﻩ ﻭ ﻧﻴﺎﺯ ﺑﻪ ﺩﺍﻧﺶ ﺯﻳﺎﺩﻱ ﻧﺪﺍﺭﺩ‬

‫ﺑﻨﺎﺑﺮﺍﻳﻦ ﺍﺯ ﺗﻮﺿﻴﺢ ﺑﻴﺸﺘﺮ ﺩﺭ ﺍﻳﻦ ﺭﺍﺑﻄﻪ ﺧﻮﺩﺩﺍﺭﻱ ﻣﻲﻛﻨﻴﻢ ‪.‬‬

‫ﺩﺭ ﺳﺮﺑﺮگ ‪ Option‬ﻭﻳﮋﮔﻲ ﻫﺎﻱ ﻓﻨﻲ ﺗﺮﻱ ﺩﺭ ﺩﺳﺘﺮﺱ ﺧﻮﺍﻫﺪ ﺑﻮﺩ ﻛﻪ ﺑﻴﺸﺘﺮ ﻣﺮﺑﻮﻁ ﺑﻪ ﻓﻮﻕ ﻧﺎﻇﺮ ﺍﺳـﺖ ‪ .‬ﺍﺯ‬

‫ﺟﻤﻠﻪ ﺍﻳﻦ ﻭﻳﮋﮔﻲﻫﺎ ﻣﻲﺗﻮﺍﻥ ﺑﻪ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺍﺷﺎﺭﻩ ﻛﺮﺩ‪:‬‬

‫‪ -‬ﺗﻐﻴﻴﺮ ﻧﻮﻉ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ) ﻭﻳﻨﺪﻭﺯ ‪ ،‬ﻟﻴﻨﻮﻛﺲ ﻭ‪(.......‬‬

‫‪ -‬ﻓﻌﺎﻝ ﻭ ﻏﻴﺮﻓﻌﺎﻝ ﻛﺮﺩﻥ ‪ VMware tools‬ﻛﻪ ﺑﺮﺭﻭﻱ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻧﺼﺐ ﻣﻲﺷـﻮﺩ ﻭ‬

‫ﺍﻣﻜﺎﻥ ﻣﺪﻳﺮﻳﺖ ﺑﻬﺘﺮ ﺁﻥ ﺭﺍﻓﺮﺍﻫﻢ ﻣﻲﻛﻨﺪ ‪.‬‬

‫‪ -‬ﺗﻨﻈﻴﻤﺎﺕ ﻣﺮﺑﻮﻁ ﺑﻪ ﺭﻭﺷﻦ ﻭ ﺧﺎﻣﻮﺵ ﻛﺮﺩﻥ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ‬

‫‪ -‬ﻓﻌﺎﻝ ﻛﺮﺩﻥ ﻭﻳﺰﮔﻲ ﻫﺎﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ﻣﺠﺎﺯﻱ ﺳﺎﺯﻱ‬

‫‪99‬‬
‫ﺳﺮﺑﺮگ ﺳﻮﻡ ‪ Resourse :‬ﺍﺳﺖ ﻛﻪ ﺩﺭ ﺁﻥ ﻣﻲﺗﻮﺍﻧﻴﺪ ﻣﺤﺪﻭﺩﻳﺖﻫﺎﻱ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠـﺎﺯﻱ ﺩﺭ ﺩﺳﺘﺮﺳـﻲ ﺑـﻪ‬

‫ﻣﻨﺎﺑﻊ ﭘﺮﺩﺍﺯﺵ ﻭ ﺣﺎﻓﻈﻪ ﺭﺍ ﺗﻨﻈﻴﻢ ﻧﻤﺎﺋﻴﺪ‪ .‬ﺩﺭﺍﻳﻦ ﺳﺮﺑﺮگ ﺩﻭ ﮔﺰﻳﻨـﻪ ﺧﻴﻠـﻲ ﻣﻬـﻢ ﻭﺟـﻮﺩ ﺩﺍﺭﺩ ﻳـﻚ ‪ CPU‬ﻭ‬

‫ﺩﻳﮕﺮﻱ ‪ Memory‬ﺩﺭ ﻫﺮﻳﻚ ﺍﺯ ﺍﻳﻦ ﺩﻭ ﺑﺨﺶ ﺳﻪ ﻗﺴﻤﺖ ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﻣﻲﻛﻨﻴﺪ‪:‬‬

‫‪ : Reservation‬ﻛﺎﻣﻼ ﺭﻭﺷﻦ ﺍﺳﺖ ﻛﻪ ﻣﻨﺎﺑﻊ ﻳﻚ ﻣﻴﺰﺑﺎﻥ ﻓﻴﺰﻳﻜﻲ ﺑﻴﻦ ﻣﺎﺷـﻴﻦ ﻣﺠـﺎﺯﻱ ﺭﺍﻩ ﺍﻧـﺪﺍﺯﻱ‬ ‫‪-‬‬

‫ﺷﺪﻩ ﺑﺮﺭﻭﻱ ﺁﻥ ﺗﺴﻬﻴﻢ ﻳﺎ ﻫﻤﺎﻥ ‪ share‬ﻣﻲﺷﻮﺩ ‪ .‬ﻣﻘﺪﺍﺭ ﻣﻮﺟﻮﺩ ﺩﺭ ‪ Reservation‬ﻣﻘﺪﺍﺭﻱ ﺍﺳﺖ ﻛﻪ‬

‫ﺑﻪ ﻣﺤﺾ ﺭﻭﺷﻦ ﺷﺪﻥ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ‪ ،‬ﺑﻪ ﺁﻥ ﺍﺧﺘﺼﺎﺹ ﻣﻲﻳﺎﺑﺪ ﺍﮔﺮ ﭼﻪ ﺍﺯ ﺁﻥ ﺍﺳﺘﻔﺎﺩﻩ ﻧﻜﻨﺪ ‪.‬‬

‫‪ :Limit‬ﺍﻳﻦ ﻣﻘﺪﺍﺭ ‪ ،‬ﺣﺪﺍﻛﺜﺮ ﻓﻀﺎﻳﻲ ﺍﺯ ﺣﺎﻓﻈﻪ ﻳﺎ ﻓﺮﻛﺎﻧﺲ ﺍﺯ ﭘﺮﺩﺍﺯﻧـﺪﻩ ﺍﺳـﺖ ﻛـﻪ ﻣﺎﺷـﻴﻦ ﻣﺠـﺎﺯﻱ‬ ‫‪-‬‬

‫ﻣﻲ ﺗﻮﺍﻧﺪ ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﺪ ‪ .‬ﺍﻟﺒﺘﻪ ﺑﺎ ﺯﺩﻥ ﺗﻴﻚ ‪ Unlimited‬ﻣﺎﺷـﻴﻦ ﻣﺠـﺎﺯﻱ ﺍﻣﻜـﺎﻥ ﺩﺳﺘﺮﺳـﻲ ﺑـﻪ ﻛـﻞ‬

‫ﻣﻨﺎﺑﻊ ) ﺩﺭ ﺻﻮﺭﺕ ﻭﺟﻮﺩ( ﺭﺍ ﺧﻮﺍﻫﺪ ﺩﺍﺷﺖ‪.‬‬

‫‪ : Shares -‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﮔﻔﺘﻪ ﺷﺪ ﻣﻨﺎﺑﻊ ﺳﺮﻭﺭ ﻓﻴﺰﻳﻜﻲ ﺑﻴﻦ ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻣﺠـﺎﺯﻱ ‪ Share‬ﻣـﻲﺷـﻮﺩ ﻭ‬

‫ﻫﺮ ﻳﻚ ﺍﺯ ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺑﺮﺍﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻣﻨﺎﺑﻊ ﺑﺎ ﺩﻳﮕﺮ ﻣﺎﺷﻴﻦﻫـﺎ ﺭﻗﺎﺑـﺖ ﻣـﻲﻛﻨـﺪ‪Shares .‬‬

‫ﻫﻤﺎﻥ ﺍﻭﻟﻮﻳﺖ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺑﺮﺍﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻣﻨﺎﺑﻊ ﻣﺸﺘﺮﻙ ﺍﺳﺖ؛ ﻛﻪ ﻣﻲ ﺗﻮﺍﻥ ﻳﻜﻲ ﺍﺯ ﻣﻘـﺪﺍﺭﻫﺎﻱ‬

‫‪ normal ، low‬ﻭ ‪ high‬ﺭﺍ ﺑﻪ ﺁﻥ ﺍﺧﺘﺼﺎﺹ ﺩﺍﺩ ‪.‬ﻭ ﻳﺎ ﺑـﺎ ﺍﻧﺘﺨـﺎﺏ ‪ Custom‬ﻣﻘـﺪﺍﺭﻱ ﺩﻟﺨـﻮﺍﻩ ﺑـﻪ ﺁﻥ‬

‫ﻧﺴﺒﺖ ﺩﺍﺩ ‪.‬‬

‫ﺗﻮﺟﻪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﺪ ﻛﻪ ﺍﮔﺮ ﻣﺎﺷـﻴﻦ ﻣﺠـﺎﺯﻱ ﻧﻴـﺎﺯ ﺑـﺎﻻﻳﻲ ﺑـﻪ ﻣﻨـﺎﺑﻊ ﺩﺍﺭﺩ ﻋـﺪﺩ ﺑـﺎﻻﺗﺮﻱ ﺩﺭ ‪ share‬ﺑـﻪ ﺁﻥ‬

‫ﺍﺧﺘﺼﺎﺹ ﺩﻫﻴﺪ؛ ﻭ ﺩﻳﮕﺮ ﺍﻳﻨﻜﻪ ﻣﻘﺪﺍﺭﻱ ﻛﻪ ﺑﻪ ‪ limit‬ﺍﺧﺘﺼـﺎﺹ ﻣـﻲﺩﻫﻴـﺪ ﺑﻬﺘـﺮ ﺍﺳـﺖ ‪ 50‬ﺩﺭﺻـﺪ ﻣﻘـﺪﺍﺭ‬

‫‪Reservation‬ﺑﺎﺷﺪ‪ .‬ﻣﻘﺪﺍﺭ ‪ Reservation‬ﻫﻢ ﺩﺭ ﺣﺪﻭﺩ ‪ 5‬ﺗﺎ ‪ 10‬ﺩﺭﺻﺪ ﻇﺮﻓﻴﺖ ﻣﻴﺰﺑﺎﻥ ﻓﻴﺰﻳﻜﻲ ﺑﺎﺷﺪ‪.‬‬

‫‪ 4-6‬ﺳﺎﺧﺖ ﻛﻼﺳﺘﺮ ﻭ ﺍﺿﺎﻓﻪ ﻛﺮﺩﻥ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ ESXi‬ﺑﻪ ﺁﻥ‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻗﺒﻼ ﻫﻢ ﮔﻔﺘﻪ ﺷﺪ ﺑﺴﻴﺎﺭﻱ ﺍﺯ ﻭﻳﮋﮔﻲ ﻫﺎ ﻭ ﻗﺎﺑﻠﻴﺖﻫﺎﻱ ‪ vSphere‬ﺑﺎ ﻭﺟـﻮﺩ ﻛﻼﺳـﺘﺮ‪ ،‬ﻣﻤﻜـﻦ‬

‫ﻣﻲﺷﻮﻧﺪ‪ .‬ﺑﺮﺍﻱ ﺳﺎﺧﺖ ﻛﻼﺳﺘﺮ ﺑﻪ ﻃﺮﻳﻖ ﺯﻳﺮ ﻋﻤﻞ ﻛﻨﻴﺪ ‪:‬‬

‫‪100‬‬
 ‫‪ -1‬ﺑﺮﺭﻭﻱ ﺩﻳﺘﺎ ﺳﻨﺘﺮ ﻣﻮﺭﺩ ﻧﻈﺮ ﺭﺍﺳﺖ ﻛﻠﻴﻚ ﻛﺮﺩﻩ ‪ new cluter،‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ .‬ﺷﻜﻞ ‪.3-6‬‬

‫ﺷﻜﻞ ‪ . 3 6‬ﺳﺎﺧﺖ ﻛﻼﺳﺘﺮ‬

‫‪ -2‬ﺩﺭ ﻭﻳﺰﺍﺭﺩ ﺍﺟﺮﺍ ﺷﺪﻩ ‪ ،‬ﺩﺭ ﻛﺎﺩﺭ ‪ ، name‬ﻧﺎﻣﻲ ﺑﺮﺍﻱ ﺁﻥ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ ،‬ﺩﺭ ﻫﻤـﻴﻦ ﻗﺴـﻤﺖ ﻣـﻲﺗﻮﺍﻧﻴـﺪ‬

‫ﻭﻳﮋﮔﻲﻫﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ﻗﺎﺑﻠﻴﺖ ﺩﺳﺘﺮﺳﻲ ﺑﺎﻻ ﻳﺎ ﻫﻤﺎﻥ ‪ HA‬ﻭ ﻫﻤﭽﻨﻴﻦ ﺯﻣﺎﻧﺒﻨﺪ ﻣﻨﺎﺑﻊ ﺗﻮﺯﻳﻊ ﺷﺪ ﻳـﺎ ‪DRS‬‬

‫ﺭﺍ ﻧﻴﺰ ﺑﺎ ﭘﺮﻛﺮﺩﻥ ﭼﻚ ﺑﺎﻛﺲ ﻣﺮﺑﻮﻁ ﺑﻪ ﻫﺮ ﻛﺪﺍﻡ ﻓﻌﺎﻝ ﻛﻨﻴﺪ‪ .‬ﺍﻟﺒﺘﻪ ﻓﻌﻼ ﺍﻳﻦ ﺩﻭﮔﺰﻳﻨـﻪ ﺭﺍ ﺍﻧﺘﺨـﺎﺏ ﻧﻜﻨﻴـﺪ‬

‫ﺩﺭ ﺍﺩﺍﻣﻪ ﻫﺮ ﺩﻭ ﺍﻳﻦ ﻭﻳﺰﮔﻲ ﻫﺎ ﺭﺍ ﺑﻄﻮﺭ ﻣﻔﺼﻞ ﺑﺮﺭﺳﻲ ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩ‪ .‬ﺣﺎﻝ ﺑﺮﺭﻭﻱ ‪ next‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ ‪.‬‬

‫‪ -3‬ﺩﺭ ﺍﻳﻦ ﻗﺴﻤﺖ ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﺑﺎ ﺍﻧﺘﺨﺎﺏ ﺷﺮﻛﺖ ﺳﺎﺯﻧﺪﻩ ﻭ ﻧﻮﻉ ﭘﺮﺩﺍﺯﻧﺪﻩ ﻣﻴﺰﺑﺎﻥﻫﺎﻱ ﻋﻀﻮ ﻛﻼﺳﺘﺮ ﻗﺎﺑﻠﻴﺖ‬

‫‪ EVC1‬ﺭﺍ ﻓﻌﺎﻝ ﻛﻨﻴﺪ‪ .‬ﺗﻮﺟﻪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﺪ ﻛـﻪ ﺑـﺮﺍﻱ ﻓﻌـﺎﻝ ﺳـﺎﺯﻱ ‪ ،EVC‬ﺍﻳـﻦ ﻗﺎﺑﻠﻴـﺖ ﻣـﻲﺑﺎﻳﺴـﺖ ﺩﺭ‬

‫ﭘﺮﺩﺍﺯﻧﺪﻩﻫﺎﻱ ﻣﻴﺰﺑﺎﻥﻫﺎﻱ ﻋﻀﻮ ﻛﻼﺳﺘﺮ ﻭﺟﻮﺩ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ ﻭ ﺩﺭ ‪ BIOS‬ﺍﻳﻦ ﻣﻴﺰﺑﺎﻧﻬﺎ ﻧﻴﺰ ﺍﻳﻦ ﻗﺎﺑﻠﻴـﺖ ﻛـﻪ‬

‫ﺩﺭ ﭘﺮﺩﺍﺯﻧﺪﻩ ﺍﻳﻨﺘﻞ ﺍﻥ ﺭﺍ ﺑﺎ ‪ Intel-VT‬ﺩﺭ ﭘﺮﺩﺍﺯﻧﺪﻩ ﻫﺎﻱ ‪ AMD‬ﺑـﺎ ﻧـﺎﻡ ‪ AMD-V‬ﺷـﻨﺎﺧﺘﻪ ﻣـﻲﺷـﻮﻧﺪ‪،‬‬

‫ﻓﻌﺎﻝ ﺑﺎﺷﺪ‪ .‬ﺩﻭﺑﺎﺭﻩ ‪ next‬ﺭﺍ ﺑﺰﻧﻴﺪ‪.‬‬

‫‪Enhanced vMotion Compatability 1‬‬

‫‪101‬‬
‫‪ -4‬ﺩ ﺭﺍﻳﻦ ﻗﺴﻤﺖ ﻣﻲﺗﻮﺍﻧﻴﺪ ﻣﺤﻞ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ‪ swap‬ﻣﺮﺑﻮﻁ ﺑﻪ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻋﻀـﻮ ﻛﻼﺳـﺘﺮ ﺭﺍ‬

‫ﻣﺸﺨﺺ ﻛﻨﻴﺪ ﺑﺎﺯﺩﻥ ‪ next‬ﺑﻪ ﻣﺮﺣﻠﻪ ﺑﻌﺪ ﺑﺮﻭﻳﺪ ‪.‬‬

‫‪ -5‬ﺩﺭ ﺍﻳﻦ ﻗﺴﻤﺖ ﻣﻲﺗﻮﺍﻧﻴﺪ ﺧﻼﺻﻪﺍﻱ ﺍﺯ ﻣﺸﺨﺼﺎﺕ ﻛﻼﺳﺘﺮ ﺍﻳﺠﺎﺩ ﺷﺪﻩ ﺭﺍ ﺑﺒﻴﻨﻴـﺪ ﻛـﻪ ﺑـﺎ ﺯﺩﻥ ‪Finish‬‬

‫ﻣﺮﺣﻠﻪ ﺳﺎﺧﺖ ﻛﻼﺳﺘﺮ ﺑﻪ ﭘﺎﻳﺎﻥ ﻣﻲﺭﺳﺪ ‪.‬‬

‫ﺑﺮﺍﻱ ﺍﺿﺎﻓﻪ ﻛﺮﺩﻥ ﻣﻴﺰﺑﺎﻥﻫﺎﻱ ‪ ESXi‬ﺑﻪ ﻛﻼﺳﺘﺮ‪ ،‬ﻣﻲﺗﻮﺍﻧﻴـﺪ ﺑـﺮﺭﻭﻱ ﺍﻥ ﺭﺍﺳـﺖ ﻛﻠﻴـﻚ ﻛـﺮﺩﻩ ﻭ ﻣﺮﺍﺣـﻞ‬

‫ﺍﻓﺰﻭﺩﻥ ﻣﻴﺰﺑﺎﻥ ﺑﻪ ﻛﻼﺳﺘﺮ ﺭﺍ ﻫﻤﺎﻧﻨﺪ ﺍﻓﺰﻭﺩﻥ ﻣﻴﺰﺑﺎﻥ ﺑﻪ ﺩﻳﺘﺎ ﺳﻨﺘﺮ ﺭﺍ ﺗﻜﺮﺍﺭ ﻛﻨﻴﺪ‪ ) .‬ﺍﻓـﺰﻭﺩﻥ ﻣﻴﺰﺑـﺎﻥ ﺑـﻪ‬

‫ﺩﻳﺘﺎ ﺳﻨﺘﺰ ﻗﺒﻼ ﺩﺭ ﻫﻤﻴﻦ ﻓﺼﻞ ﮔﻔﺘﻪ ﺷﺪ (‬

‫ﻫﻤﭽﻨﻴﻦ ﺍﮔﺮ ﺍﺯ ﻗﺒﻞ ﻣﻴﺰﺑﺎﻥﻫﺎﻳﻲ ﻋﻀﻮ ﺩﻳﺘﺎﺳﻨﺘﺮ ﻫﺴﺘﻨﺪ ﺑﺎ ﻋﻤﻞ ‪ drag&drop‬ﻣﻲﺗﻮﺍﻧﻴـﺪ ﻣﻴﺰﺑـﺎﻥﻫـﺎﻱ‬

‫‪ ESXi‬ﺭﺍ ﺑﻪ ﻋﻀﻮﻳﺖ ﻛﻼﺳﺘﺮ ﺩﺭﺁﻭﺭﻳﺪ ﻭﻳﺎ ﺑﻴﻦ ﺩﻳﺘﺎﺳﻨﺘﺮﻫﺎ ﻭ ﻛﻼﺳﺘﺮﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺟﺎﺑﻪﺟﺎ ﻛﻨﻴـﺪ ‪ .‬ﺑـﺮﺍﻱ‬

‫ﺧـﺎﺭﺝ ﻛــﺮﺩﻥ ﻳـ ﻚ ﻣﻴﺰﺑــﺎﻥ ‪ ESXi‬ﺍﺯ ﻛﻼﺳـﺘﺮ ﻧﻴـﺰ ﻣـﻲﺗﻮﺍﻧﻴــﺪ ﭘــﺲ ﺍﺯ ﻗـﺮﺍﺭﺩﺍﺩﻥ ﻣﻴﺰﺑــﺎﻥ ﺩﺭ ﺣﺎﻟــﺖ‬

‫‪ ) maintenance mode‬ﺑـﺮﺍﻱ ﻗـﺮﺍﺭﺩﺍﺩﻥ ﻣﻴﺰﺑـﺎﻥ ﺩﺭ ﺣﺎﻟـﺖ ‪ ،maintenance mode‬ﺑـﺮﺭﻭﻱ ﻣﻴﺰﺑـﺎﻥ‬

‫ﻣﻮﺭﺩﻧﻈﺮ ﺭﺍﺳﺖ ﻛﻠﻴﻚ ﻛﺮﺩﻩ ‪ Enter maintenance made‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻣﻲﻛﻨﻴﻢ‪.‬‬

‫‪ 5-6‬ﻓﻌﺎﻝﺳﺎﺯﻱ ﻭﻳﮋﮔﻲ ‪ DRS‬ﺩﺭ ﻛﻼﺳﺘﺮ‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻗﺒﻼ ﻧﻴﺰ ﮔﻔﺘﻪ ﺷﺪ ‪ DRS‬ﻳﺎ ﺯﻣﺎﻧﺒﻨﺪﻱ ﻣﻨﺎﺑﻊ ﺗﻮﺯﻳﻊ ﺷﺪ‪ ،‬ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﻓﺮﺍﻫﻢ ﻣﻲﻛﻨﺪ ﺗﺎ ﺑـﺎﺭ‬

‫ﭘﺮﺩﺍﺯﺷﻲ ﻭ ﺣﺎﻓﻈﻪ ﺍﻱ ﺑﻴﻦ ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻋﻀﻮ ﻳﻚ ﻛﻼﺳﺘﺮ ﺗﻮﺯﻳﻊ ﺷﻮﺩ ﻭﺍﺿﺢ ﺍﺳﺖ ﻛـﻪ ﺑـﺮﺍﻱ ﺍﺳـﺘﻔﺎﺩﻩ ﺍﺯ‬

‫ﺍﻳﻦ ﻗﺎﺑﻠﻴﺖ ﻣﻲﺑﺎﻳﺴﺖ ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺑﺮﺭﻭﻱ ﺫﺧﻴـﺮﻩﺳـﺎﺯﻫـﺎﻱ ‪ share‬ﺷـﺪﻩ ) ﺍﺯ ﺟﻤﻠـﻪ ‪، SAN‬‬

‫‪ (NAS‬ﻗﺮﺍﺭﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪ .‬ﺑﺮﺍﻱ ﻓﻌﺎﻝ ﺳﺎﺯﻱ ‪ DRS‬ﺑﺮﺭﺭﻭﻱ ﻛﻼﺳﺘﺮ ﻣﻮﺭﺩ ﻧﻈـﺮ ﺭﺍﺳـﺖ ﻛﻠﻴـﻚ ﻛـﺮﺩﻩ ‪edit‬‬

‫‪ setting‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻣﻲﻛﻨﻴﻢ‪.‬‬

‫ﺩﺭ ﺻﻔﺤﻪ ﺑﺎﺯ ﺷﺪﻩ‪ ،‬ﺗﻴﻚ ﮔﺰﻳﻨﻪ ‪ turn on vSphere DRS‬ﺭﺍ ﺑﺰﻧﻴﺪ ‪.‬‬

‫ﺩﺭ ﺳﻤﺖ ﭼﭗ ﺻﻔﺤﻪ ﺗﺤﺖ ﺷﺎﺧﻪ ‪ vSphere DRS‬ﻣﻲﺗﻮﺍﻧﻴﺪ ﻭﻳﮋﮔﻲﻫﺎﻱ ﻣﺨﺘﻠﻒ ﻣﺮﺑـﻮﻁ ﺑـﻪ ‪ DRS‬ﺭﺍ‬

‫ﺑﺎ ﻛﻠﻴﻚ ﺑﺮﺭﻭﻱ ﻭﻳﮋﮔﻲ ﻣﻮﺭﺩ ﻧﻈﺮ ﺗﻨﻈﻴﻢ ﻛﻨﻴﺪ ‪.‬‬

‫‪102‬‬
 ‫ﺩﺭ ﺍﺩﺍﻣﻪ ﻫﺮ ﻳﻚ ﺍﺯ ﺍﻳﻦ ﻭﻳﺰﮔﻲ ﻫﺎﺭﺍ ﺗﻮﺿﻴﺢ ﺧﻮﺍﻫﻴﻢ ﺩﺍﺩ‪.‬‬

‫‪Automation level 1-5-6‬‬

‫ﺑﺮﺍﻱ ﺗﻌﻴﻴﻦ ﺳﻄﺢ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﺍﺯ ﻫﻤﻴﻦ ﺻﻔﺤﻪ ) ﺻﻔﺤﻪ ‪ (setting‬ﺍﺯ ﺳﻤﺖ ﭼﭗ ﺻﻔﺤﻪ ﺑﺮﺭﻭﻱ ‪vSphere‬‬

‫‪ DRS‬ﻛﻠﻴﻚ ﻛﻨﻴﺪ ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺷﻜﻞ ‪ 6-4‬ﻣﺸﺎﻫﺪﻩ ﻣﻲﻛﻨﻴﺪ‪ ،‬ﺳﻪ ﺳـﻄﺢ ﺍﺯ ﺍﺗﻮﻣﺎﺳـﻴﻮﻥ ﺩﺭ ﺩﺳـﺘﺮﺱ‬

‫ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪.‬‬

‫ﺷﻜﻞ ‪ . 4 6‬ﺗﻌﻴﻴﻦ ﺳﻄﺢ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﺩﺭ ‪DRS‬‬

‫‪: Manual‬‬

‫‪103‬‬
‫ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ﻫﻨﮕﺎﻡ ﺭﻭﺷﻦ ﺷﺪﻥ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺍﺯ ﻛﺎﺭﺑﺮ ﺩﺭ ﻣﻮﺭﺩ ﻣﺤﻞ ﺍﺟﺮﺍﻱ ﻣﺎﺷـﻴﻦ ﻣﺠـﺎﺯﻱ ﺳـﻮﺍﻝ‬

‫ﻣﻲ ﺷﻮﺩ‪ ) .‬ﻳﻌﻨﻲ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺑﺮﺭﻭﻱ ﻛﺪﺍﻡ ﺳﺮﻭﺭ ‪ ESXi‬ﺍﺟﺮﺍ ﺷﻮﺩ ( ﺷﻜﻞ ‪5-6‬‬

‫ﺷﻜﻞ ‪ . 5 6‬ﺭﻭﺷﻦ ﻛﺮﺩﻥ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺩﺭ ﺣﺎﻟﺖ ‪manual DRS‬‬

‫‪Partially Automated‬‬
‫ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ﻫﻨﮕﺎﻡ ﺭﻭﺷﻦ ﺷﺪﻥ‪ ،‬ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺑﻪ ﻃﻮﺭ ﺍﺗﻮﻣﺎﺗﻴﻚ ﺩﺭ ﻣﻨﺎﺳﺐ ﺗﺮﻳﻦ ﺳﺮﻭﺭ ﺍﺟﺮﺍ ﻣﻲﺷﻮ؛‬

‫ﻭﻟﻲ ﺩﺭ ﺻﻮﺭﺗﻲ ﻛﻪ ﺑﺮﺍﺛﺮ ﺑﺎﻻﺭﻓﺘﻦ ﺑﺎﺭ ﭘﺮﺩﺍﺯﺵ ﻳﻚ ﺳﺮﻭﺭ‪ ،‬ﻧﻴﺎﺯ ﺑﻪ ﺍﻧﺘﻘﺎﻝ ﻳﻚ ﻣﺎﺷـﻴﻦ ﻣﺠـﺎﺯﻱ ﺑـﻪ ﺳـﺮﻭﺭ‬

‫ﺩﻳﮕﺮ ﻭﺟﻮﺩ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ ﺳﻴﺴﺘﻢ ‪ DRS‬ﺑﺎ ﭘﻴﻐﺎﻣﻲ ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺭﺍ ﺑﻪ ﻛﺎﺭﺑﺮ ﺍﻃـﻼﻉ ﻣـﻲ ﺩﻫـﺪ ﻭ ﺍﺯ ﻛـﺎﺭﺑﺮ)‬

‫ﻣﺪﻳﺮ ( ﺩﺭﺑﺎﺭﻩ ﺍﻧﺘﻘﺎﻝ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺳﻮﺍﻝ ﻛﺮﺩﻩ ﻭ ﺑﻬﺘﺮﻳﻦ ﺳـﺮﻭﺭ ﺭﺍ ﺑـﺮﺍﻱ ﺍﻧﺠـﺎﻡ ﺍﻳـﻦ ﺍﻧﺘﻘـﺎﻝ ﭘﻴﺸـﻨﻬﺎﺩ‬

‫ﺧﻮﺍﻫﺪ ﻛﺮﺩ ‪ .‬ﺗﻔﺎﻭﺕ ﺍﻳﻦ ﺣﺎﻟﺖ ﺑﺎ ﺣﺎﻟﺖ ﻗﺒﻞ ﻓﻘﻂ ﺩﺭ ﻫﻨﮕﺎﻡ ﺭﻭﺷﻦ ﺷـﺪﻥ ﻣﺎﺷـﻴﻦ ﻣﺠـﺎﺯﻱ ﺍﺳـﺖ ﻛـﻪ ‪،‬‬

‫ﺍﻧﺘﺨﺎﺏ ﺳﺮﻭﺭ‪ ،‬ﺩﺭ ﺣﺎﻟﺖ ﺍﻭﻝ ﺑﺼﻮﺭﺕ ﺩﺳﺘﻲ ﻭ ﺩﺭ ﺣﺎﻟﺖ ﺩﻭﻡ ﺑﺼﻮﺭﺕ ﺍﺗﻮﻣﺎﺗﻴﻚ ﺍﻧﺠﺎﻡ ﺧﻮﺍﻫﺪ ﺷﺪ‪.‬‬

‫‪Fully Automated‬‬
‫ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ﻛﻠﻴﻪ ﻣﺮﺍﺣﻞ ﺗﻨﻈﻴﻢ ﺑﺎﺭ ﭘﺮﺩﺍﺯﺷﻲ ﭼﻪ ﻫﻨﮕﺎﻡ ﺭﻭﺷﻦ ﺷﺪﻩ ﻣﺎﺷـﻴﻦ ﻣﺠـﺎﺯﻱ ﭼـﻪ ﺩﺭ ﺣـﻴﻦ‬

‫ﺍﺟﺮﺍ‪ ،‬ﻛﺎﻣﻼ ﺑﺼﻮﺭﺕ ﺧﻮﺩﻛﺎﺭ ﺍﻧﺠﺎﻡ ﺧﻮﺍﻫﺪ ﺷﺪ ‪.‬‬

‫ﺩﺭ ﻫﻤﻴﻦ ﻗﺴﻤﺖ ‪ ،‬ﭘﺎﺋﻴﻦ ﺻﻔﺤﻪ ﻳﻚ ﻧﻮﺍﺭ ﻟﻐﺰﺍﻥ ﺑﻪ ﻧﺎﻡ ‪ Migration threshold‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ﺑﻪ ﻛﻤـﻚ‬

‫ﺁﻥ ﻣﻲﺗﻮﺍﻥ ﺳﻄﺢ ﺁﺳﺘﺎﻧﻪﺍﻱ ﺑﺮﺍﻱ ﺍﻧﺘﻘﺎﻝ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺑﻪ ﺳﺮﻭﺭ ﺩﻳﮕﺮ ﺭﺍ ﺗﻌﻴﻴﻦ ﻛـﺮﺩ‪ .‬ﻫـﺮ ﭼـﻪ ﺑﺴـﻤﺖ‬

‫‪ aggressire‬ﻧﺰﺩﻳﻜﺘﺮ ﺑﺎﺷﺪ ﺗﻌﺪﺍﺩ ﺍﻧﺘﻘﺎﻝﻫﺎ ﺑﻴﺸﺘﺮ ﺧﻮﺍﻫﺪ ﺑﻮﺩ ‪.‬‬

‫ﺗﻨﻈﻴﻤﺎﺕ ﮔﻔﺘﻪ ﺷﺪﻩ ﺩﺭ ﺑﺎﻻ ﺑﺮﺭﻭﻱ ﻛﻞ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻛﻼﺳﺘﺮ ﺍﻋﻤﺎﻝ ﻣﻲﺷﻮﺩ ‪.‬‬

‫‪104‬‬
‫ﺍﻟﺒﺘﻪ ﻣﻲ ﺗﻮﺍﻥ ﺑﻌﻀﻲ ﺍﺯ ﻣﺎﺷﻴﻦﻫﺎ ﺭﺍ ﻣﺴﺘﺜﻨﻲ ﻛﺮﺩ ﻭ ﺑﺮﺍﻱ ﺍﻳﻦ ﻛـﺎﺭ ﺑـﺮﺭﻭﻱ ‪Virtual machine option‬‬

‫ﻛﻠﻴﻚ ﻛﻨﻴﺪ ‪ .‬ﻣﺸﺎﺑﻪ ﺷﻜﻞ ‪ ، 6-6‬ﺗﻤﺎﻡ ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻋﻀﻮ ﻛﻼﺳﺘﺮ ﺭﺍ ﻣﺸـﺎﻫﺪﻩ ﺧﻮﺍﻫﻴـﺪ ﻛـﺮﺩ ﺑـﺎ ﻛﻠﻴـﻚ‬

‫ﺑﺮﺭﺭﻭﻱ ﻫﺮ ﻣﺎﺷﻴﻦ ﻣﻲﺗﻮﺍﻥ ﺳﻄﺤﻲ ﺍﺯ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﺭﺍ ﺑﻪ ﻫﺮ ﻛﺪﺍﻡ ﺍﺧﺘﺼـﺎﺹ ﺩﺍﺩ‪ .‬ﺍﻟﺒﺘـﻪ ﺑﺎﻳـﺪ ﻗﺒـﻞ ﺍﺯ ﺁﻥ‬

‫ﺗﻴﻚ ﮔﺰﻳﻨﻪ ‪ Enable individual virtual machine automation‬ﺭﺍ ﻓﻌﺎﻝ ﻛﻨﻴﺪ‪.‬‬

‫ﺷﻜﻞ ‪ . 6 6‬ﺍﻧﺘﺼﺎﺏ ﺳﻄﺢ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﺩﺭ‪ DRS‬ﺑﻪ ﻣﺎﺷﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ‬

‫‪ 2-5-6‬ﮔﺮﻭﻩ ﺑﻨﺪﻱ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻭ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ESXi‬‬

‫ﺍﺯ ﺩﻳﮕﺮ ﻗﺎﺑﻠﻴﺖ ﻫﺎﻱ ﺩﻳﮕﺮ ‪ DRS‬ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﻣﻲﺗﻮﺍﻥ ﻣﺎﺷـﻴﻦﻫـﺎﻱ ﻣﺠـﺎﺯﻱ ﻭ ﻣﻴﺰﺑـﺎﻥﻫـﺎﻱ ‪ ESXi‬ﺭﺍ‬

‫ﺩﺳﺘﻪﺑﻨﺪﻱ ﻛﺮﺩﻩ ﺗﺎ ﺑﺘﻮﺍﻥ ﺑﺮﺭﻭﻱ ﺁﻧﻬﺎ ﺳﻴﺎﺳﺖ ﻫﺎﻱ ﺧﺎﺻﻲ ﺭﺍ ﺍﻋﻤﺎﻝ ﻛﺮﺩ‪ .‬ﺑﺮﺍﻱ ﺍﻳﺠﺎﺩ ﻳﻚ ﮔـﺮﻭﻩ ﻣﺎﺷـﻴﻦ‬

‫‪105‬‬
‫ﻣﺠﺎﺯﻱ‪ :‬ﺩﺭ ﺻﻔﺤﻪ ‪ Setting‬ﻣﺮﺑﻮﻁ ﺑﻪ ﻛﻼﺳﺘﺮ ﭘﺲ ﺍﺯ ﻓﻌﺎﻝ ﻛﺮﺩﻥ ‪ ) DRS‬ﺑﺎ ﺍﻧﺘﺨـﺎﺏ ﮔﺰﻳﻨـﻪ ‪Turn on‬‬

‫‪ (vSphere DRS‬ﺑﺮﺭﻭﻱ ‪ DRS group manager‬ﺍﺯ ﺳﻤﺖ ﭼﭗ ﺻﻔﺤﻪ ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪.‬‬

‫‪ 2‬ﺑﺮﺭﻭﻱ ﺻﻔﺤﻪ ‪ Add‬ﺩﺭ ﻗﺴﻤﺖ ‪ Virtual machine DRS group‬ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪.‬‬

‫‪ 3‬ﺩﺭ ﺻﻔﺤﻪ ﺟﺪﻳﺪ ﺑﺎﺯ ﺷﺪﻩ ﺩﺭ ﻗﺴﻤﺖ ‪ name‬ﻧﺎﻣﻲ ﺑﺮﺍﻱ ﮔﺮﻭﻩ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ ‪ .‬ﺷﻜﻞ ‪7-6‬‬

‫ﺷﻜﻞ ‪ . 7 6‬ﮔﺮﻭﻩ ﺑﻨﺪﻱ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺩﺭ ‪DRS‬‬

‫‪ 4‬ﺑﺮﺍﻱ ﺍﻓﺰﻭﺩﻥ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺑﻪ ﮔﺮﻭﻩ ﺍﺯ ﺳﻤﺖ ﭼﭗ ﺻﻔﺤﻪ ﺑﺮ ﺭﻭﻱ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠـﺎﺯﻱ ﻛﻠﻴـﻚ‬

‫ﻛﻨﻴﺪ‪.‬‬

‫‪ 5‬ﭘﺲ ﺍﺯ ﺍﻧﺘﺨﺎﺏ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺑﺮﺭﻭﻱ ‪ ok‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‪.‬‬

‫ﺑﺮﺍﻱ ﺳﺎﺧﺖ ﮔﺮﻭﻩ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ ESXi‬ﭘﺲ ﺍﺯ ﻛﻠﻴﻚ ﺑﺮ ﺭﻭﻱ ‪ Add‬ﺩﺭ ﻗﺴﻤﺖ ‪ ، Hostprs group‬ﻣﺎﻧﻨﺪ‬

‫ﻣﺮﺍﺣﻞ ﺍﻳﺠﺎﺩ ﮔﺮﻭﻩ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺭﺍ ﺍﻧﺠﺎﻡ ﺩﻫﻴﺪ‪.‬‬

‫‪106‬‬
 ‫‪ 3-5-6‬ﺍﻋﻤﺎﻝ ﺳﻴﺎﺳﺘﻬﺎﻱ ‪ DRS‬ﺩﺭ ﺭﺍﺑﻄﻪ ﺑﺎ ﺍﺟﺮﺍﻱ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺑﺮ‬

‫ﺭﻭﻱ ﺳﺮﻭﺭﻫﺎﻱ ‪ESXi‬‬

‫ﺑﻪ ﻛﻤﻚ ‪ DRS‬ﻣﻲﺗﻮﺍﻥ ﺳﻴﺎﺳﺖﻫﺎﻳﻲ ﺑﺮ ﺭﻭﻱ ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺍﻋﻤﺎﻝ ﻛﺮﺩ ﺗﺎ ﻫﺮ ﻳﻚ ﻓﻘﻂ ﺑﺘﻮﺍﻧﻨﺪ ﺑﺮ‬

‫ﺭﻭﻱ ﺳﺮﻭﺭﻫﺎﻳﻲ ﺧﺎﺻﻲ ﺍﺟﺮﺍ ﺷﻮﻧﺪ؛ ﻭ ﺍﻋﻤﺎﻝ ﺍﺯ ﺍﻳﻦ ﺩﺳﺖ‪ .‬ﺑﺪﻳﻦ ﻣﻨﻈﻮﺭ ﻣﻲﺗﻮﺍﻧﻴﺪ ﺭﻭﻝﻫﺎﻳﻲ ﺍﺿﺎﻓﻪ ﻛﻨﻴﺪ‪.‬‬

‫ﺑﺮﺍﻱ ﺍﺿﺎﻓﻪ ﻛﺮﺩﻥ ﺭﻭﻝ ﺍﺯ ﺻﻔﺤﻪ ‪ Setting‬ﻣﺮﺑﻮﻁ ﺑﻪ ﻛﻼﺳﺘﺮ‪ ،‬ﺑﺮ ﺭﻭﻱ ‪ Add‬ﻛﻠﻴﻚ ﻛﻨﻴﺪ‪.‬‬

‫ﺳﻪ ﻧﻮﻉ ﺳﻴﺎﺳﺖ ﻣﻲﺗﻮﺍﻥ ﺑﺮ ﺭﻭﻱ ﻣﺎﺷﻴﻦﻫﺎ ﻭ ﺳﺮﻭﺭﻫﺎ ﺍﻋﻤﺎﻝ ﻛﺮﺩ‪.‬‬

‫‪Separate virtual machines‬‬

‫ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻋﻀﻮ ﺍﻳﻦ ﺭﻭﻝ ﻫﺮ ﻳﻚ ﺑﺮ ﺭﻭﻱ ﺳﺮﻭﺭﻫﺎﻱ ﻓﻴﺰﻳﻜﻲ ﺟﺪﺍﮔﺎﻧﻪ ﺍﺟﺮﺍ ﺧﻮﺍﻫﻨﺪ ﺷﺪ‪ .‬ﺍﻳﻦ ﺣﺎﻟﺖ‬

‫ﺯﻣﺎﻥﻫﺎﻳﻲ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲﺷﻮﻧﺪ ﻛﻪ ﺑﺨﻮﺍﻫﻴﻢ ﻣﺜﻼ ﺩﻭ ﺳﺮﻭﺭ ﻛﻪ ﻳﻚ ﻛﺎﺭ ﺭﺍ ﺍﻧﺠﺎﻡ ﻣﻲﺩﻫﻨﺪ‪ ،‬ﺑﺮ ﺭﻭﻱ ﺩﻭ ﻣﻴﺰﺑﺎﻥ‬

‫ﻓﻴﺰﻳﻜﻲ ﺍﺟﺮﺍ ﺷﻮﻧﺪ ﺗﺎ ﺩﺭ ﺻﻮﺭﺗﻲ ﻛﻪ ﻳﻜﻲ ﺍﺯ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ ESXi‬ﺧﺮﺍﺏ ﻭ ﻳﺎ ﺧﺎﻣﻮﺵ ﺷﺪ ﺩﻳﮕﺮﻱ ﺩﺭ ﺩﺳﺘﺮﺱ‬

‫ﺑﺎﺷﺪ‪.‬‬

‫ﺍﻳﻦ ﺣﺎﻟﺖ ﺭﺍ ‪ Anti-Affinite Rules‬ﻣﻲﻧﺎﻣﻨﺪ‪.‬‬

‫‪Keep virtual machin Togcther‬‬

‫ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻋﻀﻮ ﺍﻳﻦ ﺭﻭﻝ‪ ،‬ﻫﻤﻮﺍﺭﻩ ﺑﺮ ﺭﻭﻱ ﻳﻚ ﻣﻴﺰﺑﺎﻥ ‪ ESXi‬ﺍﺟﺮﺍ ﺧﻮﺍﻫﻨﺪ ﺷﺪ‪ .‬ﺍﻳﻦ ﺣﺎﻟﺖ ﻧﻴﺰ‬

‫ﺯﻣﺎﻧﻲ ﻣﻔﻴﺪ ﺧﻮﺍﻫﺪ ﺑﻮﺩ ﻛﻪ ﺩﻭ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺍﺭﺗﺒﺎﻁ ﺑﺎﻻﻳﻲ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ ﻣﺜﻼ ﻳﻚ ﺳﺮﻭﺭ ﻭ ﺳﺮﻭﺭ ﭘﺎﻳﮕﺎﻩ‬

‫ﺩﺍﺩﻩ ﻣﺮﺑﻮﻁ ﺑﻪ ﺁﻥ‪ .‬ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ﺗﺮﺍﻓﻴﻚ ﺳﻮﺋﻴﭻﻫﺎﻱ ﻓﻴﺰﻳﻜﻲ ﺑﺴﻴﺎﺭ ﻛﻢ ﺧﻮﺍﻫﺪ ﺷﺪ؛ ﭼﺮﺍ ﻛﻪ ﺩﻭ ﻳﺎ ﭼﻨﺪ‬

‫ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﭘﺮ ﺗﺮﺍﻓﻴﻚ ﺑﺮ ﺭﻭﻱ ﻳﻚ ﻣﻴﺰﺑﺎﻥ ﻫﺴﺘﻨﺪ‪.‬‬

‫‪Virtual machines to hostes‬‬

‫ﺍﻳﻦ ﺳﻴﺎﺳﺖ ﺷﺮﺍﻳﻄﻲ ﺭﺍ ﺍﻳﺠﺎﺩ ﻣﻲﻛﻨﺪ ﺗﺎ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺑﺮ ﺭﻭﻱ ﻣﻴﺰﺑﺎﻧﻬﺎ ﺧﺎﺻﻲ ﺍﺟﺮﺍ ﺷﻮﻧﺪ ﻭ ﻳﺎ ﺑﺮ ﺭﻭﻱ‬

‫ﺑﻌﻀﻲ ﺍﺯ ﻣﻴﺰﺑﺎﻥﻫﺎ ﺍﺟﺮﺍ ﻧﺸﻮﻧﺪ‪ .‬ﺗﻮﺟﻪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﺪ ﻛﻪ ﺑﺮﺍﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺍﻳﻦ ﻭﻳﮋﮔﻲ ﻣﻲﺑﺎﻳﺴﺖ ﺍﺯ ﻗﺒﻞ‬

‫ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻭ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ﻣﻮﺭﺩ ﻧﻈﺮ ﺧﻮﺩ ﺭﺍ ﺩﺭ ﮔﺮﻭﻩﻫﺎﻳﻲ ﻗﺮﺍﺭ ﺩﺍﺩﻩ ﺑﺎﺷﻴﺪ‪ .‬ﺩﺭ ﺷﻜﻞ ‪8-6‬‬

‫ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻋﻀﻮ ﮔﺮﻭﻩ ‪ VM-1‬ﻧﻤﻲﺗﻮﺍﻧﻨﺪ ﺑﺮ ﺭﻭﻱ ﻣﻴﺰﺑﺎﻧﻬﺎﻱ ‪ ESXi‬ﮔﺮﻭﻩ ‪ H-4‬ﺍﺟﺮﺍ ﺷﻮﻧﺪ‪.‬‬

‫‪107‬‬
 ‫ﺷﻜﻞ ‪ . 8 6‬ﺍﻋﻤﺎﻝ ﺭﻭﻝ ﺑﺮ ﺭﻭﻱ ﮔﺮﻭﻩﻫﺎﻱ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ ﻭ ﻣﻴﺰﺑﺎﻥﻫﺎ‬

‫‪ 6-6‬ﻣﺪﻳﺮﻳﺖ ﻭ ﺗﻘﺴﻴﻢ ﺑﻨﺪﻱ ﻣﻨﺎﺑﻊ ﺑﺎ ‪Resource Pools‬‬

‫‪ vSphere‬ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﻓﺮﺍﻫﻢ ﻛﺮﺩﻩ ﺗﺎ ﺑﺘﻮﺍﻥ ﻣﻨﺎﺑﻊ ﭘﺮﺩﺍﺯﺷﻲ ﻭ ﺣﺎﻓﻈﻪ ﺍﻱ ﻳﻚ ﻛﻼﺳﺘﺮ ﺭﺍ ﺑﻪ ﻗﺴﻤﺖﻫﺎﻱ‬

‫ﻣﺨﺘﻠﻒ ﺗﻘﺴﻴﻢ ﺑﻨﺪﻱ ﻛﺮﺩﻩ ﺗﺎ ﺑﺘﻮﺍﻥ ﻣﺪﻳﺮﻳﺖ ﺑﻬﺘﺮﻱ ﺑﺮ ﺭﻭﻱ ﻣﻨﺎﺑﻊ ﺩﺍﺷﺖ‪ .‬ﺗﻮﺟﻪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﺪ ﺑﺮﺍﻱ ﺳﺎﺧﺖ‬

‫ﻳﻚ ‪ Resource pool‬ﻣﻲ ﺑﺎﻳﺴﺖ ‪ DRS‬ﺭﺍ ﺩﺭ ﻛﻼﺳﺘﺮﻱ ﻛﻪ ﻗﺼﺪ ﺩﺍﺭﻳﺪ ‪ Resource pools‬ﺭﺍ ﺩﺭ ﺁﻥ ﺑﺴﺎﺯﻳﺪ‬

‫ﻓﻌﺎﻝ ﻧﻤﺎﺋﻴﺪ‪.‬‬
‫ﺳﺎﺧﺖ ‪ Resource pools‬ﺑﺮ ﺭﻭﻱ ﻛﻼﺳﺘﺮ ﻣﻮﺭﺩ ﻧﻈﺮ ﺭﺍﺳﺖ ﻛﻠﻴﻚ ﻛﺮﺩﻩ ‪ New Resource pool‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ‬

‫ﻛﻨﻴﺪ‪.‬‬

‫ﺗﻨﻈﻴﻤﺎﺕ ﻣﺮﺑﻮﻁ ﺑﻪ ‪ Resource pool‬ﺷﺒﻴﻪ ﺑﻪ ﺗﻨﻈﻴﻢ ﻭ ﺗﺨﺼﻴﺺ ﻣﻨﺎﺑﻊ ﺩﺭ ﻣﺎﺷﻴﻦ ﻫﺎﻱ ﻣﺠﺎﺯﻱ ﺍﺳﺖ ﻛﻪ‬

‫ﺩﺭ ﻗﺴﻤﺖ ‪ 3-6‬ﮔﻔﺘﻪ ﺷﺪ‪.‬‬

‫‪ 7-6‬ﺗﻜﺜﻴﺮ ﻣﺎﺷﻴﻦﻫﺎﻱ ﻣﺠﺎﺯﻱ‬

‫ﻓﺮﺍﻳﻨﺪ ﺳﺎﺧﺖ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻭ ﻧﺼﺐ ﺳﻴﺴﺘﻢﻋﺎﻣﻞ ﻭ ﺑﺮﻧﺎﻣﻪﻫﺎﻱ ﺿﺮﻭﺭﻱ ﺑﺮ ﺭﻭﻱ ﺁﻥ ﻳﻚ ﻓﺮﺁﻳﻨﺪ ﺯﻣﺎﻧﺒﺮ‬

‫ﺍﺳﺖ ﻛﻪ ﺍﮔﺮ ﺩﺭ ﺩﻳﺘﺎﺳﻨﺘﺮﻫﺎﻱ ﺑﺰﺭگ ﺑﻪ ﺍﻳﻦ ﺭﻭﺵ ﻋﻤﻞ ﺷﻮﺩ‪،‬ﻛﺎﺭ ﻣﺪﻳﺮﻳﺖ ﻏﻴﺮ ﻣﻤﻜﻦ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪ .‬ﻳﻜﻲ ﺍﺯ‬

‫ﺍﻣﻜﺎﻧﺎﺗﻲ ﻛﻪ ﺩﺭ ‪ vSphere‬ﺑﺮﺍﻱ ﺣﻞ ﺍﻳﻦ ﻣﺴﺌﻠﻪ ﻗﺮﺍﺭﺩﺍﺩﻩ ﺷﺪﻩ‪ ،‬ﻛﭙﻲ ﻛﺮﺩﻥ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺍﺳﺖ‪ .‬ﺑﺮﺍﻱ‬

‫ﺳﺎﺧﺖ ﻳﻚ ﻧﻤﻮﻧﻪ ﻣﺸﺎﺑﻪ ﺍﺯ ﻳﻚ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻓﺮﺍﻳﻨﺪ ﺯﻳﺮ ﺭﺍ ﺍﻧﺠﺎﻡ ﺩﻫﻴﺪ‪:‬‬

‫‪.1‬ﺑﺮ ﺭﻭﻱ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻣﻮﺭﺩ ﻧﻈﺮ ﺭﺍﺳﺖ ﻛﻠﻴﻚ ﻛﺮﺩﻩ ‪ Clone‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪.‬‬

‫‪ .2‬ﺩﺭ ﻛﺎﺩﺭ ‪ ، Name‬ﻧﺎﻣﻲ ﺑﺮﺍﻱ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﻛﭙﻲ ﺷﺪﻩ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ .‬ﭘﺲ ﺍﺯ ﺍﻧﺘﺨﺎﺏ ﻣﺤﻞ ﻣﺎﺷﻴﻦ‬

‫ﻣﺠﺎﺯﻱ ﺟﺪﻳﺪ ﺩﺭ ﺩﻳﺘﺎﺳﻨﺘﺮ‪ ،‬ﺑﺮ ﺭﻭﻱ ‪ Next‬ﻛﻠﻴﻚ ﻧﻤﺎﺋﻴﺪ‬

‫‪ .3‬ﺩﺭ ﺍﻳﻦ ﻗﺴﻤﺖ ﻧﻴﺰ ﻛﻼﺳﺘﺮ ﻭ ﻳﺎ ﻣﻴﺰﺑﺎﻥ ‪ ESXi‬ﺑﺮﺍﻱ ﺍﺟﺮﺍﻱ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺟﺪﻳﺪ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ؛‪ Next‬ﺭﺍ‬

‫ﻛﻠﻴﻠﻚ ﻛﻨﻴﺪ‪.‬‬

‫‪ .4‬ﺩﺭ ﻣﺮﺣﻠﻪ ﻗﺒﻞ ﺍﮔﺮ ﻛﻼﺳﺘﺮ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ﺑﺎﺷﻴﺪ ﺩﺭ ﺍﻳﻦ ﻗﺴﻤﺖ ﻣﻲﺑﺎﻳﺴﺖ ﻣﻴﺰﺑﺎﻥ ‪ ESXi‬ﻣﻮﺭﺩ ﻧﻈﺮ ﺑﺮﺍﻱ‬

‫ﺍﺟﺮﺍﻱ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺟﺪﻳﺪ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ؛ ﺩﺭ ﻏﻴﺮ ﺍﻳﻨﺼﻮﺭﺕ ﺍﻳﻦ ﻣﺮﺣﻠﻪ ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﻧﺨﻮﺍﻫﻴﺪ ﻛﺮﺩ‪ .‬ﺑﺮﺍﻱ‬

‫ﺍﺩﺍﻣﻪ ‪ Next‬ﺭﺍ ﺑﺰﻧﻴﺪ‪.‬‬

‫‪ .5‬ﺩﻭﺑﺎﺭﻩ ﺍﮔﺮ ﺩﺭ ﻣﺮﺣﻠﻪﻱ ‪ 3‬ﻛﻼﺳﺘﺮ ﺭﺍ ﺑﺮﺍﻱ ﺍﺟﺮﺍﻱ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺟﺪﻳﺪ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ﺑﺎﺷﻴﺪ ﻭ ﺩﺭ ﺁﻥ‬

‫ﻛﻼﺳﺘﺮ ‪ Resource pools‬ﺳﺎﺧﺘﻪ ﺷﺪﻩ ﺑﺎﺷﺪ ﺩﺭ ﺍﻳﻦ ﻣﺮﺣﻠﻪ ﻣﻲﺗﻮﺍﻥ ‪ Resource pool‬ﻣﻮﺭﺩ ﻧﻈﺮ ﺧﻮﺩ ﺭﺍ‬

‫ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ .‬ﺑﺎ ﻛﻠﻴﻚ ﺑﺮ ﺭﻭﻱ ‪ Next‬ﺑﻪ ﻣﺮﺣﻠﻪ ﺑﻌﺪ ﺑﺮﻭﻳﺪ‪.‬‬

‫‪109‬‬
‫‪ .6‬ﺩﺭ ﺍﻳﻦ ﻗﺴﻤﺖ ﻣﻲﺗﻮﺍﻥ ﻣﺤﻞ ﺫﺧﻴﺮﻩﺳﺎﺯﻱ ﻓﺎﻳﻞﻫﺎﻱ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺭﺍ ﺍﺯ ﺑﻴﻦ ﺫﺧﻴﺮﻩﺳﺎﺯﻫﺎﻱ ﻣﻮﺟﻮﺩ‪،‬‬

‫ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ .‬ﺿﻤﻨﺎً ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﺍﺯ ﻣﻨﻮﻱ ﻛﺮﻛﺮﻩﺍﻱ ﺑﺎﻻﻱ ﺻﻔﺤﻪ ﻧﺤﻮﻩ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ﺭﺍ ﻧﻴﺰ ﺗﻐﻴﻴﺮ ﺩﻫﻴﺪ‪.‬‬

‫‪ .7‬ﭘﺲ ﺍﺯ ﺩﻭﺑﺎﺭ ﻛﻠﻴﻚ ﺑﺮ ﺭﻭﻱ ‪ Next‬ﻭ ﺑﻌﺪ ﺍﺯ ﻣﺸﺎﻫﺪﻩ ﺧﻼﺻﻪﺍﻱ ﺍﺯ ﻣﺸﺨﺼﺎﺕ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺟﺪﻳﺪ ﺑﺎ‬

‫ﺯﺩﻥ ‪ ،Finish‬ﻓﺮﺍﻳﻨﺪ ﻛﭙﻲ ﻣﺎﺷﻴﻦ ﻣﺠﺎﺯﻱ ﺍﺟﺮﺍ ﺧﻮﺍﻫﺪ ﺷﺪ‪.‬‬

‫ﻭ ﺍﻳﻦ ﻓﺼﻞ ﺍﺩﺍﻣﻪ ﺩﺍﺭﺩ ‪. . . .‬‬

‫‪110‬‬
 ‫ﻣﻨﺎﺑﻊ‬
- Dan Kusnetzky , Virtualization: A Manager’s Guide , Oreilly ,2011
- Mitch Tulloch , Undrestanding Microsoft Virtualization Solution , Microsoft Press ,
2011
- Scott Lowe , mastering vmware vsphere 5 ,Sybex ,2011
- Ryan Troy and Matthew Helmke , VMware Cookbook ,Orilly ,2010

‫ﺩﺍﻧﺸﮕﺎﻩ ﺻﻨﻌﺘﻲ ﺟﻨﺪﻱﺷﺎﭘﻮﺭ‬، ‫ ﭘﺎﻳﺎﻥﻧﺎﻣﻪ ﻛﺎﺭﺷﻨﺎﺳﻲ‬، ‫ ﺳﻴﺴﺘﻢﻫﺎﻱ ﭘﺮﺩﺍﺯﺵ ﺍﺑﺮﻱ‬، ‫ ﺭﺿﺎ ﻓﻼﻣﺮﺯﻱ‬-
1390 ، ‫ﺩﺯﻓﻮﻝ‬

111