I've just got my iMac so for me it was important to get TM up and running before I start doing some real work (and hard play!).
I want to share the lessons learned from my experience and from others in this forum in the hope that it will help others.
I am using a NS4300N NAS from Promise on a LAN with an iMac running Leopard 10.5.2. I connect to it using SMB. It should work with any NAS since the instructions here are not NAS specific. I haven't tried with AFP.
Here we go:
First, on the NAS:
Then, on the Mac:
Et voila! That worked for me, the first backup went really well: < 2 hours for the first 30G or so, I can browse the backups using the interface and recover deleted (on purpose) files.
However, there are still a few unanswered questions, but with experience I'm hoping to be able to answer them. For instance, is this quota thing really necessary? Since the sparse image is limited in space, TM should be able to manage the space used by itself, without the need for quota. If quotas are not necessary then of course the procedure is even simpler: no need for a separate user or separate shared folder. Second, what happens, really, when the sparse image becomes full? That's a bit like the quota question. Some say that the image gets deleted, some say that it doesn't... We'll have to wait and see. I might test it later when I install Leo on my MBP.
Feedback appreciated.
I want to share the lessons learned from my experience and from others in this forum in the hope that it will help others.
I am using a NS4300N NAS from Promise on a LAN with an iMac running Leopard 10.5.2. I connect to it using SMB. It should work with any NAS since the instructions here are not NAS specific. I haven't tried with AFP.
Here we go:
First, on the NAS:
- Login to your NAS and setup a new shared folder, I called mine TMBACKUP.
- Setup a new user called the same as the shared folder. I called mine TMBACKUP as well. The reason I did that is that when I called my user differently (it was tmuser) then the Finder would show me a new non existing mountpoint called like tmuser! I don't know if it's an Apple bug or a problem with my NAS. At this point you can setup a quota for this new user (but see note at the end)
- Assign RW privileges to the user to the TMBACKUP folder
Then, on the Mac:
- Apply the hack 'defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1' as described in this forum.
- This is where it's got to be done properly: in Finder, select Go>Connect to Server. For the server address, type smb://tmbackup@MY_NAS_IP_OR_DNS/TMBACKUP. Click Connect. When prompted, enter the password and save in your keychain.
- Check that you're connected with the right user (not yourself) or the quotas might not be applied! Here's how to do it: copy a (large, 100M or so) file to the TMBACKUP sharepoint. Go to your DS and check the user's usage. If it's gone up by about 100M then you know that you Mac is connected to TMBACKUP with that user. Get that right before going further. It's worth double checking.
- Open Disk Utility and create a new image with the following attributes:
- Location: your home directory
- Save As: your computer name, underscore, mac address. For instance: "Joe Smith's iMac_0012aabbcc34"
- Volume Size: I used 250G, under the 300G quota assigned to the user. It won't take 250G in your home directory, feel free to use as much space as you want, but less than what is assigned to the user on the NAS.
- Image Format: sparse bundle disk image.
- You may want to create an encrypted image, but I haven't tried so I don't know if it works... It should, right?
- Click Create and quite Disk Utility.
- Copy the created disk image to the TMBACKUP directory on the NAS.
- Go to TM, select your TMBACKUP share and enable backups. Backup will start within a couple of minutes or when you click Start Backing Up in the menu bar icon.
- Create an automator Application that connects to your shares first then to the TMBACKUP share. Place this application in the Login Items of your account. For some reason, it didn't work when I used a workflow or a plugin, even though I had associated them with the Automator Runner... BTW, is it just me or is Automator full of bugs???
Et voila! That worked for me, the first backup went really well: < 2 hours for the first 30G or so, I can browse the backups using the interface and recover deleted (on purpose) files.
However, there are still a few unanswered questions, but with experience I'm hoping to be able to answer them. For instance, is this quota thing really necessary? Since the sparse image is limited in space, TM should be able to manage the space used by itself, without the need for quota. If quotas are not necessary then of course the procedure is even simpler: no need for a separate user or separate shared folder. Second, what happens, really, when the sparse image becomes full? That's a bit like the quota question. Some say that the image gets deleted, some say that it doesn't... We'll have to wait and see. I might test it later when I install Leo on my MBP.
Feedback appreciated.