D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: Lucid on December 13, 2007, 05:25:31 PM
-
Is there a way to transfer the files between volumes without having to transfer them to the PC and back to the NAS? I tried setting up two FTP accounts and doing a FXP but it isn't supported. It would be a cool item for a NAS to support.
TIA
-
Is there a way to transfer the files between volumes without having to transfer them to the PC and back to the NAS? I tried setting up two FTP accounts and doing a FXP but it isn't supported. It would be a cool item for a NAS to support.
TIA
You can schedule incremental backups from one volume to another by using the download scheduler on the main login page.
-
The incremental option does not work consistently in firmware version 1.03. Mostly it performs a full backup which is useless for daily backup if you have a lot of data. You also need to set up one schedule per root folder.
I suggest that D-Link implement a simple one button backup feature that makes a daily incremental copy of all data from volume 1 to volume 2.
Best Regards, DN
-
well...if you are going to use it as a back up why not implement raid then for the same task?
I do not want an exact copy of everything on both drives, I would like to see that ability to reorganise files without having to congest the network. For example I have personal media files and training videos files on one drive. It turns out the media files are eating up space and I have to move the training video to the other volume. I do not want to spend a couple of hours transferring the files from the NAS vol1 - to my computer - and back to the NAS vol 2. That is essentially what happens when I drag over files from one volume to the other.
Tips?
-
As a workaround I am using the scheduler to organise file. It's not a real solution but it is workable for now. NOTES: It won't show you a progress rate. The other thing I was thinking about was that the abiliy to transfer files between volumes may not be feasible to do through the OS with out a driver...nassty...however one method would be through the web interface. I would also love to see the ability to rar/unrar, zip, and par natively. It would be a great feature for any NAS....and none of them have it...wink wink ...knudge knudge....xD
Merry Christmas!
Lucid
-
well...if you are going to use it as a back up why not implement raid then for the same task?
Some people may not want to use RAID.
-
well...if you are going to use it as a back up why not implement raid then for the same task?
Because RAID is not intended to be a form of backup, it only protects against a drive failure, there are numerous other causes of data loss that it will not protect you from.
-
well...if you are going to use it as a back up why not implement raid then for the same task?
- Incremental backup of everything from vol 1 to vol 2 also help recovering files that are deleted by mistake, which happens in my family.
- Using one drive (except during backup) uses less power which means less fan noise.
Regards, DN
-
True.
-
SOLUTION!
OK, here's the deal. If you are cut/copy within the same window (of course you have to navigate up and around) you will have no problems. If you cut then copy into another window you end up copying across the network.
Cheers!
-
I'm presently testing this feature. I was using "SecondCopy" to backup data, and keep track of deleted file, but the "hardware" solution (DNS-323) seem better and faster. I like it.
I found beter to have the ability to copy "incremental" file and folder from one volume to the other, than use the mirror. It's a very good "feature" on this unit.
I was using a Buffalo NAS 300 Go before. I sold it on eBay, and purchase this unit because of the interesting feature and RAID function. Now i see the Scheduler, and i don't want the RAID anymore ....
Q? : Where are located the deleted file or modified file after the Schedule event start ? Are they moved somewhere ? (where)
-
Actually this doesn't work!!!!
However i did find out a way in which you can transfer files across the two harddrives without using the network.
1)
Install Telnet by following this link
Removed. You know why.
2)
login using telnet by using the ip-address of your device assinged by the router or by you.
3) use cd, ls, mv functions to navigate and copy files between the drives.
cd - changes directories
ls - lists what's inside it
mv will move files from one location to another
...you can also you cp for copy
example
/mnt/HD_a2/BT/Complete # mv Smallville* /mnt/HD_b2/Movies/Smallville
this command starts after the # sign with the command "mv" for moving
and it will move all the files that start with Smallville from the bittorrent completed folder to a folder Smallvile on the second harddrive.
/mnt/HD_a2/ = Volume_1
/mnt/HD_b2/ = Volume_2
doing [command] ? will reveal the help and options for that command
This will move about 2 gig in couple of minutes...
-----------------
now lets find a way to unrar :)
SOLUTION!
OK, here's the deal. If you are cut/copy within the same window (of course you have to navigate up and around) you will have no problems. If you cut then copy into another window you end up copying across the network.
Cheers!
-
I use rsync to copy specific folders from drive A to drive B. You can setup a script to do this nightly at specific times. The nice thing about this is that it will only copy files that have changed, and not move everything again.
http://forum.dsmg600.info/t1150-Tutorial%3A-Backup-Everything-from-once-night.html
-
The original post simply asked for a way to directly transfer files between two hard drives that are basically on the same controller. Then things start getting weird: command lines and Telnet, incremental backups and RAID. Why is this so difficult? When I moves files between my computer's hard drives, they're not send out to someplace on my LAN first, then back. So why doesn't the DNS-323 treat its 'local' drives the same way? Why isn't Samba set up to minimize network usage instead of maximizing it?
[End of Rant]
-
The original post simply asked for a way to directly transfer files between two hard drives that are basically on the same controller. Then things start getting weird: command lines and Telnet, incremental backups and RAID. Why is this so difficult? When I moves files between my computer's hard drives, they're not send out to someplace on my LAN first, then back. So why doesn't the DNS-323 treat its 'local' drives the same way? Why isn't Samba set up to minimize network usage instead of maximizing it?
[End of Rant]
i wonder if it would do a disk to disk transfer without using the LAN if you use the the web file server interface rather than a PC based explorer window.
http://192.xxx.xxx.xxx/web/wfs_login.asp
-
The original post simply asked for a way to directly transfer files between two hard drives that are basically on the same controller. Then things start getting weird: command lines and Telnet, incremental backups and RAID. Why is this so difficult? When I moves files between my computer's hard drives, they're not send out to someplace on my LAN first, then back. So why doesn't the DNS-323 treat its 'local' drives the same way? Why isn't Samba set up to minimize network usage instead of maximizing it?
[End of Rant]
There is a very simple explanation for why it works that way - it's only doing what you told it to.
When you move files between your computer's hard drives, you're doing so from the computer's "console" - the screen, keyboard and mouse are directly attached to the same computer (or controller) as the disk drives.
The DNS-323 does in fact treat it's hard drives in exactly the same fashion, and if you were moving the files using a keyboard directly attached to it, it would transfer the data from the first drive to the second without sending it across the LAN. In case you aren't aware, there is a serial interface on the board in the DNS-323 and if you so choose you can connect a terminal to it using a suitable adapter and move the data. Telnet is simply a way to run a terminal session across the network without having to crack the unit open.
Let's go back to your PC (PC1) - if you had two drives in it and shared those drives out, and then connected to them from a second PC (PC2) and using the second PC moved files from one volume to the other, the data would flow from PC1 across the network to PC2 and then back again to PC1 - exactly like what happens now with the DNS-323.
You're telling the computer (PC2) to go and get the file from that network share on that other computer across the network (PC1 or the DNS-323) and put it on that other network share on that other computer accross the network (again PC1 or the DNS-323) - your computer lacks the intelligence to know that both network shares are actually on the same computer, so it obediently goes and fetches the file and then sends it back - because that's what you said you wanted done.
Get the idea now? That's how Network Attached Storage works - be it Windows or SAMBA.
-
Try setting up a Scheduled backup from one drive to the other save the task and unplug the Ethernet cable and see if the backup completes.
-
There is a very simple explanation for why it works that way - it's only doing what you told it to.
...
Get the idea now? That's how Network Attached Storage works - be it Windows or SAMBA.
this is a very good explanation. thanks.
:)
a thumbs up for this.
I did notice that a command to transfer files between HDDs if executed from my vista box to the dns 323 is taking too long for a normal file transfer.
it is much faster if I telnet to the dns box and execute the command from there.
your explanation makes sense of things.