You can use isolated backup in the following way:

• Prepare your local storage (e.g., the memory stick):
  This step is not strictly specific to storeBackup. This is similar to the basic task you would do to prepare almost any Linux storage media. Make a Linux file system which is able to use hard links (e.g., ext2, reiserfs). You can do this by using graphical tools like gparted or as root on the command line using fdisk -l to identify the stick and mkfs.ext2 (or mkfs.reiserfs or whatever) to create the file system. You can also use a stick with NTFS.
  Mount your stick and create a directory as the top level backup directory for storeBackup.pl.
• Use storeBackupSetupIsolatedMode.pl to automatically copy the meta data from your master backup to the media you want to use for your travel. It will copy just a few megabyte - storeBackup.pl with option lateLinks only needs these meta data; no real file data is needed in order to generate incremental backups.
  NOTE: This script also changes your configuration file for storeBackup.pl - changes depend on your usage of the tool.
  For safety reasons, storeBackupSetupIsolatedMode.pl only picks up meta data from full backups. If your last backup of the series you've chosen is not yet a full backup, it asks you to run storeBackupUpdateBackup.pl.
  Depending on the usage of storeBackupSetupIsolatedMode.pl, it will also generate a new configuration file from your existing ones.
• Use storeBackup.pl to run your normal backups. If your configuration file was adjusted by the run of storeBackupSetupIsolatedMode.pl, you can use the newly generated one. Otherwise, you have to adjust the options by yourself (e.g., backupDir, lateLinks).
• After running storeBackup.pl to make the isolated backup(s), use storeBackupMergeIsolatedBackup.pl to merge your isolated (incremental) backups into your master backup repository once you have access to it again. storeBackup makes each of these steps more convenient and easier if you use configuration files.
  As you can see, it is a good idea to use configuration files when using storeBackup in isolated mode.
• After running storeBackupMergeIsolatedBackup.pl your local backups are copied to the central repository; you should now run storeBackupUpdateBackup.pl (or wait until it runs via cron, etc.). When everything is fine, you can delete all the affected files (directories) on your local media (e.g., the memory stick).

Naturally, you can use isolated mode together with the replication of backups, see replication of backups.

You will find detailed information in storeBackupSetupIsolatedMode.pl. Also, have a look at the description of storeBackupMergeIsolatedBackup.pl.

WARNING: It is not supported to run your lateLinks backup onto a file system with fat or vfat format (e.g., on your stick)! This type of file system is not able to distinguish between filenames in upper and lower case. This means, filename file.txt is similar to File.txt without any warning or error message. If you have two files or directories with the same name (only different in upper / lower case) in one directory, you will definitely not get all files in your backup.
But you can use NTFS if you want!