The Network Attached Storage (NAS) devices are designed to add storage space to users on their local area networks (LANs).
NAS devices are "Plug 'n' Play" and can be easily attached to networks. These devices differ from traditional network servers in several ways; they do not have a keyboard, mouse, or monitor, and mostly use operating systems that emulate different server environments including Windows 2000, Windows 2003, and UNIX servers.
Operating Systems running on Network Attached Storage (NAS) Devices:
The operating system running on the NAS devices can determine the level of protection provided by Backup Exec (tm) for Windows Servers, which is as follows:
- NAS devices using Windows 2000 and Windows 2003 Operating Systems
- NAS devices using operating systems that emulate Windows or another operating system
- NAS devices using operating systems other than Windows
I. NAS Devices using Windows 2003 and Windows 2003 Operating Systems
The NAS devices in this instance are seen as remote Windows 2000 and Windows 2003 Servers. Therefore a Remote Agent for Windows Server (RAWS) and RAWS license will be required to back it up. Other Backup Exec options can be used during backups, except the Intelligent Disaster Recovery (IDR) option, which can only be used when a bootable device (tape, CD-ROM, or diskette), a keyboard and monitor are attached to the NAS device. These are not available in most NAS Configurations.
II. NAS Devices Using Operating Systems that 'Emulate' Windows 2000 and Windows 2003 Operating Systems
In this instance where the NAS devices are using an operating system properly 'emulating' Windows 2000 and Windows 2003 Servers, the emulation becomes transparent to Backup Exec. Files and directories can be backed up as 'shared network volumes' using Backup Exec for Windows Servers. In this type of configuration, the following Backup Exec options cannot be used:
- Backup Exec Intelligent Disaster Recovery (IDR) option
- Backup Exec Remote Agent for Windows (RAWS)
- Backup exec Open File Option (OFO)
For example: SNAP server comes into this category.
A <Snap> Server uses SAMBA to emulate a Windows volume. For Backup Exec, NAS/<SNAP> Server is just another Windows server on the network. This is because NAS units have the ability to mimic "real" Windows 2000/2003, UNIX, or Macintosh servers.
While backing up <SNAP> servers, Backup Exec will think it as another Windows Server on the network and thus requires the Remote Agent even though it is not possible to install it. The selections for the <SNAP> Server Backup need to be created through User-defined Shares.
Note: In Backup Exec 12.5 and earlier, a RAWS License is not required to back up these systems via User-defined Shares. The backup job log will indicate a failed backup because of the Remote Agent not being present and a licensing error. Confirm that the amount of data backed up compares with what is physically on the share and run test restores to validate the integrity of the data that was backed up.
Starting with Backup Exec 2010, at least one RAWS license is required to back up NAS systems.
III. NAS Devices Using or Emulating other Operating Systems
Backup Exec will not be able to back up NAS Devices that are not using the Windows 2000/2003 Operating System or that is emulating the Windows Operating System.
CIFS shares that are hosted on a NAS system can be backed up.
IV. Creating Backup to Disk folders on NAS Devices
If a NAS Device is emulating Windows and is not truly a Windows Operating System, please confer with the NAS manufacturer for assistance before creating backup to disk (B2D) folders on the NAS Device. Symantec does not certify non-Windows NAS Devices and if the operating system is not a true Windows Operating System, Symantec may not be able to properly troubleshoot a proprietary operating system.
Please Note: NetWare Servers cannot be used as a Backup-to-Disk (B2D) Target because of file system rights issues.