I have not tried this with the isilon, but I have had some issues with doing it against linux or FreeBSD running netatalk. Frequently, Time Machine thinks that the backup is corrupt and it needs to be regenerated.
According to a post on Server Fault this is common, and the implication is that in general, roll-your-own-time-machine is flakey.
If I were you, though, I'd just try it out for a while and see how it works. Do frequent test restores.
Peter_Sero
4 Operator
•
1.2K Posts
0
April 29th, 2014 17:00
> one puzzler is in the mount option it specifically says ,insecure, : is there an isilon equivalent? It may not be necessary or evean desirable.
"insecure" allows connections from ports above 1024
The document also suggest "resvport" on the Mac side,
which means ports lower than 1024. Somewhat inconsistent advice.
Mounting will be done as root on the Macs:
How will you prevent users from accessing other users' backups then?
One export per user, "secured" by client IP? not very secure.
In case you backup the Isilon to tape (NDMP), beware
that even after minor changes in a user's backup,
the whole Time Machine image file will to to tape...
You might also consider using rsync or unison,
which create file-by-file replica on the backup side.
hth
-- Peter
ICPSR
10 Posts
0
April 29th, 2014 19:00
I have not tried this with the isilon, but I have had some issues with doing it against linux or FreeBSD running netatalk. Frequently, Time Machine thinks that the backup is corrupt and it needs to be regenerated.
According to a post on Server Fault this is common, and the implication is that in general, roll-your-own-time-machine is flakey.
If I were you, though, I'd just try it out for a while and see how it works. Do frequent test restores.