The MxHub offers NAS storage in addition to local storage.
You can see how to set this up in this article
1. Create a Network Share on your NAS
Important: The NAS User needs to have Read and Write permissions
Mobotix recommends the following two systems for direct network sharing storage
RAID recommended: RAID 10 (Own RAID Array for MxHUB)
Direct attached storage (DAS) is a cost-effective entry into the storage sector. Here, the storage is connected directly to the respective server via a point-to-point connection (Serial Attached SCSI / SAS).
Thanks to direct attached storage, the hardware expenditure for the company is minimized: No additional switches or management units are required next to the server. Furthermore, there is no additional protocol stack. For this reason, this storage option is extremely performant, especially conceptually: No protocol overhead and low runtimes or latencies are characteristic of DAS.
However, these advantages are also offset by some weaknesses: Direct Attached Storage offers only limited scalability in terms of capacity - only scale-up is possible. In addition, DAS can only be attached at a short distance from the host, which can be a problem especially when space is very limited: A maximum distance of ten meters to the server is possible with a SAS connection.
Strengths and weaknesses of DAS
+Low hardware overhead
+No additional protocol stack
+Conceptually very performant
-Exlusively on one host
-Limited scalability in capacity
-Limited distance from host to storage
An alternative to direct attached storage is the so-called storage area network (SAN). In the meantime, a connection is usually made via Fibre Channel, although Infiniband is also possible. With this storage variant, the clients therefore access the servers via Ethernet. These in turn have their own Fibre Channel infrastructure, which is set up in the same way as the Ethernet structure. In plain language, this means that a Fibre Channel HBA is used in the same way as the network interface controller, and a Fibre Channel switch in the same way as the network switch. This makes it possible to connect several storage systems. A server can easily access several storage systems, which enables relatively good scalability - also in terms of width.
In addition to this strength, the high transfer rates in the SAN should also be mentioned. Thanks to fiber-optic transmission and the Fibre Channel protocol, these roughly correspond to those of a DAS with low overhead. In contrast to direct attached storage, however, greater distances can be covered with a storage area network. In addition, a SAN partially simplifies the administration of the storage, since only one central point has to be managed. On the other hand, however, an additional infrastructure layer is added, which also requires administration effort. Another weakness is the complicated configuration. This increases the administration effort considerably, especially at the beginning. The administrators usually have to learn their own set of commands, which is why some knowledge is necessary before a SAN can be used in a cost- and time-saving way.
Strengths and weaknesses of SAN
+Direct accessibility of all components to each other
+High transfer rates
+Greater distances possible than with DAS
+Cost savings through storage consolidation
+Simpler administration through centralization
-Additional dedicated infrastructure layer for storage
-Problems with interoperability
-High cost hardware components
RAID recommended: RAID 5/6 (Own RAID Array for MxHUB)
The last storage solution we would like to introduce in this article is Network Attached Storage (NAS). This is storage that is connected to the existing IT infrastructure via an Ethernet switch. One of the advantages of Network Attached Storage is the simple connection to the existing network or to the respective clients. The NAS is connected via standard interfaces for network controllers. This includes, for example, RJ45, SFP+,SFP28, QSFP+ or QSFP28. Particularly with 1 Gbit/s Ethernet, but also with 10 Gbit/s, a possible bottleneck can arise here depending on the application and the data carriers used (flash or HDD). This should be clarified before implementation.
In contrast to direct attached storage, connecting a NAS involves a detour via the Ethernet switch, which ultimately leads to a high load on the existing LAN. Furthermore, the underlying TCP/IP protocol is not optimized for storage traffic, as a relatively large protocol overhead is created. However, there are solutions to both problems: The protocol can be optimized by using jumbo frames (MTU 9000), and the high load on the LAN can be mitigated by a dedicated storage network with high bandwidth of 10 Gbit/s or more.
These disadvantages are offset by numerous advantages such as concurrent access by multiple clients: thanks to networking file systems (SMB/CIFS, NFS), this is easily possible. The compatibility and operability of network attached storage is guaranteed thanks to uniform standards. In addition, a LAN of 10 Gbit/s or more is now an alternative to FC-SAN in real operation, since relatively good performance can already be achieved with this.
Strengths and weaknesses of NAS
+Easy connection to existing network
+With dedicated 10 Gbit/s LAN in real operation through alternative to FC-SAN
+Easy connection to clients
+Easy concurrent access of multiple clients thanks to networking file system
+Compatibility and operability guaranteed
-Underlying TCP/IP protocol not optimized for storage traffic
-Additional high load on the existing LAN
2. Create a Lokal Admin User on your Windows Machine
a) In case you are in a workgroup :
- Create a local administrator account where the Recording Server resides.
- Create a local administrator account on the NAS drive with exactly the same username and password.
- Set this account to be the Log On account for the Recording Server and Image Server. Restart the service.
Click Start and type “Services” then click Enter. (Or, alternatively, click Start → Run → type “services.msc” in the Run dialog and press Enter.
Locate the MOBOTIX HUB Recording Server service, double-click it, and click the Log On tab.
Click on this account and then Browse.
Search the administrator account which zou have created
Put your administrator account password into the fields
Restart this Service
b) In case you are in a domain :
- Pick up/create a domain account that will be used for the connection between the MxHUB Recording Server and the NAS storage
2. Set this account as local administrator on the Recording Server.
3. Set this account as local administrator on the NAS drive.
4. Go to the Recording Server service and set this account to be the Log On account. Restart the service.
Troubleshooting when the RecordingServer does not start after setting the Login User for this service.
Right Click on the RecordingServer Icon => Server Configurator…
Select Encryption and click on Apply
After a while the message: Encryption configuration successful should appear
Start the RecordingServer again.
Now the RecoringServer should start normally again
3. Setup the Recording Storage
→ ManagementClient → Recording Server → Storage
Double Click on you Recording Path
Enter the Path of your NAS Share
Now the Recordings are send directly to the NAS
4. Create an Archive which is stored on your network Share
→ ManagementClient → Recording Server → Storage
click on the marked symbol
Setup the Archive Settings and in the path field fill in your Network Share