How to Recover NAS/SAN Data, and Configure a Network-Attached Storage System
Tags: beginners, testing, test, tutorial
Published: 2021-08-24 07:03:50

Are you looking for a solution to recover data from a hard disk within a network storage system like SAN or NAS? If you need to recover lost data from partitions using such file systems as NTFS, FAT, exFAT, ReFS, HFS+, Ext2/3/4, ReiserFS – try Hetman Partition Recovery. It will quickly scan your disk and display the available data on the screen, so you will only have to select the elements you need and recover them

![How to Recover NAS/SAN Data](https://hetmanrecovery.com/pic/blog/a224/how-to-recover-nas-san-data-how-configure-network-storage.png)

##Introduction
Regardless of how much storage space our computers have, we always need more. The issue of storing data is always relevant, for example, if you do some video editing, photography or other work that requires large volumes to store your data, or if you need to create a network-attached storage for a small office.

A viable solution to the problem of storing data for home\office use could be a network-attached storage system, NAS or SAN, depending on the user’s circumstances and needs.

Storing data requires special attention because in case of any hardware issue, error or accidental deletion, you can lose important information, and the recovery process may take quite a long time and not always be successful.

Before you can make your choice, let’s have a closer look at the differences between the two and at how they work.

Further in this tutorial for configuration of a network storage and recovery options, we will find out how NAS (Network Attached Storage) differs from SAN (Storage Area Network).

Also, we will throw some light on how to connect it to a network, configure network access, create a network drive, explore the opportunities provided by iSCSI initiator and how to configure it, and finally, we’ll also cover the procedure for lost data recovery from a SAN/NAS drive.

YouTube: {% youtube PnAW3plM6kE %}

##Network Attached Storage
A Network-Attached Storage (NAS) is a device or server with an array of disks, which is connected to a network. All members of such network can use the data stored on such device.

![Network Attached Storage](https://hetmanrecovery.com/pic/blog/a224/nas.png)

The main difference from a conventional storage device which is connected directly to a computer is that in the case of NAS, the operating system and other software is designed for the only purpose – storing data.

![main difference](https://hetmanrecovery.com/pic/blog/a224/nas-02.png)

A Storage Area Network (SAN) is an architectural solution to enable external storage devices to be connected to servers in such a way that the operating system can recognize the connected network drives as local disks.

![Storage Area Network](https://hetmanrecovery.com/pic/blog/a224/nas-03.png)

SAN is a network designed to ensure connecting equipment and software to servers. It can transfer information from one storage device to another, and help different servers to exchange information, which accelerates data backup and recovery processes.

SAN accesses data at the block level. Its main input-output protocol is iSCSI (Small Computer System Interface). A computer “sees” such storage as its own local disk.

![SAN accesses data at the block level](https://hetmanrecovery.com/pic/blog/a224/nas-04.png)

iSCSI is a network protocol for working with data storage systems, and it lets them interact with computers within a network.

Such storage system can be organized with almost any operating system, because it is built on the logical level and doesn’t require any special hardware for handling data (such as disks or disk controllers). This feature is included into most operating systems and can be enabled easily.

Windows is no exception, and it includes iSCSI components as extra elements.

So what’s the difference between the two approaches? In plain English, SAN is a network drive which enables data exchange in blocks, just as it happens in local disks.

Meanwhile, NAS is a network file system, and a resource with shared access. It is a kind of a file server which can be access through your home network.

SAN is a block-based device delivered over the network. and NAS is a file system delivered over the network.

In fact, NAS provides both a storage and a file system. It is often contrary to SAN, which only provides block-based storage and leaves any file system issues on the side of the “client”. Typical SAN protocols include Fibre Channel, iSCSI, ATA over Ethernet (AoE) and HyperSCSI.

What is inside the block-based concept of SAN? A block is a contiguous set of bits or bytes that forms an identifiable unit of data. This term is used in database management, word processing, and network communications.

So which way of storing data should you choose: NAS or SAN? The answer depends on your needs and opportunities, because these are two different configurations designed for different tasks. Access to files and shared use of information for apps on various server platforms within a local network – choose NAS. High-speed block access to data bases, consolidated storage with improved effectiveness and efficiency – go for SAN.

Despite their differences, SAN and NAS are not mutually exclusive and can be united into a hybrid SAN-NAS system, a combination of file-level protocols (NAS) and block-based protocols (SAN) within one configuration. The file system of a shared drive can also be run over SAN to provide file system services.

The shared use of a storage usually simplifies the task of its administration and adds more flexibility, because for moving the storage from one server to another you don’t have to physically move cables and storage devices around.

##How to connect an SAN storage to a network
In what follows you will learn how to assemble and configure a SAN storage based on D-Link DSN-1100-10 supporting RAID 0, 1, 1+0 and 5.

First of all, assemble the storage, fix the drives in the bays.

![fix the drives in the bays](https://hetmanrecovery.com/pic/blog/a224/san.png)

![assemble the storage](https://hetmanrecovery.com/pic/blog/a224/san-02.png)

Then slide them into the corresponding slots of the main case.

![slide them into the corresponding slots](https://hetmanrecovery.com/pic/blog/a224/san-04.png)

That’s actually all you need to do in terms of assembly. The final step is to connect it to a power outlet and to the network.

To configure the SAN storage, you need to connect it to the network, or directly to a computer, with the help of a network cable. Plug one end of the cable into the Management Port of the storage,

![you need to connect it to the network](https://hetmanrecovery.com/pic/blog/a224/san-05.png)

and the other – into the LAN port of the router.

![LAN port of the router](https://hetmanrecovery.com/pic/blog/a224/lan.png)

Plug in the power cable and connect it to the power outlet.

If you choose to connect the storage directly to the computer, you’ll need a network cable of a special type, known as crossover cable.

![choose to connect the storage directly to the computer](https://hetmanrecovery.com/pic/blog/a224/lan-02.png)

For such connection type, you plug the other end of the network cable into the LAN port of your computer instead of the router.

![computer instead of the router](https://hetmanrecovery.com/pic/blog/a224/san-06.png)

Turn on the storage system and wait until a LED light appears on the front panel – it means the server has booted.

![LED light appears](https://hetmanrecovery.com/pic/blog/a224/san-07.png)

##Initial configuration of the network storage
For initial configuration of the storage, you should open a browser on your computer which is connected either to the network or directly to the storage. Type the network storage address in the corresponding line – this address is specified in the user’s manual or other documents that come supplied with the storage. After that, the web assistant will start looking for it.

![Initial configuration of the network storage](https://hetmanrecovery.com/pic/blog/a224/d-link.png)