{"id":17243,"date":"2012-06-21T10:19:34","date_gmt":"2012-06-21T10:19:34","guid":{"rendered":"http:\/\/blog.open-e.com\/?p=17243"},"modified":"2025-04-04T06:41:49","modified_gmt":"2025-04-04T06:41:49","slug":"unusual-request","status":"publish","type":"post","link":"https:\/\/www.open-e.com\/blog\/unusual-request\/","title":{"rendered":"Unusual request…"},"content":{"rendered":"

\t\t\t\tLast week I was visiting a customer in Sweden for product training. One of the main reasons they required an on-site training was for a very unusual request:<\/p>\n

The goal was a system with two RAID arrays configured as NAS volumes. Once one of volumes is full of data, it must be removed from the system then replaced with the new fresh and empty array. The full one must be shipped to another location where it has to be attached to another system and used for data analysis.<\/p>\n

All the arrays swap need to be done online without a system reboot. This is really interesting to say the least as my thinking is: what kind of features require this from what applications? Luckily and thanks to an option where placing the RAID array to an offline position is possible. In this particular case the system was equipped with an ARECA RAID controller. Using the controller function of placing the RAID volume into offline state enabled me to remove all trays belonging to this array. Additionally after putting the arrays into offline mode all LEDs of the off-lined trays were blinking, so it was not a problem to identify the off-lined trays. In DSS V6<\/a> the volume group just disappeared of course with an error about missing volume group in the event viewer, but all the rest was working uninterrupted.<\/p>\n

After inserting the array into the other system we just needed to click the re-scan function and all was properly recognized.<\/p>\n

\"\"<\/a><\/p>\n

If you face a similar request please make sure you test it at least a few times before starting production. Also the best practice would require some data replication<\/a> into the other system. The replication can be overwritten after successful shipping of the array to another location. Also the volume group name must be unique in the system, so every time you create new volume group please think about good unique name.<\/p>\n

So, I hope that this unusual request is of some interest to you. Maybe you get customer request for archiving the data on regular bases. Such functionality can help you to think about hard disk based archiving solution.\t\t<\/p>\n","protected":false},"excerpt":{"rendered":"

Last week I was visiting a customer in Sweden for product training. One of the main reasons they required an on-site training was for a very unusual request: The goal …<\/p>\n","protected":false},"author":2,"featured_media":45753,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[29,779,765,28],"tags":[96,417,460,465,523,528,653],"class_list":["post-17243","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-data-protection","category-nas","category-open-e-legacy-products","category-raid","tag-best-practice","tag-nas-volumes","tag-open-e","tag-open-e-dss-v6","tag-raid","tag-raid-array","tag-swap"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t