DIY SAN Windows Server 2.Storage Spaces and i.SCSI target. Windows Server 2.There are exciting and totally new features like Storage Spaces that aggregate storage across drives and disk controllers.Another valuable file server feature is now built into Windows Server 2.SCSI target on the Windows Server, essentially turning the server into a SAN head.Provisioning a Windows Server 2.SAN. A new option for server based storage entered the market in April, 2.Microsoft made available for free public download a software package that transforms a standard Windows Server 2.R2 computer into a Windows Storage Server, aka an i.SCSI SAN provider.An i. SCSI target server and supporting features are now bundled with Windows Server 2.Figure A shows the File and i.SCSI Services selected in the Windows Server 2.Add Roles and Features Wizard.Figure AWindows Server 2.File and Storage Services installed via Server Manager.Preparing the i. SCSI target server.For production deployments, a dedicated i.Connect Windows 7 To Iscsi Target Software FreeSCSI network for storage traffic is usually indicated.In enterprise scenarios, prepare a network interface card NIC or NIC team to use for i.SCSI traffic alone.In demonstration and lab settings, as well as converged networks running at 1.GBPS or faster, you can use the same NIC used by the operating system for network traffic.Of course, the i.Dealing with iSCSI remains a challenge for some IT pros.Find out tips you forgot to remember when configuring the system.SCSI Target server should be provisioning with lots of local or direct attached storage to share out as SAN based disks to other computers on the i.SCSI network. With Windows Server 2.Storage Space, a pooled model for managing local and direct attached storage.Storage Spaces maintains the health of these drives and any redundancy selected.Create a Storage Pool, Virtual Hard Disk, and Volume.The scenario is presenting three 3 9.GB SATA hard disks over the network in a fault tolerant manner via i.SCSIWizard-1024x503.png' alt='Connect Windows 7 To Iscsi Target Software For Windows' title='Connect Windows 7 To Iscsi Target Software For Windows' />In my previous post, I mentioned that I use StarWind Softwares iSCSI SAN software to provide iSCSI LUNs for my home lab.In this post, Ill document the process.SCSI to a DPM server.The i. SCSI client initiator feature on the DPM server will view the storage as local or directly attached.DPM can use a volume in this storage for backup of other servers and applications.The business objective is to efficiently use storage that already exists on the network, without for example, growing a conventional SAN.Follow these steps to create a storage pool and a virtual disk to be used for i.SCSI storage. 1. In the Windows Server 2.Server Manager, navigate to File and Storage Services Volumes Storage Pools.Click Tasks New Storage Pool.This launches the Storage Pool Wizard.Name the storage pool and select the group of available raw disks also known as a primordial pool to use.Figure B shows the option to select and modify physical disk allocation.Unless you want to manually specify one or more hot spare disks, leave the disk allocation type set to Automatic.Figure BSelect physical disks to include in the storage pool.Proceed to create virtual disks after completing the Storage Pool Wizard.The New Virtual Disk Wizard will launch.Select the storage pool created in step 2 and name the volume.In this application, the volume is going to be presented to a System Center Data Protection Manager DPM server, so the name DPM i.SCSI Storage will be used.Select either Simple, Mirror, or Parity storage layout.Since this storage space in this environment includes three 3 or more hard disks, the parity type is a good choice.Next select either Thin or Static Thick provisioning for the volume.These settings are similar to Dynamic and Fixed virtual hard disks however this setting is at the aggregate volume level of the storage pool.For DPM, Static provisioning is highly recommended.Specify the size of the virtual disk.If using thin provisioning, the size can be greater than the free space in the storage pool.For this DPM backup volume application, the option to create the maximum size volume using all the disk space was selected.Figure C shows the confirm selections page, ready to create the virtual disk inside the storage pool.Click Create to continue.Figure CCreating a virtual disk inside the storage pool.Proceed to create a new volume after completing the New Virtual Disk Wizard.The New Volume Wizard will launch.Confirm the server, select the disk created in step 4, select a volume size, and assign a drive letter if any for the new volume.For the DPM backup volume, this demonstration is using all the available space and assigning the drive letter R.Name the volume and as shown in Figure D, optionally enable data deduplication.Windows Server 2.Confirm the new volume settings and create the volume.Figure DOptionally enable data duplication on the new volume.Create an i. SCSI Virtual Disk.Now that a volume is prepared in this demonstration, a 2.TB R drive on the storage server, you can create an i.SCSI virtual hard disk VHD on the volume and present it to i.SCSI clients. Follow these steps to create an i.SCSI virtual disk In the Windows Server 2.Server Manager, navigate to File and Storage Services i.SCSI. Click Tasks New i.SCSI Virtual Disk.This launches the New i.SCSI Virtual Disk Wizard.Select the volume created previously R drive in this demonstration, name the VHD, and select the VHD size, up to the maximum usable space on the volume.Tip This should be a bit smaller than the volume size to avoid low disk alerts.Select to create a New i.SCSI Target and provide a name.This name will be discovered by the i.SCSI initiator, and used for the connection.Add the initiator IDif the i.SCSI client is a Windows Server 2.IQN. An example IQN is iqn.Confirm the new i.SCSI virtual disk settings and create the disk.The i. SCSI target and virtual disk are ready to use for production or other purposes.With the i. SCSI Initiator applet on any networked i.SCSI client computer such as the DPM server this i.SCSI disk was prepared for you can connect to the new i.SCSI virtual disk and start using the storage.SCSI Errors in Windows Event Log Windows Server.So, I am seeing three distinct Windows Event Log error messages when performing any write operations from my Windows 2.R2 server via MSi.SCSI to a d. Robo B1.SAN. The volume mounts without issue and I can browse the contents with relative ease.The write operations seem to move along quite nicely I have a job running at night to sync the contents of this new volume with an existing volume and large amounts of data are getting copied.However, after the second or third day of copying and seeing the errors in the Event log only during the time period of the copy operation some weird things start to happen.When I open Windows Explorer there is no preview for the new volume like there was when the volume is initially attached to the server.Also, Explorer takes a long time to refresh the view.If I open the drive, it will also take a while to display the contents.During this time when this flakiness is occurring, the same Event IDs show up in the event log.Im at a loss as to why.The server is an HP Pro.Liant DL1. 20 G7 using the onboard NIC connected at 1.Gbps in its own VLAN and subnet over an HP 2.G switch to the d.Robo B1. 20. 0i SAN with no Jumbo Frames configured.This volume was previously attached to a different server that was virtualized on VMware and I was getting the same errors.In an effort to rule out the hypervisor, I attached the volume to the physical server described here.Robo says that everything on the SAN looks fine of course and the switches have the latest firmware as does the server.These are the error messages Log Name System.Source i. Scsi.Prt. Date 41.AMEvent ID 3.Task Category None.Level Error.Keywords Classic.User NAComputer IMAGESERVERDescription Initiator sent a task management command to reset the target.The target name is given in the dump data.Event Xml lt Event xmlnshttp schemas.System lt Provider Namei.Scsi. Prt lt Event.ID Qualifiers4. Event.ID lt Level 2lt Level lt Task 0lt Task lt Keywords 0x.Keywords lt Time.Created System. Time2.T1. 5 0. 6 0. 4. Z lt Event.Record. ID 6. Event.Record. ID lt Channel Systemlt Channel lt Computer IMAGESERVERlt Computer lt Security lt System lt Event.Data lt Data DeviceRaid.Port. 2lt Data lt Binary 0.C0. 00. 00. 00. 00.E0. 02. E0. 03. 20.D0. 03. 00. 03. 60.E0. 06. 30. 06. F0.D0. 02. E0. 06. 40.F0. 06. 20. 06. F0.A0. 06. 20. 03. 10.E0. 06. 40. 07. 20.E0. 06. 90. 06. 40.Binary lt Event. Data lt Event Log Name System.Source i. Scsi.Prt. Date 41.AMEvent ID 9.Task Category None.Level Error.Keywords Classic.User NAComputer IMAGESERVERDescription Target did not respond in time for a SCSI request.The CDB is given in the dump data.Event Xml lt Event xmlnshttp schemas.System lt Provider Namei.Scsi. Prt lt Event.ID Qualifiers4. Event.ID lt Level 2lt Level lt Task 0lt Task lt Keywords 0x.Keywords lt Time.Created System. Time2.T1. 5 0. 6 0. 4. Z lt Event.Record. ID 6. Event.Record. ID lt Channel Systemlt Channel lt Computer IMAGESERVERlt Computer lt Security lt System lt Event.Data lt Data DeviceRaid.Port. 2lt Data lt Binary 0.C0. 00. 00. 00. 00.A0. 00. 00. 00. 00.D1. 00. 00. 00. 01.E0. 02. E0. 03. 20.D0. 03. 00. 03. 60.E0. 06. 30. 06. F0.D0. 02. E0. 06. 40.F0. 06. 20. 06. F0.A0. 06. 20. 03. 10.E0. 06. 40. 07. 20.E0. 06. 90. 06. 40.Binary lt Event. Data lt Event Log Name System.Source i. Scsi.Prt. Date 41.AMEvent ID 1.Task Category None.Level Warning.Keywords Classic.User NAComputer IMAGESERVERDescription The description for Event ID 1.Scsi. Prt cannot be found.Either the component that raises this event is not installed on your local computer or the installation is corrupted.You can install or repair the component on the local computer.If the event originated on another computer, the display information had to be saved with the event.The following information was included with the event DeviceRaid.Port. 2the message resource is present but the message is not found in the stringmessage table.Event Xml lt Event xmlnshttp schemas.System lt Provider Namei.Scsi. Prt lt Event.ID Qualifiers3. Event.ID lt Level 3lt Level lt Task 0lt Task lt Keywords 0x.Keywords lt Time.Created System. Time2. El Mejor Manual Para Aprender A Tocar Guitarra Electrica Mercado . T1. 5 0. 6 0. 4. Z lt Event.Record. ID 6. Event.Record. ID lt Channel Systemlt Channel lt Computer IMAGESERVERlt Computer lt Security lt System lt Event.Data lt Data DeviceRaid.Port. 2lt Data lt Binary 0.F0. 01. 80. 00. 10.Binary lt Event. Data lt Event Any ideas Ive searched these event IDs and there is a myriad of different responses ranging from switch firmware to Jumbo Frames to receive side scaling to Flow Control.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |