time machine network to ZFS / support lock stealing?

Moderators: jhartley, MSR734, nola

Re: time machine network to ZFS / support lock stealing?

Post by chipped » Fri Jan 18, 2013 7:23 pm

I actually reconfigured my ZFS this week, scrap and build from scratch and ran into problems with Time Machine too. Not sure if I did this last time and forgot, it looks familiar. I'll document it this time!! haha

I simplified the instructions a little for newbies to understand easily. These worked perfectly for me.

1) Make sure you have Server App and liberate hack installed
2) Open Server App
3) Go to File Sharing
4) Add file system you would like to use for Time Machine
5) Open Terminal
6) Type "sudo serveradmin settings sharing:sharePointList:_array_id:/Volumes/My/Backup/Location:isTimeMachineBackup = yes"
7) Quit Server App if open
8) Open Server App and Turn on Time Machine
9) Should now be available as a Time Machine Destination
chipped Offline


 
Posts: 22
Joined: Sun Sep 16, 2012 3:31 am

Re: time machine network to ZFS / support lock stealing?

Post by LaMosca » Sun Jan 27, 2013 2:19 pm

It appears you can skip steps 3 and 4 (updated minimized steps listed below). Doing initial backup of our iMac now.

1) create ZFS file system
2) in server app go to File Sharing, enable this FS for sharing (this assumes installation of liberate hack)
3) then open terminal and via serveradmin tool change parameter "isTimeMachineBackup" to yes for this share
6) start the timemachine service

Thanks to all for their contributions in getting this setup and working! I'll decide later if I want to tweak things (create separate filesystem on my mirrored ZFS Time Machine pool that uses compression, etc, but it's at least backing things up for now. We only have about 120GB for backup to a 2TB target at this point.
LaMosca Offline


 
Posts: 11
Joined: Thu Dec 06, 2012 10:42 pm

Re: time machine network to ZFS / support lock stealing?

Post by mk01 » Thu Jan 31, 2013 2:33 pm

beauty of ifs

if you decide to experiment, with zfs is with no cost. create snapshot of what you have. create clone. you can rename the filesystems, so you don't have to update server config. with zero hustle with data. you can try new options, how they perform and via snapshot send to recv original filesystem you can sync both copies. again due to copy on write design, minimal data transfer. and if you later decide, you want to revert, just destroy new fs, and rename back the old one.

years ago every document about backup, data and strategies was starting with sentence like, think twice, because once you deploy, there is no way back. and they have been mistaken. now you don't have to cry later.
mk01 Offline


 
Posts: 65
Joined: Mon Sep 17, 2012 1:16 am

Previous

Return to General Discussion

Who is online

Users browsing this forum: ilovezfs and 1 guest

cron