Timemachine Succesfully backing up to SMB windows share

Hi After much googling a post on this page
http://forum.dsmg600.info/viewtopic.php?pid=7395#p7395
states the following command allows timemachine to backup to any mounted network share, and they are correct. I am succesfully running my 1st backup to a Windows share over SMB. Will keep you posted on how it goes. But here is the command:
defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1

I have been running Time Machine on an network SMB mounted partition for a couple of weeks (using the trick where you disabled the time machine disk check
defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1)...
I know it was a bad idea... but I have plenty of SMB space available at my lab, while no real hard disk (until today )
Everything went fine until today, where finally the disk filled up... and I got this in the console
20/11/07 15:10:42 /System/Library/CoreServices/backupd[11539] Trusting backup times for remote backups.
20/11/07 15:10:51 /System/Library/CoreServices/backupd[11539] Starting pre-backup thinning: 5.03 GB requested (including padding), 3.07 GB available
20/11/07 15:11:30 /System/Library/CoreServices/backupd[11539] Deleted backup /Volumes/Backup of Zig/Backups.backupdb/Zig/2007-11-19-145728: 3.07 GB now available
20/11/07 15:11:30 /System/Library/CoreServices/backupd[11539] Removed all 1 expired backups, more space is needed - deleting oldest backups to make room
20/11/07 15:12:20 /System/Library/CoreServices/backupd[11539] Deleted backup /Volumes/Backup of Zig/Backups.backupdb/Zig/2007-11-09-145354: 3.07 GB now available
20/11/07 15:13:08 /System/Library/CoreServices/backupd[11539] Deleted backup /Volumes/Backup of Zig/Backups.backupdb/Zig/2007-11-12-085647: 3.07 GB now available
20/11/07 15:14:02 /System/Library/CoreServices/backupd[11539] Deleted backup /Volumes/Backup of Zig/Backups.backupdb/Zig/2007-11-13-105151: 3.07 GB now available
20/11/07 15:14:57 /System/Library/CoreServices/backupd[11539] Deleted backup /Volumes/Backup of Zig/Backups.backupdb/Zig/2007-11-14-094201: 3.07 GB now available
20/11/07 15:15:49 /System/Library/CoreServices/backupd[11539] Deleted backup /Volumes/Backup of Zig/Backups.backupdb/Zig/2007-11-15-093340: 3.07 GB now available
20/11/07 15:16:58 /System/Library/CoreServices/backupd[11539] Deleted backup /Volumes/Backup of Zig/Backups.backupdb/Zig/2007-11-16-091426: 3.07 GB now available
20/11/07 15:19:39 /System/Library/CoreServices/backupd[11539] Deleted backup /Volumes/Backup of Zig/Backups.backupdb/Zig/2007-11-19-084944: 3.07 GB now available
20/11/07 15:19:51 /System/Library/CoreServices/backupd[11539] Deleted backup /Volumes/Backup of Zig/Backups.backupdb/Zig/2007-11-19-160038: 3.07 GB now available
20/11/07 15:20:25 /System/Library/CoreServices/backupd[11539] Deleted backup /Volumes/Backup of Zig/Backups.backupdb/Zig/2007-11-19-164736: 3.07 GB now available
20/11/07 15:21:14 /System/Library/CoreServices/backupd[11539] Deleted backup /Volumes/Backup of Zig/Backups.backupdb/Zig/2007-11-19-174849: 3.07 GB now available
20/11/07 15:21:39 /System/Library/CoreServices/backupd[11539] Deleted backup /Volumes/Backup of Zig/Backups.backupdb/Zig/2007-11-20-100005: 3.07 GB now available
20/11/07 15:22:07 /System/Library/CoreServices/backupd[11539] Deleted backup /Volumes/Backup of Zig/Backups.backupdb/Zig/2007-11-20-104417: 3.07 GB now available
20/11/07 15:22:39 /System/Library/CoreServices/backupd[11539] Deleted backup /Volumes/Backup of Zig/Backups.backupdb/Zig/2007-11-20-114450: 3.07 GB now available
20/11/07 15:23:00 /System/Library/CoreServices/backupd[11539] Deleted backup /Volumes/Backup of Zig/Backups.backupdb/Zig/2007-11-20-124449: 3.07 GB now available
20/11/07 15:23:00 /System/Library/CoreServices/backupd[11539] Error: backup disk is full - all 15 possible backups were removed, but space is still needed.
20/11/07 15:23:00 /System/Library/CoreServices/backupd[11539] Backup Failed: unable to free 5.03 GB needed space
20/11/07 15:23:01 /System/Library/CoreServices/backupd[11539] Backup failed with error: Not enough available disk space on the target volume.
20/11/07 15:23:03 /System/Library/CoreServices/backupd[11539] Ejected Time Machine disk image.
20/11/07 15:23:03 /System/Library/CoreServices/backupd[11539] Ejected Time Machine network volume.
Do you see where I am coming? this is already scary... it deleted ALL but one backups, without recovering one byte... Jez... without a warning (despite the check box in the TM pref option pane)
Look at this:
[zig:~] felix% mount
/dev/disk0s2 on / (hfs, local, journaled)
devfs on /dev (devfs, local)
fdesc on /dev (fdesc, union)
map -hosts on /net (autofs, automounted)
map auto_home on /home (autofs, automounted)
//[email protected]/local/users/felix on /Volumes/felix (smbfs, nodev, nosuid, mounted by felix)
This is the SMB partition:
[zig:~] felix% df -g /Volumes/felix/
Filesystem 1G-blocks Used Available Capacity Mounted on
//[email protected]/local/users/felix 66 63 3 96% /Volumes/felix
[zig:~] felix% ls /Volumes/felix/
Zig_0017f2c89d46.sparsebundle/
[zig:~] felix%
<here I mounted the sparsebundle image using the finder>
[zig:~] felix% mount
/dev/disk0s2 on / (hfs, local, journaled)
devfs on /dev (devfs, local)
fdesc on /dev (fdesc, union)
map -hosts on /net (autofs, automounted)
map auto_home on /home (autofs, automounted)
//[email protected]/local/users/felix on /Volumes/felix (smbfs, nodev, nosuid, mounted by felix)
/dev/disk2s2 on /Volumes/Backup of Zig (hfs, local, nodev, nosuid, journaled, mounted by felix)
[zig:~] felix% df -g /Volumes/Backup\ of\ Zig/
Filesystem 1G-blocks Used Available Capacity Mounted on
/dev/disk2s2 132 129 3 98% /Volumes/Backup of Zig
So the Backup partition pretend to use 129 Gig (weird as its containing SMB partition is 66 Gig big) and 3 Gig left...
[zig:~] felix% cd /Volumes/Backup\ of\ Zig/
[zig:/Volumes/Backup of Zig] felix% ls
Backups.backupdb/
[zig:/Volumes/Backup of Zig] felix% ls Backups.backupdb/
Zig/
[zig:/Volumes/Backup of Zig] felix% ls Backups.backupdb/Zig/
2007-11-20-141210/ 2007-11-20-151041.inProgress/ Latest@
[zig:/Volumes/Backup of Zig] felix% sudo du -sk .
Password:
35637816 .
But all the files on this partition amount to 35 gigs... (which is indead more or less the size of one backup)... where are the other 31 gig gone? My explanation is that the space has not been properly recovered after the old backups deletion... (which indeed also explains why backupd deleted ALL but one backups)
In any case, I would advise any SMB mounted partition Time Machine user to NOT rely completely on those backup. I will try to see if one can recover the space in a sparsebundle image... but even so, it makes the whole process dangerous.
You have been warned...
Moreover:
[zig:/Volumes/felix] felix% hdiutil compact Zig_0017f2c89d46.sparsebundle
Starting to compactâ¦
Reclaiming free spaceâ¦
Finishing compactionâ¦
Reclaimed 19.5 GB out of 97.9 GB possible.
[zig:/Volumes/felix] felix% df -g .
Filesystem 1G-blocks Used Available Capacity Mounted on
//[email protected]/local/users/felix 66 43 22 66% /Volumes/felix
[zig:/Volumes/felix] felix%
Note that I only recover (by hand) 22 gig while 31 should be available... but this is explained in man hdiutil:
"For SPARSEBUNDLE images, completely unused band files are simply removed."
Completely... so Iguess only 22 gig of bands were free 9 gigas are in band which are partially used by good data.
[zig:/Volumes/felix] felix% cd /Volumes/Backup\ of\ Zig/
[zig:/Volumes/Backup of Zig] felix% df -g .
Filesystem 1G-blocks Used Available Capacity Mounted on
/dev/disk2s2 132 109 22 83% /Volumes/Backup of Zig
[zig:/Volumes/Backup of Zig] felix%
So the space has been indeed returned to the SMB volume... and I was able to restart TM after that and complete a backup...
In any case, I say it again... do not rely on SMB mounted partition based TM backup.
As for me, I am ordering a 200 gig external HD :-D

Similar Messages

  • Accessing SMB/Windows Shares on OS X

    I have an invisible windows share called public$, which I allow anyone to (read-only) access on my network. But to be able to access it on a mac I had to give it a password. Are there anyways around this password problem? On windows machines I am able to access this folder without the need for authentication which is what I want since this is read-only and contains documents for general public use which I need the public to automatically have access to it without the need for authentication.

    SMB never really likes symbols in shares.
    A couple of things. Is this part of a Windows Domain (200,2003, 2008) or part of a Home network? Plus make sure the Mac and Windows machine are using the same Time Server. Also check out the reader reports at MacWindows.com:Snow Leopard and File Sharing Tips and Rerports because one of the current reports might help you.

  • How do I stop the Finder from seeing SMB (Windows) shares on the network?

    I have the OPPOSITE problem most people have -- Windows Sharing works TOO WELL.
    I've donated a refurbished eMac to the local homeless shelter. I figured I'd made the system secure, and prevented any monkey business. Turns out the windows machines on the network are COMPLETELY insecure (guest access to everything is enabled). The problem is that the Mac is TOO friendly -- it automatically connects to the server as a guest, and happily presents everything to the user.
    I've tried a dozen different things (I've removed the 'Shared' section from the sidebar in the Finder windows (Go->Network is still there, Doh.), tried to turn off File Sharing, and even disabled the mount_smbfs command in the /sbin directory with "chmod 0 mount_smbfs".)
    I've asked the folks there to call in a PC tech and fix their security problem -- but it's a good question to which I've found no suitable answer... How to I stop the Mac from connecting to SMB Shares on the local network?
    Thanks.
    -JD.

    Same problem, keep getting a pop up with connection failed you do not have permission to access the server. The server is a windows 7 box, Starting happening after an up grade to windows 7. Nowhere can I find how to stop trying to connect. I am sure its at the unix level of samba but what to do is another question

  • Cannot connect to an SMB Windows share point in Yosemite.

    After upgrading to Yosemite this weekend, I am no longer able to connect to a Windows server that worked fine in Mavericks. Does anyone know a solution that I can work on my end that does not involve the server? This is not a server that I can access to make changes on.
    Thanks,
    Scott

    Scott, did you have disable the device signing in the prior OS 10.9? Or did you do it in Yosemite? I am having a similar issue but I cannot support the OS edit to the enable. This needs to be a simple setting/adjustment for stablity reasons in my opinion, here are a few refernces:
    - Can't connect to SMB share after upgrade
    http://hints.macworld.com/article.php?story=20131122083837447
    Please advise.
    Thank You

  • Time Machine backup to Windows Share Now Failing Verify

    Hi Everyone - I have searched everywhere and can't find any help.
    This is my situation. I have my TM backup to an SMB windows share and its been working fine for months. Two things changed recently: a) I installed Windows 7 on my windows box and b) I installed that TM update that provides greater reliability. Backups worked fine for weeks after both of these changes, but just this week backups failed and TM wanted to create a new backup. I tried to recreate a new backup, but it keeps failing with errors below. When I try to run a verify disk on the sparsebundle (with disk util) I always get errors, but of course, I can not fix the errors when the sparsebundle is on an SMB. I am currently running a chkdsk on the windows drive, but I don't think its damaged.
    8/18/10 11:39:02 PM com.apple.backupd[800] Copied 18.3 GB of 20.3 GB, 164128 of 640370 items
    8/18/10 11:39:41 PM com.apple.backupd[800] Copied 164129 files (18.4 GB) from volume IntelSSD160.
    8/18/10 11:39:43 PM com.apple.backupd[800] No pre-backup thinning needed: 828.7 MB requested (including padding), 578.34 GB available
    8/18/10 11:39:51 PM com.apple.backupd[800] Copied 379 files (7.3 MB) from volume IntelSSD160.
    8/18/10 11:39:51 PM kernel hfs: node=4844 fileID=4 volume=Backup of MYMBP device=/dev/disk3s2
    8/18/10 11:39:51 PM kernel hfs: Runtime corruption detected on Backup of MYMBP, fsck will be forced on next mount.
    8/18/10 11:39:51 PM kernel hfs: cat_delete() failed to delete thread record on volume Backup of MYMBP
    8/18/10 11:39:51 PM kernel hfs: Runtime corruption detected on Backup of MYMBP, fsck will be forced on next mount.
    8/18/10 11:39:51 PM kernel hfs: node=4844 fileID=4 volume=Backup of MYMBP device=/dev/disk3s2
    8/18/10 11:39:51 PM kernel hfs: Runtime corruption detected on Backup of MYMBP, fsck will be forced on next mount.
    8/18/10 11:39:51 PM com.apple.backupd[800] Starting post-backup thinning
    8/18/10 11:39:51 PM com.apple.backupd[800] No post-back up thinning needed: no expired backups exist
    8/18/10 11:39:51 PM com.apple.backupd[800] Backup completed successfully.
    8/18/10 11:39:57 PM com.apple.backupd[800] Ejected Time Machine disk image.
    8/18/10 11:39:57 PM com.apple.backupd[800] Ejected Time Machine network volume.
    8/19/10 12:31:04 AM com.apple.backupd[1120] Starting standard backup
    8/19/10 12:31:04 AM com.apple.backupd[1120] Attempting to mount network destination using URL: smb://GUEST:@192.168.1.107/TM
    8/19/10 12:31:07 AM com.apple.backupd[1120] Mounted network destination using URL: smb://GUEST:@192.168.1.107/TM
    8/19/10 12:31:19 AM com.apple.backupd[1120] QUICKCHECK ONLY; FILESYSTEM DIRTY
    8/19/10 12:31:19 AM com.apple.backupd[1120] Runtime corruption detected on /Volumes/TM-1/MYMBP_58b035f1b3d1.sparsebundle (fsck_hfs -q termination status: 3)
    8/19/10 12:31:19 AM com.apple.backupd[1120] Attempting to mount network destination using URL: smb://GUEST:@192.168.1.107/TM
    Anyone encounter this? I essentially can not use TM right now. Could the TM update and/or windows 7 upgrade be a contributor? Any help is much appreciated.

    abnospam wrote:
    Hi Everyone - I have searched everywhere and can't find any help.
    This is my situation. I have my TM backup to an SMB windows share and its been working fine for months.
    Is that a "supported" destination? According to this Apple article: Disks that can be used with Time Machine
    *+If your backup disk is on a network, the network server must use Apple File Protocol (AFP) file sharing, and both your computer, and the networked backup disk, should have Mac OS X 10.5.6 or later.*+
    8/18/10 11:39:41 PM com.apple.backupd800 Copied 164129 files (18.4 GB) from volume IntelSSD160.
    8/18/10 11:39:43 PM com.apple.backupd800 No pre-backup thinning needed: 828.7 MB requested (including padding), 578.34 GB available
    8/18/10 11:39:51 PM com.apple.backupd800 Copied 379 files (7.3 MB) from volume IntelSSD160.
    It appears to have finished the actual backup (two passes).
    8/18/10 11:39:51 PM kernel hfs: node=4844 fileID=4 volume=Backup of MYMBP device=/dev/disk3s2
    8/18/10 11:39:51 PM kernel hfs: Runtime corruption detected on Backup of MYMBP, fsck will be forced on next mount.
    8/18/10 11:39:51 PM kernel hfs: cat_delete() failed to delete thread record on volume Backup of MYMBP
    Then has a problem; apparently unable to delete the thread record, although listed 3rd, seems to be where it choked.
    8/19/10 12:31:19 AM com.apple.backupd[1120] QUICKCHECK ONLY; FILESYSTEM DIRTY
    8/19/10 12:31:19 AM com.apple.backupd[1120] Runtime corruption detected on /Volumes/TM-1/MYMBP_58b035f1b3d1.sparsebundle (fsck_hfs -q termination status: 3)
    And can't fix it on remount.

  • Lost a lot of files during move to a mounted Windows share via SMB

    Hi,
    after mounting a network Windows share via SMB and then using the Finder to move files from my local disk to that share all the files that were to be moved are lost in ****. I am totally upset because these were very important files. What is it that drives 10.5.2 nuts here? Has anybody any ideas?

    Look in \Music\iTunes\iTunes media\ (or \iTunes music\).

  • SMB/CIFS share of encrypted windows directory

    I have a windows 8.1 pro stand alone computer. It has one directory that is encrypted. This computer shares that directory and others with a linux computer. Just after the windows 8.1 computer reboots, linux is unable to access the encrypted directory, but
    it can access other unencrypted directories. Once I log on the windows computer as a user with access to the encrypted directory, the linux computer is suddenly able access the encrypted folder. The linux computer can continue to access the encrypted directory
    from linux after the user logs off the windows computer.
    To be able to access the encrypted directory, I only need to log on to the windows console, i don't need to start any programs. It's as if windows cannot access some kind of key until the a user with access to the encrypted folder logs on to the windows
    system from the console. I've tried many different linux command line options for opening the windows share and it doesn't seem to change the behavior. It is typically mounted with:
    mount
    -t cifs //192.168.1.2/efsdirectory ~/mnt --verbose -o rw,user=username,uid=1000,gid=1000
    The behavior is identical if a directory above the efs directory is mounted.
    I searched all of the windows event logs for errors from the failed access to the encrypted directory, but I don't see any.
    Thanks for your help.

    Hi,
    Thanks for your help.
    if all your systems are in Domain or not.
    The windows and linux computers are not on a windows domain, just the same workgroup that is named "workgroup".
    Also please help confirm if "encrypted" means encrypted by EFS (or Bitlocker).
    The directory that i'm trying to access is encrypted with EFS. Since this is a desktop computer, it does not use bitlocker
    What's the exact username here in your command? Is it the same account as the one you logged on Windows 8.1?
    the username in the unix mount command is the same one used to log onto the windows system. The linux username is different, but that's specified in the mount command with the UID and GID.
    The problem occurs after a full reboot, I have disabled the windows 8.1 fast reboot 'feature'.
    I'll check tonight, but is it possible that the "Encrypting file system service" is not starting when I mount the drive? Perhaps it only starts when I log on. I noticed that this service is set to 'automatic' on another (windows 7) computer.
    Here's a timeline of what happens:
    1) Log off of the windows computer. Reboot. (not fast boot)
    2)
    mount drive on linux computer
    3)  brouse directory structure on linux. Can open files that are not in encrypted directories. Cannot open files that are in encrypted directories.
    4) log onto windows machine
    5) brouse directory structure. Now I can open files that are in encrypted directories.
    6) log off windows machine
    7) brouse directory structure. I can still open files that are in encrypted directories.
    Looking at the windows logs, I can see 2 login entries exactly when I mount the drive:
    Special privileges
    assigned to new logon.
    Subject:
    Security ID:   
    HOSTNAME\USERNAME
    Account Name:   
    USERNAME
    Account Domain:   
    HOSTNAME
    Logon ID:   
    0x43C3B
    Privileges:   
    SeSecurityPrivilege
    SeBackupPrivilege
    SeRestorePrivilege
    SeTakeOwnershipPrivilege
    SeDebugPrivilege
    SeSystemEnvironmentPrivilege
    SeLoadDriverPrivilege
    SeImpersonatePrivilege
    An account was successfully
    logged on.
    Subject:
    Security ID:   
    NULL SID
    Account Name:   
    Account Domain:   
    Logon ID:   
    0x0
    Logon Type:   
    3
    Impersonation Level:   
    Impersonation
    New Logon:
    Security ID:   
    HOSTNAME\USERNAME
    Account Name:   
    USERNAME
    Account Domain:   
    HOSTNAME
    Logon ID:   
    0x43C3B
    Logon GUID:   
    {00000000-0000-0000-0000-000000000000}
    Process Information:
    Process ID:   
    0x0
    Process Name:   
    Network Information:
    Workstation Name:   
    Source Network Address:   
    192.168.1.7
    Source Port:   
    58432
    Detailed Authentication
    Information:
    Logon Process:   
    NtLmSsp
    Authentication Package:   
    NTLM
    Transited Services:   
    Package Name (NTLM only):   
    NTLM V2
    Key Length:   
    0
    Thanks again.

  • FSDB to Windows Share on UNIX Portal

    Hi all,
    I'm struggling to setup a FSDB to a windows share (actually a Distributed File System) on a AIX based portal. I've gone through the steps of this blog: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/284(but this blog is somewhat outdated) and verified the settings on help.sap.com but they are not very clear.
    Has anyone succesfully setup such a CM repository manager? When I set it up as a FileSystem Repository Manager it works immediatly.
    There are two things that confuse me the most:
    the network path -> is it required or not and if so where do you enter this information in the RM config? According to the blog you entere the full network path in the Windows Landscape System but in the [online help|http://help.sap.com/saphelp_nw70/helpdata/EN/62/468698a8e611d5993600508b6b8b11/frameset.htm] it sais that this field is not required for CM repository managers on UNIX???? if you don't use the network path how do you provide the network credentials of the shared drive to the portal?
    slashes -> when so you use forward slashes in the config and when the backward to the network shares?
    Points will be awarded of course!
    Marcel

    This doesn't quite work at all. I can understand for OSX to be serving the files the need too change /etc/smb.conf, however, my OSX machine doesn't serve any files, thus the smb service is offline. I have tried adding that tag to my fileserver using samba (its a linux nas box) and it still is slow as ****. I know it works with tiger because one of my sisters is using a macbook on tiger and is able to connect wirelesssly to it and download files as fast as my MBP downloads through ethernet (mine is leopard). My other sister has the exact same configuratino of macbook, however hers is leopard like mine and it moves crazy slow. I know this is the reason why apple pedaled back about network drive time machine because they realized the broke something so I'm giving them the beneffit of the dooubt. If 10.5.2 rolls around and I don't see improvement I think i'll just go back to tiger...

  • Samba mounting windows share

    Hi, I'm trying to mount a windows share but all I can do after mounting is seeing the folders and files on the share. I can not read any file, I get "permission denied". On windows everything should be set to allow for the files to be read (if my brother didn't forget, overlooked anything). I even disabled the windows firewall.
    The windows 2000 computer can access the arch linux samba shares without a problem.
    I'm running arch current up to date.
    Here's how I mount, as root:
    mount -t smbfs -o username=gast,password=gast //192.168.0.132/Muziek /mnt/LW/Muziek/
    (gets mounted succesfully, but I can't read the files)
    Here's my /etc/samba/smb.conf:
    #Global Parameters
    [global]
    workgroup = THUIS
    netbios name = gel
    passdb backend = smbpasswd
    force create mode = 0770
    force directory mode = 0770
    wins support = yes
    case sensitive = no
    encrypt passwords = yes
    security = share
    server string = Linux                 
    [share]
    path = /mnt/hda1
    public = yes
    only guest = yes
    writable = no
    printable = no
    create mask = 777
    Can anyone help me out? I've been trying to get it working for at least a few hours :s.

    You are right. I did not need the dir_mode and file_mode, and I did have full control enable, but no dice.
    However it seems there is a folder aliasing feature, that was introduced in windows vista (though I don't recall the windows name for the feature and I am running win7), I believe to be the problem. For example, if I share and mount  C:\Users I have access to C:\Users\myuser and can create folders and documents there. However the predefined folders Music, Documents, Pictures I have no write permission inside of.
    Next if I share and mount C:\Users\myuser I have the same result for those folders however now I can see additional folders  one is 'My Documents' in this folder I have write access and changes are mapped back to the Documents Folder. Additionally there are now showing in the Documents folder, I had no write access to, additional folders which also weren't showing before 'My Music', 'My Pictures', and 'My Videos' in which I now have write access and they map back as well.
    When I connected to the shares from an XP machine I could simply access the original folders.

  • Using Time Machine to back up to a Windows 2003 Server

    I am trying to set up my Time Machine to back up to a windows 2003 server share. I have found some hacks on how to do so, however i am not successful.
    What I have done so far:
    TMShowUnsupportedNetworkVolumes 1 in terminal, which got TM to see my shared drives, however, when i try to backup to my specific drive it gives me an error of not being able to write disk image. So i did:
    hdiutil create -size 100g -fs HFS+J -volname “TimeMachine Hcomp” Hcomp_000045128a91.sparsebundle
    using the appropriate mac address, volume name, and OSX computer name. However, when i run that in terminal, it comes back with a message saying it can only create one volume at a time.
    I'm not quite sure where to go from here, I feel so close, but im stuck.
    Also, on another side note, If I get this working, I would like to find a way where when TM is backing up data, it does not pop up the work bar window, I would prefer if it just worked in the background, and show it's status in the menu. I dont know if this is possible, But any suggestions would be of help
    Thanks in advance!

    AFreeman wrote:
    Thanks for the response,
    I understand the requirements for TM to work, and In the steps i've been trying, you'll see that the command 'hdiutil create -size 100g -fs HFS+J -volname “TimeMachine Hcomp” Hcomp_000045128a91.sparsebundle ' creates and HFS drive partition on my server share.
    I guess i'm not looking for an answer as to why when i enter this command, I get a response of only one volume can be created at a time. Am I missing something in this command?
    Thanks!
    Since you are using a hack, and therefore in an unsupported area, I suppose anything possible.
    You might browse around the TimeCapsule forum which more closely represents what you are doing than this forum
    The TC forum is here:
    http://discussions.apple.com/forum.jspa?forumID=1253
    It's possible that it may be a limitation of the system, hack or no hack.

  • No Windows Shares in Finder

    Hello,
    We have several Windows boxes and a linux server (which runns smb) and three macs here. On the "old" macs (10.6.8 and 10.5.8) all windows shares are shown in Finder, but on the MBPro where we installed 10.7 no more windows shares are there. OS X Version is now 10.7.4.
    I already deleted com.apple.finder.plist but after a reboot still no windows (or smb) shares in finder. However if i connect via Cmd+K it works
    BTW the other macs (via afp) are shown in Finder.
    WINS setting is set to the correct workgroup, well except that the characters are all UPPERCASE while on all other boxes in the network they are LOWERCASE, but i can´t change this.
    Everytime i try to write them LOWERCASE for the workgroup it automaticaly changes back to UPPERCASE again. Could this have something to do with it?
    Thanks,
    t.

    Problem fixed upon updating to 10.6.2.

  • Kernel Panic when Unmounting $ Windows Shares

    So I have been dealing with this problem for quite a while and can't seem to find any solutions for the problem anywhere.
    When I mount a hidden windows share using smb (EXAMPLE: "smb://windowsbox/c$")and then unmount it more than 10 minutes later I inevitably get a KP. It may take a few seconds, but it happens without fail. Now I can connect to NON hidden shares on a windows box all day long, but if I have to include that '$' at the end of the share, it kills me. It's also with any windows box, not just one or one share in particular. If I stay connected to the share I have no problems, but that isn't possible when I go home for the day. I've tried disabling IPv6 (saw it somewhere on a thread with a pseudo-similar problem) and tried umount using the CLI. Still getting a KP. Since I am currently connected to one and will get the error when I unmount in a few minutes when my file transfer is done, I will come back and post the details of the KP. But any thoughts you might have in the mean time would be welcome.
    adTHXvance

    There are some longstanding bugs in dealing with SMB networks that have yet to be resolved.
    Sorry I can't help you further, but if you use the Search box to look in some of the other threads concerning panics and SMB, perhaps one of them could help you further.

  • File Monitor - Not working properly on SMB file share

    The "File Monitor" does not trigger on SMB file share, i think this might be a bug.
    I have tried the same "File Monitor" on a windows share, and it works like intended. However, when I use the same runbook on a Solaris SMB share, it does not trigger properly. It triggers when I delete or rename a file, but not any thing else (like
    create, changed, etc) I have turned all the triggers on just to see what actually makes it trigger...
    I'm using specified authentication (domain user and password)
    The SMB folder is shared on a Solaris (SunOS 5.10).
    Can anyone confirm that they also have this problem?
    Is there a patch to fix this? Thanks.

    Can someone please verify that they also have this problem?
    Thanks.

  • Windows shares discoverability no longer working

    I never used to have a problem with this in Leopard. Windows shares always appeared in the Shared section of finder just fine.
    But a few months ago they just stopped appearing, and not just on one mac, I have an iMac Core Duo and an iBook G4 and they have stopped appearing on both. The 3 windows machines see each other just fine.
    I've tried restoring my router to factory defaults, that hasn't helped, so I've ruled that out. The only thing I can imagine is that a software update some months ago has broken it.
    I've been experimenting and have found that if I change the workgroup name on one of the macs and one of the windows machines they start to see each other again. But after an hour or so the windows share will disappear again. And rebooting both machines will not get it back, I have to rename the workgroup again. It's mental!
    Using the ip addresses in connect to server works just fine, it's only the discovering of netbios names that is broken. Also, the windows machines can see the macs just fine.
    What is going on?

    I have the same exact problem. Only thing I've found that makes it tolerable is I created an alias of the shared windows folder so I don't have to use the IP address every time I want to connect to it, I just click on the alias from my mac and it will automatically mount the shared volume.
    Still, I'd love to figure out why it won't list it under the shared section of the sidebar like it used to...

  • Leopard Server 10.5.4 + SMB + Windows XP Clients

    Hello!
    I got quite some interesting problems with my Xserv under Leopard Server 10.5.4 with Windows XP Clients.
    The server runs as an open directory master and a standalone server for smb.
    Shares are setup for AFP and SMB clients, ACLs are set up with read+write access for the user's group. So far everything works, users can connect from their Macs (OS X 10.3.x - 10.5.4) without problems.
    My problem are the windows clients.
    Connecting works fine, and apart from one permission bug (more on that later) they can access all files and do everything the macs can do.
    Problem 1:
    Users cannot rename files if they don't have write permission at the POSIX-level as either owner or group on the enclosing folder. ACLs do not matter at this point, if the user connects through SMB he cannot rename files or folders.
    No big problem, I just put all users into one group and set this group as the POSIX-group and do a chmod -R g+w on all shares.
    Inheritate this settings for SMB-connections works.
    But not for AFP-connections. Every new folder a mac-client creates comes with permissions 755. So I changed UMasks on the clients to 002, and at least folders created by the finder now have the right permissions of 775.
    Folders created by "new folder" on most applications load/save dialogs still come as 755 which screws up renaming for windows-clients.
    Folders created when expanding a zip-file also behave this way.
    The only solution I found for this was to make a cronjob that does a chmod -R g+w on the shares. Not that great.
    Another "fun" feature with POSIX-permissions and SMB:
    Files inside a folder. Files+Folder have an ACL set up that specifically denies deleting files+folders for a user. This users group has POSIX-permissions with write access to the enclosing folder. Window's explorer will let that user delete files and folders without any complaint about missing permissions to do so. They even disappear from the explorer-window, but are not actually deleted.
    If you refresh the view, the files+folders are there again.
    If the user instead has no POSIX-permission that grants him write-access, but an ACL that grants him delete, explorer happily deletes the files the user wishes to. And these files actually get deleted.
    If the user has no write POSIX-permission and no ACL-permission to delete files, explorer complains about missing rights to delete files/folders.
    I tried adding "acl check permissions = no" to smb.conf, but that didn't change this behaviour.
    Problem 2:
    Sometimes, when copying "large" files to a server share with windows explorer (from 50 MB upto 3 GB), the user immidiately gets an error message: "Cannot copy. The specified network name is no longer available."
    The copied file shows up at once in the destination directory and has the correct file size, but only contains "garbage". Half a second later the same copy works and the file is actually copied successfully.
    Sometimes this error shows up while a large file is copied and if you browse through other shared folders while the copy takes place.
    Most often it will show up when you copy&paste with explorer.
    I am stomped and have no idea where to search for a solution to this one.
    I tried changing ethernet cables (premade and selfmade), the network switch, ethernet port of the Xserv ... connected a workstation directly to the Xserv - no change.
    DNS works, all clients+Xserv have static IPs and the same settings for DNS-Server. Name resolution works, as does reverse resolution.
    I even tried using a windows server 2003 as a WINS-Server without success for this problem.
    There are no event log entries on the clients when this happens, and smbd.log on the server shows
    read failure for 4 bytes to client 192.168.1.137. Error Connection reset by peer
    I used wireshark to monitor what exactly happens when this shows up, but it just happens out of nowhere ... the clients just sends a TCP_RST. No unusual things before or after the TCP_RST.
    I ran some tests with samba 3.0.32 and samba 3.2.x under linux 2.6.x - no such errors at all.
    I tried installing Leopard Server on my Mac Pro, same behaviour.
    I ran some batch-scripts that would copy large and small files in excess from/to the server from 4 different windows xp clients for a whole weekend 24 hours - not a single error. As soon as I use windows explorer to copy a file this error has a chance of showing itself.
    Problem 3, more of an application bug:
    Adobe InDesign CS2 (Windows again ;)) cannot export a PDF to a shared folder if the filename is longer than 8 characters. It starts exporting and after reaching 100% it just stops with the error "PDF cannot be exported." If the filename is shorter than 8 characters, all works fine. Exporting locally or to other samba servers (linux) or windows servers (2003) works fine. Copying this files to the share works, too.
    Exporting any other filetype from IDCS2 (eps, inx, jpeg ...) works regardless of filename length. So does saving InDesign-files.
    InDesign CS1 and CS3 do not show this, so I guess it's safe to assume this one is Adobe's problem
    Did anyone experience similar problems or even better has a solution to some of these?
    The real showstopper is problem #2, at least for us.
    Thanks in advance and excuse my poor english skills!

    I tried several new approaches, but nothing worked so far.
    The update to 10.5.5 made things worse. Connections are dropping all over the place, when saving from Adobe programs in particular.
    Printing from clients to a Xerox Phaser 5500 works, but choosing a different paper size than the default chosen in the cups admin interface goes all wrong and either prints on the default paper size, but down/upscaled to the chosen paper size or prints on the chosen paper size and down/upscaled as if you were printing to the default paper size. (e.g. default paper size is A4, you choose A3 with an A3 document. Document prints on A4 and is downscaled to A4, or prints on A3 and is downscaled to A4.)
    There is no way I can keep this thing in production much longer. I tried reinstalling again, but that did not change any behaviour. Another nice "feature": InDesign disables "edit original" when the path to the linked file contains any directoryname with more than 8 characters in length.
    Coupled with a sometimes disappearing "dirserv" (it just stops working until I reboot the whole computer) the decision stands to move away from the Xserve.
    Leopard Server 10.5.x just does not seem to work well with windows clients.
    We will migrate to a windows server 2003 running ExtremZ-IP for the macintosh clients this weekend. Too bad that Apple does not allow Bootcamp to work on Xserves, at least the hardware would have been useful then.
    (As a nice finishing touch, the harddisk partition where all data resides did become corrupt over the weekend. "The volume Daten could not be repaired."
    Disk Utility and first aid did show nothing on friday ... saturday after no work being done on the partition this error shows up. The only solution I could find was to reformat the partition and restore from a previous backup. Another weekend down the drain. Sorry for the rant, but 6 weekends in a row is enough.)

Maybe you are looking for