Time machine slow in leopard server unlimited client

I installed today the leopard server unlimited client,
The time machine is in "preparing".. and it keepts preparing....
the backup drive is another internal drive.
1)it seems that it has taken a lot of time to backup an operating system disk!
2)maybe I am stupid, but 20 years ago, the scientific computers had versions for file. with that you could avoid all that "time machine" stuff and delays and need to backups.. with versions and an array you get the time machine instantly!.. with out of this waste of hours-time waiting for the " newest time machine".
.. 20 years after, an a bad solution is the top of the mac marketing???
i hope tomorrow the time machine could show more than a "preparing" window...

Are you backing-up the clients, or the server, or both?
Like most folks here, I'm not very familiar with the Server product, but I understand TM can do either or both.
You may find better advice in the Server forums, at: http://discussions.apple.com/category.jspa?categoryID=96

Similar Messages

Is Time Machine bad on Leopard Server?

Hi,
I'm pretty much a newbie when it comes to setting up osx server, however is it true that using time machine to backup Leopard Server is bad? Our office is running leopard server off a G5 dual-core 2.0 with 2.5GB ram. The boot drive is mirrored in a raid 1, and we have a Sonnet D800RAID (RAID 5) connected via ATTO raid card. All employees will work off the server, meaning all projects will be stored there on the RAID 5.
We wanted to use time machine to do incremental backups of the RAID 5, however apparently from what I hear, using time machine on a server is a no,no. Why though? Does it really use a lot of the CPU running in the background?
I really want to implement, but not if there's a BIG problem going to arise from it in the future.
Thanks in advance~
noiceT

Hi
I guess it depends? The current version of the Server Admin Manual available here:
http://images.apple.com/server/macosx/docs/ServerAdministration_v10.5_2ndEd.pdf
does not have a lot to say about it one way or another. However the previous version of the Admin Manual clearly states on page 37:
*+"Leopard’s Time Machine feature is not recommended for server file and system backup of advanced configuration servers"+*
If you purchased the boxed copy of Leopard Server 6-9 months ago it may still state this in the provided manual? There have been some who have used it successfully when the server is configured as Advanced. I have no personal experience of this but if you search the Mail Forums you should find recommendations to not use it if configured as Advanced/Mail Server. Its not so much backing up but rather problems develop when restoring.
I've not had chance to test with Open Directory, perhaps others have?
Just a thought but I would consider carefully (depending on server role) if I had need to use it for the Server itself. On the other hand I think it works fine as a source for client backups.
Tony

Time Machine on Snow Leopard Server

I would like to setup a backup service using Time Machine of a Mac Pro Snow Leopard Server (10.6.5) to an external hard drive connected with USB. Are there any gotcha's with this type of setup that I need to be aware of? My faint memory recalls an issue with Time Machine backing up a server.
The server is mainly used for file sharing in a small (<10) person office.

Are you backing-up the clients, or the server, or both?
Like most folks here, I'm not very familiar with the Server product, but I understand TM can do either or both.
You may find better advice in the Server forums, at: http://discussions.apple.com/category.jspa?categoryID=96

Reliability of Time Machine on Snow Leopard Server

I ran across a message that even though Time Machine is included in OSX 10.6 Server, Apple does not support its use in this system.
Now I can't find it again. Is that true?
Not trying to clone an entire computer, just the Library (for WebServer and QuickTime Streaming), would it be reliable enough for this?
I am using the second internal drive for the backup disk, and already have the entire computer backed up to an external image.
Not asking about strategy, but does Time Machine work reliably for what I am doing?
Second question, is TimeMachineEditor a good way to change the backup time in OSX Server 10.6?
Want to now make it in the middle of the night.
Thanking anyone for answers.
Frank
(I have to say this new forum structure is poor compared to the last one! Much harder to find topics and subtopics, who cares about the fancy toolbar)

It's actually quite usual for backup programs to suck at databases. I believe that even the high end backup systems like Retrospect etc have to take the database off line before it'll successfully perform the backup.
Databases just don't like to be backed up! In fact, if you tail the log in OS X server, when you perform an archive on it, it checks to make sure that the parts of the database that it's backing up that moment are not in use. For a program like time machine, that would just not be reasonable considering the way that it's designed to work.
They include it with OS X server so that tech guys like us can tell it NOT to back up things like the .mach folder and the /System Folder. ...and the netboot images etc. Most importantly, we tell it NOT to back up the Database files.
What it SHOULD back up is those files that your users can delete accidentally. That way you get to look like the hero when you get it back for them!
All that said... Here's what I do with time machine:
I don't back up any files that are duplicated everywhere else. (netboot images, restore images, CD/DVD images) I don't back up Mail, MySQL, and OD. Lastly, I don't back up my Roaming Profile shared folder.
Since my Open Directory only has user information in it, and I don't often delete or add users, I only perform an archive every other month or so.
MySQL gets a back up once a month. - though I only use the MySQL databases for a Forum that I've set up for the students at my school. If they lose a months of social networking posts, I'm not too concerned about it.
Mail... Well, I don't actually use mail on OS X. Being an education institution, we get google apps for free. So I got that route. One less thing to manage.

Time Machine Slow - Snow Leopard

I have been using time machine for almost a year with no problems, but today it started taking forever to back up. There is plenty of space on the external drive, but after about 5 minutes it has only backed up 21 KB out of 79GB!
I used disk utility on my external my mac drive and it said everything was okay.
Does anyone know why it could be doing this?

It does take a while over a network; there's a lot of "setup" that seems to be required.
You might try the things in #E4 of [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).

Can Time Capsule be used as a time machine on a Windows Server. Is this possible, and how do i configure this?

I like to use the new TC in my office as a time machine on a Windows Server. Is this possible, and how do i configure this?
In fact my plan is to make the first back up by connecting to the server via an ethernet cable, but thereafter i like to bring the TC to my home and perform the incremental backups over the internet. This is for safety reasons, in case for example the office is broken into, or flooded, or fire (god forbid).
I sincerely hope it is possible, and not complicated.
Alternatively i would not mind replacing our current Windows server 2003 with an Apple server, but all computers in the network (except mine) are Windows 7 or 8. Would it work?
Thanks in advance.
Paris

I will consider the WD My Cloud device.
It is a NAS.. it is designed to provide a cheap centralised file storage.
What is NAS?? http://en.wikipedia.org/wiki/Network-attached_storage
A file server like windows uses heaps of power to do very little.. in your setup.. In most setups like SBS it will do exchange server and provide a heap of useful connectivity to your clients.
Since you are not using the windows server in anything but simple file serving you can replace with a NAS..
Problem with the TC is, it is a router with a hard disk inside.. designed specifically for Time Machine.. it fails to provide what a NAS does.. easy access to any clients, local or remote.. TC is designed by apple for apple and the rest of world is not really invited to the party.
It provides no backup.. no data protection.. and is so specifically apple orientated I do not think it works at all well with windows.
For a simple example.. windows will have file issues with large files.. because it is only NTserver FAT32 to windows.. bad luck if you have large files.. !!
Plainly if you use active directory in windows that facility is gone.
I just like Apple products, find them more stable than Windows and easier to use. Plus i can access the server from home if it is an Apple Server.
If you only need remote access for yourself that is fine.. too bad for the windows clients I guess.
Or you open it up to the world and bad luck for security.
Apple do not design for mixed environment.. in fact with the TC there is no provision for windows access officially at all.. so anything you do is a fudge.
You can use the TC for your Mac backups within the network.. that is fine. Apple provide no software at all to help with your windows clients.

Time Machine Service Page in Server App says "Error Reading Settings"

I have a Mac Mini running 10.8.3.
For some reason the Time Machine Page in the Server App refuses to work properly. If I reboot the server it looks fine for about 10 minutes. It displays the backup location and the list of individual backups. Then I get this message:
25/03/2013 14:37:51.673 Server[286]: Error: The server '127.0.0.1' reported an error while processing command of type: 'readSettings' in plug-in: 'servermgr_timemachine'. Error: Error Domain=XSActionErrorDomain Code=1000 "An unknown error occurred" UserInfo=0x7fdc1b2445e0 {NSLocalizedDescription=An unknown error occurred}
Also the Time Machine page in Server Apps is blank apart from "Error Reading Settings" and the slider at the top says Time Machine is off.
However Time Machine does work for some clients.
Anyone got any idea?
I think it started having problems when I got a "The network confirguration has changed" alert.

Hi Linc Davis
here are the logs from reboot to failure to load:
26/03/2013 16:57:50.256 servermgrd[1379]: [1379] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 16:59:55.633 servermgrd[1527]: [1527] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 17:01:58.077 servermgrd[1546]: [1546] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 17:04:03.937 servermgrd[1561]: [1561] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 17:04:05.220 Server[1154]: Error: The server '127.0.0.1' reported an error while processing a command of type: 'readSettings' in plug-in: 'servermgr_timemachine'. Error: Error Domain=XSActionErrorDomain Code=1000 "An unknown error occurred" UserInfo=0x7ffac4620f20 {NSLocalizedDescription=An unknown error occurred}
26/03/2013 17:06:07.359 servermgrd[1666]: [1666] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 17:06:07.829 Server[1154]: Error: The server '127.0.0.1' reported an error while processing a command of type: 'getBackups' in plug-in: 'servermgr_timemachine'. Error: Error Domain=XSActionErrorDomain Code=1000 "An unknown error occurred" UserInfo=0x7ffac480f000 {NSLocalizedDescription=An unknown error occurred}
26/03/2013 19:18:51.737 servermgrd[1678]: [1678] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 19:18:51.777 servermgrd[1678]: [1678] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 19:20:55.346 servermgrd[2846]: [2846] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 19:20:55.381 servermgrd[2846]: [2846] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 19:22:57.682 servermgrd[2861]: [2861] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 19:22:57.683 servermgrd[2861]: [2861] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 19:22:58.114 Server[1154]: Error: The server '127.0.0.1' reported an error while processing a command of type: 'readSettings' in plug-in: 'servermgr_timemachine'. Error: Error Domain=XSActionErrorDomain Code=1000 "An unknown error occurred" UserInfo=0x7ffac4836250 {NSLocalizedDescription=An unknown error occurred}
26/03/2013 19:25:00.016 servermgrd[2872]: [2872] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 19:25:00.135 Server[1154]: Error: The server '127.0.0.1' reported an error while processing a command of type: 'readSettings' in plug-in: 'servermgr_timemachine'. Error: Error Domain=XSActionErrorDomain Code=1000 "An unknown error occurred" UserInfo=0x7ffac494c120 {NSLocalizedDescription=An unknown error occurred}
26/03/2013 19:26:02.690 Server[1154]: Error: The server '127.0.0.1' reported an error while processing a command of type: 'getBackups' in plug-in: 'servermgr_timemachine'. Error: Error Domain=XSActionErrorDomain Code=1000 "An unknown error occurred" UserInfo=0x7ffac4826a80 {NSLocalizedDescription=An unknown error occurred}
26/03/2013 19:33:51.868 servermgrd[2886]: [2886] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 19:33:51.901 servermgrd[2886]: [2886] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 19:35:54.539 servermgrd[2932]: [2932] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 19:35:54.580 servermgrd[2932]: [2932] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 19:37:56.926 servermgrd[2947]: [2947] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 19:37:57.424 Server[1154]: Error: The server '127.0.0.1' reported an error while processing a command of type: 'readSettings' in plug-in: 'servermgr_timemachine'. Error: Error Domain=XSActionErrorDomain Code=1000 "An unknown error occurred" UserInfo=0x7ffac472ad50 {NSLocalizedDescription=An unknown error occurred}
26/03/2013 19:39:59.284 servermgrd[2958]: [2958] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 19:40:01.135 Server[1154]: Error: The server '127.0.0.1' reported an error while processing a command of type: 'getState' in plug-in: 'servermgr_timemachine'. Error: Error Domain=XSActionErrorDomain Code=1000 "An unknown error occurred" UserInfo=0x7ffac4657ce0 {NSLocalizedDescription=An unknown error occurred}
26/03/2013 19:42:04.286 servermgrd[2973]: [2973] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 19:42:04.322 servermgrd[2973]: [2973] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
26/03/2013 19:45:20.502 Server[1154]: Error: The server '127.0.0.1' reported an error while processing a command of type: 'getState' in plug-in: 'servermgr_timemachine'. Error: Error Domain=XSActionErrorDomain Code=1000 "An unknown error occurred" UserInfo=0x7ffac43f84a0 {NSLocalizedDescription=An unknown error occurred}
27/03/2013 11:56:52.191 servermgrd[110]: [110] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out
27/03/2013 11:58:54.217 servermgrd[371]: [371] error in getAndLockContext: flock(servermgr_timemachine) FATAL time out

HT1277 Mail has gone crazy. Header's and messages are mixed up. New Mac Book Pro. Migrated files from Time machine running snow leopard. Reinstall or new computer needed?

Mail has gone crazy. Header's and messages are mixed up. New Mac Book Pro. Migrated files from Time machine running snow leopard. Reinstall or new computer needed?

Ok; I'm not sure what you're doing. 36 hours is rather long. Seems like a new migration. Not what I intended.
Here's what I intended: from the newly-migrated and apparently-corrupt environment, create a new user, not related to any existing user, nor any migration-created user, or any other user for that matter. That is, use  > System Preferences > Users and Groups, authenticate yourself by clicking on the padlock, and then click the + and create a wholly new user. Then log in under that user and establish the mail access.
36 hours? I'm wondering if there's an error or an exceedingly slow network here? Or a really, really slow disk? Or a sick backup? (WiFi isn't the path I'd usually choose, either.)
Failing the attempted second migration, I'd try a different tactic. Does your existing (old) system work? If so, I'd bypass the backup and connect an external (scratch) USB disk drive to the (old) sstem and then boot and use Disk Utility booted from the installer DVD disk or boot and use Disk Utility from the recovery partition or booted from a recovery partition created on some other external storage (details here vary by the OS X version and what hardware you have), and perform a full-disk backup of your original internal disk to (scratch) external storage. (Make sure you get the source and target disks chosen correctly here; copying the wrong way — from the scratch disk to your existing disk — will clobber your data!) In esssence, this will clone your existing boot disk. Then dismount the (formerly-scratch) external disk, transfer it over to the new system, and use it as the source of the migration, by performing a fresh OS X installation on the new system.
Target Disk Mode is also sometimes an option for accessing the disk for a migration, but that requires the right cable, and requires systems that have the same external connection; newer MacBook Pro systems use Thunderbolt for this, and older systems tend to use FireWire. And I'm guessing you don't have compatible hardware.
The details here can and do vary by your OS X versions and your particular Mac systems — if you'll identify the specific models and hardware, somebody might be able to better tailor the above (fairly generic) sequence to your particular configuration.

Backing up an encrypted drive with Time Machine under Snow Leopard

In a nutshell, my question is “Can I back up an encrypted drive using Time Machine under Snow Leopard, and if so, how do I access its data from a previous day?”
I have a 1Tb USB drive connected to my MacBook, which runs Snow Leopard. The drive is formatted as Mac OS Extended (Journaled). This drive is included in the drives that Time Machine backs up. I used Disk Utility to create an encrypted drive on the USB drive (998Gb), also formatted as Mac OS Extended (Journaled). The encrypted drive is not on TimeMachine’s list of excluded files/drives.
When I go into Time Machine, I can see the USB drive and the encrypted drive in the side bar. I can access the files on the encrypted drive as long as I’m looking at how it stands now. But if I move backward in time, the encrypted drive is grayed out and inaccessible. If I click on the USB drive, I get a window that tells me it is 75.9Gb in size, and nothing else is available to me.
When I open the back-up drive in Finder and navigate to Backups.backupdb > macbook name > some date and time, I see my MacBook’s hard drive and the USB drive. The encrypted drive is not shown. When I click on the USB drive, I see an entry for drivename.sparsebundle. When I click on that I’m prompted for the password for the encrypted drive. When I enter it, I get a warning telling me that the disk image could not be opened and that the encrypted drive has no mountable file systems.
Is my encrypted drive really be backed-up and if so, how do I access the backed-up data?

Having received a bunch of views but no replies over the last 5 days, I decided to venture into my local Apple store and ask this same question. The response I got from the geniuses was that you can't get a reliable back-up of an encrypted drive using Time Machine under Snow Leopard. So, my only alternative is to copy the encrypted drive's contents elsewhere, unencrypt the drive, and then copy the contents back. This is what I expected, but not what I wanted to hear.

Why can I no longer backup to Time Machine on OS X Server?

We have a Windows Server and a Mac Server. The OS X Server is basically only for backups from workstations via Time Machine and as a Software Update Server.
I can no longer backup from my MacBook to the Server. If I try to add the location again in Time Machine Prefs, it asks for username and password. I try my AD account, but it fails. Guest doesn't work either. Any suguestions? When I set up the Time Machine service on the server, it was very easy. What did I miss?

You have to enter the name and password of an administrator on the server.

Transfer time machine data (snow leopard) to new mb air (lion)

MB Pro died. How do I transfer external Time Machine backup (Snow Leopard) to new MB Air (Lion)?

Your best bet, by far, is to use Setup Assistant when your new Mac first starts up, to transfer your 3rd-party apps, user accounts, data, settings, etc. from the backups. See Using Setup Assistant on Lion for detailed instuctions.
If the backups are on a Time Capsule, get a USB-to-Ethernet connector, so you can do this via Ethernet -- it's 2-3 times faster, and much more reliable, than WIFIl.

Entering Time Machine - slow after update to Snow Leopard

Entering Time Machine via the icon in my top menu bar has never been fast. However, last week I moved from Leopard to Snow Leopard (since fully updated). Tonight I needed to restore a file from yesterday's backup, so I selected "Enter Time Machine." The "universe" with the timeline along the right loaded, but several minutes passed and I was still not able to use the arrows at the lower right to move backwards in time. Nor would the timeline at the right show any date markers other than "Now," "Today," and "January 2010" and "January 2009." I let it sit for several minutes with no apparent progress. Even the "cancel" button took nearly 60 seconds to function.
As an alternative, I tried running the Time Machine application from my apps folder. It was slower to bring up the "universe" but did, after a couple of minutes, get me to a window with a functional timeline.
Any idea what the problem might be? I feel like entry into my Time Capsule has gotten slower and slower, but tonight was really egregious.

It does take a while over a network; there's a lot of "setup" that seems to be required.
You might try the things in #E4 of [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).

An old macbook running 10.6.8 was restored using Time Machine then Snow Leopard was reinstalled and updated to 10.6.8. Now the machine is slow and repair disc permissions results in a cancelled by user message.

Our old macbook was getting a gray screen with flashing ? on bootup. Eventually I restored it using Time Machine then decided to reinstall Snow Leopard since it would not boot. Machine now boots but is slow. Ran repair disc and tried to run repair disc permissions but got a message that it was cancelled by user.
This machine is at least 6 years old and I just want to limp it along until I can afford to replace it in the spring.

You may be smelling it because with the new OS the processor is having to work harder causing it to get hotter then it would with the other OS. I can't say there is nothing wrong, but what could be happening is just that, it's getting hotter so the fan is spinning faster and moving more air so you are getting more of the smell then you would before. I would still continue to back it up, and take it to the Apple Store at a Genius Bar and have them look at it to make sure. Was the computer ever in a smoky environment??

Time Machine Backup to Mac Server

If I missed the solution to this in the forums, I apologize in advance. I have been searching these forums and Google all afternoon to find a solution to this problem. If this is addressed elsewhere, please be kind enough to post a link.
Network - Mac XServe and managed client all running the latest updates. Managed settings are the mobile account with manual home sync, login message and display and SUS.
On the server, I set up the /Volumes/Server HD/Backups directory in Server Admin and checked the box to make it a Time Machine destination as the instructions stated.
On the client, I ran the command so that the network volume would show up (defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1) and I am able to select the disk.
When I selected the disk initially, it told me my ID did not have permission to read/write/append to the network volume. So in Server Admin, I added my network ID with Read/Write access in the ACL section. After doing this, I can select the disk and start the backup. It acts like it is going to work, then I get the following error:
+Time Machine could not complete the backup.+
+The network backup disk could not be accessed because there was a problem with the network username or password.+
+Open Time Machine preferences to select the network backup disk and re-enter the correct username and password.+
I have spent the afternoon trying to figure this out. Is there something simple I'm missing and making this more difficult than it has to be?
Thanks in advance for any ideas you can give. I will mention this is my first XServe to administer, so if I'm making this harder than it has to be, that's why.

I have the same issue, but with a WD mybook 1TB NAS drive. It works for a day or two, then fails. Re-entering the username and password corrects it for a day or two, and it fails again. Has been a problem since the NAS was installed. I never used Time Machine before that.
Gigabit wired ethernet, iMac Snow Leopard as follows:
Model Name: iMac
Model Identifier: iMac7,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 2 GB
Bus Speed: 800 MHz
Boot ROM Version: IM71.007A.B03
SMC Version (system): 1.20f4
System Version: Mac OS X 10.6.2 (10C540)
Kernel Version: Darwin 10.2.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Computer Name: Studio Mac
User Name: Denis DuBois (dubois)
Secure Virtual Memory: Not Enabled
64-bit Kernel and Extensions: No
Western Digital:
Device Name NAS1
Version 01.01.16 with MioNet 4.1.0.0.171
built on Fri Nov 6 13:28:12 CST 2009

Time Machine on Mountain Lion Server Accepts But Doesn't See Backups From Lion

I recently (hopefully) upgraded our Mac Mini Server from Snow Leopard Server to Mountain Lion plus the Server app. A Drobo F is attached via FireWire and has a Time Machine partition on it. I've configured the Server app to offer the Time Machine partition on the Drobo for backups and we've got three machines using it: a relatively new MacBook Air running 10.8.2, an aging MacBook Pro running 10.8.2, and a pretty new MacBook Pro running 10.7.5. All three of the machines are able to backup to the Time Machine volume on the Mini. However…
Only the backups from the two machines running ML show up on the Time Machine Backups tab in the Server app. There is an entry for the Backups from the Lion machine, but the latest backup is reported as "Unknown." If I click on the Time Machine icon in the menu bar on the Lion machine it shows a reasonable (and recent) time for the latest backup. The log entries in Console for com.apple.backupd also look reasonable – and uninteresting. And newly backuped up files are visible in Time Machine.
The on obvious difference that I notice is that the in the .sparsebundle folders for the ML machines there are two files called:
com.apple.TimeMachine.Results.plist, and
com.apple.TimeMachine.SnapshotHistory.plist
Those files are not present in the .sparsebundle folder for the Lion machine (even after a successful backup).
Is this a clue or is it a Lion vs ML difference?
Does anybody have a Lion machine successfully backing up to a ML server and showing up on the Backups tab?
Any advice on this would be appreciated!

Same here - TM clients running 10.6.8 display as "unknown" on the /Backups tab on ML Server (ML 10.8.3).
My one client on a ML machine is correctly displayed (time/date of last TM backup).
As far as I can tell, the TM backups are working properly on the 10.6.8 machines. The problem seems to be a bug in ML Server
Solution: upgrade all 10.6.8 machines to Mountain Lion.
Roadblock: my 1st-gen MacBook Air doesn't support ML.

Time machine slow in leopard server unlimited client

Similar Messages

Maybe you are looking for