NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
CryptoLocker and a backup strategy
I am requesting the community to evaluate and criticize this approach to CyberLocker We are basically a Windows shop and we are scared to death about the CyperLocker virus. From what I read, ...
Thanks for clarifying the cryptolocker info. As your links point out there is other ransomware too.
Bains wrote:You said disable SMB for these hidden shares most of the time. That sounds like a great idea since those shares would not need to be accessed except in case of an emergency and the setting could be turned on at that time. In its place would I just use RSYNC as the file protocol??
You described the backup as I envisioned it – multiple days each independent of the other using the ReadyNAS backup capability – disk to disk operation.in our case within the same cabinet.
Yes, I was thinking there'd be one hidden SMB share used as the windows backup destination, and 7 rsync protocol shares (perhaps with https also enabled, so you check on them easily). You'd enable SMB either to audit them, or to restore data - otherwise it would be off.
Note to do this you'd need to set up the rsync backup jobs' source as an rsync server, using 127.0.0.1 as the source IP address.
Puzzled.
I changed our test location to remove SMB protocol and add RSYNC.protocol.
At that time it seemed to eliminate a lot of data but I did not care.
I changed our test backup job.to go from one share to the Test share (no SMB access, only RSYNC)
Did not encounter any issue.
Ran job and it worked.
I did not encounter the backup jobs' source as an rsync server, using 127.0.0.1.
Did I flub this test?
Bains wrote:
Puzzled.
I changed our test location to remove SMB protocol and add RSYNC.protocol.
At that time it seemed to eliminate a lot of data but I did not care.
I changed our test backup job.to go from one share to the Test share (no SMB access, only RSYNC)
Did not encounter any issue.
Ran job and it worked.
I did not encounter the backup jobs' source as an rsync server, using 127.0.0.1.
Did I flub this test?
What settings did you use?
Share established without SMB and with RSYNC -- called Test
Established a Backup event
Source was an exsiting share
Destination was share "Test"
No other options selected.
Manually started the backup operation and it completed.
did not encounter the backup jobs' source as an rsync server, using 127.0.0.1. That is different than you suggested so that is why I am asking.
What you did was choose local for both the source and the destination. That uses straight linux copy - which is not incremental.
If the backup share is large (with most stuff not changing) then you want incremental backup - which means rsync.
Incremental requires that you choose "remote" for either the source or destination. Since you want to isolate the destination (which is the one you enabled rsync for), then make the destination remote.
Then select "rsync server" as the protocol for the remote machine, and use 127.0.0.1 as the host IP address.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
