Buffalo Resilient NAS by Design A deployment guide to disaster recovery Page 1
Table of contents Introduction. 3 1.0 RAID configuration. 4 1.1 RAID Disk crash recovery..4 1.2 RAID Disk crash recovery Procedure..4 2.0 NAS unit with backup to external storage....7 3.0 A Dual Server Backup.....9 4.0 Dual redundant NAS units with automatic Failover..12 4.1 Hardware Connection Automatic Failover.13 4.2 Configure Failover on main unit 14 4.3 Safely trigger a failover condition..15 5.0 NAS units with replication to external Storage...17 6.0 System Crash recovery...21 6.1 RAID volume Data recovery on Linux..26 7.0 WiKi solution based on HDD boot image... 32 Page 2
Introduction For mission critical applications and businesses with small or large computing environment, server down time and loss of critical data may not be an option. Building redundancy is the key to reliable recovery in case of possible hardware or software failure. To reduce the risk, a recovery infrastructure built on redundancy on every level is the solution. Even with the best of intentions, in real world, software and hardware errors do occur. Hard disk Failure is the most common hardware failure in network attached storage (NAS) or file servers. As with any electro-mechanical device, the hard disk failure is due to the moving parts which are prone to breakdown as parts wear out over time. The most common hard disk failure is due to head crash. Having multiple storage units in a single NAS unit is the basic building block of a reliable recovery infrastructure. Intrinsically, NAS devices support data recovery through the built-in RAID (redundant array of independent disks) multiple hard disk redundancy. The built in RAID technology, provides reliability and fault tolerance through multiple drive redundancy. The TeraStation (TS7000) supports redundant power supply as well. If one power unit fails the other power unit can keep TeraStation operational. Even with RAID configuration, there is the possibility of server or multiple hard disks failure beyond RAID recovery capability to rebuild the unit. This guide provides deployment options and disaster recovery plan to build a more resilient NAS application to reduce sever down time and the risk of data loss. Specifically, building the following backup recovery support infrastructure: 1) RIAD disk crash recovery procedure 2) NAS unit with secondary back up to external storage unit. 3) Dual Server backup 4) A dual redundant NAS units with automatic fail over For mission critical applications, data are automatically backed up to backup unit in near real time. An automatic fail over will switch to back up unit when source/main unit is no longer accessible. 5) NAS unit with replication to external storage. 6) Finally, System crash recovery & data retrival. Page 3
Chapter 1.0 RAID configuration Buffalo NAS products support the following RAID levels: 1 RAID60 RAID61 RAID6 RAID50 RAID51 RAID5 RAID10 RAID1 RAID0 Depending on the RAID level, there is an upper limit on the number of disk failure at any one time beyond which recovery is not possible. For more information refer to appendix A2 at end of this document. 1.1 RIAD disk crash recovery In event of disk failure, Buffalo NAS can recover data by simply replacing the failed hard disk drives to rebuild the RAID configuration. The defective drive can be removed and replaced with a new drive. The Hot Swap feature in TeraStation will automatically power down the faulty drive to allow its safe removal and replacement without the need to interrupt the units operation. The "Hot swappable" drives ensure that users can continue to work while the defective drive is being replaced. The procedure requires no special treatment and can be carried out by a novice user. Please refer to appendix A2, for details on RAID configuration. 1.2 Raid disk crash recovery procedure Important: Replace the damaged disk with the same disk size. In WEB UI, Click drives to see Unit Capacity per disk. With RAID already configured, replace one disk drive at a time and repeat the bellow outlined procedure for any additional failed hard disk. Page 4
1- Open the front cover with the key included in the product package. 2- Push the cartridge tab of the failed hard disk (denoted by the status LED lighting in red) to the left, and pull it out toward the front of the unit. Hard disks with the status LEDs not lighting are still active. Do not unplug or remove them. 3- Pull out the hard disk together with the cartridge, and remove it from the TeraStation. 4- Replace it with new hard disk. Insert the new internal hard disk (sold separately) into the empty slot. Page 5
5- Push the disk into the TeraStation, and push the tab towards the back of the TeraStation until you hear a clicking sound. If TeraStation is off, turn it back on. 6-When the new hard disk is recognized, the LED will flash in red, and the LCD on the front of the TeraStation will display the message, "Press FuncSW I31 New disk (some number from 1 to 4) ready. 7- Press and hold the FUNCTION button on the front of the TeraStation for 3 seconds (until it beeps). The TeraStation will start re-configuring RAID. Page 6
Chapter 2.0 NAS unit with backup to external storage The simplest disaster recovery plan is a single NAS unit setup with attached external USB storage for periodic data backup. 2 Important: Backup the NAS configuration (and boot up image) into separate USB memory device (1GB size). See appendix B for details. Even with RAID protection, there is always the possibility of total server failure or multiple hard disks failure beyond limits allowed for RIAD configuration recovery. To protect against such scenario, first backup TeraStation configuration on USB flash disk. Second always keep a back up of data on a secondary storage unit. The simplest backup setup is a NAS unit with external USB storage attachment. In event of server failure, data can be restored from external storage by simply coping data back to server. In case of total catastrophic server failure, It is important to have backup of NAS configuration to restore server or re-build entirely new boot disks and RAID form the ground up. Please see appendix B for details on storing and re-booting from stored server configuration. The attach external USB unit will appears as a folder on the same NAS, backup source and destination therefore are source folders from the same NAS unit to destination usb-folder on the same unit. To backup: 1) Attach USB storage to NAS USB port 2) Navigate to File Sharing -> Folder Setup and click. 3) Page 7 4) Click USB folder and next Edit button and enable Backup folder option:
5) Navigate Backup and click configuration button. 6) Click [Create New Job] 7) Give the backup task a name and select type of back up and schedule. Next, select Source Folder and the destination folder. Alternatively, if there are multiple servers in one location, backup can be preformed over the network from one unit to the other and vice versa. For more secure backup and disaster recovery plan, offsite backup to another TeraStation server can be configured as easily as attached USB option. The backup features built into every TeraStation enables novice users to easily create backup jobs that backup the contents of one server to another server. Page 8
Chapter 3.0 Dual Server backup 3 UPS NAS1 NAS2 NASn UPS LAN1 Back up NETWORK Local office [VPN] Optional for remote Branch office Backup can be done to USB attached external storage unit or transparently to another unit in local LAN or remotely across the intranet or internet to a branch office. For all practical purposes remote and local servers are configured for backup as easily and exactly in the same way. For remote backup to another offsite server, all that's required is network infrastructure setup and access (through intranet or through VPN over Internet). The examples below illustrate a typical dual [remote] server setup. This same procedure is used for external USB storage backup by simply selecting destination backup folder. From WEB UI, select shared folder -> create Folder, and create the destination shared folder on target device and enable the backup option. Next, enter a password for the remote backup access. Page 9
Next, move to DATA source NAS server. 1. Start a browser and login to administrators WEB UI 2. Click Backup and next click configure backup button. 3. Next, click the backup password [Set] button The password is destination (target) server s shared folder Remote backup password : Enter the same password as destination folder on target NAS : shared folder settings Source NAS setting Page 10 Destination Folder settings
Next, click [create new job] button. Give the backup task a name and select source and destination folder. Note external folders are displayed NAS-name@Folder-name. Next, click the [OK] button to start the backup task. Page 11
Chapter 4.0 Dual redundant NAS units with automatic Failover 4 MAIN NAS SERVER LAN2 Backup / COPY Backup / Standby NAS SERVER LAN2 UPS NETWORK LAN1 UPS LAN1 Figure 1- Automatic Failover For mission critical applications, dual redundant NAS severs with automatic failover is the recommended setup. Data are automatically backed up to the standby unit in near real time. In an event of main NAS server failure, the standby server will automatically take over as if it were the main server. The failover will switch to the standby unit when source/main unit is no longer accessible. The transition is transparent to the network clients, since standby IP address is updated to main server IP address. Automatic failover setup will significantly reduce downtime to a minimum. Page 12
4.1 Hardware Connection Automatic Failover To setup fail over connection, connect Ethernet cable from LAN2 port on main server to LAN2 port on the standby server. Normal, network traffic is carried over LAN port 1 and backup copy is done over LAN port2. Once failover is configured, you will not be able to set up a UPS link for the backup TeraStation. Configure UPS settings before configuring the failover. UPS settings of the main TeraStation are not copied to the backup TeraStation. UPS settings for both TeraStations should be configured manually before configuring failover. LAN Main Server Standby LAN1 192.168.11.200 192.168.11.210 LAN2 192.168.12.201 192.168.12.211 Figure 2- Automatic Failover Since the IP address of standby server should not be changed, assign static IP address to LAN1 and LAN2 on both main and failover servers. Navigate to Network -> settings and click the [Modify Settings] button. Set LAN1 and LAN2 to IP to static IP address. To avoid duplicate IPs, make sure the IP address is outside the DHCP range. Page 13
4.2 Configure Failover on the main unit. Important: To setup failover, both Terastations should be the same model and with the same storage capacity. In Web UI, click drives to confirm each units Capacity per disk. Start a browser and login to administrators WEB UI. 1. In the TeraStation's Web Admin interface, click next to [SMB]. Next, Click [Edit] and Disable [SMB2 Protocol], then [OK]. 2. Click Backup. 3. Click configure failover button. 4. Click [Enable Failover] button 5. Select a TeraStation from the drop-down list to be the target backup device. Page 14
6. Enter the administrator password of the standby TeraStation, and click [Failover Start]. 7. If the administration password is correct, the standby TeraStation will start beeping. 8. To accept the settings from the source TeratStation, hold down the function button on the front of the Standby TeraStation for 10 seconds. Important: Note, all data stored in the failover/standby TeraStation will be deleted when it is configured as failover/standby. Message in WEB UI on main NAS Confirm the same model and same capacity TeraStation are used for both the main TeraStation and backup/standby TeraStation. Click drives to see Unit Capacity per disk. Depending on size of data on main unit, the failover setup will take time to complete since data will be copied over to standby unit. 4.3 Safely trigger a failover condition To test the failover setup, trigger a failover condition by disconnecting main NAS server from the network i.e. unplug the Ethernet cable from LAN1 port on main server.. Page 15
The following information is shown on LCD panels when operation switches from main TeraStation to backup TeraStation: This message (I49) is displayed on the LCD panel of the backup TeraStation when operation switches from the main TeraStation to the backup TeraStation. FailOver I49 LostMainTarget This message (E27) is displayed on the LCD panel of the main TeraStation if it is no longer able to detect the backup TeraStation on the network. FailOver E27 LostBackupTarget 4.4 Re-arm the failover After a failover condition, the main unit can be re-armed by disabling and re-configure failover back on the initial main unit. However, since re-configuring failover back on main unit will delete any new data updates on running server since the failover, it is best to swap the server roles. Configure the currently running standby server as main server and previously configured main (failed) servers as standby server. Set the current running server as Main server and the failed server as a standby. To disable failover, in the main TeraStation's Web Admin interface, navigate to [Failover] and click [Dissolve Failover]. Failover can also be disabled by clicking [Dissolve Failover] in the backup TeraStation's Web Admin interface. If failover cannot be disabled, in the main TeraStation's Web Admin interface, navigate to [Backup] next to [Failover] and click [Force Failover to Stop]. After performing a forced disable, restart the main TeraStation and the backup TeraStation. After restarting, check the settings (such as the IP address) and data in the shared folder for both the main TeraStation and the backup TeraStation. After a forced disable, the shared folder of the backup TeraStation is set to read-only. If necessary, re-configure failover again. Page 16
Chapter 5.0 A NAS units with replication to external Storage 5 Figure 3- Replication setup in local office The replication feature provides an easy and high performance data redundancy in near real time. Replication mirrors the data in a folder on the source TeraStation to a folder on another TeraStation in near real time. Simply by selecting source and destination folder, data is copied from one Buffalo NAS device to another Buffalo NAS device on local network or over Internet to remote branch office. Page 17
Figure 3- Replication setup over Internet A NAS device can be configured to operate in both directions to replicate and receive replicated data from other NAS device. When configured, two shares on two NAS devices will be completely synchronized regardless of which NAS receives new files, changes files, or deletes files. After the initial mirroring of data, only changes at the byte level cross the network. Thus, if changes were made to a large file, only the changes would be sent, not the entire file. Replication works only in one direction: From the source to the destination. Changes or deletions on the destination are not reflected back to the source, but all changes, additions and deletions made on the source are reflected on the destination. Buffalo NAS allows for one-to-many and many-to-one replication; replication to multiple NAS targets and vice versa, multiple NAS devices can replicate to a single supported NAS device. This allows for all information from branch locations to be replicated onto a single NAS device at headquarters. 5.1 Configure Replication in six easy steps 1. Start a browser and login to administrators WEB UI 2. Click Backup. Page 18
3. Click the configure replication button: 4. Click [Add] button followed by [browse] button to select source folder from this NAS device. 5. Under backup target (left), click browse to select destination folder where data will be copied. After folder selection, click OK. Page 19
6- Click OK, to complete the setup Page 20
6.0 System Crash recovery In case of catastrophic failure: In case of multiple hard disk failure, the unit can be re-built from ground up using the following procedure: Re-boot the unit using USB memory key with boot and configuration backup prepared previously (See appendix B for details). If you have not prepared the configuration backup/boot USB, contact your local Customer Service for help. CS will provide you with USB boot up image for download. 1- Turn power off by disconnecting power cord. 2- Open the front cover with the included key. 3- Replace all damaged HDD: Squeeze the tab to the left on drive bay and swing out the drive lock. Slide the cartridge out of the TeraStation. 4- Next, replace HDD in the cartridge with a new hard drive. 5- Slide the drive into the TeraStation, then swing the lock back down until it clicks into. place. 6- Re-Connect the TeraStation with the power cable. 7- Set the Boot Mode switch on the rear to [USB]. Connect the USB recovery with backup configuration (appendix B) to device to the USB 2.0 Page 21
port of the TeraStation. Before connecting the supplied USB recovery device, be sure to remove any other USB devices connected to the TeraStation. 8- Press the power button. The LCD panel will light up as the TeraStation boots. 9- When Recovery I41 PushFuncToStart is displayed on the LCD panel, press the function button. As the firmware is read, the LCD panel will show Recovery I37 SystemRecovering. While this message is displayed, all of the status LEDs are lit green 10- During installation, the TeraStation will reboot after the firmware files are read from the USB recovery device. Unplug the USB recovery device from the TeraStation and move the Boot Mode switch to [HDD]. The firmware will now install. When installation is complete, the TeraStation will shut down completely. After automatic shutdown, the message on the LCD panel changes from Recovery I38 RecoveryFinished to Recovery I39 Change Boot. Unplug the USB recovery device from the TeraStation and move the Boot Mode switch to [HDD]. Next, Press the power button to power on the TeraStation. At this point you have an entirely rebuild and uninitialized system. To retrieve previous configuration, 1- Re-insert the configuration recovery USB back in and follow instructions in appendix B. to recover configuration settings. 2- To restore lost data, attach external USB storage with backup data to the NAS unit. Next, copy the data from USB storage folder to NAS unit by creating a (reverse) backup task to recover data. Alternatively, you can copy data through Webaccess browser to NAS unit by copy folder (drag and drop folder) through the GUI. Not all Terastation models support USB boot recovery. Some older models have on board boot image. Depending on the Terastation model Page 22
The following is general procedure to re-boot (re-initialize), NAS unit after boot failure. Determine the course of action based on TeraStation model. TeraStation Re-Boot Recovery Procedure Check units Support USB BOOT Yes Does It support USB boot (does it have a USB boot sw.)? USB memory BOOT Procedure No Check units Support On board boot No Get HDD boot Image Does it have On Board (NAND) Boot F/W? Yes Force device into EM Mode (procedure). Page 23
LinkStation re-boot recovery procedure (HDD boot sector re-initialization). Table 2.LinkStation re-boot (boot sector initialization) supported method LinkStation Series On Board Boot (NAND) USB BOOT LS-X series /E (Enclosure) YES NO LS-X series NO NO LS-W series /E (Enclosure) YES NO LS-W series NO NO LS-Q series /E (enclouse) YES NO LS-Q series NO NO LS-V series NO NO LinkStation Re-Boot Recovery Procedure Check table if unit Support on board boot Yes Enclosure Type? Does it have on board (NAND) boot Firmware? Force device into EM Mode (procedure). For Single HDD LS units will require HDD replacement or boot image. Contact Customer Service. Page 24
TeraStation and Linkstation Emergency Mode(EM)/BOOT re-initialization Procedure HDD boot Sector re-initialization Some TeraStation and LinkStation (all Enclosure type) support boot up from on board (NAND) flash memory/firmware. There are two possible ways to force boot up from on board flash memory/firmware: 1- The easy way; repeatedly recycle power (more than three times) to the unit. Push the Power button in rapid successive motion. 2- Alternatively, pull the disks from the NAS unit and attach to SATA interface on a desktop PC (Linux OS preferably). Delete the files on the first partition. Put disks back in the unit and power the unit up. Either way, the unit will boot from on board Flash RAM and will enter EM mode. When In EM mode, the NAS Navigator client software will display the device IOCN with (?) question mark. If the unit is in EM mode, download firmware with updater application from Buffalo web site and update the device firmware. Page 25
6.1 RAID volume Data recovery on Linux The following is guide on how to retrieve data from RAID Volumes on Linux in case of NAS crash. Background Hard disks on Terastation and Linkstation have 6 partitions Disk1 ( sda ) Disk2 ( sdb ) User Data is in the 6 th partition sdx6 { where x is the disk a,b,c } To retrieve user data on RAID, a Linux PC with adequate number of SATA interfaces to attach the minimum number of RAID hard disks is required. i.e. RAID1 requires at least 1 additional SATA where as RAID5 requires at least 3 additional SATA interface. 6.1.1 The Procedure Using Linux command: To retrieve data using Linux command line is very simple. Attach HDDs to SATA on PC before booting and NEXT boot PC. On most Linux implementations, RAID volume will be detected on boot and activated. 1) Open terminal console and log in as root by exciting su. 2) Execute cat /proc/mdstat Look for a line with sdx6 in it, and confirm it is active. With raid one, all you have to do next is simply mount the disk. If raid is other than raid 1, confirm all disks are listed in the same line Next Execute mount /dev/mdn /mnt/some_tmp_dir Page 26
3) If the 6 th partition not listed or active but does not include listing of all the disks; Execute the following commands: mdadm Eb /dev/sdx6 >> /etc/mdadm.conf mdadm As mount /dev/mdn /mnt/some_temp_dir for example if for raid 5 with 3 disks sdb, sdc and sdd. this would look like this : mdadm Eb /dev/sdb6 /dev/sdc6 /dev/sdd6 >> /etc/mdadm.conf mdadm As mount /dev/mdn /mnt/some_temp_dir Example for raid1 with 1 HDD (sdb):. In case of RAID5 with 3 disks, the command would be something like this: Page 27
[root@] #mdadm As 6.1.2 The Procedure Using Linux Fedora disk utility: The fedora disk utility is simple and user friendly alternative in order to activate and mount RAID volumes. We recommend Fedora release 14 which includes Disk utility with higher functionality. The version used for this guide is : 1- Attach HDDs yo SATA and boot PC. 2- Log-in and start Disk Utility (from Applications->system tools) 3- For RAID you will see the following sequences : Page 28
3.1 Example for raid1 with 1 HDD (sdb) : Example for raid5 with 3 HDD (sdb,sdc and sdd) : Page 29
3.2. Click the 6 th partition and Go to array 3.3 Click Start array 3.4 Click mount volume. If you do not see mount volume, Click Stop RAID array and start again. Page 30
The Raid volume will be mounted & a link will be displayed. Page 31
7.0 WiKi solution based on HDD [boot] image Currentely, Buffalo CS provide crash recovery HDD Image sloution. CS Global Team WEB PAGE. CS can provide HDD disk image and HDD image tools for recovery. Please contact buffalo Customer Support for details. APPENDIX A1 : Page 32
RAID-0 uses all drives as a single array of storage. All drives are seen as one-massive drive. The capacity of the drive is the combined capacity of all drives in the array. RAID 0 uses a method of writing to the disks called striping which distributes the data across all drives. The disadvantage to RAID-0 is that it offers no fault-tolerance. If one hard drive in the array fails, then the data in the entire RAID array is compromised. The fact that there are multiple drives in a RAID-0 array increases the opportunity for a hard drive failure. Since a single hard drive failure makes all of the data in the array unusable, RAID-0 is significantly more prone to data loss than a single drive configuration. RAID-0 should be used in cases where maximum capacity is required but data redundancy is not a requirement. RAID-1: Mirroring (with Redundancy) RAID-1 provides fault tolerance but also decreases overall capacity. RAID-1 is often referred to as disk mirroring. In a RAID-1 array, the system will save the data to all hard drives in the array simultaneously. In the case of a drive failure, the healthy drive will assume the role of the main drive and the data is accessible without interruption. Once the faulty drive is replaced, the RAID array will be restored to its original condition. RAID-1 is ideal in two-drive configurations seeking redundancy in lieu of capacity. RAID-1 is the Buffalo recommended configuration for all devices with 2 hard drives. Page 33
Area filled in with red represents parity/redundant information. RAID-5:(with Redundancy) RAID-5 requires at least 3 physical drives. Data is split into blocks and stored over all of the drives. Parity data is distributed amongst all of the drives and is used to regenerate lost data during a drive failure. In case of a drive failure, RAID-5 will be able to regenerate the missing data from the parity data remaining on the healthy drives. This regeneration occurs automatically and on-the-fly, meaning a user still has immediate access to their data after a single drive failure. RAID-5 is ideal in configurations with three or more drives seeking a combination of increased capacity and redundancy. RAID-5 is the Buffalo recommended configuration for all devices with 3 or more drives. Area filled in with red represents parity/redundant information. RAID6 Page 34
RAID 6 based on same technology as raid RAID 5, except it allows for 2/X frailer as opposed 1/X. When 2 hard disks in the RAID array break down, it is possible to salvage the data with changing the hard disk. RAID 60 consists of multiple RAID 6 arrays that are striped (as with RAID 0). Capacity [ (The number of hard disks 2)-2 2]. RAID61 consists of RAID 6 paired arrays that are mirrored (as with RAID 1). Capacity [ The number of hard disk 2-2]. RAID 50 consists of multiple RAID 5 arrays that are striped (as with RAID 0). Capacity [(The number of hard disk 2-1) 2]. RAID51 consists of multiple RAID 5 paired arrays that are mirrored (as with RAID 1). The capacity available is [The number of hard disk 2-1]. RAID 10 consists to multiple RAID 1 arrays that are striped (as with RAID 0). RAID 01 consists of RAID 0 paired arrays that are mirrored (as with RAID 1) Page 35
TeraStation RAID Configuration 1. Log onto the Terastation. the login prompt will appear, enter admin for the user name. Until you change it, the password for the admin account will be password. Press the OK button when finished. User name: admin Password: password 2. Click on Disk Management then RAID Configuration, configure the desired RAID setup. This page shows your current RAID arrays. You may delete old arrays or create new ones by clicking on the underlined RAID Array # under RAID Array Configuration. You may also disable RAID Array Error Detection Response from this page. Normally, this is set to automatically shut down the RAID array when an error is detected. Though it is not recommended, you may disable that behavior by clicking Disable and then Apply under RAID Array Error Detection Response. Note that your TeraStation has four internal hard drives. Before creating a new RAID array, you may have to delete one or more pre-existing RAID Arrays to clear up the hard drives for your new one. This will destroy all data currently on the disks, so back up any important data before deleting RAID arrays. Whether you want to clear out an old array or create a new one, begin by clicking on the array underlined RAID Array #, under Name. TeraStation uses RAID (Redundant Array of Independent Disks) technology to control the fourhard drives in your TeraStation. RAID may be configured several ways: RAID Spanning - All four drives are striped into one large drive, giving the maximum capacity for your TeraStation. RAID 1 (mirroring) - Hard drives (or spanned pairs of hard drives) are arranged in mirrored pairs. Each half of the pair reads and writes exactly the same data. RAID 5 (parity) - All drives in a RAID 5 array reserve part of their data space for parity information, allowing all data to be recovered if a single drive fails. Buffalo Technology recommends RAID 5 for its excellent balance of efficiency and security. 3. A configured RAID array may be deleted by pushing the Delete RAID Array button. This will free up all hard drives listed under Disk Structure. 4. To configure an unconfigured array, put checks next to the hard disks you want included in the array (under Disk Structure) and choose your RAID mode. Click Setup RAID Array when ready. It may take several minutes to complete setting up the RAID array. When it is finished, a Disk Check will run. 5. When RAID Configuration is done, you'll see this screen. To configure a new array, click on RAID Array # and go back to step 2. Page 36
APPENDIX A2 : The symbol indicates supported RAID mode. The symbol * indicates default RAID mode for that model. RAID mode Model RAID60 RAID61 RAID6 RAID50 RAID51 RAID5 RAID10 RAID1 RAID0 TS5200D02 * TS5400D04 * TS-2RZ * TS-8VHL/R6 * TS-6VHL/R6 * TS-QVHL/R6 * TS-WVHL/R1 * TS-RVHL/R6 * TS-XHL/R6 * TS-XL/R5 * TS-XEL/R5 * TS-RXL/R5 * TS-WXL/R1 * Page 37
APPENDIX B: Starting with TeraStation TS5000 series, there is a built-in support feature to create emergency configuration and boot up image backup on a USB memory device. This would allow a simple recovery mechanism in event of system crash. To Backup system configuration and create boot up USB image (or restore a configuration): 1- Launch browser to TeraStation WEB UI and log-in. 2- click [Management] 3- Click next to [Restore/Erase]. 4- Disconnect any attached USB device and insert the backup USB flash memory device in USB 2.0 Port (pay attention there are 2 different USB ports 2.0 and 3.0). 5- From [Target USB drive], select the USB memory device that is connected to the USB 2.0 port of the TeraStation. Page 38
Recommended, select [Create special USB drive for password recovery] and then click [Execute]. [Save setting to USB drive] to save current configuration and write boot up image to the USB drive. [Transfer settings from USB drive] to restore configuration from the USB drive. [Create USB drive to initialize settings] to save default factory configuration and write boot up image to the USB drive. [Create special USB drive for password recovery] to save current configuration with exception to administrator password and write boot up image to the USB drive. Administrator account is reset to factory default (i.e. Admin/password). To restore a previously saved configuration, select [Transfer settings from USB drive] and then click [Execute]. Page 39