netvault backup 8.0 update 1 release notesend user release notes - netvault backup 8.0 page 4 of...

Copyright © 2007 BakBone Software K.K.

本ドキュメントには、 NetVault Backup version 8.0 のリリースに関する重要な情報が含まれています。本ドキュメント

では NetVault Backup 8.0 の新機能に関する簡単な説明とプログラム修正情報を提供します。 NetVault Backup 8.0の使用方法に関する詳細は、 NetVault Backup 8.x アドミニストレータズ・ガイドや関連する技術情報をご覧ください。

アドミニストレータズ・ガイド等は、バックボーン・ソフトウエアの下記 URL からダウンロードいただけます。

http://www.bakbone.co.jp/products/product_documentation.html

Section 1.0 - NetVault Backup 8.0 について .............................................. 2

Section 2.0 - 新機能 .................................................................................... 2

Section 3.0 - 一般的な注意事項................................................................... 3

Section 4.0 - NetVault Backup 8.0 のインストール ..................................... 4

Section 5.0 - NetVault Backup 8.0 にアップグレードするには ..................... 5

Section 6.0 - NetVault Backup 8.0 用ドキュメント ....................................... 9

Section 7.0 - 既知の問題点 ......................................................................... 9

Section 8.0 - ソフトウェア修正 .................................................................... 18

Section 9.0 - バックボーン・ソフトウエア株式会社について ........................ 20

NetVault Backup 8.0 Update 1 Release Notes

Contents

End User Release Notes - NetVault Backup 8.0 of 20

NVE 7006-66A 11/30/07

http://www.bakbone.com/support/product_documentation

オープン・システムのデータ・バックアップ／リカバリ・ソリューションを提供するバックボーン・ソフトウエアのNetVault Backup 8.0 は、あらゆる規模のシステム要求に合わせ拡張することのできるエンタープライズ・クラスの

データ保護機能を提供します。 NetVault Backup の柔軟なモジュラ・アークテクチャにより、様々な機能を組み合わ

せることで、現在の、そして将来のデータ保護要求にも応えることができるよう設計されており、実績ある信頼性と高性能を提供しています。 .

NetVault Backup の本バージョンにおける新機能は、下記の通りです。

新規対応クラスタ・アプリケーション - Veritas Cluster Server for Windows、 Sun Cluster (SPARC/x64)、Fujitsu PRIMECLUSTER を新たにサポートしました。

NetVault TrueCDP オプションの追加 - NetVault TrueCDP オプションがリリースされ次第、 NetVault Backup バージョン 8 から、この NetVault TrueCDP 機能をサポートします。

バックアップの一時停止 / 再開 - File System プラグインを使用してバックアップを行う際、” Restartable Backup” オプションをチェックすることで、バックアップ・データの転送時にバックアッ

プ・ジョブを GUI から一時停止し、その後再開させることが可能になりました。

サポート Audit ツール - テクニカル・サポート・チームによるレビューが行えるよう、お客様のシステ

ム環境に関する情報を簡単に収集することが可能になりました。

クライアント毎のファイアウォール設定 - クライアント毎に、ファイアウォール内のマシンかファイア

ウォール外のマシンかを設定することができるようになりました。クライアント毎にファイアウォールの状態を設定できることにより、 NetVault の通信に必要な開放ポート数を最小限に抑えることができる

ようになりました。

パスワードの有効期限ポリシーの設定 - 管理者が、全てのユーザにグローバル・パスワードの有効期限

ポリシーを設定できるようになりました。

ユーザによるパスワード変更 - NetVault Backup へのアクセス用パスワードを、ユーザが自分でログオ

ン・ウィンドウから変更できるようになりました。

ソース・デバイスの選択 - コンソリデーション、データ・コピー、リストアを行う際に、新規に追加さ

れたソース・タブから、データ元となるメディアを含むデバイスを指定できるようになりました。この機能を使用することで、必ずローカルのデータを使用してこれらジョブを実行するといった操作も可能になります。

複製およびデータ・コピーの暗号化対応 - バックアップ・セットの複製、データ・コピーの際にも、

データの暗号化機能が使用できるようになりました。

NVDB チェック機能 - NetVault Backup 8.0 から、NVDB Plugin で NetVault データベースのバックアップ

を実行する前に Media データベースと Scheduler データベースの整合性をチェックすることができる

オプション機能を提供します。これにより、いざという時 " 使用可能な " NVDB のコピーを確実に取得

することを可能にします。また NVDB チェック機能により、 NVDB を保存している物理ディスク・ス

ペースのボリュームの空き容量が少なくなってくると警告メッセージを出すことも可能です。

SVTL の容量拡張を行う CLI ツール - 新しい ”nvsvtlgrow” CLI ツールを使用して、SVTL ( 共有仮想テー

プ・ライブラリ ) のメディアの数、サイズを拡張できるようになりました。

1.0 - NetVault Backup 8.0 について

2.0 - 新機能


NetApp VTL のシャドウ・テープのサポート - NetVault Backup 8.0 から、物理テープがなくても、シャ

ドウ・テープ・プールからエクスポートされたテープを " クイック・インポート " することができる

NetApp VTL のシャドウ・テープ機能をサポートします。 File System Plugin v 7.1.6 の提供 - NetVault Backup 8.0 では、File System Plugin v 7.1.6 が標準インス

トールで含まれています。

NetVault Backup 8.0 とそれ以前のバージョンとの非互換性について - NetVault Backup 8.0 での変更に

より、バージョン 8.0 をインストールしているマシンは、 8.0 より前のバージョンをインストールして

いるマシンと下記のインスタンスにおいて互換性がありません。

NDMP 接続デバイスへのバックップの実行

NDMP Plugin を使用したバックアップの実行

上記どちらの場合においても、 NetVault Server と NetVault Client の両方に NetVault Backup 8.0 をイン

ストールする必要があります。

NetVault Backup 8.0 で NDMP Plugin を使用する際は、必ず NDMP Plugin v6.5 を使用してください。 SVTL ライセンス・チェックの廃止 - NetVault Backup 8.0 から、SVTL 機能を有効にする SVTL ライセン

スが不要になりました。 SVTL のライセンス容量は、通常の VTL と同じライセンスを使用します。

TrueCDP を使用する際の File System Plugin の更新 - NetVault TrueCDP を使用するには、File System Plugin をバージョン 7.2 以降にアップデートする必要があります。

NetVault Backup 8.0 では、 AIX で SVTL はご使用いただけません。

使用可能な Command Line Interface ツールについて - 本NetVault Backupバージョンで使用可能な CLIベースのコマンドはすべて、 NetVault Backup 8.0 Command Line Interface Guide に記載されています。

本ガイドに使用方法が記載されているコマンドは、 NetVault Backup 製品でのみご使用いただけます。

また、本ガイドに記載のない “...\NetVault\util” ディレクトリ ( または、その他の NetVault Backup ディ

レクトリ ) にあるコマンドのご使用はサポートされていませんので、絶対に使用しないでください。

NetVault の “\tmp” ディレクトリに、充分な空き容量があることを確認してください。 NetVault の "\tmp" ディレクトリは、バックアップ・オペレーションの間テンポラリ・スペースとして使用されます。ハード・ディスク上に使用可能な充分な空き容量がない場合、エラー警告が表示されログ・エントリが生成されます。

マイクロソフト社の Volume Shadow Service (VSS) ライセンスは、 NetVault のコア・モジュールに組み込まれ

ており、 NetVault のデフォルト・インストールで 45 日間ご試用いただけます。 VSS 機能を使用する前に、

Packages/Extra ディレクトリ以下にある評価ライセンスをインストールする必要があります。 Windows 2003で標準で提供されている VSS 機能を利用したバックアップをお勧めしますが必須オプションではありません。

NetVault Backup ｖ6.5.2または 6.5.3から v8.0へ直接バージョンアップすることはできません。v8.0へバージョ

ンアップする前に、まず v7.1.2 へバージョンアップする必要があります。

Backup Saveset インデックス・サイズの制限値の引き上げ - 以前のバージョンでは、 NetVault Database に

保持される各 Backup Saveset 毎のインデックス・サイズの最大値が 2GB でした。本バージョンから、この

制限が 2GB から 4GB に増えました。本機能の拡張は、 NetVault Server としてサポートされているすべて

の OS にあてはまります。

3.0 - 一般的な注意事項


CLI ベースへ変更する変数 - NetVault には CLI ベースのコマンドが多数あり、“%MACHINE” 変数を使用する

ことが可能です。この変数は、 “%LIBRARYMACHINE” に変更されています。例えば、構文に “-format” スイッチを使用して、この名前がレポートに含まれるフィールドを呼び出す場合下記のように表示されていることを確認してください : -format “%BARCODE %LABEL %LIBRARYMACHINE”VMWare ESX Server環境のバックアップ /リストアのサポート - “VMWare ESX Server” ソフトウェアは、1台の

物理的なサーバ上でひとつのホスト OS を稼動し、その上で複数のゲスト OS を稼動させることを可能にする

製品です。 NetVault は前バージョンと同様に、 VMWare ESX Server 環境のバックアップ／リストアをサポー

トします。

NetVault Backup のインストールを実行する前に、本セクションに記載の事項を必ずお読みください。 NetVault Backup v8.0 のインストール方法の詳細は、 NetVault Backup 8.0 インストレーション / アップグレード・ガイドをご覧く

ださい。

End User Release Notes の本セクションでは、 NetVault Backup を新規インストールする前に、事前に考慮しておく

べき点に絞ってご説明します。

Red Hat Enterprise Linux 5.0 for Itanium (IA64) サポートの事前要件 - Itanium で稼動する Red Hat Enterprise Linux 5.0 を NetVault Backup でサポートするには、 "libXm.so.3" ライブラリを手動でイン

ストールする必要があります。 "libXm.so.3" は、 RHEL v4.0 for Itanium (IA64) で入手するか、下記

ウェブサイトからダウンロードしてください：

http://www.rpmfind.net

Red Hat Enterprise Linux 5.0 サポートの事前要件 - Red Hat Enterprise Linux 5.0 を NetVault Backup でサポートするには、 "libXp.so.6" ライブラリがインストールされている必要があります。本ライブラ

リは、 Red Hat v5.0 の標準インストールではインストールされませんので、システムにインストールさ

れていない場合は、手動でインストールしておく必要があります。 "libXp.so.6" は、インスタレーショ

ン CD の "libXp-1.0.0-8.i386.rpm"(i386 の場合 ) 内に含まれています。

NetVault Replicator 製品とのインストレーション・ディレクトリの衝突 - ターゲット・マシンに NetVault Replicator 製品が既にインストールされている場合、インストール時、 NetVault Backup が NetVault Replicator に上書きしないよう措置をとる必要があります。標準設定では、 NetVault Replicator と NetVault Backup は両製品とも “...\NetVault” ディレクトリにインストールしようとします。同ディレクトリへのインストール

を行う表示が出たら、デフォルトのインストレーション・パスの最後に以下を追加し、 NetVault Replicator のインストレーション・ファイルへの上書きを避けてください。

重要事項：バックアップ／リストアを適切に行うには、本インデックスを保管する NetVault Backup の "tmp" フォル

ダは、同インデックス・ファイル・サイズの少なくとも空き容量の 3 倍必要です。例えば、バックアップ・ジョブに

より 3GB のインデックス・ファイルが生成された場合は、 NetVault Server 上の "tmp" ディレクトリは、少なくとも

9GB の空き容量が必要となります。

重要事項： VMWare ESX Server 環境のバックアップ / リストアを行なう場合は、ご使用前に NetVault Implementation Guide for VMWare ESX Server をお読みになり、動作確認を行ってください。本ガイドは、

BakBone Software の下記サイトからダウンロードいただけます。

http://www.bakbone.co.jp/products/product_documentation.html#implementation_guide

4.0 - NetVault Backup 8.0 のインストール


http://www.rpmfind.net

Linux/UNIX ベースの OS: “/backup”Windows ベースの OS: “\backup”

これにより、 “...\NetVault\backup” ディレクトリに NetVault Backup はインストールされます。

英語以外環境でのインストレーション・ファイル要件 (Windows の場合のみ ) - Windows マシンで

NetVault のインストール実行ファイルを選択する場合、必ず "install.exe" ファイルを使用してくださ

い ( 例えば “install_ja.exe” 等、特定言語のインストールに関連しているように見える ".exe" ファイル

は使用しないでください。 ).

NetVault Backup のアップグレードを実行する前に、本セクションに記載の事項を必ずお読みください。その他アップ

グレード手順に関する詳細は、下記 BakBone ホームページに掲載の「NetVault Backup 8.0 インストレーション /アップグレード・ガイド」をご覧ください。

http://www.bakbone.co.jp/products/product_documentation.html #manual

Solaris 10 でのアップグレードについて

NetVault Backup 8.0 では、すべてのライブラリ・チェンジャの “robotic devices” に接続するため Solaris が提

供している SGEN デバイス・ドライバを使用しています。以前のバージョンの NetVault Backup では、

NetVault ネイティブの “nvdriver” コンポーネントを使用してこの通信を行っていました。NetVault Backup 8.0へアップグレードした後は、下記方法のどれか 1 つを選択し、既存のデバイスを新しい SGEN ドライブへ変

更してください。

方法 1: 既存のデバイスと削除するデバイスを利用しているすべてのジョブを削除するAs the title states, you must remove any devices in use, and then delete any existing jobs that target these devices. While this method presents the most overall work, it offers the best overall solution to the issue. It offers the easiest method for adding additional backup devices in the future (i.e., once you have converted to the SGEN device driver in place of NetVault:Backup’s driver, you will be able to easily add new devices using the NetVault:Backup GUI). To properly use this method, follow the steps outlined below:1. Perform a complete backup of the existing NetVault Database on the Solaris 10 NetVault Server that

is to be upgraded.2. Access the Job Management window and thoroughly review all pertinent jobs that target any devices

that are currently under the control of this NetVault Server. Make note of all settings and options.3. With all settings noted, delete all existing jobs that target devices controlled by this NetVault Server.

重要事項：

1. 本問題は NetVault を新規インストールする際にのみ発生し、アップグレードの際には問題ありません。

2. 上記のインストール手順を実行せず、そのままインストールした場合、既にインストールしてある NetVault Replicator に NetVault Backup が上書きされ、 NetVault Replicator は消去されます。

5.0 - NetVault Backup 8.0 にアップグレードするには

重要事項：バックボーン・ソフトウエアは、方法 1 を実行されることをお奨めします。方法 1 は、より確実で、将

来的な使用にも耐えうるソリューションです。


4. Access the Device Management window of the GUI. Remove all devices that are currently under the control of this NetVault Server.

5. Upgrade to version 8.0 on the target Solaris 10 NetVault Server (as outlined in the NetVault:Backup - Install/Upgrade Guide for 8.0).

6. Stop NetVault services (i.e., using the NetVault:Backup Configurator).7. Navigate to the following directory on the Solaris 10 system (where “...” refers to the complete path to

the installation of NetVault:Backup):...\netvault\config

8. Locate the “scsi.cfg” file and open it for editing with a text editor. Locate the [SCSI] stanza, and edit it to appear as follows:- [SCSI] - Use NV driver=FALSE

9. Navigate to the following directory:/kernel/drv/

10.Locate the “sgen.conf” file and open it with a text editor. Edit the file to appear as follows. Lines shown below, prefaced with a “#” are existing lines in the file. Locate each and preface it with a “#” in order to leave it in the file, but have NetVault ignore the entry. Non-”#” prefaced lines indicate new entries that must be added.- #name=“sgen” class="scsi" target=0 lun=0; - #name=“sgen” class="scsi" target=1 lun=0; - #name="sgen" class="scsi" target=2 lun=0; - #name="sgen" class="scsi" target=3 lun=0; - #name="sgen" class="scsi" target=4 lun=0; - #name="sgen" class="scsi" target=5 lun=0; - #name="sgen" class="scsi" target=6 lun=0; - #name="sgen" class="scsi" target=7 lun=0; - #name="sgen" class="scsi" target=8 lun=0; - #name="sgen" class="scsi" target=9 lun=0; - #name="sgen" class="scsi" target=10 lun=0; - #name="sgen" class="scsi" target=11 lun=0; - #name="sgen" class="scsi" target=12 lun=0; - #name="sgen" class="scsi" target=13 lun=0; - #name="sgen" class="scsi" target=14 lun=0; - #name="sgen" class="scsi" target=15 lun=0; - #NV additions - auto generated by postinstall - device-type-config-list="changer"; - name="sgen" class="scsi" target=0 lun=0; - name="sgen" class="scsi" target=1 lun=0; - name="sgen" class="scsi" target=2 lun=0;

Important: If the [SCSI] stanza is all that exists in the scsi.cfg file, you can simply delete this file to obtain the necessary result. However if any other entries exist in this file, it must remain in the “...\netvault\config” directory (and you must edit the file to appear as outlined above).


- name="sgen" class="scsi" target=3 lun=0; - name="sgen" class="scsi" target=4 lun=0; - name="sgen" class="scsi" target=5 lun=0; - name="sgen" class="scsi" target=6 lun=0; - name="sgen" class="scsi" target=7 lun=0; - name="sgen" class="scsi" target=8 lun=0; - name="sgen" class="scsi" target=9 lun=0; - name="sgen" class="scsi" target=10 lun=0; - name="sgen" class="scsi" target=11 lun=0; - name="sgen" class="scsi" target=12 lun=0; - name="sgen" class="scsi" target=13 lun=0; - name="sgen" class="scsi" target=14 lun=0; - name="sgen" class="scsi" target=15 lun=0;

11.With the file properly edited save and close it.12.Issue the following command to generate a required link at “/dev/scsi/changer”:

devfsadm -v -i sgen13.Restart NetVault services (i.e., via the NetVault:Backup Configurator).14.Re-add the removed device(s).15.Re-create all deleted jobs (i.e., using the information gathered in Step 2).方法 2: 適用デバイスを含む sgen.cfg ファイルを編集するOverall, this is the shortest method to employ. However, it only accommodates those devices that are currently under the control of the NetVault Server (i.e., if you need to add additional devices to the NetVault Server at a later date, they will not be automatically recognized by the software, and additional configuration steps would be required). This method also presents a potential risk because if the machine is re-configured, the links that are manually created here may be lost, preventing NetVault:Backup from detecting the devices. 1. Log in to the existing Solaris 10 NetVault Server, using an account with at least super-user level

access.2. Stop NetVault services (i.e., using the NetVault:Backup Configurator)3. Open a terminal session and issue the following command to list the current NetVault driver entries:

ls -l /dev/nv*4. The resulting output will appear, similar to the following for each device:

/dev/nv42 -> ../devices/pci@1c,600000/scsi@2,1/nv@5,0:42The last segment of information reveals “/nv@5,0:42”. This information consists of the SCSI ID - “5”, the LUN value - “0”, and the device instance number - “42”. Record all of these values for each device revealed.

5. Determine which of the identified devices are actually in use by using the “prtconf” command:prtconf | grep nv, | grep <device instance number>

If a value of “nv, instance <device instance number>” is returned, the device is in use, and should be re-configured using the remaining steps illustrated here. Otherwise, it can remain unchanged.

6. Remove the existing NetVault driver by issuing the following command:rem_drv nv


7. With the driver removed, ensure that it’s related configuration file is renamed, in order to remove it, but also preserve this file for future access, if necessary. This can be accomplished by issuing the fol-lowing command:

rename /usr/kernel/drv/nv.conf /usr/kernel/drv/nvold.conf8. Navigate to the following directory:

/kernel/drv/9. Locate the “sgen.conf” file and open it for editing.10.Add the following stanza to it:

- #NV additions- device-type-config-list=“changer”- name=“sgen” class=“scsi” target=<SCSI ID> lun=<LUN value>The “SCSI ID” and “LUN value” variables in the final line apply to what you recorded in Step 4 for these values.

11.Save and close the file.

12.Update the SGEN driver to use the new configuration, by issuing the following command:update_drv sgen

There will now be a new link created to the SCSI device using Solaris 10’s native SGEN driver, and saved in the format “c<x>t<SCSI ID>d<LUN value>” (e.g., “c2t5d0”), in the directory, “/dev/scsi/changer/”. Navigate to this directory, and make note of this link name (i.e., using the SCSI ID - “t<x>” and LUN value “d<x>” to identify the file).

13.It is next necessary to identify the device to which the created link file applies. Issue the following command to accomplish this (where “c<x>t<x>d<x>” applies to the link file identified in “/dev/scsi/changer/”:

ls -l /dev/scsi/changer/c<x>t<x>d<x>The command should return a result similar to the following:

/dev/scsi/changer/c<x>t<x>d<x> -> ../../../devices/pci@1c,600000/scsi@2,1/sgen@5,0:changer14.Note all of the resulting information that occurs (e.g., in the above example, the resulting information

consists of “/devices/pci@1c,600000/scsi@2,1/sgen@5,0:changer”).15.Navigate back to the directory housing the NetVault driver entry for this specific device -- “/dev/

nv<X>” (i.e., the path revealed for the selected device back in Step 4 -- “/dev/nv42” in that exam-ple), delete the entry in this directory, but leave the directory itself intact.

16.Re-link the new SGEN driver device, by issuing the following command (i.e., where the variable “<path information for device>” refers to the resulting information recorded from Step 14, and the variable “<x>” refers to the device’s instance number -- as noted in Steps 4 and 15).

ln -s <path information for device> /dev/nv<x>17. Restart NetVault services (i.e., via the NetVault:Backup Configurator). The device will be available in

NetVault, using the SGEN driver.

Important: if further changers are to be added in the future, it may be beneficial to add 'name' entries for all of the currently unused “target” and “lun” combinations (i.e., in order to distinguish a specific device).


HP-UX (PA-RISC)、 HP-UX (Itanium)、 AIX でのアップグレードについて HP-UX と AIX では、クライアントとしてのインストールのみをサポートします。 HP-UX または AIX で NetVault Backup サーバのアップグレードは行えません。 HP-UX または AIX で NetVault Backup サーバのアップグレードを行

うと、 NetVault Backup は正しく動作しません。

その他サポートしている OS でのアップグレードについて

Solaris 10 以外の OS では、 NetVault Backup 8.0 Installation and Upgrade Guide に記載されている事項以外に

アップグレード時必要な作業はありません。 .

NetVault Backup 製品向けのマニュアルには、下記の 5 種類が用意されています。ステップ順にお読みいただ

くことで、 NetVault のインストール、導入をより簡単に進めていただくことができます :

Step 1: NetVault Backup 8.0 インストレーション / アップグレード・ガイド - 本ガイドには、 NetVault のインス

トール、バージョンアップに関する全手順を説明しています。

Step 2: NetVault Backup 8.0 ゲッティング・スタート・ガイド - NetVualt の開始、操作方法に関する基本情

報を説明しています。もしくは、 NetVault 8.0 簡単設定ガイドをご覧ください。

Step 3: NetVault Backup 8.0 アドミニストレーターズ・ガイド - NetVault で利用可能な全機能を完全に詳細

にわたって説明しています。

Step 4: NetVault Backup 8.0 コンフィギュレータ・ガイド - NetVault のコンパニオン・ユーティリティ、つまり

NetVault Configurator で利用可能な機能のみを説明しています。

Step 5: NetVault Backup 8.0 Command Line Interface User's Guide (英語のみ ) - NetVault CLI機能を

説明しています。

本セクションでは、 NetVault Backup の既知の問題点について説明します。

Known Issues with the NetVault:Backup File System PluginBackup Through Mount Points Option (Windows ONLY) (NVG-3082) (NVG-3594) - All backup jobs that utilize the “Backup Through Mount Points?” option that were originally created using a version of the Filesystem Plugin prior to 7.1 should be recreated. Once the job is recreated, it is necessary to modify the “Backup Through Mount Points” option manually and submit it. This option will need to be modified manually every time the job is resubmitted. Unix File System on Windows Platform (FSG-29) - If you submit a job created for a Unix file system to a Windows system, the job will complete with warnings, but no data will be backed up.Inclusion List Limitation (FSG-82) - When an inclusion list has 1,000,000 file entries or more, the backup job will fail with the error “Can not allocate memory”. Backup of Symbolic Links (FSG-256) - When a symbolic link is selected for backup, only the informa-tion for the symbolic link is backed up and not the directory it points to.Backup Job is Delayed (FSG-389) - The start of a backup job may be delayed in an environment with a large number of direct automounts on Solaris clients. This delay is caused when the Filesystem Plugin

6.0 - NetVault Backup 8.0 用ドキュメント

7.0 - 既知の問題点


attempts to mount all of the configured mount points. To prevent the Filesystem Plugin from attempting to load all automounts one of the following solutions can be implemented.

Select the “Backup through remote mounts” option when submitting a backup job. This will prevent the Filesystem Plugin from scanning for automounts.Open the nvfs.cfg config file located under the NetVault installation path in the folder named “config” and find the following stanza [Performance:DoRecursiveAutoMountScan]Value=TRUEChange the value to FALSE so that the stanza reads[Performance:DoRecursiveAutoMountScan]Value=FALSE

Browse Window in the Selection Tab is Delayed (FSG-372) - The display of the browse window in the Filesystem plugin may be delayed in an environment with a large number of direct automounts on Solaris clients. This delay is especially likely if a WAN connection is employed.Backup/Restore Windows File Short Names Options (FSG-46) - The following known issues apply to the use of these options:

Incompatible with Windows 2000 - Short names are successfully backed up when the option is enabled, but due to limitations with Windows 2000, they can not be successfully restored (However, they can be recovered to another supported version of Windows).Restoring Short Names Only Works if an Existing File with the Same Short Name Does NOT Already ExistNot supported with Windows Encryption and Windows Compression - If Microsoft Windows based Compression and/or Encryption functionality are enabled on a target system, attempts to backup/restore short names will fail.Access Timestamp Reset (FSG-25) - When performing a backup with the File System Plugin, the access timestamp established for directories will be reset from the last time the directory was actually accessed, to the current date/time (because NetVault is effectively accessing the item for use). To contradict this, arguments can be appended to nvfs.cfg file in NetVault that allow you to preserve access timestamps on directories. If this is the case in your environment, enabling “Backup/Restore of Windows File Short Names” will have no affect.

Selections Not Recognized in Previously Created File System Plugin Jobs - This version of the File System Plugin may not recognize data selections made for jobs created with previous versions of the plugin (i.e., data items selected for inclusion in a File System Plugin backup job created with a previous version of the plugin may not be recognized with this version of the plugin). Therefore, attempts to run the job may fail. To resolve this issue, load the job, re-select the necessary data items and re-save it with the same Job Title. Incompatibility with Some Older Version File System Plugin Backups - All backups made by very old versions of the File System Plugin (i.e., from NetVault version 6.0.2 and earlier) will not be restored by version 6.17 and later of the File System Plugin. The user will receive a log message and the job will fail. The actual version of the File System Plugin used to create the backup to be restored will be needed to recover this data.Changing a Directory to a Mount Point Causes Incremental Backup to Run as a Full Backup - If a directory included in the Selection Set for a File System Plugin backup job is ever changed to a Mount Point, any future Incremental backups performed using this Selection Set will be performed as Full back-ups (i.e., all selected data will be fully backed up). This will occur even if an intervening Full backup is performed of the Selection Set (i.e., if a Full backup is performed to try to reset the Incremental scenario,


future Incrementals will still be performed as fulls). To accommodate for this issue, you must recreate/manually edit the Selection Set.Restoring over “Read Only” Files - It is not always possible to restore a file over a file marked as “read-only”. As a result, the plugin attempts to remove read-only status from a file before restoring over it. Again, success is not guaranteed because the SetFileAttributes call is not sensitive to the elevated privi-leges of the plugin.Restoring Non-Encrypted Files Over Encrypted Ones - It is not possible to restore a non-encrypted file over an encrypted file. To work around this, the plugin attempts to delete the encrypted file first. Again, success is not guaranteed because the DeleteFile call is not sensitive to the elevated privileges of the plugin.

Other Known Issues with NetVault:BackupJobs with “Backup Stopped” or “Restarted Backup Stopped” Status are Unavailable After Restarting the NetVault GUI (Affects All Language Versions EXCEPT English) (NVG-3972) - If NetVault:Backup is configured for a language other than English and the NetVault:Backup GUI is restarted, then all jobs with “Backup Stopped” or “Restarted Backup Stopped” status will no longer be highlighted in blue and the “Restart Job” option will not be available. Windows Registry Value Causes Backups to Fail - There is a known issue with a DRM value in the Windows registry called “FilesNotToBackup”. When upgrading from Windows Media Player 9 or 10 to Windows Media Player 11 (or upgrading from Windows 2000 to 2003) this registry value is incorrectly ter-minated. A work-around for this issue is available:

Use regedit to edit the DRM value (path) and save the value. This will correct the termination of the DRM value.

NetVault Databases Check Commands (NVG-3895) - Running a database check command such as nvmeddbcheck or nvscheddbcheck on a Netvault database created prior to NetVault:Backup version 7.4 will fail. A work-around for this issue is available:1. Create a backup of the NetVault database using NetVault:Backup 8.0.2. Delete the ScheduleDatabase and the MediaDatabase.3. Restart the database.4. Perform a full NVDB restore.

For more information on database check commands please refer to the NetVault:Backup CLI User’s Guide.Startup Script Needs to Be Modified in Ubuntu (NVG-3646) - When attempting to install NetVault: Backup on an Ubuntu OS, NetVault: Backup is mounted to a temporary file system by default which causes it to be removed every time the OS shuts down. A work-around for this issue is available.1. Locate the file /usr/netvault/etc/startup.sh.2. Find the following section of the startup.sh file:

if [ $OS = Linux ]thentouch /var/lock/subsys/netvault

3. Add the following entry (shown in bold) to the startup.sh file:if [ $OS = Linux ]then[ -d /var/lock/subsys ] || mkdir -p /var/lock/subsystouch /var/lock/subsys/netvault


Locale of NetVault Server and NetVault Client (NVG-2810) - A NetVault Server and its Client must be set to the same locale in order to display the NetVault GUI correctly.Restore Limitation of 2GB on Itanium Platforms (NVG-3643) - Attempting to restore an index larger than 2GB may result in a failed restore on Itanium platforms. If a restore fails with the error message “Failed when sorting items to restore” you will need to manually increase the stack size by using one of the following methods:

On standard Unix platforms, this can be resolved by editing the ulimit (-s option) in the CLI Terminal to increase the stack size. Open a CLI Terminal and utilize the following commands:- “ulimit –a” provides all the settings for the environment- “ulimit –s” provides the current stack size setting.- “ulimit –s unlimited” sets an unlimited stack size.- “ulimit –s n” (where n is the desired value) sets stack size to n.- “man ulimit” provides for more details on the ulimit command.After modification, enter a ‘ulimit –a’ command to ensure that the setting has been changed.On a HP-UX IA64 platform the bash command kmtune or kctune (depending on the operating system) can be used to access to the kernel stack size information. The stack vars are maxssiz for 32-bit applications and maxssiz_64bit for 64-bit applications. Open a CLI Terminal and utilize the fol-lowing commands:- “kmtune -l -q maxssiz” provides the verbose setting information for a 32-bit application.- “kmtune -l -q maxssiz_64bit” provides the verbose setting information for a 64-bit application.- “kmtune –u –s maxssiz=n” (where n is the desired value) sets the new stack size to n for a

32-bit application. - “kmtune –u –s maxssiz_64bit =n” (where n is the desired value) sets the new stack size to n for

a 64-bit application.- “kmtune –u –s maxssiz+n” (where n is the desired value) increases the stack size by n for a

32-bit application.- “kmtune –u –s maxssiz_64bit +n” (where n is the desired value) increases the stack size by n

for a 64-bit application.Note that all instances of “kmtune” should be replaced by “kctune” depending on the operating sys-tem. Enter the man command in a CLI Terminal for more details.

CLI Issues (All CLI commands for version 8.0 of NetVault are documented in the NetVault:Backup - Command Line Interface User’s Guide).

asf_load_media - This command will fail if the machine name contains any spaces.asf_release_drive - When this command is issued to various brands of library device (e.g., those containing various Exabyte or 9840 drives), a delay of up to eight (8) minutes may occur before the media is unloaded. A known work-around for this issue is covered in the steps that follow:1. Launch the GUI on the NetVault Server and access the Device Management window.2. In the Devices tab, locate the target drive and right-click on it.3. In the pop-up menu that appears, select the Unload command.4. The drive will remain in an “Idle” state and the media will not be unloaded as expected. If the logs

for the selected device are viewed, an entry stating “Unload media in drive <X> failed - Device unavailable” will now be revealed. Repeat Steps 2 - 3 a second time, and the media will be unloaded.

nvacslsmedia - The range function does not work properly. The work-around is to explicitly run this command for each media label/barcode the user wishes to allocate or deallocate. This can be accom-plished in a script.


nvexpiresaveset - Used with a NULL input for Saveset ID will cause random Saveset to be expired. nvcleandrive - When a space character is all that is input for a library’s name with this command, the first library in NetVault:Backup’s device management configuration will perform a clean operation on a respective drive. For example, if the syntax ‘nvcleandrive -libraryname “<space character only>” -librarydrivenumber <X>’ is input and executed, NetVault will automatically target the first library in its configuration order (i.e., the first library displayed in the Devices tab of the Device Management win-dow in the GUI), and perform a clean operation on drive “<X>”.nvjoblist - When this command is initially issued, the output may not report consistently. The work-around suggested for this is to launch the NetVault:Backup GUI, access the Job Management win-dow and then return to the Command Prompt/Terminal Session and re-issue the command.nvjobmodify- Does not function properly when this command’s “-type” switch is used in conjunction with it’s

“BS” option.- The “-change” switch does not function properly when attempting to modify backup options for a

job. - After execution of the command, the job is actually submitted to be run, even if the “-submit”

switch is not included in the syntax.nvsetcreate - Data selections below the “Fixed Drives” level of the selection tree can not be named using this command’s “-include” switch (i.e., it is only possible to include an entire fixed drive in the the creation of a Backup/Restore Selection Set when using this command).nvsetcleaninglives - Allows erroneous live count to be set. nvsetdrivecleaning - The following are known issues with the use of this command:- Does not support the use of multiple switches.- Does not display drive cleaning properties correctly.- If invalid input is provided with this command, actual drive properties may be changed. Ensure that

the syntax is properly input.nvsyncronizesilomeda - CLI does not update media status in Device Management window for Win-dows-based installations.nvremovemedia - With NULL string deletes first entry in media list.CLI Commands will not Function Properly when the Locale is Set to a non-English Language - When the language selection is set to anything other than English (i.e., in the Language Selection field located in the General tab of the Configurator), attempts to use NetVault:Backup command line interface commands may fail.Duplicate CLI Utilities After Upgrade from Version 7.1.1 to 8.0 - With an installation of NetVault:Backup Version 7.1.1, the CLI commands listed below were installed to the noted directories (where “...” refers to the complete path to the installation of NetVault:Backup): - nvreadlog: “.../netvault/bin”- nvtrigger: “.../netvault/util”- nvsettrace: “.../netvault/util”Upgrades to Version 8.0 will install new versions of these same utilities in the following directories:- nvsettrace: “.../netvault/bin” - nvtrigger: “.../netvault/bin” - nvreadlog: “.../netvault/util” After upgrade, navigate to the “.../netvault/bin” directory and delete the 7.1.1 version of the “nvread-log” utility (i.e., there should be no “nvreadlog” utility in the “.../netvault/bin” directory). Once com-


pleted, navigate to the “.../netvault/util” directory and delete the 7.1.1 version of both the “nvtrigger” and “nvsettrace” utilities, as well.

Loss of the NetVault Database and Software Compression Functionality (VTL Devices, ONLY) - In the event that you are to lose your NetVault Database and recover a backup of it, NetVault will be unable to accurately report back the amount of space available on a virtual tape that contains backup job(s) that had the Software Compression functionality enabled (i.e., the tape will not be automatically scanned by the NetVault Device Manager -- The drive housing the media will be labeled as “Waiting for Media”, and eventually time out, failing the job). This only appears to be an issue when the job targeting this type of media also has the Software Compression functionality enabled. As a work-around, you can perform either of the following:

Disable Software Compression and Re-launch the Job - In this instance, NetVault will perform the automatic scan of the media and use it accordingly.Manually Scan the Target Media - From the Device Management window, perform a full Scan of all of the media currently present in the Virtual Library. If you have already encountered this issue, the media may appear as if it has vanished from the Virtual Library. In this case, follow these steps:

1. Select the Media Request tab2. Locate the request in the window and right-click on it.3. Select the Hold command from the pop-up menu.4. Return to the Devices tab and perform a full Scan of the VTL (i.e., right -click on the VTL node

and select the Scan command). The media will be returned to the drive. 5. Return to the Media Request tab, and take the Media Request off of “Hold”.

Working with VMWare ESX Server - If this software component is in use, the following points must be taken into consideration:

Client/SmartClient Use Only - This build is only supported for use as a NetVault Client or SmartCli-ent within VMware guest operating environmentsSCSI Drive Limitation - ESX Server and Virtual SmartClients should be configured with SCSI tape drives onlySCSI IDs Must Match - The virtual SCSI ID must match the physical SCSI ID of the tape deviceRobotic Arm Configuration Requirement - The Robotic Arm should only be configured through non-virtual systems such as the backup server or service console serverDynamic Drive Sharing Should Not be UsedSmart Client Performance - Performance with SmartClients is less than when using standard non-VM configurationsRestoring “vmdk” Files Directly into the VMFS - This is only supported to existing directories. Cre-ating non-existent directory structures within this file system through the recovery job is not supportedOnly Adaptec HBAs are Supported

NetVault Does Not Recognize a Standalone Device (Red Hat Enterprise Linux 4, Update 1, Only) - When a standalone tape device is locally attached to a machine running Red Hat Enterprise Linux 4, Update 1 (RHEL4U1), the device may not be recognizable to the NetVault Server. With this version of RHEL, the SG driver used to support this form of device is not automatically loaded, and must be manu-ally loaded on the RHEL4U1 system, in order to support these devices. After manual load of the driver, it is necessary to stop and restart NetVault Services on the NetVault Server. This issue only occurs in instances in which the RHEL4U1 machine does not also have some form of library/changer device locally attached (i.e., the standalone device is the only type of backup device locally attached to the RHEL4U1 machine). The Linux “SG” driver is an upper level SCSI subsystem device driver that is used primarily to handle devices such as a standalone tape drive. For complete details on obtaining and loading this driver, please see the relevant RHEL4U1 documentation.


Stopping NetVault Services does not Log an Event in the Windows Application Event Log (Win-dows 2000 Installations, ONLY) - In previous versions of NetVault installed on a Windows 2000 system, attempts to stop the NetVault Service would generate a log in the Windows Application Event Log. This version of NetVault does not log an event when the service is stopped. This only applies to NetVault installed on a Windows 2000 system (other Windows platforms will log the event).SVTL Error Logs Generated When No SVTL Devices Exist - In various instances, error messages have been revealed in the NetVault Logs pertaining to Shared Virtual Tape Libraries (SVTL) when none have been set up for use (e.g., Mar 17 05:10:06 NetVault[403]: NetVault: Client: '<client name>' Class: 'System' Job: 'N/A' Warnlevel: 'Error' Msg: 'Failed to spawn 'SVTL Library Manager' (/usr/netvault/bin/nvsvtlchgmgr)). If no SVTL devices have been created, and these messages appear in the NetVault Logs, they can be ignored.Inability to Have a Large Number of Jobs Running Simultaneously (Windows-based NetVault Servers, ONLY) - The default value established for a Windows’ system memory setting, “non-interactive desktop heap” has the potential to be exhausted if a large number of NetVault jobs are running simulta-neously on the machine (e.g., tests running 30+ NetVault jobs have realized this error). As an end-result, a certain number of the jobs will stay active and run, while the remainder of the jobs will fail (i.e., return a result of “Job Died Unexpectedly” as its Run Status in the Job Management window). This is a known Windows operating system issue, and specific changes to the O/S can be made to resolve it. If running a large quantity of simultaneous jobs and this error occurs, please do not attempt to resolve it yourself, but instead contact BakBone Technical Support for the resolution (please see on page 20 for contact information.Certain Text is Partially Hidden in the Media Management Window - In certain instances when the Media Management window is initially accessed, it will appear to crop text from the window. The pro-posed work-around for this issue is to simply resize the window. Once this is done, repeat attempts to access the window will reveal it in its resized dimensions.Default Setting for Job Keep Alive Rate Option in the NetVault:Backup Configurator May Result in Job Failures - Inactive message chan-nels between the NetVault Server’s job manager and the APM/plugin installed on a target NetVault Client may be seen as inferior by network administration configuration devices (e.g., routers, etc.), and may be subsequently removed after a certain threshold. As a result, currently active jobs may fail. This can be resolved by adjusting the time set for the Job Keep Alive Rate option in the Job Manager tab of the NetVault:Backup Configurator from its default value of zero (e.g., to 5 minutes). For information on this option and the Configurator, please see the NetVault:Backup - Configurator Guide (for 7.4.x).Default Setting for Job Keep Alive Rate Option in the NetVault:Backup Configurator May Result in Job Failures - Inactive message channels between the NetVault Server’s job manager and the APM/plu-gin installed on a target NetVault Client may be seen as inferior by network administration configuration devices (e.g., routers, etc.), and may be subsequently removed after a certain threshold. As a result, cur-rently active jobs may fail. This can be resolved by adjusting the time set for the Job Keep Alive Rate option in the Job Manager tab of the NetVault:Backup Configurator from its default value of zero (e.g., to 5 minutes). For information on this option and the Configurator, please see the NetVault:Backup - Config-urator Guide (for 8.0).No Case-sensitivity when Setting Up and Using Group Labels - If two separate Group Labels are created with the same name, but are differentiated through the use of capital letters (e.g., “Group-1” and “group-1” are created as separate Group Labels), NetVault may ignore this difference and assume that all of the media between the two groups actually only exist in a single group. For example, “Group-1” and “group-1” were created, and separate pieces of media are included in each group. If Group-1 is called out for use in a job, NetVault may include not only the media established in “Group-1” but also those named in “group-1” (i.e., NetVault will ignore the capitalization difference and assume that only one Group Label actually exists, thereby including all media named in both groups).


Consolidate Incremental Backup Plugin Backups and Expired Backup Savesets - In the event that a backup saveset has expired (i.e., it has reached its designated Backup Life, as set in the Advanced Options tab in the Backup window), an attempt to include this retired backup in a new Consolidated Full backup will not reveal a result of “Failed”, as it should. Instead, the backup will attempt to run and return a completion status of “Completed with Warnings”. In actuality, the Consolidate job will fail and inspec-tion of the NetVault:Backup Log entries for the job will reveal such (e.g., An entry of “LogError” with the accompanying message, “No backups for set <backup saveset name> found”). This should only be an issue if a Consolidate Incremental Backups Plugin backup has been scheduled to occur at a later time, and any target backup saveset is retired before the scheduled run time for the Consolidated backup. Therefore, to avoid this issue, ensure that your Consolidate backup is scheduled to run before the Backup Life for its target backup savesets have elapsed. If setting up a new Consolidate job, this will not be an issue, because only currently available backup savesets will be revealed for inclusion in the Consolidated backup (i.e., retired backup savesets will not be shown for selection).Delete Non-Scheduled Jobs Option Deletes Triggered Jobs - This option is intended to delete any non-scheduled jobs, after a specified amount of time. However, since jobs using the “Triggered” schedule type have no physical scheduled time, they are also deleted after the input amount of time elapses. If you are using Triggered jobs in your NetVault environment, do not use the Delete Non-Scheduled Jobs functionality.Selecting Multiple Duplication Jobs and Using the “Run Now” Command will Result in Failed Jobs - If multiple jobs that have been set up as a duplications (i.e., via the “Duplication” option in the Advanced Options tab of the Backup window), are selected in the Job Management or Status win-dows of the GUI and the Run Now command is used via the pop-up menu, the jobs will fail.NetVault:Backup GUI can Shut Down when the Client View Button in the Policy Management Win-dow is Clicked Multiple Times (Linux-based Installations, ONLY) - If you are to click on the Client View button in the Policy Management window more than once, and then close the Policy Manage-ment window, the GUI will shut down. There is no data loss as a result of this shut down.Running a Multi-job with Auto-Deletion Set to Default (i.e., “On”) in the NDMP Plugin - Parent and child jobs may still be visible when opening the Job Manager. This is a refresh issue and can be over-come by closing the NetVault GUI and reopening it. There is no need to stop/restart NetVault services.Problem of NVDB restore on NetVault 8.0. - Restoring of events is not working, but full restores do complete successfully. In addition, do not individually select the “Events” item when restoring the NetVault Database.NetVault:Backup 8.0 Installation Fails if Installation Directories are Mount Points (Linux/UNIX-based O/S Only) - The NetVault installation script tries to delete the existing contents on the mount point (which isn’t allowed in a UNIX-based environment) and the installation will fail. To work-around this issue, create a sub-directory below the mount point, and install NetVault to that directory.Unable to set a Drive Offline and Bring the Drive Back online (Drive goes down) - For physical drives, when media is in the device, you can not bring the drive online. The user must either stop and restart NetVault, or remove the media before bringing the drive online. This functionality works correctly for Virtual Drives and Libraries but not for Standalone drives.Issue with Data Copy Plugin Backups of NetWare Thin Client Full/Incremental Backup Series - When a Data Copy Plugin backup is set up for a NetWare Thin Client Plugin backup, and the “Auto-matically Get a Set’s Last Full Backup” option is enabled in the Backup Options tab, NetVault will tar-get the actual last backup performed for the data copy, regardless if that last backup was a Full or Incremental backup (i.e., the “Automatically Get a Set’s Last Full Backup” option sees all NetWare Thin Client Plugin backups as Full backups).Issue with Installation Script on Solaris platform - Even though NVDB is not installed on NetVault: Backup Clients, the installation script prompts for the NVDB path during client installations on Solaris


platform. This path can be left as is during installation as NVDB location is irrelevant for NetVault: Backup Clients.Non-English Version/Localization Known Issues - All of the points that follow correspond to Known Issues that apply only to non-English versions of this release of NetVault:Backup:

If Asianux 2.0 machine is rebooted, nvpmgr starts with LANG=C - After installing NetVault 8.0 on Miracle Linux 4.0 (LANG=ja_JP.UTF-8), nvpmgr starts in LANG=ja_JP.UTF-8. However, if the machine is rebooted, nvpmgr starts in LANG=C (actually, no LANG setting). NetVault cannot display Japanese UTF-8 characters correctly because it looks like the UTF-8 -> EUC conversion function does not get activated. The work around for this is to set LANG in startup.sh.Use of Non-English Characters in the Set Filter Options Window - Various fields of the Set Filter Options window (i.e., accessed from the Job Management window) do not allow for the input of non-English characters.End User License Agreement (EULA) Display Issue - If the default locale is changed (e.g., from UTF8 to EUC or vice-versa), the EULA may not be displayed properly. The proposed work-around for this issue is to use an EUC displayable terminal to view the EULA.Display of Simple Chinese Characters in Microsoft Windows XP Installations - This format of character is not properly displayed when performing backup and restore operations from a Windows XP installation of NetVault:Backup. The recommended work-around is to access the General tab in the NetVault:Backup Configurator and set the Language drop-down option to “English”.Display of Characters on the Main GUI May Not Display Properly in Japanese/Korean Locales Running a Linux IA64 Operating System (NVG-1463) - The labels accompanying the large buttons in the main window of the GUI my not display properly in these environments.


本セクションは、本バージョンの NetVault Backup で修正された事項を掲載しています。

8.0 - ソフトウェア修正

Fault Number Description

TRG-107 Issue with the Local Drives Only Option and the Teradata Plugin - In the previous release of NetVault:Backup the "Local Drives Only" option conflicted with the existing Teradata global configuration parameter "Allow use of Network Attached Devices". This issue has been resolved in this release.

NVG-1689 In the previous release of NetVault:Backup the Index Compression feature located in the Media Management tab of the NetVault Configurator would not compress indexes auto-matically. This issue has been resolved in this release.

NVG-1695 In the previous release of NetVault:Backup NDMP attached drives were placed in the Media group as "BAD" when they were functioning properly. This issue has been resolved in this release.

NVG-1721 Error Occurs when NetVault is Removed from a System and then is Re-installed to that System (Solaris (SPARC) O/S ONLY) - In the previous release of NetVault:Backup if NetVault was uninstalled on a machine running Solaris (SPARC) certain NetVault direc-tories remained on that machine that caused re-installation to fail. This issue has been resolved in this release.

NVG-1852 Various NetVault:Backup Reports Are Not Generated when Run (Linux Itanium Installations, ONLY) - In the previous release of NetVault:Backup the error message, "Failed to run reporting job. Failed when running job to produce output. Please see job log." would be returned when various reports were selected from the Reports window and run on a Linux Itanium NetVault Server. This issue has been resolved in this release.

NVG-2122 NetVault:Backup GUI May Inadvertently Shut Down in Japanese EUC Locale Instal-lations (Red Hat Enterprise Linux Advanced Server Installations, ONLY) - In the pre-vious release of NetVault:Backup various navigation operations in the NetVault:Backup GUI caused NetVault to shut down abnormally in Red Hat Enterprise Linux Advanced Server installations. This issue has been resolved in this release.

NVG-2126 Status Window Operator Message Frame Corruption on Linux-based O/S (Japa-nese EUC) - In the previous release of NetVault:Backup messages in the Operator Mes-sages frame of the Status window that were not acknowledged (i.e., those entries that appear in bold text in this frame) were displayed incorrectly in Japanese EUC installa-tions of NetVault:Backup. This issue has been resolved in this release.

NVG-2837 In the previous release of NetVault:Backup in some cases it was not possible to create an SVTL on a Unix platform because they were incorrectly identified as tape drives. In this release a new SVTL config file allows alternate devices to be specified. For example:[DeviceNode:Solaris]device=emcpower

NVG-3017 A new ADIC Scalar 100 Library template has been added in this release that prevents the device from going offline unexpectedly.


NVG-3068 In the previous release of NetVault:Backup the Consolidate Incremental Backups plugin would fail to allocate memory properly and terminate abnormally. This issue has been resolved in this release.

NVG-3113 In the previous release of NetVault:Backup the nvsetdelete command's usage statement did not include a description of the "BO" type. This issue has been resolved in this release.

NVG-3294 In the previous release of NetVault:Backup adding a client via the nvclientadd command on Red Hat 4, update 4 would result in a segmentation fault. This issue has been resolved with this release.

NVG-3320 In the previous release of NetVault:Backup double clicking on a differential restore saveset in the Restore window would cause the error "Plugin died unexpectedly." This issue has been resolved in this release.

NVG-3405 LTO Tape Drives Directly Attached to a NAS - In the previous release of NetVault:Backup NDMP backups would fail with the error, "Filer attached LTO drive Error Command failed, re-initializing driver." if LTO tape drives were directly attached to a NAS and being used as NDMP devices. This issue has been resolved in this release.

NVG-3417 The Seagate/Certance LTO3 (viper200.tpl) media description in the Device Management window has been corrected. This issue did not affect the functionality of NetVault:Backup.

NVG-3506 In the previous release Overnight Job Summary and Policies Summary Report Jobs failed in Japanese installations of NetVault:Backup. This issue has been resolved in this release.

NVG-3623 In the previous release of NetVault:Backup on MP-RAS, the user was required to enter a password during installation. This is no longer the case in this release.

NVG-3748 Japanese installations of NetVault:Backup no longer attempt to scan for devices when the Device Management window is opened when "Neither" is selected for the Enable Automatic Device Scanning option.

Fault Number Description


バックボーン・ソフトウエアは、業界をリードするバックアップ／リストア・ソリューション・プロバイダーです。ネットワーク・ストレージ環境に、データのバックアップ、リストア、ディザスタ・リカバリ・ソフトウェアを開発し、世界中に販売しています。バックボーン・ソフトウエア株式会社は、米国 BakBone Software, Inc. の日本法人で、

BakBone 製品の日本における開発、販売、サポートを行っています。バックボーン・ソフトウエアが提供する拡張

性に優れたソリューションは、大規模なエンタープライズ環境から、中小規模のビジネス環境までお客様のあらゆるニーズにお応えすることが可能です。 1998 年の設立以来、バックボーン・ソフトウエアの製品は、 OEM パートナー

やソリューション・プロバイダーを通じて販売され、世界中の企業に使用されています。

9.0 - バックボーン・ソフトウエア株式会社について

BakBone Software K.K. - Web Site: www.bakbone.co.jp

Worldwide Headquarters Asia/Pacific Rim EMEA

BakBone Software, Inc.9540 Towne Centre Drive,

Suite 100San Diego, California 92121 USA

Phone 858 450-9009FAX: 858 450-9929

e-mail: [email protected]

バックボーン・ソフトウエア株式会社〒 163-0711

東京都新宿区西新宿 2-7-1 新宿第一生命ビル 11F Phone: 03-5908-3511

Fax: 03-5908-3512E-mail: [email protected]

技術サポート窓口：http://www.bakbone.co.jp/support/

contact_support.html

BakBone Software Ltd. 100 Longwater Avenue.

Green Park.Reading,

RG2 6GP EnglandPhone: +44(0)-1189-224800FAX: +44(0)-1189-224899

e-mail: [email protected]


netvault backup 8.0 update 1 release notesend user release notes - netvault backup 8.0 page 4 of...

Documents