HSS Replication requires attention when upgrading to 5.x

Call to action

 

It is strongly recommended to perform either or both actions below on your Time Navigator HSS drive configuration.

 

1 Change the username in the drive properties to include the tenant followed by a / as shown

 

Or using the new web-interface

 

 

 

2 Remove the environment variable  mirror  from the drives

Optionally you might want to set the debug variable to 1

Using Classic

Or with the web

You should remove the mirror variable unless you have older Tina agents that would not have the cache mechanism implemented.

We do recommend to set the debug variable to 1 on the drives at least for initial testing of the failover as this will give additional logging in the Tina events on how tina is selecting the target for the backup and restores.

Tenant name can be found as shown below

Note : the target of a replication tenant is colored RED on the replica

See the next section for more details on why this is required

Detailed background

 

Version 5.0 of ADE introduced the notion of tenants in the product

The tenants are logical servers within the physical server and tenants are managed independently.

The replication takes advantage of tenants and can operate on the tenant level.

However in versions prior to 5.0 tenants did not exist and steps were taken to allow upgrades to convert to the new model smoothly.

When a replication target is created you will notice that on the target a tenant is created in read_only mode with the  name of the source tenant. Behind the screens the user/password information is also replicated and streams or Lina databases will get replicated as being positioned in this tenant.

This is true for both Global and Selective replication.

Version 5.0 also introduced HVDS-2 and with Time Navigator 4.6 the HVDS-1 data was converted to HVDS-2 during the upgrades.

One of the benefits of HVDS-2 is the ability to fail-over to the replica automatically when the source ADE server was out of order as was already the case with HSS.

To allow time navigator to identify the replication destination (to fail over to) HSS drives used a specific variable

”mirror” that carried as a value the hostname:port of the replication target.

With 5.x and time Navigator 4.6.5 a new mechanism was introduced to provide that information to the tina agent although the old drive parameter continues to operate.

The new mechanism creates a hidden cache file on the agent performing a backup to HSS to indicate the mirror configuration (hostname, ports and tenant) this allows HVDS-2 to operate the same way even though HVDS-2 does not use tapes or drives.

 

 

Contact




    Skip to content