Tag Archives: backup

Two Mac OS terminal commands to remember

I just upgraded to Mac OS Mountain Lion and I had to use my two favorite terminal commands and thought I’d share them with you, even though you can easily find them in the internet.

First: Since OS X Lion Apple decided to hide the Library folder from the user.  Since for example the Lotus Notes Data folder is located there from time to time I need to access it.  To see it permanently you need to open the terminal and run the following command:

sudo chflags nohidden ~/Library

You will need to provide your admin password.

This will set the access rights so the Library folder is visible again. But be warned, this only lasts until you “repair” the disc / file permission using the disc utility. That will reset the folder to be hidden. Just rerun the command then.

The second one is regarding the fabulous Time Machine.  Whenever your near your Time Capsule or do your backups regulary when time machine is enabled, then everything is fine. But once you are on the road the Time Machine starts making backups on your local hard drive until you reach your home again. While this is very smart in regards of file history, this can be bad when you have a SSD with limited room left.  To turn of the local backups you need to run this command:

sudo tmutil disablelocal

Here, too, you will have to provide your admin password after firing the command.

Backup / Restore of an IBM Connections environment on file basis

In todays time of virtual machines the easiest and simplest way of getting a backup is doing a snapshot. I usually recommend it everytime bigger changes such as upgrades are done.  But not always there is the option to get a timely snapshot and therefore other means of backups are necessary.  One “quick and dirty” way is copying all necessary files to a backup folder.

In a standard Connections environment (all Components in a /IBM directory) this usally means backing up two directories:

  • the database directory (/DB2) if DB2 is installed locally
  • the complete aforemeantioned /IBM directory (at least the /WebSphere and /LotusConnections directories under it)

Since IBM Connections 3 the IBM Installation Manager is used for installing the solution and its upgrades.  Now I ran into a problem during an upgrade to 3.0.1 (always check the the remote desktop is started using the /console setting 😉 ) and hat copy back the recovered folders.  Unfortunately the Installation Manager copies files some files in a separate directory no matter what you said when installing. And these files contain the information which upgrades have already been installed.  So the IBM Installation Manager was still believing 3.0.1 was installed even though it did not and I copied back the “old” 3.0.0 environment. Having not enough time to play around I went the way of deinstalling Connections completely and reinstalling it.

So when you do a backup, make sure to add the following folder, too:

  • C:\ProgamData\IBM\Installation Manager