Bosch DLA 1400 Restore Guide

Bosch DLA 1400 SeriesVideo Storage Array Restore Guide

Bosch DLA

Bosch DLA 1400 Series Video Storage Array Restore Guide

1 DLA 14000 Series - Technical note

Technical note

ContentsStart Up 2

3

8

10

10

11

MegaRAID BIOS Utility

Windows Storage Server

Veri�cation

Updates

References

Cyprus © 2015

cy.linkedin.com/pub/panagiotis-karagiannis/1b/176/305/

The WebBIOS Con�guration Utility, unlike the MegaRAID StorageManager software, resides in the SAS controller BIOS and operatesindependently of the operating system.

Reset or power on the server having a monitor and a keyboardconnected.

NOTE: On systems that do not have the PS2 port, you must enable“port 60/64 emulation” in the System BIOS to emulate USB as PS2.When this option is disabled on this system, WebBIOS doesn’t work.

Start Up

After this screen you’ll have two choices.Press <Ctrl><H> for WebBIOS or Press <Ctrl><Y> for Preboot CLI

Press <Ctrl><H> to enter the WebBIOS Con�guration Utility.


Cyprus © 2015

LSI MegaRAID BIOS Con�guration Utility window appears.

In the Adapter Selection screen, click Start. The LSI MegaRAID BIOSCon�guration Utility Virtual Con�guration screen appears.

Select “Virtual Drives” to view all virtual drives.

Select “Drives” to view all physical drive information and status.

Click Con�guration Wizard on the WebBIOS main screen. Select “New Con�guration”. This clears the existing con�gurationand lets you create a new one.

Accept above warning by pressing “Yes”.

Select “Manual Con�guration”. This will allow you to control allattributes of the new storage con�guration as you create drivegroups and virtual drives, and set their parameters.

MegaRAID BIOS Utility

DLA 14000 Series - Technical note 3

Cyprus © 2015

Here are brief explanations of the virtual drive options:

RAID Level:The drop-down menu lists the possible RAID levels for the virtual drive. RAID 5 uses drive striping at the block level and parity. In RAID 5, the parity information is written to all drives. It is best suited for networks that perform a lot of small input/output (I/O) transactions simultaneously. RAID 5 provides data redundancy, high read rates, and good performance in most environments. It also provides redundancy with lowest loss of capacity. RAID 5 provides high data throughput. RAID 5 is useful for transaction processing applications because each drive can read and write independently. If a drive fails, the RAID controller uses the parity drive to recreate all missing information. RAID 5 is good for any application that has high read request rates but low write request rates. Select “RAID 5”.

Strip SizeThe strip size is the portion of a stripe that resides on a single drive in the drive group. The stripe consists of the data segments that the RAID controller writes across multiple drives, not including parity drives. For example, consider a stripe that contains 64 KB of drive space and has 16 KB of data residing on each drive in the stripe. In this case, the stripe size is 64 KB and the strip size is 16 KB.

You can set the strip size to 8, 16, 32, 64, 128, 256, 512, and 1024 KB. A larger strip size produces higher read performance. If your computer regularly performs random read requests, choose a smaller strip size. The default is 64 KB.

Access Policy:Select the type of data access that is allowed for this virtual drive:RW: Allow read/write access. This is the default.Read Only: Allow read-only access.Blocked: Do not allow access.

Read Policy:Specify the read policy for this virtual drive:Normal: This option disables the read ahead capability. This is the default.Ahead: This option enables read ahead capability, which allows the controller to read sequentially ahead of requested data and to store the additional data in cache memory, anticipating that the data will be needed soon. This speeds up reads for sequential data, but there is little improvement when accessing random data.

Write Policy:Specify the write policy for this virtual drive:WBack: In Writeback mode the controller sends a data transfer completion signal to the host when the controller cache has received all of the data in a transaction. This setting is recommended in Standard mode.WThru: In Writethrough mode the controller sends a data transfer completion signal to the host when the drive subsystem has received all of the data in a transaction. This is the default.Bad BBU: Select this mode if you want the controller to use Writeback mode but the controller has no BBU or the BBU is bad. If you do not choose this option, the controller �rmware automatically switches to Writethrough mode if it detects a bad or missing BBU.

IO Policy:The IO Policy applies to reads on a speci�c virtual drive. It does not a�ect the read ahead cache.Direct: In Direct I/O mode, reads are not bu�ered in cache memory. Data is transferred to the cache and the host concurrently. If the same data block is read again, it comes from cache memory. This is the default.Cached: In Cached I/O mode, all reads are bu�ered in cache memory.

Drive Policy:Specify the drive cache policy:Enable: Enable the drive cache.Disable: Disable the drive cache.NoChange: Leave the current drive cache policy as is.This drive policy is the default.

Disable BGI:Specify the background initialization status:No: Leave background initialization enabled. This means that a new con�guration can be initialized in the background while you use WebBIOS to do other con�guration tasks. This is the default.Yes: Select Yes if you do not want to allow background initializations for con�gurations on this controller.

Select Size:Specify the size of the virtual drive in megabytes. Normally, thiswould be the full size for RAID 5 shown in the Con�guration panel

Select all desired drives for the drive group and click “Add To Array”to move the drives to a proposed drive group con�guration in theDrive Groups panel on the right. If you need to undo the changes,select Reclaim. After you �nish selecting drives for the drive group,click “Accept DG”. Click “Next”.

Array hole will be added to the span. Array hole addition can beundone by selecting the “Reclaim” button. Click “Next”.

The Virtual Drive De�nition screen appears. This screen lists thepossible RAID levels for the drive group. Use this screen to selectthe RAID level, strip size, read policy, and other attributes for thenew virtual drives.

Span De�nition screen will appear. To add an array hole to a span,select an array hole from the drop down. Click on Add to span.


on the right. We have to create two virtual drives. One for the WSS OS and one for the Video Storage. Select a size of 99.999 MB for the Windows Storage Server, Bosch SW, LSI SW and Supermicro SW.

Click “Accept” to accept the changes to the virtual drive de�nition. If you need to undo the changes, click “Reclaim”.

Cyprus © 2015

Here are brief explanations of the virtual drive options:

RAID Level:The drop-down menu lists the possible RAID levels for the virtual drive. RAID 5 uses drive striping at the block level and parity. In RAID 5, the parity information is written to all drives. It is best suited for networks that perform a lot of small input/output (I/O) transactions simultaneously. RAID 5 provides data redundancy, high read rates, and good performance in most environments. It also provides redundancy with lowest loss of capacity. RAID 5 provides high data throughput. RAID 5 is useful for transaction processing applications because each drive can read and write independently. If a drive fails, the RAID controller uses the parity drive to recreate all missing information. RAID 5 is good for any application that has high read request rates but low write request rates. Select “RAID 5”.

Strip SizeThe strip size is the portion of a stripe that resides on a single drive in the drive group. The stripe consists of the data segments that the RAID controller writes across multiple drives, not including parity drives. For example, consider a stripe that contains 64 KB of drive space and has 16 KB of data residing on each drive in the stripe. In this case, the stripe size is 64 KB and the strip size is 16 KB.

You can set the strip size to 8, 16, 32, 64, 128, 256, 512, and 1024 KB. A larger strip size produces higher read performance. If your computer regularly performs random read requests, choose a smaller strip size. The default is 64 KB.

Access Policy:Select the type of data access that is allowed for this virtual drive:RW: Allow read/write access. This is the default.Read Only: Allow read-only access.Blocked: Do not allow access.

Read Policy:Specify the read policy for this virtual drive:Normal: This option disables the read ahead capability. This is the default.Ahead: This option enables read ahead capability, which allows the controller to read sequentially ahead of requested data and to store the additional data in cache memory, anticipating that the data will be needed soon. This speeds up reads for sequential data, but there is little improvement when accessing random data.

Write Policy:Specify the write policy for this virtual drive:WBack: In Writeback mode the controller sends a data transfer completion signal to the host when the controller cache has received all of the data in a transaction. This setting is recommended in Standard mode.WThru: In Writethrough mode the controller sends a data transfer completion signal to the host when the drive subsystem has received all of the data in a transaction. This is the default.Bad BBU: Select this mode if you want the controller to use Writeback mode but the controller has no BBU or the BBU is bad. If you do not choose this option, the controller �rmware automatically switches to Writethrough mode if it detects a bad or missing BBU.

IO Policy:The IO Policy applies to reads on a speci�c virtual drive. It does not a�ect the read ahead cache.Direct: In Direct I/O mode, reads are not bu�ered in cache memory. Data is transferred to the cache and the host concurrently. If the same data block is read again, it comes from cache memory. This is the default.Cached: In Cached I/O mode, all reads are bu�ered in cache memory.

Drive Policy:Specify the drive cache policy:Enable: Enable the drive cache.Disable: Disable the drive cache.NoChange: Leave the current drive cache policy as is.This drive policy is the default.

Disable BGI:Specify the background initialization status:No: Leave background initialization enabled. This means that a new con�guration can be initialized in the background while you use WebBIOS to do other con�guration tasks. This is the default.Yes: Select Yes if you do not want to allow background initializations for con�gurations on this controller.

Select Size:Specify the size of the virtual drive in megabytes. Normally, thiswould be the full size for RAID 5 shown in the Con�guration panel


on the right. We have to create two virtual drives. One for the WSS OS and one for the Video Storage. Select a size of 99.999 MB for the Windows Storage Server, Bosch SW, LSI SW and Supermicro SW.

Click “Accept” to accept the changes to the virtual drive de�nition. If you need to undo the changes, click “Reclaim”.

Select “Yes” to the Write Back with BBU warning.

Cyprus © 2015


Click “Yes”.

A virtual drive named “VD 0” will be created under Drive Group 0.Select “Back” to add the second virtual drive. Select “Add to SPAN”for the remaining array size ad select “Next”.

A review of your con�guration will show up. Click Check the information in the con�guration preview. If the virtualdrive con�guration is acceptable, click “Accept”. Otherwise, click“Cancel” to end the operation and return to the WebBIOS mainmenu, or click “Back” to return to the previous screens and changethe con�guration.

For the second virtual drive you will only be able to have RAID5. Seethe remaining size and type in the same value to the “Select Size”entry �eld. Click “Next”.

Select “Yes” to the Write Back with BBU warning.

Drive Group 0 now has two virtual drives “VD 0” and “VD 1”. Select“Next” to continue.

Cyprus © 2015


Select “Cancel” for the SSD caching option. When �nished select “Home” and “Exit”.

Select “Yes” to start the initialization of your system. Reboot the unit to restore Windows Storage Server 2008 from aSystem Image.

“Fast Initialize” should work, but “Slow Initialize” is recommended.It will take about 30min per 1 TB of storage. Fast initialization quicklywrites zeroes to the �rst and last 10-MB regions of the new virtualdrive and then completes the initialization in the background.A slow initialization is not complete until the entire virtual drive hasbeen initialized with zeroes.

Cyprus © 2015


Windows Storage ServerLet the unit run its normal startup procedure.

Type “1” and press enter to start the WSS initial setup.

Wait for the system maintenance menu to show up.

The unit will reboot.

Cyprus © 2015


Veri�cationOpen Server Manager and check that everithing is in order.Navigate to Storage > Microshoft iSCSI Software Target > Devicesto view your virtual disks.

UpdatesYou should now update Bosch VRM, LSI® MegaRAID® StorageManager for Windows and Supermicro SuperDoctor® III ServerManagement.

For some reason, above updates, may disrupt communication ofthe VRM. Running again the latest VRM version will �x this.

(D:) drive should have 12 VHD (Virtual Hard Disk) �les along withtheir corresponding CBM (Change Bitmap) �les. These are yourLUNs (Logical Unit Number).

Cyprus © 2015


Note:All data given in this technical note is for brief information and convenience only. It should be read inconjunction with recognised industry best practice and standards and other technical publications.

1200 and 1400 Series iSCSI Disk Arrays Installation Manual v.1 - 2010.081200 and 1400 Series iSCSI Disk Arrays Installation Guide v.1 - 2010.09MegaRAID SAS Software User Guide (Rev J Sept 2010) 80-00156-01MegaRAID SAS Software User Guide (Rev. P, August 2014) 51530-00

Written by:Panagiotis Karagiannis

Cyprus © 2015

Rev.0.2 - CY © 2015

References



http://www.youtube.com/user/MossBrosSecurity/videos

Bosch DLA 1400 Restore Guide

Documents

Transcript of Bosch DLA 1400 Restore Guide