Tags: smb

07/12/11

  07:29:54 am, by The Dreamer   , 382 words  
Categories: Hardware, Computer, Storage

Speaking of running out of space....

....I ran out of space in backuppc last night.

However, it was party due to a bug that hits me now and then. An rsync backup of a large ~7GB file on the remote system, was resulting in a file file on my backuppc server that was growing without bound. If there were only some way that backuppc would know that if a file of size 'x' on remote was resulting in a file of size 'y' (where 'y' >> 'x') that maybe something is going wrong.

Sure the built-in compression might result in some increase in size for already compressed or incompressible files, which is typically the case of large files coming from the remote....TEBE backup file.

But, it seems pretty obvious to me that at 300GB and growing...something has gone wrong.

Silly thing is that the particular remote is being backed up twice. And, rsync backup's exclude list keeps growing and growing to avoid the difficult large files and letting just the other (SMB) backup get it.

Originally, when I first set up Zen, the smbclient in ubuntu had stopped being able to talk to Windows 7 shares. I had set up work machine using rsync method, just to see what that was like in comparison to the more traditional of using SMB method for my Windows boxes. But, some Windows update changed how Windows 7 shares worked....and samba could no longer talk to it.

I tried fiddling with registry and package uninstall/installs, etc. Looking for tweaks to the smbclient source that I could compile my own version, there was a time (early on) where I was using my own compiled version of smbclient....but I didn't block updates, and the next update worked. Well, after some point in time, another update for smbclient appeared from ubuntu....and it could connect to Windows 7 shares again. So, I put Zen back in with SMB. The total backup size is so much larger than the rsync version. Because tar doesn't seem to have any of the trouble of rsync (normally I think rsync is better than tar though, but suspect its all about the perl re-implementation of rsync functionality in BackupPC that is the problem....I heard in 4.0 that they have abandoned this approach and will run rsync on the backuppc server.

Ya...I think that's what I'll do....

07/08/11

  07:32:00 pm, by The Dreamer   , 693 words  
Categories: Hardware, Computer, Networking, Storage, Ubuntu

Time machine & NFS

Link: http://blog.mediafederation.com/andy-hawkins/mac-os-x-time-machine-via-nfs-on-linux-ubuntu-complete-guide-fixes-error-13-etc/

So, during the long weekend...I got to wonder why I couldn't have my work MacBookPro do Time Machine backups to a network share, I had envisioned coming up with a drive to attach to one of my Airport Extremes and doing that some day. Though it doesn't look like that's actually going to happen anytime soon.

Did a quick google search on Time Machine and SMB, and found out about:

defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1

And, so trying to make it work started. I created a Samba shared named 'SIDRAT' on ORAC...which I think is the name of the removable 160G drive that I had been using at home for Time Machine backups. The one at work is named 'TARDIS'. But, I already have a Samba shared named 'TARDIS' on ORAC....that's the 1TB volume for the HSTi Media Stick. Also not to be confused with computers named TARDIS and SIDRAT. Though SIDRAT died a long time ago, and I still haven't gotten around to replacing it....it was my Windows laptop.

At first I didn't have dedicated storage on ORAC for this...I was just exporting the subdirectory of another Samba share as SIDRAT. And, it didn't really make sense for it to be a subdirectory on that share...but it was where I had at least 80GB to spare to this....the drive in the MacBookPro is only 80GB.

It seemed to start, but then it would fail. I had picked just the usual options for creating the Samba share, and wondered if the Mac needed special stuff to work. So, I went looking....

Read about the:

touch .com.apple.timemachine.supported

trick...but that didn't work. And, wasn't necessary when I did get it working. :))

So, then I read about creating the sparsebundle to get it started. There was conflicting info on how to name it....the usual was start Time Machine, and see what name it creates and use that.

So, was creating "<host>.tmp.sparsebundle" And, there were some variations on how to invoke hdiutil to create this. Well, it went further...it slowly made it get smaller and smaller until it was gone and then went on to try to create "<host>.sparsebundle". Creating that as well didn't help. I had heard about "<host>_<MAC_ADDRESS>.sparsebundle", but the hits I found didn't explain just what MAC_ADDRESS would look like, or which one to use. Decided this wasn't going anywhere and the long weekend was nearly over....I did at least (after many long attempts) get a backuppc backup of parts of my MacBookPro. So, I got rid of the Samba share and undid most of the other stuff.

Full story »

Now instead of subjecting some poor random forum to a long rambling thought, I will try to consolidate those things into this blog where they can be more easily ignored profess to be collected thoughts from my mind.

Latest Poopli Updaters -- http://lkc.me/poop

bloglovin

There are 20 years 1 month 25 days 6 hours 59 minutes and 6 seconds until the end of time.
And, it has been 4 years 11 months 2 days 7 hours 3 minutes and 50 seconds since The Doctor saved us all from the end of the World!

Search

November 2017
Mon Tue Wed Thu Fri Sat Sun
 << <   > >>
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30      
Google

Linkblog

  XML Feeds

Who's Online?

  • Guest Users: 0
This seal is issued to lawrencechen.net by StopTheHacker Inc.
free blog software

hosted by
Green Web Hosting! This site hosted by DreamHost.

monitored by
Monitored by eXternalTest
SiteUptime Web Site Monitoring Service
website uptime