Revolving around the core of technology
I want to buy a NAS and syncrify licenses for office.
The NAS will be offsite over internet connection. The first fill can be on LAN, later (delta) backups per DSL.
Every of the 6 PCs will take an daily backup with about 80 changed files.
Is a NAS With a Marvell CPU sufficient or is a NAS with Atom-CPU needed.
Thera are significant speed differences? My reason for this question is the price, I have to invest in syncrify and NAS.
Dear Lars,
We recommend an Intel Atom CPU for Marvell. Most NAS do not run any CPU intensive tasks. Syncrify on the other hand requires CPU chrunching on the server, particularly when you enable versioning. Therefore, a better CPU and a faster hard drive is always recommended.
Another problem with Marvel CPU is getting Java installed on it. AFAIK, Marvell is based on ARM and a Java VM is available. Getting it and installing it may be somewhat challenging.
Regards,
Imran
Many thanks for the info!
Therefore the question of Benny in the forum "feature request" also very interesting for me: "Disaster Recovery over slow connection".
One NAS will be at the office, the other at home. If one is stolen or office burns down, then I have the backup on the other offsite. The connection is relative slow: 500 kBit upload each, 6 MBit download.
Dear Lars,
Disaster recover over a slow connection is similar to running a Syncrify client on one machine and transfering the data to the other. This will use rsync and therefore, won't put a strain on your network.
The only reason why the current DR implement is discouraged over a slow network is that it transfers the entire file. This is done to keep the CPU free for real backup jobs.
Imran
Thanks for info!
In the next weeks I will buy licenses. Currently works evaluation period.
NAS are picked out: Netgear ReadyNAS 300 series. I think, installation on these are simplest because there have a clean Debian system with paket manager on board. The other like Qnap or Synology looks like more "boxed systems". I hope this is the right choice. The future will show.
Is there a plan for more time options on client? E.g. if backup fails, because the notebook is in my bag or with no connection to server with other reasons.
In my opinion a additional preference are useful: if fails on defined time on daily backup, then retry every hour or something like that.Another idea is a option for retry if backup-server is accessible.
Then a notebook backup fails, and then the notebook checks e.g. every ten minutes wether server is accessible.
sorry please for my scrappy english.
Hi,
Just curious: any particular reason for buying a NAS just for this? Why not use a regular desktop from Walmart that costs $300 and put Debian on it? That will have an AMD or Intel cpu powerful enough to run Syncrify and a few other things if needed.
One suggestion: don't use daily backup for scheduling. Interval works much better. For example, if you set the interval to 10 hours, if your machine goes to sleep and wakes up after 12 hours, a backup will run immediately.
Danny
Did you purchase the ReadyNAS 300 series and install Syncrify OK? We have a ReadyNAS 314 and have had difficulties getting it stable. It installs, but Java tends to crash frequently.
I have limited time, therefore I write in german.
Ich habe es installiert und es läuft wunderbar.
Gelegentliche Abstürze könnten folgende Ursache haben:
Wenn Synrify eine Datei inkrementell sichert, benötigt es ein temp-Verzeichnis. Syncrify empfängt die geänderten Teile der Datei und setzt zusammen mit der auf dem NAS vorhandenen Version der Datei die geänderte Datei zusammen. Dies geschieht im temp-Verzeichnis.
Bei einer großen Datei sieht das dann so aus:
root@NasCranzahl:~# vi /opt/Syncrify/config/server.properties |
Inhalt der Datei:
java.io.tmpdir=/NAME_OF_VOLUME/NAME_OF_NEW_SYNCRIFY_TEMP_FOLDER
check: ist die Datei da?
root@NasCranzahl:~# ls /NAME_OF_VOLUME
BackupDeltaCopyDestEncrypt BackupRsncSource ReplicateSystemTest home
public_ssh_key.txt NAME_OF_NEW_SYNCRIFY_TEMP_FOLDER