The improvementsįor one, when working with the server itself, you’ll note that the interface is now significantly more responsive. But still, there is plenty to love about the new OS. The point is don’t expect DSM 7 to make data move between your NAS server and network devices faster magically. Still, you’ll need a Multi-Gig switch and a similarly capable computer to experience that.Īnd even then, keep in mind that most NAS servers use regular hard drives with the technical cap speed of SATA 3, 6Gbps.
Some servers, like the DS1621+ or DS1618+, do have the option for 10Gbps via a PCIe add-on adapter. The reason is a server’s network ports generally limit data speeds, and home Synology NAS so far are all Gigabit. So far, I’ve seen no discernible difference in file copying speeds between DSM 7 and DSM 6.
It has a host of improvements, most notably in the user experience.īut let’s get one thing out of the way: You won’t see faster network data throughputs with it. And in my up-to-now experience, the new release is a win. OK, I’m one of those who couldn’t wait to try DSM 7.0 out. Synology DSM 7: An overall major improvement with some surprises
#Idrive synology upgrade
Extra: Some housecleaning before upgrade.Synology DSM 7.0: Lists of supported NAS servers.Third-party apps and DSM 7 compatibility.
(Many) third-party apps not (fully) or not yet supported.Synology DSM 7: An overall major improvement with some surprises.IDrive - when will you fix this issue?!?!?īackup Start Time: Tue Jun 7 00:01:03 2016 So I checked the iDrive log via the iDrive app on Synology, here I see the following error has been happening since the latest DSM update. When I logon to the iDrive website to check my account everything is there, all files I would expect and my account and key are working correctly. It appears to start and stop correctly but when I connect to the iDrive console on Synology to check the backup there are no files shown, as in nothing is backed up to iDrive.
#Idrive synology update
Since the Synology DSM 7393 update iDrive is no longer backing up. Looks like iDrive on Synology is broken again.
#Idrive synology software
It's pretty hard to trust backup software that just completely disregards certain files and file types. There are 3 folders in /Android/, data, media, and obb, but only media and obb get backed up.Īs a test I tried changing where FolderSync saves its settings backup to the /Download/ folder, however it *still* didn't backup the FolderSync settings backup files, even though it does backup other files in the /Download/ folder. I also use a program called FolderSync that saves it's settings backup to /Android/data/dk./files/backup/, however it seems as though the /Android/data/ folder gets completely ignored by IDrive. When I navigate to the /CallRecordings/ directory through IDrive I can't even see the files, so the backup button is greyed out. amr files in it, and when I backup 'Other Files' they get completely ignored. I have an internal /CallRecordings/ directory that has some.
#Idrive synology android
It seems as though the Android app completely skips over certain files and file types. IDrive should have per-user (not global!) deduplication and/or file move detection and handle it more appropriately. Re-uploading wastes the user's bandwidth, and iDrive's bandwidth *and* storage space. Then you can just change the folder that the backup set indicates that file belongs to, rather than re-uploading the entire thing. I realize there is encryption involved, but if the local client simply generates file hashes, you should be able to easily detect whether a file that shows as "new" is in fact simply a *moved* file that already existed. This seems like a fundamental missing feature, and one I expect any good backup program to have. Instead iDrive re-uploaded all 150GB of data, which required saturating my cable connection's outgoing bandwidth for days. After moving this data I expected iDrive to simply recognize that these files had changed location and update the file locations, but not re-upload the data (as the data itself had *not* changed). Both drives are being backed up by iDrive in the same backup set, both locally and to iDrive servers. I recently moved 150GB of data from one drive to another.
0 kommentar(er)
