New answers tagged nas
I would highly recommend that you get in touch with Dell support with this question. Though you're looking for the "fastest" way to achieve this, it would be best to have their guidance in ensuring that it's done the "right" way too. The fastest way to migrate the data is by copying with multi-threaded I/O, which takes advantage of the distributed nature of ...
With Equallogic, it's probably the fastest way to use the built in group move tool for a volume. See here for details. To move a volume to a new pool: Click Volumes. Expand Volumes and select the volume name. Click Move volume to open the Move volume dialog. If you are changing the pool assignment for a synchronous replication volume, you ...
It really depends on your usage, though. Big files that are written once, and then only read? Doesn't fragment, can fill up closer to capacity. Traditional UNIX home directories with lots of small files, some rewriting, lots of snapshots. Maybe even snapshot retention that keeps lots of recent snapshots, but removes some of them while keeping some older ...
Yes, it's still the convention, and yes, it holds true even as you scale. With ZFS, in fact, you really don't want to get to the 75% mark in your zpool too often. Fragmentation, snapshots and general performance tend to be impacted. If building anew, don't start with anything more than 40% utilization and be sure to plan for growth.
You have to make sure there's enough space on the disk. We use Synology as well and run into the same problems. Synology does not automatically delete "old" backups from the external disk if you're doing incremental backups or naming backup files differently with timestamps or other methods. Basically, you have to do this manually while ensuring there's ...
NFS doesn't save file modification times or attributes like that. If you need it, use a LUN and iSCSI to a server that can host the files and use a filesystem that does this (NTFS, etc).
Some thoughts... Can you access the resource using its fully-qualified name, e.g.: net view \\mynas.mydomain.com Assuming you're not already doing this, and this actually works, I'd be thinking along the lines of NetBIOS over TCP/IP (NBT) vs SMB. When using the short name, it might be your server trying to access the NAS box via NBT (TCP 137), as ...
Sounds like a WINS problem. Ping uses DNS, while CIFS uses WINS. Are both the NAS and the server in the same workgroup/domain?
IPV6 has been known to cause some dns related issues, where you can/can't nslookup the host, browse by host, ping by host. If this is a non-prod box, try disabling IPV6 on the NAS and your client host.
Sounds alot like the dns for the iscsi device is now expired. That explains the ip only access. Try putting the names in the c:\windows\system32\drivers\etc\hosts file. Format is: name ip, like: theiscsidevice 188.8.131.52 Try to ping by name, it should then start working
No the existing data will not be erased when you add a disk to the SHR array. The message is simply saying the new drive being added will be formatted. You data and applications will actually remain available during the expansion process; there is no need at all to even stop using the NAS whilst SHR Vertical Expansion is taking place. That said - before ...
Top 50 recent answers are included