Time Navigator

Time Navigator
Migration Guide
Upgrading Time Navigator Version 4.0.1

or 4.1 to Version 4.2
Version 4.2 SP8

Ref: mig42e_sp8_rev1_20111028
October 28, 2011
Table of Contents
OVERVIEW...................................................................................................... 4
Whats inside........................................................................................................................................... 4
Getting assistance ................................................................................................................................... 4
Getting information ................................................................................................................................ 4
PLANNING YOUR UPGRADE ........................................................................ 5

Overview of Upgrade Preparation Steps .............................................................................................. 5
1.
Verify the State of your Physical Environment ........................................................................... 5

Modifying the catalog maximum size to 256 or 512 GB...................................................................... 5
2.
Back Up Your Catalog ................................................................................................................... 6

Once the backup is complete ................................................................................................................ 6
3.
Request a 4.2 License File .............................................................................................................. 6

To request an add-on to an existing license file:................................................................................... 7
4.
Verify Agents/Clients Compatibility-Limitations ........................................................................ 7

Restrictions: .......................................................................................................................................... 7
5.
Verify Tunables, Command Line Interface and API .................................................................. 8

Modified Tunables................................................................................................................................ 8
Obsolete Tunables ................................................................................................................................ 9
Command Line Interface .................................................................................................................... 10
API ..................................................................................................................................................... 11
6.
Scheduling your Upgrade ............................................................................................................ 11
7.
Upgrading Time Navigator for Exchange from V4.1.0 SP4 and Earlier to V4.2 .................... 11
exmerge .............................................................................................................................................. 12
Individual Message Restore: SER with CDP ..................................................................................... 12
Environment Variables: X2K_SER vs. TINA_X2K_SER ................................................................. 12
Backup Selections .............................................................................................................................. 12
8.
Upgrading toTime Navigator Version 4.2SP7 for HyperStream Users ................................... 12
9.
Upgrading to HyperStream 2.1SP3 from a version prior to 2.1SP1 P4483 ............................. 13
10.
Upgrading from a Time Navigator 32-bit Version to a 64-bit Version ................................ 13
Time Navigator Server ....................................................................................................................... 13
Time Navigator Agent ........................................................................................................................ 13
11.
Upgrading a Time Navigator multi-catalog with LSM version ........................................... 14
12.
Additional Upgrading Information ......................................................................................... 14
SharePoint 2010: New Atempo VSS Requestor Setup ....................................................................... 14
Parameters, alarms_filter and domains configuration files ................................................................. 14
New Schedule Rule Types in Version 4.2 .......................................................................................... 14
Filtering Processes in the Conf/parameters file .................................................................................. 14
Restore of Large Files may Freeze with Backup using Tar Format (Technical Note 1042)............... 15
Computation of the Archived Volume ............................................................................................... 15
2
VMware .............................................................................................................................................. 15
VLSA.................................................................................................................................................. 15
UPGRADING FROM TIME NAVIGATOR 4.0.1 TO TIME NAVIGATOR 4.2 . 16

1.
Installing a License Add-on ......................................................................................................... 16
2.
Upgrading your 4.0.1 Time Navigator Server ............................................................................ 16
3.
Restoring the Catalog ................................................................................................................... 17
4.
Upgrading Your 4.0.1 Storage Nodes.......................................................................................... 18
5.
Upgrading your 4.0.1 Agents ....................................................................................................... 18
6.
Additional Catalog Operations .................................................................................................... 19

To Back up an AS400 Platform .......................................................................................................... 19
To Back up a VMware Platform......................................................................................................... 19
MAC OS X: Upgrading a Time Navigator Server Version 4.0 with X11 to Version 4.2 with Native
GUI ........................................................................................................................................................ 20
UPGRADING FROM TIME NAVIGATOR 4.1 TO TIME NAVIGATOR 4.2 .... 21

1.
Installing a License Add-on ......................................................................................................... 21
2.
Upgrading your 4.1 Time Navigator Server ............................................................................... 22
3.
Restoring the Catalog ................................................................................................................... 23
4.
Upgrading your 4.1 Storage Nodes ............................................................................................. 23
5.
Upgrading your 4.1 Agents .......................................................................................................... 24
Overview
This document will assist you in performing a seamless migration by guiding you through the upgrade
steps, and pointing out the issues requiring special attention.
Whats inside
This document contains information on the following topics:
Planning your upgrade

There is a series of steps that you must follow to ensure a successful upgrade.
Upgrading Time Navigator

This section describes the actual software upgrade process.
Verifying the Time Navigator upgrade

Several verifications as recommended before you start using the new version.
Getting assistance
Although the migration is a normal phase when using Time Navigator, it remains a sensitive
phase and must be performed with great care.
Most users do prefer to seek Atempos Professional Services assistance to guide them
through the migration of their Time Navigator environment.
At the very least, we encourage you to contact your Atempo Sales Representative when you
are ready to migrate.
Getting information
In addition to reading the present guide, which is designed to take you through all the
migration steps, you can also refer to the following information sources:
Time Navigator Release Notes Guide: Lists all new features and behaviors for the newly
released version. This document is located on Atempo Customer Support Web site.
Time Navigator Knowledge Base, located on our Web site at the following address:
http://support.atempo.com
Time Navigator DVD-ROM, where you will find all the Time Navigator guides. In
particular:
Time Navigator Installation Guide: Contains details about installing,

upgrading, uninstalling and configuring Time Navigator Server and the various
Agents backed up by Time Navigator.
Time Navigator Bug Fixes and Known Issues Guide: Describes the bug fixes
and known issues for Time Navigator version 4.2.
Throughout this document, you will find references to the guides above, where appropriate.
Planning your upgrade

In order to successfully upgrade to Time Navigator Version 4.2, you need to prepare as described in the
following Upgrade Preparation Steps. These steps apply whether you are migrating from a version 4.0.1 or
4.1 to Time Navigator 4.2.
Overview of Upgrade Preparation Steps

Step
How do I know the step is completed?
1.
Verify the state of your physical

environment
You have at least 2.5 times the size of your current catalog
available when performing the upgrade and eventually up to
512 GB to accommodate future growth of the catalog.
2.
Perform a Catalog Backup
You generated a catalog_save1.cod file in the directory

you specified for the backup.
3.
Request a License File (for addons only)
You have received an email from Atempo containing a link to the

License Generation Web page.
4.
Verify Agents Compatibility
You know what components are still supported in V4.2, and what
solution to adopt for the components that are no longer supported.
5.
Verify Tunables, Command Line

Interface and API compatibility
You know if the tunables, commands or API attributes you use on

a regular basis have been modified. If so, you have taken the
modifications into account.
6.
Plan your upgrade before a

scheduled full backup
You have verified that the backup that will follow the upgrade is a
full backup.
1. Verify the State of your Physical Environment

Catalog Size
When you restore your 4.0.1 or 4.1 catalog in version 4.2, its size will increase to
approximately 2.5 times its initial size, depending on the filling rate of your catalog before
the upgrade. This is due to a new catalog internal organization.
In addition, the 4.2 catalog has the capacity to grow as needed, up to a maximum size of:
256 GB if the catalog includes agents prior to version 4.2
512 GB if the catalog only contains version 4.2 agents.
Modifying the catalog maximum size to 256 or 512 GB
The catalog maximum size modification takes place during the catalog restore step, once the
software upgrade is complete:
Launch the command
tina_init -max_catalog_size 256 -file_size 2048
for a 256 GB maximum size
or
tina_init -max_catalog_size 512 -file_size 4096
for a 512 GB maximum size
Follow the restore steps as described in Restoring the Catalog page 23.
When you reached the advanced parameter informations, enter y to view the
advanced parameters and verify that the Maximum Size is 256GB or 512GB, and that
the odb File Size is 2048MB or 4096MB (depending on the tina_init command you
launched).
Advanced parameters definition? (y(es) / n(o)): (n) y
Note: The maximum size cannot be greater than the available space on your disk.
2. Back Up Your Catalog

Perform this task when you are ready to upgrade, right before launching the actual software
update.
a.
Open the Command Line Interface.

Windows: Choose the menu Start-All Programs-Time Navigator-UtilitiesCommand Line Interface. This opens a command prompt window preset to use
Time Navigator environment variables.
Unix: Open a shell window. Go to the Time Navigator installation directory .
The Time Navigator environment variables must be set. To do so, launch the
tina.sh or tina.csh script, depending on the shell you are using.
Mac OS X: Open a terminal. Provide the password of the administrator using
the command: sudo s. Move to the Time Navigator installation directory.
Set the Time Navigator environment with the following command:
. ./.tina.sh
b.
Stop the tina service with the command tina_stop
c.
Use the tina_odbsave command to back up your catalog:

For instance, if the name of your catalog is mycatalog and you want to store
the catalog backup in the directory c:\savetina, enter the following command:
tina_odbsave -catalog mycatalog -file
c:\savetina\mycatalog.cod
d.
Repeat the command for all the catalogs you want to back up.
e.
Unix: Exit the $TINA_HOME\Bin directory, as it will prevent the installer to

run successfully.
Once the backup is complete
Verify that a catalog_save1.cod file has been created in the directory

you specified. The size of that file should be around 10% of the catalog size.
Verify in the events that there are no error logs concerning the catalog backup.
3. Request a 4.2 License File

A new license file is only needed if you want to add functionalities to your existing license
file and in the cases listed below.
From version To version You need to request a new license file

4.0.1
4.2
No. Your 4.0.1 license file will work in version 4.2.
Except if you were using:
- an NDMP application to back up an AS400 platform
- a List application to back up a VMware platform.
4.1
4.2SP6
4.2
4.2SP7
In these two cases, you must request an add-on to your

license.
No. Your 4.1 license file will work in version 4.2.
Only if you were using:
- VMware VCB VStorage API, you need to request
an add-on to your license to keep using it in 4.2SP7.
- Hyper-V, you need to request a license for a second
agent if you want to use the CSV cluster feature.
To request an add-on to an existing license file:
Send an email to
LKS@atempo.com if you are located in Europe or Asia
lksus@atempo.com if you are located in North America

requesting an add-on to your existing license. Indicate how many new agents
will be included in the add-on..
Join a copy of the existing main atempo.lic file located on the License
Manager to your request.
You will receive from Atempo an email containing a link that will allow you to
generate your license add-on when you are in the actual upgrading process.
Keep this message in a safe place as you will need it later.
For more details about License Manager, refer to the Appendix of the Time Navigator
Installation Guide.
4. Verify Agents/Clients Compatibility-Limitations
Time Navigator 4.0.1 and 4.1 agents can be backed up and restored with a
version 4.2 server.
Restrictions:
HyperStream Server
If you were using HyperStream V1.0 with Time Navigator 4.2SP5 and you are
upgrading to HyperStream V1.2 with Time Navigator 4.2SP6, note that both
HyperStream Server and Time Navigator clients (server and agents) must use the
same version.
Administration Console
A version 4.0.1 or 4.1.0 catalog cannot be administered with a version 4.2
Administration Console. This is why catalogs must be backed up prior to the
migration and restored thereafter.
Note: A version 4.0.1 or 4.1.0 agent can however be administered via a version 4.2
Administration Console.
Backup Master
A version 4.2 host cannot be a backup master for 4.0.1 or 4.1 agent. The master must
be in the same version as the masterized agent.
SnapBackup
It is not possible with a Time Navigator 4.2 server to delete or use the new Verify
feature on snapshots from a 4.0.1 or 4.1.0 agent. It is recommended to upgrade both
the server and the agents at the same time.
Restore and Archive Manager
To ensure that version 4.0.1 or 4.1.0 agents can be restored with a version 4.2 Restore
& Archive Manager, you must open the Restore interface from the Administration
Console. Do not open it directly from the Start Menu or using the command line.
Web Interfaces
A version 4.2 Web Restore interface cannot be used to restore a 4.0.1 or 4.1.0 agent.
A version 4.2 Web Supervision interface cannot monitor version 4.0.1 or 4.1.0
catalogs.
Command Line
The tina_restore , tin@, tina_del, tina_alpha commands in version 4.2
cannot be used for version 4.0.1 or 4.1.0 agents.
API/tina_shell/tina_perl
API/tina_shell/tina_perl scripts executed on a version 4.2 platform using the objects
TNNavigator, TNRestore, TNBackup, TNArchive, or TNFolder, will not work on a
4.0.1 or 4.1.0 agent.
Likewise, API/tina_shell/tina_perl scripts executed on a version 4.0.1 or 4.1.0
platform will not allow you to execute version 4.2 administrative tasks.
Time Navigator 4.2 agents cannot be backed up or restored with a 4.0.1 or

4.1.0 server.
The complete Time Navigators Compatibility guide is located on Atempo web

site:
http://www.atempo.com/products/timeNavigator/compatibility.asp
5. Verify Tunables, Command Line Interface and API

Some modifications took place concerning tunables, commands and API object attributes
between version 4.0.1 and 4.2. Following is a summary of these changes.
Note: See the Time Navigator Release Notes for additional details.
Modified Tunables
Tunable Name
Modification
Versions 4.0.1
Catalog File Location

(global_odb_translation_path)
The syntax used is now the native syntax of the

operating system and no longer the POSIX syntax.
Warning: If you used this tunable in version 3.7.xx in a
Windows environment, make sure you modify the
syntax of the catalog file path. Otherwise, you will not
be able to restore your catalog after the upgrade.
Tunable Name
Modification
Split Catalog File

(odb_translation_path_n)
The syntax used is now the native syntax of the

operating system and no longer the POSIX syntax.
Warning: If you used this tunable in version 3.7.xx in a
Windows environment, make sure you modify the
syntax of the catalog file path. Otherwise, you will not
be able to restore your catalog after the upgrade.
Macromultiplexing (MMX) Job Reading

and Writing from the same Disk
(disable_axe_lock)
It is replaced by enable_axe_lock and its behavior is

reversed
Cache Allocation per Job

(running_job_percent_in_cache)
The default value changes from 0% to 90%
Tape File Size (sizeof_tile)
The default value is now 7 168 MB instead of 1 024 MB
-xdr_buf_size (start tunable)
The default value is now 128 KB instead of 32 KB
Versions 4.2
Filesystem Backup with SGI Backup API
(bapi_fs)
The sidf format is now supported
Force the Remote Mover Listening Port

(rem_dtm_data_tcp_num)
This tunable is no longer internal.

It is now possible to launch simultaneaous backup and
restore operations when this tunable is set.
Language
Three new possible values: German, Chinese and

Korean
Use Remote Mover

(lan_free_use_remote_dtm)
The default value is now AUTOMATIC
Obsolete Tunables
Tunable Name
Disappeared in Version
Versions 4.1.0
Limit Number of Simultaneous Jobs

(limit_nb_jobs)
4.1.0
Maximum Number of Simultaneous Jobs

(max_nb_jobs)
4.1.0
Versions 4.2
Accounting Event Retention Time
(keep_acct_days)
4.2 SP0
Catalog Filling Rate Alarm

(catalog_filling_rate_alarm)
4.2 SP6
Critical Alarm Retention Time

(keep_a_crit_days)
4.2 SP0
Debugging Event Retention Time

(keep_debug_days)
4.2 SP0
Tunable Name
Disappeared in Version
4.2 SP4
Disable Catalog Auto Expansion

(disable_auto_expand)
Error Event Retention Time
(keep_error_days)
4.2 SP0
Fatal Event Retention Time
4.2 SP0
(keep_fatal_days)
Information Event Retention Time
(keep_info_days)
4.2 SP0
Major Alarm Retention Time

(keep_a_maj_days)
4.2 SP0
Minor Alarm Retention Time

(keep_a_min_days)
4.2 SP0
Retention Time for Fuzzy Object Events

(keep_fuzzy_obj_days)
4.2 SP0
Script to Run During Media Allocation on

Restore (cart_allocation_script_on_restore)
4.2 SP1
Time Navigator Administration Domain Filter

(domain_filter)
4.2 SP3
Timeout before Scheduled Jobs Terminate

(timeout_on_scheduled_jobs)
4.2 SP0
Users Localization (Localization)
4.2 SP1
Warning Event Retention Time

(keep_warn_days)
4.2 SP0
Command Line Interface
Command Name
Modification
Versions 4.1.0 SP1
tina_sched
-estimation
tina_scm_control
erase certificate (obsolete)

import certificate (obsolete)
export certificate (obsolete)
Versions 4.2 SP0

tina_init
-catalog_name option becomes -catalog
tina_job_control
-abort option becomes -cancel

-suspend option becomes -pause
tina_restore
-all_inst option becomes -all_vers
Versions 4.2 SP3

tina_export
-drive_dest option becomes obsolete
tina_find
-job_id becomes -jobid, but -job_id is kept as

10
Command Name
Modification
an alias
API
The new attributes of the strategy object are not compatible with the deleted strategy
attributes. You must modify and recompile any executable or tina_shell script that uses
the old attributes.
The deleted attributes are:
TNStrategyFullFirstDate
TNStrategyFullFirstWeek
TNStrategyFullFirstYear
TNStrategyFullFreqDay
TNStrategyFullFreqHour
TNStrategyFullFreqTime
TNStrategyFullFreqWeek
TNStrategyFullFreqValue
TNStrategyFullFreqUnit
TNStrategyFullFreqMinute
TNStrategyIncrHour
TNStrategyIncrMinute
TNStrategyIncrPhaseDay
TNStrategyIncrPhaseTime
The deleted attributes are replaced by two new attributes:
TNStrategyFullSchedule
TNStrategyIncrSchedule
Modified Attributes:
TNDriveConnectType
TNJobPropertyMask
TNScheduleRuleFrequency
TNScheduleRuleProperties
6. Scheduling your Upgrade

Due to a change in the backup mode of file attributes, it is recommended to perform the
upgrade to Time Navigator 4.2 before a scheduled full backup. If the backup following the
upgrade is an incremental, it could be as voluminous as a full backup.
7. Upgrading Time Navigator for Exchange from V4.1.0 SP4 and Earlier to V4.2
Version 4.2 Exchange agent has been redesigned and differs from the Exchange agent found
in version 410SP4 and earlier versions. Note the following points before upgrading your
Time Navigator for Exchange agents:
Warning: If you are upgrading from version 4.1.0 SP5, this section does not apply since you
are already using the redesigned Exchange Agent.
11
exmerge
The restore of individual mailboxes using the exmerge utility is no longer supported with
version 4.2.
Individual Message Restore: SER with CDP
The new V4.2 Exchange agent is not compatible with previous agents, using SER.
Messages backed up in version 4.1.0 SP4 with SER cannot be restored with version 4.2, since
Time Navigator now uses Continuous Data Protection technology for the SER functionality.
In order to restore such messages, you need to:
Keep V4.1.0 SP4 on your agent, i.e., when you update the agent, create a new 4.2
environment rather than upgrading the existing environment. This will ensure that
the Time Navigator service (daemon) for version 410SP4 is still present on the
agent.
Uncheck the option use etc/services when upgrading in order to allow the creation
of a second service using the same ports.
Use the new 4.2 environment to perform Exchange backups of your agent. This
implies that only the Time Navigator 4.2 service (daemon) is running. The Time
Navigator 410 SP4 service (daemon) should be stopped and set to Manual.
Whenever you need to restore a message that was backed up with version 410 SP4,
close Time Navigator and stop the 4.2 service on the agent. Manually start the
410SP4 service, open Time Navigator and perform the restore. Restart version 4.2
when you are done.
Alternatively, you can choose not to upgrade your Exchange agents and upgrade only the
server. This option is supported by Time Navigator. If you do so, you will not be able to use
the new CDP feature.
Note: This restriction concerns only messages backed up with the SER. Exchange databases
backed up in V4.1.0 SP4 can be restored in V4.2.
Environment Variables: X2K_SER vs. TINA_X2K_SER
The variable X2K_SER has been renamed to TINA_X2K_SER. If you were using the
variable in version 410SP4, you need to reset the new variable to on in version 4.2.
Backup Selections
The 410SP4 backup selections used to back up all members of a department (for instance
/Private Folders/department_name/) are no longer valid. They must be replaced by individual
selections for each department member (for instance /mailbox/user1, /mailbox/user2 ). In
addition, to avoid the generation of alarms, you should delete the former selections set on
Private Folders.
8. Upgrading toTime Navigator Version 4.2SP7 for HyperStream Users

Deduplication performances for HyperStream users have been greatly improved by
modifying the block division method for Windows data. The data and the metadata (i.e.,
attributes and ACLs) are now kept in separate blocks. The main benefit is that identical files
having different metadata will now be deduplicated across hosts and directories, greatly
reducing the amount of unnecessary data sent across the network and unnecessary storage for
the data. This optimization is activated by default on all new Time Navigator 4.2SP7
Windows agents.
12
However with this new method, all previously deduplicated blocks are seen as new blocks,
and the first HyperStream backup following the upgrade to Time Navigator 4.2SP7 will again
send all unique blocks of the Windows agent to the HyperStream repository. This could
cause the repository storage of the agent to temporarily grow up to twice its size, until old
blocks are recycled by retention.
For this reason, when you upgrade to Time Navigator 4.2SP7 the new method is deactivated
by default. To activate it, following the upgrade to Time Navigator 4.2SP7, you must set the
value of the tunable dtm_single_stream_per_object to 0 on the agents for which
you want to use the new method. Atempo recommends that you activate it progressively on
multiple Windows agents, to monitor the total repository growth and adjust your repository
space accordingly.
9. Upgrading to HyperStream 2.1SP3 from a version prior to 2.1SP1 P4483

For users wanting to upgrade to HSS 2.1 SP3 from a version prior to 2.1SP1 P4483, the
upgrade is a two-step process:
Request both versions HSS 2.1SP1 P4483 and HSS 2.1SP3 from Atempo Customer
Support service.
Run the setup for HSS 2.1SP1 P4483and perform the upgrade.
Then run the setup for HSS 2.1SP3 to complete the upgrade.
10. Upgrading from a Time Navigator 32-bit Version to a 64-bit Version

Time Navigator Server
To update a Time Navigator Server 32-bit to a 64-bit version, proceed as follows:
a.
Copy your configuration files

Make a copy of the contents of the Conf directory of the new version installation
directory. For instance c:\Program Files\Atempo\tina42\Conf.
b.
Replace the 32-bit version with a 64-bit version

1. Back up your catalog and keep the backup readily available (not in the
Time Navigator installation directory since it is going to be removed)
2. Uninstall Time Navigator
3. [Mac OS X only] : Reboot your Mac OS platform in 64-bit mode
4. Install Time Navigator 64-bit using the same environment name and port
numbers as the uninstalled version
c.
Overwrite the Conf directory

Overwrite the Conf directory of the 64-bit Time navigator version with the 32-bit
Conf directory that you copied in step a. above. This is to ensure that any
configuration customization you performed will be carried over to the new 64-bit
version.
d.
Restore your catalog

To complete the upgrade process, retore your catalog using the command tina_init
(see Restoring the Catalog p.17 or p.21).
Time Navigator Agent

The update procedure is the same as the server one, without the catalog backup and restore
steps.
13
11. Upgrading a Time Navigator multi-catalog with LSM version

If you are upgrading a multi-catalog with LSM version, you need to upgrade the storage node
(machine controlling the library) last, to make sure that the storage node is compatible with
the servers hosting the catalogs.
12. Additional Upgrading Information

SharePoint 2010: New Atempo VSS Requestor Setup
Beginning with version 4.2SP7, you no longer need to have a Time Navigator agent installed
on every server in the farm. A single agent on the Web server for the farm is enough. On the
other hand, you need to install the Atempo Vss Requestor service on all the servers in the
farm that you want to back up. A new Setup is available to install, configure and update the
Atempo VSS Requestor service.
Parameters, alarms_filter and domains configuration files
During the migration to the 4.2 version, the parameters, alarms_filter and domains
configuration files (all having a .txt extension on Windows systems) are upgraded and
converted to XML format. These files are UTF-8 encoded and can be viewed with a web
browser. You can edit them only via the Preferences Tool.
The old parameters, alarms_filter and domains files are renamed with a .old extension. They
are not used anymore.
New Schedule Rule Types in Version 4.2
Version 4.2 introduces three different schedule rule types whereas there was only one in
previous versions. When you upgrade, your rules will automatically be assigned a type
depending on the information they contain. The rule types are:
Start Rules
To define the days and times when backups should be launched.
Activity interval rules

To define time intervals during the day when backup can take place
Exclusion Rules
To define the days when backups should not take place.
Filtering Processes in the Conf/parameters file
Beginning with version 4.1.0, in the event file, tina_daemon processes are now suffixed
with their operation code. This has an impact on the use and configuration of tunables in the
Preferences Tool. It is now possible through the graphical interface to filter the processes
upon which the tunable values apply.
From the Configuration-Tunables menu of the Preferences Tool:
a. Click on New to add a parameter OR Properties to modify it.
b. In the Executables tab of the Tunable Properties window, select the executable(s ) upon
which you want to apply the parameters or click on Add all.
c. Once you have finished your modifications, click on OK.
In the Preferences Tool window, you will see the name of the tunable you have just defined,
followed by the keyword binaries indicating the executable(s ) concerned by the tunable. The
asterisk character, *, means that the tunable applies to all executables.
Please find below a few examples of tunables configurations:
To apply a tunable to all the processes:
Language: English, binaries: *, catalogs: *
14
To apply a tunable to the tina_adm executable only:

Soundless Message Box: yes, binaries: tina_adm, catalogs: *
Restore of Large Files may Freeze with Backup using Tar Format (Technical Note
1042)
A restore session under Time Navigator 4.0 or 4.1 can freeze with a file (larger than 8 GB)
backed up with a Time Navigator 4.0 catalog in tar format.
This happens when using the Lan-Free mode for the tar restore. The process simply locks up.
Explanation
Before Time Navigator version 4.1, tar POSIX was used when backing up using the tar
format. But this tar has some limitations. For example, files cannot be larger than 8 GB.
When Time Navigator backs up some files larger than 8 GB with versions 4.0.1, restore
works properly through the cache, because Time Navigator gets file details from catalog
only. File headers on tape are not taken into account.
However, when using the Lan-Free mode, Time Navigator gets file details from the file
header (not correct if larger than 8 GB). Therefore, the restore may freeze when reading the
tape.
This issue does not exist when backing up and restoring with Time Navigator version 4.1 or
4.2.
But you can still have an issue when restoring data backed up with older versions of Time
Navigator.
Solutions
1/ Run backups using Time Navigator version 4.1 or 4.2.
2/ If you have to restore tar backups containing files larger than 8 GB performed with older
versions of Time Navigator, change strategies properties of the host (or application) and
disable the Lan-Free option.
Then, the restore will be performed through the cache.
3/ If you still use older versions of Time Navigator (4.0.1), avoid files larger than 8 GB.
Computation of the Archived Volume
If your license uses volume based billing, you need to upgrade the agents where the archiving
is performed at the same time as your server. This is due to a change in the computation of
the archived volume. The computation now takes place on the server side and is scheduled
once a day at 8 AM .
VMware
Due to a change in the VMware application organization in the Restore & Archive Manager,
only backup classes set at the root of the application will remain valid after a migration from
a Time Navigator version prior to 4.2SP1 or 4.1SP5. All other classes will have to be
redefined in version 4.2SP4. In addition, the configuration file TINA_VCB_CONFIG_FILE
must be reinitialized following the migration..
VLSA
If you are upgrading from a version prior to 4.2SP6 and you were using the Virtual Library
System Application on a Windows platform, you need to uninstall and reinstalll the
Scheduling service in the Virtual Library System Application (Menu Scheduling ServiceUninstall then Scheduling Service-Install).
15
Upgrading from Time Navigator 4.0.1 to Time Navigator 4.2

Once you have completed all steps of the planning phase, the following procedure allows you to upgrade
your current Time Navigator 4.0.1 environment to a Time Navigator 4.2 environment.
1. Installing a License Add-on

If you have requested an add-on to your license file, you must:
Manually copy the add-on contents at the bottom of the main License file. Do
not copy the top lines (i.e., the three first lines with the SERVER, VENDOR
and USE_SERVER information), only the new component information. For
instance:
Restart the FlexLM service

or
In the FlexLM directory, run the command:
Lmutil lmreread c /atempo.lic
2. Upgrading your 4.0.1 Time Navigator Server

To upgrade a Windows server:
You must be logged in as Administrator to upgrade Time Navigator.
a.
b.
c.
d.
e.
Insert the Time Navigator DVD-ROM in your drive. If the installation autorun
does not start, execute Autorun.exe in the Windows Explorer.
Select Install Time Navigator 4.2.
Select Upgrade in the Operation Type Selection window.
Select the environment you want to upgrade.
Carefully check the Summary windows contents and click on Execute to start
the environment upgrade.
Note: During the upgrade, the version 4.0.1 Bin, Lib and Conf directories are moved to
the %TINA_HOME%\TinaSave directory. If you had created your own binaries and scripts
and stored them in either one of these directories, you need to move these binaries and scripts
back to the newly installed %TINA_HOME%\Bin, %TINA_HOME%\Lib or
%TINA_HOME%\Conf directory.
To upgrade a Unix server:
The DISPLAY environment variable must be set to allow the display on the machine on
which you are logged in.
You must be logged in as root to upgrade Time Navigator.
On Linux systems, the ncompress and binutils packages must be installed, in order to
be able to use the uncompress and strings programs.
a.
b.
Launch the install.sh script to start the Time Navigator Setup.

16
c.
d.

Note:
During the upgrade, the version 4.0.1 Bin, Lib and Conf directories are moved to the
$TINA_HOME/TinaSave directory. If you had created your own binaries and scripts and
stored them in either one of these directories, you need to move these binaries and scripts
back to the newly installed $TINA_HOME/Bin , $TINA_HOME/Lib or
$TINA_HOME/Conf directory.
The upgrade also modifies the contents of the tina.sh script. If you had modified
environment variables in that script, for instance to change the value of the
LD_LIBRARY_PATH for Oracle or DB2 agents, make sure you report these changes in the
Conf\tina.env.local file.
3. Restoring the Catalog

Note: Prior to restoring the catalog, make sure you have enough disk space available,
See Verify the state of your physical environment, page 5 for details.
This procedure allows you to restore the catalog mycatalog.cod that was backed up in
the c:\savetina directory during the upgrade preparation phase.
a.

Windows:
Choose the menu Start-All Programs-Time Navigator-Utilities-Command Line
Interface. This opens a command prompt window preset to use Time Navigator
environment variables.
Unix:
Open a shell window. Go to the Time Navigator installation directory. The
Time Navigator environment variables must be set. To do so, launch the
Mac OS X:
Open a terminal. Provide the password of the administrator using the
command: sudo s. Move to the Time Navigator installation directory. Set
the Time Navigator environment with the following command:
. ./.tina.sh
b.
Use the tina_init command to restore your catalog:

Note: In the following example, change the path, catalog and file name with
your own information.
C:\Program Files\Atempo\tina42\Bin>tina_init -catalog mycatalog
-file c:\savetina\mycatalog.cod
c.
d.
Repeat the command for all the catalogs you want to restore.
Make sure you keep a copy of the catalog backup file,
catalog_save1.cod in our example, should you need to revert to a premigration state.
17
4. Upgrading Your 4.0.1 Storage Nodes

Once the Time Navigator server has been updated to version 4.2, you can proceed with the
upgrade of the storage node.
To upgrade a Windows Storage Node:
a.
b.
c.
d.
e.
the storage node upgrade.
To upgrade a Unix Storage Node:

use the uncompress and strings programs.
a.
b.
c.
d.

Note: The upgrade modifies the contents of the tina.sh script. If you had modified
5. Upgrading your 4.0.1 Agents

upgrade of the agents.
To upgrade a Windows Agent:
a.
b.
c.
d.
e.
the agent upgrade.
To upgrade a Unix Agent:

18
a.
b.
c.
d.

the agent upgrade.
6. Additional Catalog Operations

To Back up an AS400 Platform
In Time Navigator version 4.0.1, an AS400 was backed up through an NDMP application.
With version 4.2, an AS400 is backed up with a new, dedicated, iSeries application: I5/OS.
Note: This procedure is mandatory. You will not be able to keep backing up an AS400 with
an NDMP application with version 4.2.
There is no automatic transformation of the NDMP application backing up an AS400 to a
version 4.2 I5/OS application. You have to proceed as follows:
Before upgrading:
Request a license upgrade to use the new I5/OS application.
Set the parameter NDMP_SERVER_TYPE of the application to the value
"TiNa AS400".
Upgrade the Time Navigator server and the agent on the AS400 platform.
After the upgrade, in command line, on the Time Navigator Server, run the
command:
tina_odbedit -opcode 31
To Back up a VMware Platform

In Time Navigator versions 4.0.1, a VMware platform was backed up through a List
application on a Linux host. In version 4.2, VMware platforms are backed up on VMware
host, by a VMware application.
Note: This procedure is not mandatory. You can keep using the Linux host and List
application to back up your VMware platform in version 4.2.
There is no automatic transformation of the List application and Linux Host into a VMware
application and VMware host You need to manually modify both objects. Proceed as follows:
Before upgrading, request a license add-on to use the new VMware

application.
Upgrade the Time Navigator server and the agent on the VMware platform.
After the upgrade, in command line, on the Time Navigator Server, run the
command:
tina_odbedit -opcode 30
19
MAC OS X: Upgrading a Time Navigator Server Version 4.0 with X11 to Version 4.2
with Native GUI
Following is the complete procedure to upgrade your Mac OS X server from the Time Navigator
4.0 version using X11 to Version 4.2 using native GUI. You need to back up your catalog(s)
(format as changed between 4.0 and 4.2), uninstall the 4.0 X11 version, install the 4.2 version and
restore your catalog(s).
Note: Adapt the paths and names used in the procedure to your own installation.
1.
2.
Open a terminal window and connect as root.

Stop Time Navigator
# cd /Applications/Atempo/tina
# . ./.tina.sh
# tina_stop
# ps awx | grep tina
There should not be any tina_daemons running.
3.
Save the current catalog:

# cd /Applications/
# mkdir Atempo.Save
# tina_odbsave catalog <your_catalog_name> -dir_dest
/Applications/Atempo.Save/
Change <your_catalog_name> with the name of your catalog. At the end of that command,
you should have a catalog_save1.cod backup file in the folder
/Applications/Atempo.Save/. Check the size, it should be approximately the same
size as usual catalog backup files.
Run the tina_event_viewer GUI, display "debug" severity messages, and check that
"tina_odbsave" did not generate any errors, or suspicious messages.
If yes, contact Atempo support.
4.
Copy configuration files.

Since the uninstallation is going to delete everything, copy the Conf directory, and if youre
using a Virtual Library (VLS) for backups, the Vtl directory.
# mv Conf/ /Applications/Atempo.Save
And if you have a VLS:
# mv Vtl/ /Applications/Atempo.Save
5.
Uninstall Time Navigator X11 4.0 version:

Insert the 4.0 CD-ROM in your CD-ROM drive
# cd <cdrom_mount_point>
# ./install.sh
Using the GUI, choose the uninstall option. At the end of the uninstallation, verify that the
folders /Applications/Atempo/tina and /etc/Atempo/tina have been deleted.
For added security, run the following command:
# cd /etc
# mv Atempo Atempo.old
In the file /etc/services, verify that there is no entry concerning tina (typically TCP port 2525
and UDP port 2526 were reserved for tina).
20
6.
Install Time Navigator 4.2 native GUI version:

Make sure to use ports 2525 and 2526 (or the one you use to work with), and be sure to
specify the Atempo License Manager hostname correctly.
At the end of the installation, exit from the setup, DO NOT CONFIGURE A NEW
CATALOG. Then restart your server, as you need to run a script to modify the SHMMAX
SIZE.
When the reboot is done, open a terminal and connect as root.
7.
Copy back the configuration files

# cd /Applications/Atempo.Save/
# cp Conf/catalogs /Applications/Atempo/tina/Conf/
# cp Conf/parameters /Applications/Atempo/tina/Conf/
# cp Conf/domains /Applications/Atempo/tina/Conf/ (if it
exists)
# cp Conf/hosts /Applications/Atempo/tina/Conf/ (if it exists)
# cp Conf/logs /Applications/Atempo/tina/Conf/ (if it exists)
# cp Conf/tina_env.local /Applications/Atempo/tina/Conf/ (if it
exists)
# cp Conf/web_supervisor_cfg /Applications/Atempo/tina/Conf/
(if it exists)
If you use a VLS:
# cp R Vtl /Applications/Atempo/tina/
8.
Restore your catalog.

The catalog must be stopped
# . ./.tina.sh
# tina_stop
# tina_init file /Applications/Atempo.Save/catalog_save1.cod
catalog_name <your_catalog_name>
9. Restart Time Navigator:

# tina_daemon
Run the Administration Console and connect to your catalog. It
should be fine.
Upgrading from Time Navigator 4.1 to Time Navigator 4.2

Once you have completed all steps of the planning phase, the following procedure allows you to upgrade
your current Time Navigator 4.1.0 environment to a Time Navigator 4.2 environment.
1. Installing a License Add-on

If you have requested an add-on to your license file, you must:
Manually copy the add-on contents at the bottom of the main License file. Do
not copy the top lines (i.e., the three first lines with the SERVER, VENDOR
and USE_SERVER information), only the new component information. For
instance:
21
Restart the FlexLM service

or
In the FlexLM directory, run the command:
Lmutil lmreread c /atempo.lic
2. Upgrading your 4.1 Time Navigator Server

To upgrade a Windows server:
a.
b.
c.
d.
e.
Note: During the upgrade, version 4.1.0 Bin, Lib and Conf directories are moved to the
%TINA_HOME%\TinaSave directory. If you had created your own binaries and scripts and
back to the newly installed %TINA_HOME%\Bin, %TINA_HOME%\Lib or
%TINA_HOME%\Conf directory.
To upgrade a Unix server:
be able to use the uncompress and strings programs.
a.
b.
c.
d.

Note:
During the upgrade, the version 4.1.0 Bin, Lib and Conf directories are moved to the
$TINA_HOME/TinaSave directory. If you had created your own binaries and scripts and
back to the newly installed $TINA_HOME/Bin , $TINA_HOME/Lib or
$TINA_HOME/Conf directory.
The upgrade also modifies the contents of the tina.sh script. If you had modified
22
3. Restoring the Catalog

Note: Prior to restoring the catalog, make sure you have enough disk space available.
See Verify the State of your Physical Environment, 5 for details.
This procedure allows you to restore the catalog mycatalog.cod that was backed up in
the c:\savetina directory during the upgrade preparation phase.
a.

Windows:
Choose the menu Start-All Programs-Time Navigator-Utilities-Command Line
Interface. This opens a command prompt window preset to use Time Navigator
environment variables.
Unix:
Open a shell window. Go to the Time Navigator installation directory. The
Time Navigator environment variables must be set. To do so, launch the
Mac OS X:
Open a terminal. Provide the password of the administrator using the
command: sudo s. Move to the Time Navigator installation directory. Set
the Time Navigator environment with the following command:
. ./.tina.sh
b.
Use the tina_init command to restore your catalog:

Note: In the following example, change the path, catalog and file name with
your own information..
C:\Program Files\Atempo\tina42\Bin>tina_init -catalog mycatalog
-file c:\savetina\mycatalog.cod
c.
d.
Repeat the command for all the catalogs you want to restore.
Make sure you keep a copy of the catalog backup file,
catalog_save1.cod in our example, should you need to revert to a premigration state.
4. Upgrading your 4.1 Storage Nodes

upgrade of the storage node.
To upgrade a Windows Storage Node:
a.
b.
c.
d.
23
e.
To upgrade a Unix Storage Node:

a.
b.
c.
d.

5. Upgrading your 4.1 Agents

upgrade of the agents.
To upgrade a Windows Agent:
a.
b.
c.
d.
e.
the agent upgrade.
To upgrade a Unix Agent:

a.
b.
c.
d.

the agent upgrade.
24

Time Navigator - Migration Guide - Mig42e

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Time Navigator - Migration Guide - Mig42e

Uploaded by

Copyright:

Available Formats

Upgrading Time Navigator Version 4.0.1

Version 4.2 SP8

PLANNING YOUR UPGRADE ........................................................................ 5

Verify the State of your Physical Environment ........................................................................... 5

Back Up Your Catalog ................................................................................................................... 6

Request a 4.2 License File .............................................................................................................. 6

Verify Agents/Clients Compatibility-Limitations ........................................................................ 7

Verify Tunables, Command Line Interface and API .................................................................. 8

Scheduling your Upgrade ............................................................................................................ 11

Upgrading toTime Navigator Version 4.2SP7 for HyperStream Users ................................... 12

Upgrading to HyperStream 2.1SP3 from a version prior to 2.1SP1 P4483 ............................. 13

Upgrading a Time Navigator multi-catalog with LSM version ........................................... 14

UPGRADING FROM TIME NAVIGATOR 4.0.1 TO TIME NAVIGATOR 4.2 . 16

Installing a License Add-on ......................................................................................................... 16

Upgrading your 4.0.1 Time Navigator Server ............................................................................ 16

Restoring the Catalog ................................................................................................................... 17

Upgrading Your 4.0.1 Storage Nodes.......................................................................................... 18

Upgrading your 4.0.1 Agents ....................................................................................................... 18

Additional Catalog Operations .................................................................................................... 19

UPGRADING FROM TIME NAVIGATOR 4.1 TO TIME NAVIGATOR 4.2 .... 21

Installing a License Add-on ......................................................................................................... 21

Upgrading your 4.1 Time Navigator Server ............................................................................... 22

Restoring the Catalog ................................................................................................................... 23

Upgrading your 4.1 Storage Nodes ............................................................................................. 23

Upgrading your 4.1 Agents .......................................................................................................... 24

Planning your upgrade

Upgrading Time Navigator

Verifying the Time Navigator upgrade

Time Navigator Installation Guide: Contains details about installing,

Planning your upgrade

Overview of Upgrade Preparation Steps

How do I know the step is completed?

Verify the state of your physical

Perform a Catalog Backup

You generated a catalog_save1.cod file in the directory

Request a License File (for addons only)

You have received an email from Atempo containing a link to the

Verify Agents Compatibility

Verify Tunables, Command Line

You know if the tunables, commands or API attributes you use on

Plan your upgrade before a

1. Verify the State of your Physical Environment

2. Back Up Your Catalog

Open the Command Line Interface.

Stop the tina service with the command tina_stop

Use the tina_odbsave command to back up your catalog:

Unix: Exit the $TINA_HOME\Bin directory, as it will prevent the installer to

Once the backup is complete

Verify that a catalog_save1.cod file has been created in the directory

3. Request a 4.2 License File

From version To version You need to request a new license file

In these two cases, you must request an add-on to your

To request an add-on to an existing license file:

LKS@atempo.com if you are located in Europe or Asia

lksus@atempo.com if you are located in North America

4. Verify Agents/Clients Compatibility-Limitations

Time Navigator 4.2 agents cannot be backed up or restored with a 4.0.1 or

The complete Time Navigators Compatibility guide is located on Atempo web

5. Verify Tunables, Command Line Interface and API

Catalog File Location

The syntax used is now the native syntax of the

Split Catalog File