Seagate Backup Plus Unboxing Photos

A few weeks ago, I bought a 4TB Seagate Backup Plus Portable online from one of the local sellers in Manila. This drive will serve as a storage for snapshot backups of my NAS (Network-Attached Storage) at home. Below are the pictures I took during the unboxing. 🙂

The label on the box says 200GB of Cloud Storage for OneDrive is included but must be activated by June 20, 2017.

The top of the box is has a tamper-evident seal that guarantees that the initial contents of the drive came straight form the manufacturer.

The same tamper-evident seal can be found on the bottom of the box. This is how it would look like if the seal has been tampered with.

The contents of the box are the Quick Start Guide and the drive itself inside a protective plastic shell which also contains the USB cable.

Here’s the “top” of the protective plastic shell. Notice the six nubs that should somehow absorb and distribute the force should there be any impact from this side during transit. The protective shell is easy to open, much like Amazon’s frustration-free packages.

The drive is wrapped in plastic inside the plastic shell together with the USB cable.

The drive itself comes with a Micro-B SuperSpeed USB receptacle.

The included cable is a Micro-B SuperSpeed on one end and a standard Type-A on the other end.

After plugging it in on my laptop, it was recognized immediately by Windows 10 without the need to install any drivers. The OS reports that the total drive space is 3.63TB and so far, this is more than enough of what I need for my NAS but as the saying goes, “you can never have too much backups.” 🙂

How To: Auto-mount A Network Share On Raspberry Pi On Boot

Find Out What’s Available

The first thing I did was to show all the mount points available on the server where the network share is:

$ showmount -e

The result should be something like this:

Export list for

Create Mount Folder in the Raspberry Pi

Then I created a folder in /mnt so that I can mount the network share on the folder:

$ sudo mkdir /mnt/multimedia_share

OPTIONAL: Mount Manually Before Attempting To Auto-mount

I manually played around with the mounting before actually trying to get it to auto-mount. A fun exercise for n00bs like me.

If the network share allows anonymous access, the following command should “map” the network share to the /mnt/multimedia_share

$ sudo mount -t cifs -o guest // /mnt/multimedia_share

Otherwise, a mount error will be returned:

mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

If the network share requires credentials for access, the following command should be used:

$ sudo mount -t cifs -o username=user_name,password=plain_text_password // /mnt/multimedia_share

To unmount, use the following command:

$ sudo umount //

Configure Auto-mount on Boot

If we manually mount the network share, we will lose the “mapping” once the Raspberry Pi reboots. To have it mount upon boot, we have to edit the /etc/fstab file:

$ sudo nano /etc/fstab

Add the following line at the end of the file:

// /mnt/multimedia_share cifs username=user_name,password=plain_text_password,file_mode=0777,dir_mode=0777 0 0

Save the file and run the following to have the network share mounted:

$ sudo mount -a

There wouldn’t be any feedback like a success message if there are no errors. So to see if the mount was successful, run the following:

$ df -h

That command should return something like this:

Filesystem --- Size --- Used --- Avail --- Use% --- Mounted on
/dev/root --- 15G --- 2.9G --- 11G --- 21% --- /
// --- 5.4T --- 3.1T --- 2.4T --- 58% --- /mnt/multimedia_share

Note the last line where the details of the network share is displayed including the total size, used and available space.

To test if the auto-mount configuration worked, reboot the RPi:

$ sudo reboot

After it restarts, connect to the RPi and try to access the contents of the network share by going into:

$ cd /mnt/multimedia_share

How To: Generate SQL scripts from Liquibase changesets

There is a useful feature in Liquibase called Offline Database Support that allows you to generate the SQL scripts from the changesets without actually updating the database. This Offline Database Support functionality is called updateSql. This becomes handy when you cannot directly run Liquibase changesets on the target database or if the output of the changesets needs to be reviewed.

Note that updateSql checks the transactions within the DATABASECHANGELOG table to determine what SQL statements to generate. With that said, in the event that you cannot directly run the changesets against the target database, you can ask for the DATABASECHANGELOG table and use that to keep the history correct.

To streamline the process of generating SQL scripts, it would be useful to create a batch file that would contain the command and parameters. Let’s say that the filename is GenerateSQL.bat which currently contains the following values targeting an Oracle database:

C:\Dev\liquibase-3.3.2-bin\liquibase ^
--classpath="C:\Dev\liquibase-3.3.2-bin\lib\ojdbc7.jar" ^
--driver="oracle.jdbc.driver.OracleDriver" ^
--url=jdbc:"oracle:thin:@ORA-DBDEV:1521:DEVORA11G" ^
--password=asd123 ^
--changeLogFile="C:\Dev\LiquiBase\ORACLE\%1" ^
--logLevel=debug ^
--logFile="C:\Dev\LiquiBase\ORACLE\" ^
updateSQL > C:\Dev\LiquiBase\ORACLE\

Line 01: Location of Liquibase binary
Line 02: Location of JDBC driver. Valid values are:

  • ojdbc7.jar (ORACLE)
  • sqljdbc41.jar (MSSQL)

Line 03: Name of the JDBC driver. Valid values are:

  • oracle.jdbc.driver.OracleDriver (ORACLE)
  • (MSSQL)

Line 04: Details of the database server. Valid values are:

  • jdbc:”oracle:thin:@<SERVER_NAME>:<PORT>:<SERVICE_ID>” (ORACLE)
    • jdbc:”oracle:thin:@SERVER01:1521:DEVORA11G”
  • jdbc:”sqlserver://<SERVER_NAME><SERVER_INSTANCE>;databaseName=<DB_NAME>” (MSSQL)
    • jdbc:”sqlserver://SERVER01SQL2014;databaseName=DEVSQL”

Line 05: Database server username
Line 06: Database server password
Line 07: Location of the Liquibase change set file (*.xml)
Line 09: The log file for the operation
Line 10: The file where the generated SQL scripts will be stored.

Lines 07 and 10 have “%1” which represents an argument passed during execution of the batch file. This batch file can be used as follows:

C:\Dev\Liquibase\GenerateSQL.bat ChangeSetFileName.xml

This command will create and

You can integrate this process in Visual Studio by following this article. Note that you need to change the contents of the batch file to use updateSql.

How To: Install Liquibase On Your Local Machine


Download all pre-requisites and dependencies:

* – Download sqljdbc_4.1.5605.100_enu.tar.gz then extract sqljdbc41.jar
** – Download ojdbc7.jar


  • Install Java JDK
  • Extract Liquibase to a folder on your local machine (e.g. c:devliquibase-3.3.3-bin)
  • Copy sqljdbc41.jar and ojdbc7.jar to the lib folder of Liquibase (e.g. c:devliquibase-3.3.3-binlib)
  • Modify the liquibase shell file located on the root folder (e.g. c:devliquibase-3.3.3-binliquibase.bat) by adding “-Xmx1024m” after JAVA_OPTS=

java -cp "%CP%" %JAVA_OPTS% liquibase.integration.commandline.Main %CMD_LINE_ARGS%


  • Add Liquibase to your PATH environment variable by:
  • Right-clicking Computer > Properties > Advanced System Settings > Advanced tab
  • Click Environment Variables button
  • Edit PATH variable and put in the Liquibase folder (e.g. c:\dev\liquibase-3.3.3-bin)

Congratulations! You are now a proud owner of a computer with Liquibase.

How To: Execute Liquibase Database Change Log file (a.k.a. "driver file") from Visual Studio

The Liquibase Database Change Log file or as we refer to it, the “driver” file, is the root of all changesets. This is the file that is passed to Liquibase during execution as the changeLogFile parameter which lists all changesets that needs to be executed in order. And because we love Visual Studio, we’d like to execute the driver file right from the IDE.

First step is to create a batch file with the following contents. Place this file in a folder that you can easily remember (c:\Dev\Liquibase\LBUpdateSQL.bat):

C:\Dev\liquibase-3.3.3-bin\liquibase ^
--classpath="C:\Dev\liquibase-3.3.3-bin\lib\sqljdbc41.jar" ^
--driver="" ^
--url=jdbc:"sqlserver://;databaseName=TARGET_DB" ^
--defaultSchemaName=dbo ^
--username=******** ^
--password=******** ^
--changeLogFile=%1 ^
--logLevel=info ^
--logFile="C:\Dev\LiquiBase\logs\output.log" ^

Don’t forget to change the values for TARGET_DB, username and password. Also make sure that the paths are valid and appropriate (lines 1, 2 and 10).

Next step is to open Visual Studio and click on TOOLS > External Tools… and click the Add button. Fill-out all the fields as in below and make sure Close on exit is not checked:


Now this part is important. Make sure that the Initial directory points to the location of the driver file (in this case its C:\Dev\git-repos\DatabaseScripts\(project_name)\updates). This will ensure that the filename field in the DATABASECHANGELOG table only contains the filename of the changeset and not the full path. To understand why this is important, read more here.

Click on Ok to close the External Tools window.

Lastly,open the driver file in Visual Studio and click on TOOLS > Liquibase (this is what you placed in the Title field in the screenshot above).


There should be a command window that pops up that shows if the execution has failed or succeeded. The equivalent of all of this is like executing the batch file via command window while on the folder that contains the driver file with the driver file as an argument.

How Liquibase Considers A Changeset As Unique

We have a sandbox here in the office that has a database that we run the Liquibase Database Change Log file (a.k.a. “driver file”) against every now and then. We do not develop against this database since one of its purpose is to ensure that the latest version of the driver file runs without problems.

A few days ago, I took a backup of that database and restored it to my local machine. According to the DATABASECHANGELOG table, the driver file was last ran on 17 JUN (see screenshot below). However, when I tried running the latest Liquibase driver file from /develop against my now local db, I got a variety of errors ranging from duplicate key values to tables/columns already existing.


I might have missed the email but last time I checked, the idea was to allow running and re-running of the changesets without having a negative effect and without having the execution error out. I had to exclude a bunch of changeset entries in the driver file to get it to finish without reporting any errors. Below is the list with the reason why it failed:


An officemate tried to run the latest driver file on his local machine and worked without any problems. We checked the DATABASECHANGELOG table for the existence of the IDs of the changesets and to our surprise, they were already there. The errors being thrown due to the lack of precondition in the changesets are just a manifestation of a different problem altogether (although the lack of precondition on the changeset is a problem on its own). We were able to come to that conclusion because Liquibase will only try and run the changeset if that changeset’s ID is not on the DATABASECHANGELOG table. So why is Liquibase trying to execute a changeset when the ID of the changeset is already in the DATABASECHANGELOG table?

Upon further investigation, we came upon this question on StackOverflow: Liquibase tried to apply all changeset, even if database is present‌
The take away is that Liquibase tracks each changeset as a row in the DATABASECHANGELOG table which is composed of the combination of the “id”, “author” and a “filename” column.

If we go back to the first screenshot above, you’ll notice that the value for the FILENAME column after 17 JUN 2015 has changed. At this point, it means that I’ve restored a backup of that database to my local machine and the path where I’ve been executing Liquibase is different from the path where Liquibase was being executed on the sandbox in the office.

So how did we solve the problem?

1.) We cleaned up the filename column so that it only contains the actual filename of the changeset.*

2.) Made modifications on the way we were executing the driver file moving forward so that the FILENAME column only contains that – the filename without paths. (How To: Execute Liquibase Database Change Log file (a.k.a. “driver file”) from Visual Studio).


.* truncated the DATABASECHANGELOG table, dropped all affected tables and ran the driver file.

7 Lessons I Learned When I Got Married

To my mind, these are the things that I learned after I got married. Well, it doesn’t really mean that everything listed here are new to me, it’s just that some of these got more emphasized in the months that came by after tying the knot.

#1: If The World Ends On 2011, 2012 Or Any Other Year, It Doesn’t Matter

On 2011, doomsayers were predicting that the world would end on May 21. For some reason, nothing happened and it got rescheduled at October 21 of the same year – just a day after my wedding. Despite not knowing what the future holds, my wedding vow went like “… to love you, take care of you and provide for our family… This is my promise, this is my vow and this is what I intend to keep for all the rest of my days in this life and the next…” To some, it might be too ideal and unrealistic but to me, it doesn’t matter what they say. I got married to the woman I love, the one I know I will grow old with, to the one whom I know I would like to be with until the end of time – either the end of my time in this world as an individual or the world’s end at a cosmic scale. Either way, I’m the happiest man dead or alive.

#2: Individual Personalities Will Clash

I grew up with only one big brother; she grew up with two big sisters and one big brother. We are both the youngest in our families (“bunso”) thus, as I am told (and I do not believe in this by the way), we always get our ways. Assuming that the last statement is true, that fact alone merits as a good excuse as to why we will always have our different views on things, different stand and different expectations. Every now and then, we get to a point where stubbornness sets in and we can’t even agree to disagree. It’s like being alone for the longest time then you bump into something in the dark and all of a sudden that something bumps back. But the kicker is that it’s ok. It’s ok to get into fights and make a mess every once in a while just as long as you both clean up the mess and try to find closure.

#3: Money Is Essential But Not The Purpose Of Life

This lesson is best explained by Twitter CEO Dick Costolo when he said that “we should think of revenue like breathing – it’s necessary for life, but it’s not the purpose of life.” Due to the nature of my family’s business, there are times when the grass is green and there are times when the well is dry (at the time of writing this, the well is not only dry, but has already accumulated dust). Maybe it serves as a reminder that the value of money is always more than what you think it is but it doesn’t mean that that is all there is to it. It’s true that money makes almost everything in the world happen. Keyword: almost. For the simple joys in life, no amount of money can ever replace rare instances where you both know that you are truly happy. Like raiding the kitchen at midnight or staying in bed on a lazy rainy Sunday afternoon or singing at the top of your lungs while on a road trip or just sitting in the park watching the leaves fall down as you welcome winter on a foreign land. Money will buy you a lot of things but money and all the things that you bought with it won’t last. Shared happy memories do.

#4: Being Married Doesn’t Mean Giving Up Time For Yourself

Social norm dictates that married couples should always be together, most especially for newlyweds. I don’t know why that is but I believe that it exists for a reason. Is it relevant at this day and age? Maybe or maybe not. But my point is that the demands of society can put most of one’s plan in the backburner. This includes personal goals and targets like a master’s degree or a solitary trip to Europe or a pilot’s license. Most often than not, when faced with a choice between an activity that involves both me and my wife on one hand and an activity that can be done with just myself on the other hand, I end up choosing the one with my wife on it. I’ll admit that during the first stages of my realization, it felt like the dreams I’ve set way back before I got married will never come true. But as they say, never say never right? What I didn’t realize back then was that my dreams are still the same. They’re still dreams, the same ones I had before getting married. They may be a lot harder to achieve now but when I do, success will be so much sweeter and more fulfilling now that I have someone to share it with. If I fail, I know that someone will always believe in me even at times when I don’t.

#5: Be Ready To Add More Rules

As you both discover more about each other in the context of married life, expect to add more rules in your relationship in every waking hour. These rules vary from the mundane to the complex such as shaving your smug face before seeing her mom or when it’s time to become that psychic mind reader once again just to know if she wants flowers, chocolates, coffee, a new bag and shoes or all of the above. [DISCLAIMER: these are out-of-this-world examples only. The names/identities of the person(s) involved are changed for their protection. Yeah, you know who you are.] But despite how crazy these rules are, you know that it goes both ways. Sooner or later you’ll realize that you have the power to do the same. What is important is to know the rules so you’ll know how to bend them and make them work in your favor. Spend an afternoon finding loop holes just for fun and have the courage to break them every now and then for sanity’s sake. The most important thing to determine is to know if the rules are worth breaking. Pfffft! Rules? They’re just guidelines anyway. 🙂

#6: Don’t Be Afraid To Ask Married Couples

The best teacher is experience. So what will you do when you don’t have any experience and you’re not sure what to do next? Ask. Just ask. There’s no definitive manual for living a married life. You play it by ear. So when you ask, listen. For sure, someone has experienced something somewhere sometime that is somewhat similar to your situation. You can learn a lot from their stories and how they handled the situation as well as from their mistakes and how they would have done things differently. Families and friends are more than happy to share a story or two especially if they went through similar situations that you’re in now. What’s good about this is that as you progress in your married life, you’ll realize that you knew that right thing to do in certain situations all along. You just needed to hear the right words to boost your confidence and the affirmation that everything is going to be alright.

#7: Parents Hit The Bull’s Eye When They Said “You’ll understand this better when you get married”

When you’re young, you’re probably curious, eager and stupid. And mostly stupid. You tend to question a lot of things on why they are the way they are. It’s not farfetched that you’ve probably heard this line a couple of times: “You’ll understand this better when you’re married.” Then it’s the end of the conversation. There are simply no words that can describe what married couples have that most single people don’t have. I cannot accurately pin point it if it’s the unspoken connection and understanding, the motivation that drives the couple on certain decisions or the trust on each other that the right thing will and shall be done.

To my Mom and Dad, thank you and I love you both. I think I understand now.