NovaNET 9.00 SP7D 7 March 2005
This document includes updated
information for the documentation provided with NovaNET 9.00. In addition to
addressing new issues in Service Pack 7D (SP7D), it addresses and updates some
issues from Service Pack 1A, 2A, 2B, 2C, 2D, 3A, 3B, 4A, 4B, 4C, 5A, 5B, 5C,
6A, 7A, 7B, 7C and NovaNET 8.50. Any previous issues that are updated in this
version now appear under the 8.50 heading.
Note If you are running NovaNET on a network, always install the latest service pack on each machine for which you have purchased a license. If you require technical support, you will be asked which service pack is installed on your machine. To determine which service pack you are running, open NovaNET and click on Help, About NovaNET.
Note
New
NovaNET features and corrections appear in sections 2 and 3. Platform-specific
features and corrections appear in each platform’s section (sections 5 through
9).
1. Accessing Online Documentation
1. Printed
documentation — Adobe Acrobat
2. Expanded
support for backups to WORM media
4. Working
with Oracle databases
6. Expanded
support for multiple local instances of Microsoft SQL Server
7. Increased
number of open files in the NovaNET database
8. NovaNET
now scans a maximum of 64 data streams simultaneously
9. Revised
subject lines for email messages
10. Time
stamps added to tape alerts
11. NovaNET
now supports NetWare 6.5
12. Enhanced
email alert messages
13. New
timeout and filter settings for alerts.
15. Novell
NetWare 6.0 Service Pack 3 support
16. Recognizing
LUNs on a Linux system
17. Empty
autoloader devices when starting NovaNET for the first time
19. Enhanced
keyboard navigation and shortcuts
20. NovaNET
supports higher logical unit numbers (LUNs)
21. NovaNET
supports additional bootable tape drives
22. Standardized
filename for Disaster Recover CD image.
25. NovaNET
jobs may complete immediately with no errors and zero completed objects.
26. Displays
media name during job
2. Automatic
instalation for service packs on a client machine
3. Miscellaneous
corrections and device support
4. Database
corruption issues identified and repaired
5. Improved
handling of machine connections with the NovaNET database
6. Improved
network connections to devices
7. Unknown
errors when backing up Windows encrypted files
8. Restoring
incremental and differential logs on Microsoft Exchange
9. Restoring
incremental and differential logs on Microsoft SQL
10. Misleading
media alerts caused users to insert incorrect media during long backups
11. Better
error reporting when disk partitions are full
12. Reporting
fewer files as backed up while not registering any errors
13. Untransformed
string messages no longer appear in the NNtrace.txt file
14. Disaster
Recovery support for Windows Server 2003 with HP 5i RAID Controllers
16. Changed
instructions for restoring transaction log files for Microsoft SQL databases
17. Restoring
the NovaNET database from password-protected media
18. Performing
multiple operations on autoloaders
19. Space
commands causing Error 333 timeout errors on some Travan IDE devices
20. Content
Indexing backups run when the service is stopped
21. Disaster
Recovery ignores unmounted volumes
22. NovaNET
displays changes to newly-created objects in the title bar
23. Databases
created with earlier versions of NovaNET on multi-processor machines can be
restored
24. NovaNET
logs messages created by a client administrator when a service is running
25. Resolved
stream sync errors on systems with 1GB RAM or more
26. Corrected
autoloader status display
27. Error
514: End of Data errors may occur when backup job spans more than one media
2. Changing
NovaNET configuration
3. System
administrator privileges required to install and run NovaNET
4. Error
logging when creating disaster recovery media
5. Managing
backup jobs in installations with multiple tape drives
1. Support
for Iomega REV™ drives
2. Installing
NovaNET on a Japanese-language Microsoft Windows operating system
3. Reading
media contents when restoring Microsoft Exchange 5.5
4. Restoring
master databses of obsolete versions of Microsoft SQL Server 6.5
5. Resolving
busy connectors for the System State
6. Launching
the NovaNET Service Control Manager while Internet Explorer is open
7. Logging
messages on client machines
8. Correct
interpretation of reserved Japanese characters
9. NovaNET
backs up more Windows System folder files
10. Improved
error messages when restoring System State
11. NovaNET
now supports the System State object
12. Language
text display on later phases of Disaster Recovery
1. Creating
disaster recovery media on systems running Windows 2000 and later with dynamic
disk
3. NovaNET
tree control on the Device tab no longer crashes on systems running Windows NT
4.0
4. Silent
installation for NovaNET with your predefined settings
5. Encrypting
media passwords when formatting media from the Web Gateway
6. Importing
password-protected media in the Web Gateway
7. Buttons
remain active while running jobs from the Web Gateway
8. Viewing
diagnostics information from the Web Gateway
9. Restoring
busy files across volumes
10. Restoring
short filenames stored in the registry.
12. Restoring
files generated by content indexing on Windows 2000 systems set up as NTFS
14. Enabling
Web Gateway after installation
16. NovaNET
restores read-only files on Windows 2000 and later
17. Error
messages when restoring databases over 4GB on Microsoft Exchange 2000 servers
18. NovaNET
Disaster Recovery supports dynamic disk partitions under Windows 2000 and later
19. NovaNET
now backs up and restores Disk Quota information
20. NovaNET
now restores short path names
21. Volume
mount points and directory junctions
22. Distributed
Transaction Coordinator (DTC) error occurs after disaster recovery
23. NovaNET
restores files even if the Windows administrator cannot access the object
24. NovaNET
verifies user access to Windows Cluster 2000 Server drives
25. Corrected
issue with Unicode separator characters
26. Prevents
simultaneous backup of IS and DS in Microsoft Exchange Server 5.5
27. Restoring
Exchange Server 2000 instances from backups from earlier NovaNET versions
28. Installing
NovaNET on Windows Terminal Server
29. Disaster
Recovery for Windows 2000 Small Business Server
30. Installing
the correct OnStream ADR2.60usb device driver
2. Importing
System State if the NovaNET database is corrupted on Windows 9.x systems
3. NovaNET
no longer supports Windows 95
4. Logical
volumes now correctly appear
5. Disaster
Recovery limitations
1. Syntax
changes for recognizing multiple LUNs on NetWare 6.5
2. NovaNET
now supports NetWare 6.5
3. Restoring
trustee rights during Disaster Recovery on systems running NetWare 5.1 or
higher
4. Novell
NetWare 6.0 Service Pack 3 support
5. Support
for NetWare 6.0 installations with LSI SCSI adapters and Fusion-MPT
6. NovaNET
only supports NetWare 4.2, 5.1 and 6.x.
7. Network
problems with NetWare
8. NovaNET
Disaster Recovery requirements for NetWare 6
9. NovaNET
does not back up the NSS administration volume by default
10. NovaNET
and NSS partitions larger than 4GB in NetWare 6
11. NovaNET
completes Phase 3 of Disaster Recovery in NetWare 6 installations
1. Rebooting
with LILO while restoring from a disaster
2. Linking
to libraries for Oracle 8i
3. Secure
erase pop-up messages when performing Quick Erase operations on Linux systems
4. nntrace.txt
write file errors on Linux systems
5. Re-enabling
hardware compression while running the NovaNET in X Window
7. Disaster
Recovery problem corrected on United Linux
8. Recognizing
LUNs on a Linux system
9. Empty
autoloader devices when starting NovaNET for the first time
10. NovaNET
now backs up and restores extended attributes and access control lists (ACLs)
11. Red
Hat 8.0 and the F10 key
12. Changes
to supported list of Linux versions
13. Linux
Symbios SCSI drivers not functioning properly
14. NovaNET
may take longer to load
15. Using
IDE devices under Linux
The following
documentation is included with NovaNET to help you install and use all NovaNET
features and options.
Note In this section, <dir> represents the
platform-specific directory on the NovaNET CD-ROM, for example, win (Windows), lin (Linux) and net (NetWare).
Note In this section, <lng> represents eng (English), fre (French), ger (German),
ita (Italian), jpn (Japanese) or spa (Spanish).
· NovaNET Quick Install Guide (twquick.pdf)
· NovaNET Installation Guide (install.pdf)
· NovaNET User’s Guide and Technical Reference (usersgd.pdf)
·
NovaNET Error Code Reference errcodes.pdf)
· NovaNET Addendum (addendum.pdf) – English only
Note You can also download these documents from the NovaNET
website.
To view or print this
documentation, Adobe Acrobat or Acrobat Reader (version 4.0 or higher) must be
installed on your Windows or X Window (Linux) computer. If not currently
installed, you can it from the Adobe Acrobat Reader website at http://www.adobe.com/products/acrobat/readstep2.html.
Note This link may change without notice.
Note Adobe Acrobat Reader does not offer versions for DOS or
NetWare systems. Therefore, you can only view or print the NovaNET
documentation on Windows and X Window (Linux) systems.
Windows: NovaNET installs the
print documents onto your computer. Then you can access them directly from the Start menu: Start | Programs | NovaNET | NovaNET Documentation | Printable
Documents | <document name>.
X
Window (Linux): NovaNET does not
install the print documents onto your computer. You must manually access or
extract them from the NovaNET installation CD-ROM.
Windows (Winhelp): You can access both
the online help system and context-sensitive help from most NovaNET screens.
· Select Help topics from the Help menu at the top of the screen. The main help screen appears.
· Press F1 or click the Help button. The help topic associated with the screen appears.
· On many screens, you can click the ? button in the top right corner. The mouse pointer changes to the help pointer. When you click a screen item, more information appears.
DOS/NetWare/Linux
(Onscreen): You can press F1 to access online help from most NovaNET
screens.
You can install the HTML help version of our online help
system. Then you can access it with a web browser. Please note that only the X
Window version of NovaNET will access HTML help topics.
Note You can also download
the HTML help system from the NovaNET website.
Windows
a. Copy htmlhelp.zip from the \doc\<lng>\htmlhelp subdirectory on the NovaNET CD‑ROM.
b. Use WinZip or some other file extraction software to unpack it onto your computer.
X Window (Linux)
The NovaNET installation program installs the htmlhelp
system automatically. If you are not installing NovaNET from the NovaNET
CD-ROM, or if you want to use a different browser, you must install the
htmlhelp system manually, as follows:
a. Copy htmlhelp.tgz from the source directory (CD-ROM, download directory, etc.) to the /usr/local/novanet directory.
b. Use tar, gzip or some other file extraction software to unpack it into the /usr/local/novanet/htmlhelp subdirectory, e.g., tar xvzf htmlhelp.tgz.
c. Install Netscape 4.7 or higher as well as the Java applet.
d. Create a symbolic link:
i. Open a terminal window and change the directory to /usr/local/novanet/htmlhelp/.
ii. Type ln -sf INDEX.HTM index.htm.
e. Open and log in to NovaNET.
f. To use a different browser, identify the browser in the NovaNET preferences:
i. Select the Preferences option from the File menu. The Preferences screen appears.
ii. Click the Browse button and identify the browser to use.
iii. Click OK to save the changes.
iv. Exit and restart NovaNET.
Now you can access the help system directly from the Help menu in NovaNET.
Note The HTML help system
requires the Java Plug-in. Internet Explorer users must enable it. Netscape
offers to install the plug-in if it is not installed.
Note For best results on X
Window (Linux) systems, we recommend that you upgrade to Netscape v6.x.
To launch
HTML help, use your browser to open INDEX.HTM.
Note
Platform-specific new
features now appear in each platform’s section.
In addition to general performance improvements, NovaNET now comes with the following new features:
-------- 9.00 SP7D --------
Enhance your data storage and recovery
options in NovaNET by creating emulated disk devices with Backup to Disk Folder
(B2DF). This optional feature lets you set up any disk folder to emulate a tape
device. With backups to disk folders you can back up and restore your data to
or from any local disk folder.
NovaNET treats a disk folder like any
other tape. You can overwrite it or append to it during future backups,
password protect it, import it into the database, and so forth. Some commands
are not available. For example, you cannot eject a disk folder as you might
with a tape in an autoloader.
The amount of data that you can store on
a disk folder is limited only by the amount of hard disk space on the computer
on which the disk folder is created. $mfgshort$ recommends that you create disk
folders on hard disks other than the one on which the main operating system
resides.
You can configure as many disk folders
as you need either in the NovaNET Administrator or from the character user
interface. Once configured, these disk folders are displayed on the Device tab
along with other tape devices, REV storage devices, or autoloaders.
1.
Open
the NovaNET Administrator and select Tools, Configuration, Disk Device.
The Disk Device configuration screen
appears. You can add, edit or delete devices from this screen.
2.
Click
Add to display the New Disk Device screen.
3.
Enter
a name for the disk device and select a pre-existing path for the disk
directory.
4.
If
you do not know the path, click Browse to locate it.
5.
Click
OK to save the disk folder and return to the configuration screen.
6.
Restart
the NovaNET service to be able to view the disk folder on the Device tab.
WARNING: If you delete a disk folder that contains backup jobs, the device will no longer be available as a data source during restore jobs. Do not delete a disk folder unless you are certain you no longer need to restore any files from it.
1.
Locate
the file NNCfg.ini in the NovaNET installation directory and open it with any
text editor.
Two entries are required for disk
folders: a list of all disk folders, and an individual entry for each
configured folder.
2.
Scroll
to the bottom of the file and create the entries needed for disk folders.
3.
To
create a list of disk folders enter the following text:
[virtualDiskDevices]
vdd.1=DiskFolder1
vdd.2=DiskFolder2
Note that each disk device must have a
unique number and name.
4.
Create
an entry for each. For example, each disk folder named above needs a separate
entry as follows:
[DiskFolder1]
volumePath=d:\mydiskfolderpath1
[DiskFolder2]
volumePath=d:\mydiskfolderpath2
Each disk folder must have a unique
pre-existing path listed as the volumePath.
5.
Save
this file as a text file.
6.
Restart
the NovaNET service to be able to view the disk folder.
7.
To
delete a disk folder, merely remove its entry from this file.
WARNING: If you delete a disk folder that contains backup jobs, the device will no longer be available as a data source during restore jobs. Do not delete a disk folder unless you are certain you no longer need to restore any files from it.
-------- 9.00 SP7C --------
NovaNET now supports backup, restore and
disaster recovery operations with WORM media (write once, read many) on SDLT600
devices. With DLTSage xTalk from Quantum Corporation, your SDLT600 device may
support WORM media regardless of manufacturer. DLTSage xTalk is a diagnostic
software that utilizes DLTIce™ technology and
is available at no additional charge directly from Quantum. To learn more about
DLTSage xTalk and DLTIce, visit the Quantum download center at the following
link:
http://www.quantum.com/am/service_support/downloads/software/sdlt600.htm
Locate and download the version of
DLTSage for your operating system. You may also need to upgrade your drive to
the latest version of firmware.
NOTE:
Internet addresses are subject to change. If you cannot reach this site,
locate the software downloads page at the Quantum web site and search for
DLTSage xTalk.
-------- 9.00 SP7A --------
NovaNET now supports backup, restore and
disaster recovery operations with WORM media (write once, read many) on HP LTO3
devices. With NovaNET and the HP LTO3 device, you can be create a backup plan
that complies with government regulations related to permanent storage of your
documents and data.
Once you install SP7A, NovaNET will
distinguish between traditional and WORM media and will prevent you from
overwriting it during backups.
To manage permanent backups, consider
creating a separate backup job that includes those files and folders for which
you need to maintain a permanent backup record. For the backup device, select
the HP LTO3 as the device destination.
-------- 9.00 SP5A --------
SP5A enables NovaNET to perform backup, restore and disaster
recovery operations of Oracle 8.x (8i)
and 9.x (9i) database servers running
on the following platforms:
· Microsoft Windows 2000 server and Windows Server 2003
· Red Hat Linux Advanced Server 2.1
·
SuSE Linux
For information on
installing, configuring, and running the NovaNET Oracle connector , refer to Chapter 8 – Working with Oracle databases in
the NovaNET Addendum located on the NovaNET
CD-ROM in the directory /doc/<lng>/acrobat.
To purchase the
optional NovaNET Oracle connector, visit www.NovaStor.com.
See the instructions
below in section 9. Linux for
specific configuration issuses on Linux systems.
The NovaNET Addendum
has been updated to include a new chapter called Chapter 8 – Working with Oracle databases. Refer to the /doc/<lng>/acrobat
directory on the NovaNET CD-ROM for the printed documentation. The NovaNET Addendum is available only in English.
NovaNET supports
multiple local instances of Microsoft SQL Server. Follow the instructions below
to set up multiple instances from the Microsoft Windows Administrative Tools
menu and in NovaNET. Do not back up remote instances of Microsoft SQL Server.
1. Working with multiple SQL Servers
To work with several
instances of SQL Servers in NovaNET, you must first set up additional instances
using the operating system’s Administrative Tools.These instructions also
assume that you already have a default localhost instance.
a.
Locate the Administrative Tools menu on your
Microsoft Windows machine, for example, select Start, Settings, Control Panel,
Administrative Tools.
b.
On the Administrative Tools menu, double-click
on Data Sources (ODBC).
c.
The ODBC Data Sources Administrator screen
opens.
d.
On the System
DSN tab, click Add … .
e.
The Create New Data Source screen appears.
f.
Scroll through the list of available data
sources, select SQL Server, and
click Finish.
g.
The Create a New Data Source to SQL Server
screen appears.
h.
Enter a name, description and server name for
the new instance. If not already created and your database resides on the local
system, you can create a default unnamed instance by entering localhost for
both the Name and Server fields.
If you are creating a
database connection by using ODBC, the Server
field must be entered as <Local
Server Name>\<SQL
Server Instance Name> where <Local Server Name> is the name of the SQL Server machine
excluding the domain name and <SQL
Server Instance Name> is the name of the Microsoft SQL Server
instance.
To locate a machine
name, select Start, Programs, Accessories, System Tools. Open the System Information menu on the selected
machine and view the Computer Name
tab. The Full computer name field lists the machine name followed by the
company domain name. For example, if
Serv1.ab_company.com appeared in the Full
computer name field, you would enter Serv1 as the Server name followed by
the database instance.
i. Click Next to display the ODBC Microsoft SQL Server Setup screen.
j. To test the configuration, click Test Data Source. Otherwise, click OK to accept the configuration and return to the ODBC Data Source Administrator screen.
k. Click OK.
l. The new SQL Server instance is now ready to be configured in NovaNET.
2. Setting up the server to use named pipes
Before configuring
additional servers in NovaNET, you must verify that the servers are configured
to use named pipes.
a. From the Windows desktop, select Start, Programs, Microsoft SQL Server, Client Network Utility.
b. Open the General tab.
c. In the Named Pipes field, verify that "Enable Protocols by Order" is selected. If not, select it in the Disabled protocols list and click Enable.
3. Configure additional SQL Server instances in NovaNET
Once you have
additional SQL Server instances set up in Microsoft Windows, you must configure
them in NovaNET.
a. From the Tools menu in NovaNET, select Configurations, Microsoft SQL. The Microsoft SQL Configuration screen appears.
b. Click the New button to display the SQL Server information screen.
In the ODBC DSN field, enter the ODBC data source name as you entered it in Step 8 in Working with Multiple SQL Servers, above. In the User name and Password fields, enter the name and password of the SQL administrator who has rights to this SQL Server instance. Passwords and user names are case-sensitive. Note that NovaNET requires that you enter the SQL Server user name, not a Windows user name that might have access to the SQL Server.
c. Click OK to accept the information and return to the Microsoft SQL Configuration screen.
The next time you stop and restart both the NovaNET service and NovaNET Administrator, the new instance appears in the list of ODBC data source names.
To delete a SQL Server instance, select it from this list and click Remove. To update a SQL Server instance, select it from the list and click Modify.
4. Restoring SQL database instances from backup tapes created before installing SP5A
Prior to this service pack NovaNET would read databases only
from the LocalServer database instance and would list these databases directly
underneath the Microsoft SQL Databases container. Since NovaNET now permits multiple instances
of databases, a Microsoft SQL object in NovaNET must now distinguish between
each instance. To do so, each instance is listed in a new sub-folder within a
SQL object. If you backed up your LocalServer database instance before installing SP5A, NovaNET will not
be able to locate these databases during a restore job performed after installing SP5A.
To restore these databases, you must specify a new
destination when you create a restore job. To do so in NovaNET you create a
move restore job. The exact procedures depend on how you set up the ODBC
connection and named the LocalServer. However, follow the procedures below to
locate the new destination to restore multiple instances of Microsoft SQL
databases.
5.
Setting up the move-restore job
a.
Open
the NovaNET Administrator and create a restore job.
b.
Select
the Microsoft SQL Databases container.
c.
Notice
that old LocalServer databases listed on the screen are not available.
d.
Right-click
the database to be restored and choose Move.
e.
In
the Confirm Move dialog box, choose Browse… and select the new destination
to restore the database. Expand the tree to the Microsoft SQL Databases
container to locate the LocalServer database. Click OK.
f.
Click
OK again to confirm the move.
g.
Repeat
steps 3 – 6 for each database that needs to be restored.
h.
Change
any additional settings for the restore job and run it.
NovaNET retains this new location for the databases for all
future backup and restore jobs.
The number of open files internal to the NovaNET database has been doubled from 64 to 128.
By default NovaNET now scans eight (8) data streams simultaneously. This means that each machine or object in the database that has the setting "Create new stream" will be scanned simultaneously instead of in sequence. To increase the number of data streams you must modify the file NNCfg.ini as follows:
a. On the master server, open the file NNCfg.ini with a text editor. This file is located in the NovaNET installation directory.
b. Locate the section heading [Svc-Database Service]. If this section does not exist, add it to the file.
c. Edit the line selectionListThreadCount=8 to contain the proper number of data streams that NovaNET should scan simultaneously. Replace the number 8 with a number between 1 and 64.
d. Save the file as a text file.
Note that NovaNET will scan data streams in sequence instead of simultaneously if you set this number to 1.
The next time you restart the NovaNET service and NovaNET Administrator your changes will take effect. For more information about data streams, see the section Maintaining the Flow of Data in Chapter 10 — Tips Techniques and Strategies in the NovaNET User's Guide and Technical Reference.
Along with the name of the job, the subject lines of email messages generated in NovaNET now contain the name of the Storage Management Zone to which the emails are related.
NovaNET now includes a time stamp for tape alerts.
-------- 9.00 SP3A --------
NovaNET can now fully support backup, restore and disaster
recovery operations on systems running NetWare version 6.5. If you would
like to upgrade your Novell system to NetWare 6.5, visit www.novell.com for
purchasing and download information.
NovaNET can now send email alerts when errors occur while
you are running jobs. For example, if NovaNET issues an alert that another tape
is needed to finish a backup job, that alert can be emailed to the
administrator. To enable this feature, you must modify NNCfg.ini as follows:
Note: Before
modifying the NNCfg.ini make a copy
of it.
1.
Open NNCfg.ini with a text
editor, for example, Windows Notepad.
The file is located in the NovaNET installation directory.
2.
Search for the
[configuration] section.
3.
Add the
following setting:
4.
alertEmail=Yes
5.
With this
setting NovaNET will send email messages every time it issues an error message.
6.
To disable
this setting, change the entry to alertEmail=No or comment
out the setting by placing a semi-colon (;) at the beginning of the line.
7.
Save the file
to accept your changes.
8.
If NovaNET or
the NovaNET service are running, you must stop and restart them in order for
your settings to take effect.
In order
to receive these email alerts, you must set up an email address for the NovaNET
administrator.
1.
In NovaNET, click the Securities tab, right-click the user (e.g., Admin), and select Properties from the shortcut menu.
2.
Click the Email
tab and enter an email address.
3.
Click OK
to save the settings.
NovaNET now provides timeout and filtering settings for
error alerts. These settings let you add a time period after which NovaNET will
automatically cancel an error during a job so that NovaNET can continue processing
jobs. Filtering settings let you tell NovaNET which errors it can cancel
automatically and which ones must be cancelled by a user. To enable this
feature, you must modify NNCfg.ini as follows:
Note: Before
modifying the NNCfg.ini make a copy
of it.
1.
Open NNCfg.ini with a text
editor, for example, Windows Notepad.
The file is located in the NovaNET installation directory.
2.
Search for the
[configuration] section.
3.
Add the
following settings:
alertFilter=<all/(blank)/nn>
alertUnfilter=<all/(blank)/nn>
alertTimeout=<seconds>
These settings work as follows:
·
alertFilter=
tells NovaNET whether or not to cancel error alerts automatically after the
specified timeout period. Valid values for this setting are all to cancel error alerts, blank to not cancel error alerts, or a
string of numbers to cancel only the specified error alerts. To specify which
errors should be cancelled automatically enter the error numbers separated by a
comma. A range of error numbers can be separated by a hyphen. For example, the
setting alertFilter=5,10,25,36-45,80
would tell NovaNET to cancel error
alerts for only the specified errors.
·
alertUnfilter= tells NovaNET
to exclude specific errors when deciding whether or not to cancel them
automatically after the specified timeout period. If an error alert number is
specified in alertFilter= and also in alertUnfilter=, a user must
manually cancel the alert. Errors listed for this setting must be canceled by a
user before NovaNET can continue processing a job.
·
alertTimeout= tells NovaNET
how many seconds it should wait before canceling an error. For example, alertTimeout=300 sets the time limit at five (5) minutes. To disable the
timeout, set the number of seconds to zero (0). When set to zero NovaNET
will not cancel errors automatically; users must press Cancel manually if errors occur.
4.
To cancel all
but a few error alerts after 50 seconds, enter the settings as follows:
alertFilter=all
alertUnfilter=5,10,23,28-45,210,310,400
alertTimeout=50
Include only those error alerts that NovaNET should cancel
automatically. Refer to the NovaNET Error
Codes manual for a list of error code numbers. This manual is available in
.PDF format on the NovaNET CD and in the installation directory on your
computer.
5.
Save the file
to accept your changes.
6.
If NovaNET or
the NovaNET service are running, you must stop and restart them in order for
your settings to take effect.
If you set alertFilter= to all (i.e., NovaNET will cancel all errors automatically), several
alert numbers will require special handling.
For example, if you want an operator to manually cancel Error 76 –
Operator Cancel, you must also list both Error 76 and Error 177 – Alert Job
Status in alertUnfilter=. This is so
because NovaNET displays Error 177 alerts when some other error occurs. If you
list the other errors, but not 177, then NovaNET will automatically cancel
Error 177 alerts for users. The following job status alert numbers should be
specified for filtering or unfiltering purposes:
·
175: Alerts generated during Disaster Recovery
operations
·
176: Alerts generated that require a user to
insert new media
·
177: Alerts related to Job Status
·
178: Alerts that generate a Wrong Media message
·
179: Alerts that prompt the user to reset the
machine
·
180: Alerts that prompt the user to reset NovaNET
The NovaNET Addendum
has been updated to include revisions to Chapter
6 – New Autoloader Features and a new chapter called Chapter 7 – The Text User Interface. Refer to the /doc/<lng>/acrobat
directory on the NovaNET CD-ROM for the printed documentation. The NovaNET Addendum is available only in English.
--------
9.00 SP2C --------
NovaNET now runs on NetWare 6.0 Service Pack 3. Contact
Novell to obtain this service pack.
-------- 9.00 SP2A --------
If you are using a LUN-based autoloader or library on a
Linux system, some LUNS for the device might not be recognized at first.
To verify that all LUNS are recognized, use the following command:
“cat
/proc/scsi/scsi”.
If a LUN does not
appear, force the system to recognize it with the following command:
echo
"scsi add-single-device w x y z" > /proc/scsi/scsi
Where the parameters are set as follows:
·
w
is the host adapter ID, where the first adapter is zero (0)
·
x
is the SCSI channel on the host adaptor, where the first channel is zero (0)
·
y
is the SCSI ID of the device
·
z
is the LUN number of the missing LUN, where the first LUN is zero (0)
Once your device has been detected, stop and restart NovaNET. You must also stop and restart the NovaNET service if it is running.
If you are running NovaNET
for the first time on a system with an attached autoloader or library, NovaStor
Corporation recommends that the autoloader be empty. NovaNET might not be able
to eject media from the autoloader. If this happens, NovaNET displays an alert
asking you to eject the media manually.
NovaNET provides more
features for backing up and restoring data from an autoloader. Refer to Chapter 6 — New Autoloader Features in
the NovaNET Addendum for more
information.
NovaNET now provides
more keyboard navigation options and keyboard shortcuts. Press Tab to select
toolbar commands or to navigate to different objects on the screen. To find an
object in the database, press Ctrl+F. To view an object property sheet, select
an object and press Alt+Enter.
-------- 9.00 --------
NovaNET now supports devices that use logical unit numbers
(LUNs) from 0 to 255.
NovaNET now supports additional bootable tape drives. This
feature lets you create bootable tapes to simplify the disaster recovery
process. For a list of supported tape drives, refer to www.NovaStor.com.
The default filename for the Disaster Recover CD image file
on all platforms is now BOOTCD.ISO.
By default, it is located in the NovaNET directory. On Windows and X Window
(Linux) computers, you may change this filename and its location before
creating the image file.
NovaNET 9.00 includes many performance improvements,
including CPU usage, system resources management and network communications.
In addition to an updated NovaNET User’s Guide and Technical Reference, this release includes
the new NovaNET Installation Guide and
NovaNET Addendum.
When running a backup job, the job may complete immediately
with no errors and zero completed objects. This can occur when you select the Append to all tapes and No auto format options on the Options tab and you are using blank
media.
The job cannot run because these settings prevent NovaNET
from formatting the blank media. Furthermore, NovaNET cannot append to a blank
tape.
To correct this problem, format the blank media before you
run the job. You can also change the Auto
format mode option to Auto format
blank media or Auto format all.
-------- 8.50 --------
Since NovaNET creates long paths whenever you run a custom
schedule, NovaNET now displays a portion of the path name with ‘…’, e.g., Media – Home\Admin Folder\...\daily4. As a result, you can
see the media name.
Note
Platform-specific
corrections now appear in each platform’s section.
In addition to resolving several minor issues, we have corrected the following:
-------- 9.00 SP6A
--------
Maintaining two versions of NovaNET on the same machine or on different machines that are part of the same storage management zone can lead to incompatibility issues between these versions. You should always run the latest NovaNET service pack especially if you are working on a network on which NovaNET is installed on several machines.
Users may have noticed that the auto update feature of the NovaNET installer was not working correctly when installing updated versions of NovaNET on client machines. Now the NovaNET installer will ask users to update their older builds when installing on client machines.
-------- 9.00 SP5B
--------
This service pack contains fixes to issues that were detected since the release of SP5A and includes support for additional devices. For a complete list of supported devices, go to www.NovaStor.com.
--------
9.00 SP5A --------
Several causes of database corruption have been identified and repaired. The problems occurred most frequently on multi-processor machines and frequently caused NovaNET to create duplicate object records in the database. The problem was most apparent when four or more jobs were scheduled to start at the same time.
Users with several machines attached to a Storage Management Zone might have noticed that a machine was still connected to the zone even after the machine lost connection. NovaNET now properly registers when a machine is disconnected which frees up the license for use by another workstation.
Users might have noticed that NovaNET jobs failed to complete if a network connection with an attached device failed. This occurred if NovaNET could not skip over the files located on the device with the failed connection. The problem has been fixed and users will see improvements to jobs running when there are problems with network connections.
When restoring over a busy encrypted file NovaNET issued “unknown error” messages instead of a “busy file detected” message. NovaNET now issues the correct error message and completes these restore jobs successfully.
The NovaNET Microsoft Exchange agent incorrectly identified full and incremental backups on Microsoft Exchange as full backups in the NovaNET log files. The problem has been resolved and NovaNET properly identifies the backup as full or incremental.
The NovaNET Microsoft SQL agent failed to restore SQL incremental and differential log files under certain circumstances. The problem has been resolved.
NovaNET displayed the wrong alert message during longer backups if the tape was full which caused some users to insert the incorrect media. NovaNET now displays the correct alert that instructs users to insert the proper media for these jobs.
NovaNET now properly reports when hard disk partitions are full.
Some NovaNET users might have noticed that NovaNET sometimes counted selected files more than once toward the total number of files selected but actually reported the correct number of files backed up. Since the job indicated no failures, customers were confused about the success or failure of the job. The problem primarily occurred when a directory was selected, one of its subdirectories was deselected and then selected again. Changes in how NovaNET selects files for backups eliminate the condition.
Entries no longer appear in the NNtrace.txt file about untransformed strings while NovaNET generated disaster recovery information. Although untransformed strings did not affect data retention, users found them confusing. NovaNET no longer creates entries in the trace file.
--------
9.00 SP3B --------
Users running Windows Server 2003 with HP 5i RAID controllers might have noticed errors when performing disaster recovery operations after the following support pack had been applied:
Proliant Support Pack for Microsoft Windows Server 2003 (version 6.40 A) released on 1st July 2003.
http://h18004.www1.hp.com/support/files/server/us/locate/69_1342.html#0
DR support has been added for this configuration.
--------
9.00 SP3A --------
With the release of Microsoft SQL 2000, a change was made in the application for the addition of the “Recovery Model” of a SQL database. These new models are called Full, Simple, and Bulk-Logged. In Microsoft SQL versions 6.5 and 7.0 these models have the following equivalent flags:
SQL 2000 Truncate Log on Select Into/
Recovery Model Checkpoint Flag==? Bulk Copy==?
Simple TRUE TRUE or FALSE
Bulk-Logged FALSE TRUE
Full FALSE FALSE
When the Recovery Model for a non-master database in MS SQL 2000 or 7.0 is set to Full, NovaNET restores the non-master database as expected. However, NovaNET fails to restore a non-master database from an incremental or differential backup. To avoid this failure, set the Recovery Model to Full and back up non-master databases using full backups in NovaNET. Alternatively, you can set the Recovery Model to Simple. There is no impact to master SQL databases backups since NovaNET always creates full backups for them.
In Microsoft SQL 6.5, there is no impact in NovaNET for restore jobs involving master SQL databases; however, NovaNET might fail to complete restore jobs for non-master databases due to database device storage limitations. View the logs in NNtrace.txt for the exact error. This issue will be resolved in a future service pack.
Procedures for restoring transaction log files for a Microsoft SQL database have changed. You must restore the most recent full backup and all subsequent incremental/differential backups in the order in which they were performed. For example, if you performed a full backup on Monday and incremental backups on Tuesday through Thursday, you would create and run five restore jobs as follows:
1. Launch NovaNET and click the Restore tab.
2. Right-click on a folder name and select New Restore Job from the shortcut menu.
3. On the General tab, name the restore job (e.g., Restore Full backup, Restore Incremental 1, Restore Incremental 2, etc.).
4. On the Selection tab, check the box next to the objects to be restored.
5. On the Options tab, click the Advanced Options button.
6. Click the check-box next to Finalize restore to remove the check-box and deselect the option.
7. Click OK to save the setting.
8. Click OK to save the restore job.
9. Repeat these steps to create restore jobs for each incremental or differential backup job performed since the full backup.
10. For the last incremental or differential job, select Finalize restore on the Advanced Options screen to enable this option.
Note: Finalize restore should be enabled only for the final restore job. All other jobs should have this option disabled.
11. Once created, select the full restore job and run it.
12. Run the remaining incremental or differential restore jobs.
Previously NovaNET allowed users to restore the NovaNET database from password-protected media without requesting the password. A field has been added to the Restore Database dialog and users will be asked to enter the password for media while restoring the database.
Performing multiple asynchronous loader operations simultaneously on autoloaders with more than one device may cause the User Interface to hang in some cases. This has been fixed in this current release.
-------- 9.00 SP2D --------
NovaNET was causing Error 333 – unexpected bus free timeout
errors with space commands on some Travan IDE devices. The timeout parameter
for space commands has been increased and the commands no longer generate the
errors.
-------- 9.00 SP2A --------
NovaNET now runs Content Indexing
backup jobs if the Content Indexing service is stopped. Previously, NovaNET
generated an error message that the service was down but did not perform the
backup.
NovaNET ignores unmounted volumes or
volumes to which it does not have access during disaster recovery operations,
such as utility volumes.
NovaNET properly displays changes to
database objects in the title bar after a user clicks Apply. Previously, if a
user updated object information, NovaNET did not update the object properties
information without closing and then reopening the properties screen.
Some users experienced problems
restoring databases created with a prior version of NovaNET on a
multi-processor machine. Now NovaNET successfully backs up these databases on
these machines.
Administrators on client machines might
notice that log files were not updated if NovaNET was also running as a
service. Now both the administrator and the NovaNET service can write to the
log files.
-------- 9.00 --------
Some users experienced stream sync
errors on systems with 1GB RAM or more. Now NovaNET computes the device buffer
size correctly on these systems. For information on changing device buffer
sizes, please see Device Buffer Sizes in
Chapter 4 — Installation Notes in the
NovaNET Installation Guide.
Question marks appeared on the
autoloader status screen when the user tried to change the slot status. This
was related to some autoloaders not returning a serial number to NovaNET.
In some installations, when a backup
job spans more than one media, users could encounter Error 514: End of Data
when restoring or verifying objects that were written near the end of the
media. While this problem will not occur on any new backups, some users may
encounter this error with media that was created prior to 8.50 SP3A.
When you upgrade to NovaNET 9.00 from a previous version,
you must install NovaNET and any NovaNET options individually. The automatic
upgrade feature is available only when upgrading to a new service pack.
Note The NovaNET Installation Guide incorrectly
states that the installation manager displays the automatic upgrade message
when you are upgrading to a new version or service pack. Actually, this message
only appears if you are upgrading to a new service pack. If does not appear if
you are upgrading from a previous version of NovaNET.
You can customize the following NovaNET configuration
settings, which are located in the NNCfg.ini:
· Increasing maximum size of emailed job logs
· Enabling Encrypting File System (EFS)
· Enabling Files not to back up
· Removable Storage Manager (RSM) and NovaNET
Refer to Chapter 4 —
Changing NovaNET Configuration in the NovaNET
Addendum for more information.
Backup and restore
operations require access to all system files and functions. Therefore, before
you install or run NovaNET, you must log in to your operating system with a
system administrator account (or equivalent).
When running NovaNET
as a service while creating disaster recovery media, NovaNET only logs trace
messages to the NovaNET Messages screen.
If an error occurs, NovaNET may not log the trace messages in the NNtrace.txt
file in the NovaNET directory. However, NovaNET will log the trace messages in
the NovaNET Messages screen.
To save the trace
messages to a text file, perform one of the following:
· From the NovaNET administrator, click Tools | Messages. Click Save to save the trace messages to file.
· Stop the NovaNET service (see Appendix E — NovaNET Service in the NovaNET Installation Guide) and run the NovaNET administrator. Then try creating your bootable disaster recovery media again. NovaNET writes the trace messages to the NNtrace.txt file in the NovaNET directory.
--------
8.50 --------
In
installations with more than one tape drive, NovaNET tries to use all available
drives. When a backup job starts, it determines whether or not it needs a
second drive. Users with this type of configuration could experience either of
the following scenarios:
· NovaNET allocates two or more tape drives for the job. The first drive contains a tape, but the second drive is empty. As the job runs, NovaNET asks the user to insert a tape in the second drive. To run the job on the first drive only, click Abort. The job no longer tries to access the second drive.
· The media in the first drive becomes full. NovaNET continues backing up to the media in the second drive. NovaNET waits until it fills the media in the second drive before it ejects the media in the first drive.
Note
You
can specify the tape devices to use when you create the backup job.
-------- 9.00 SP6A
--------
NovaNET now supports backup, restore and disaster recovery
operations using REV™ drives. Follow these guidelines when using REV drives.
By default NovaNET uses REV disks exclusively for
backups or disaster recovery operations; that is, NovaNET overwrites the entire
contents of your REV disks. If you routinely copy files to REV disks, you
should store this media separately from REV disks that you use for backups and
disaster recovery. Any files copied onto this media will be overwritten by NovaNET backups.
If you use the NovaNET agent for Disaster Recovery,
follow these instructions to prepare disaster recovery media and to perform a
DR operation with a REV disk.
Preparing
for disaster recovery is a four-step process:
1. Install NovaNET and the Disaster Recovery option.
2. Create a full backup of your system:
a. Launch NovaNET and access the Wizard options screen.
b. Click or select Backup Local Machine.
c. On the Options tab, select Full for the Backup mode and Overwrite all tapes for the Write mode.
d. Run the backup job, inserting media as requested.
3. Create the bootable media:
Note If you are using a bootable REV drive, NovaNET created a bootable REV disk when you ran the full backup.
a. Access Disaster Recovery from the Wizard options screen.
b. Select either Create Diskettes or Create CD Image.
c. Follow the onscreen instructions until the CD image, bootable REV disk or all diskettes are created. If you created a CD image, burn the BOOTCD.ISO file to a blank CD‑R/CD-RW.
4. Test the bootable media to make sure it was created properly.
1. Insert the bootable media (diskette, CD-R/CD-RW, bootable REV disk) into the computer.
2. Power on your computer and REV drive.
3. Follow the onscreen instructions.
4. As each phase completes, eject the REV disk before rebooting your computer.
5. When the operating system displays the message "Attempting to boot from Iomega RRD, waiting for device…", insert the bootable REV disk.
6. Follow the onscreen instructions until the disaster recovery process is complete.
-------- 9.00 SP5C
--------
A change in the NovaNET buffer size that halted installations on Japanese-language versions of Microsoft operating systems has been resolved. NovaNET now installs as expected on supported Japanese-language versions of Microsoft Windows operating systems.
Users restoring Microsoft Exchange 5.5 databases might have noticed that NovaNET failed to restore these files because it did not locate the database files properly on the media. The issue has been resolved and NovaNET reads the media contents properly and restores Microsoft Exchange 5.5 databases as expected.
Users restoring master databases of obsolete versions of Microsoft SQL Server 6.5 might notice unexpected errors in NovaNET. Even though these errors occur, NovaNET successfully restores the databases. Please contact NovaStor Corporation Technical Support for information regarding the errors and procedures for minimizing their impact in NovaNET. Note that Microsoft SQL Server 6.5 was replaced in 1997. If you are restoring master databases for a newer version of Microsoft SQL Server, you do not need to contact Technical Support.
--------
9.00 SP5A --------
NovaNET failed to release System State connectors if errors
occurred or connection was lost during backup and restore jobs in which the
System State was selected. NovaNET now includes more safeguards for resolving
busy
--------
9.00 SP4A --------
The NovaNET Service Control Manager could not be launched if Internet Explorer was open. The issue has been resolved and Internet Explorer no longer interferes with the NovaNET Service Control Manager. For more information about the NovaNET Service Control Manager, see Appendix E – NovaNET Service in the NovaNET Installation Guide.
--------
9.00 SP3A --------
NovaNET users might have noticed that log files were not being created. A syntax error that inhibited the creation of log files has been corrected and users will now see all log files.
--------
9.00 SP2C --------
NovaNET improperly interpreted some
reserved double-byte characters (e.g., Japanese), which interfered with the
backup of some files. NovaNET now correctly interprets these characters and
backs up the files.
-------- 9.00 SP2A --------
NovaNET now backs up more files in your
Windows System folder. It only excludes registry and event logs from backups.
NovaNET now offers improved onscreen
and log file messages when you have a problem while restoring your
-------- 9.00 --------
The
During backup, this object identifies
the order in which to restore system files. During restore, the system files
are restored in their correct order. This process eliminates possible problems
as a result of the restore.
The
· Windows Boot and SFP (system file protection) files
· Windows COM+ Database connector
· Windows Event Log connector
· Windows Registry
· Terminal service database connector, which backs up the terminal licensing database
· DHCP connector, which backs up the DHCP database
· Windows Active Directory
· System volume
· Cluster database connector
· Content Indexing Service
-------- 8.50 --------
The final phases of Disaster Recovery
in Windows installations are not displayed in Japanese. Due to font problems,
these screens appear in English on Japanese installations. However, all files
will be recovered with their correct names in their correct locations. The
final phases of Disaster Recovery in all other languages display correctly.
Also, during the final phases of
Disaster Recovery, some non-English characters may display as black boxes on
the log screen. You can ignore this. It will not affect file names and
locations.
--------
9.00 SP5B --------
NovaNET has fixed a problem with creating disaster recovery media on systems running Windows 2000 or later with dynamic disk. Customers can now create disaster recovery media as expected.
--------
9.00 SP5A --------
NovaNET reported that files were busy if a user tried to access a file to which they did not have access rights. This occurred when accessing either files or directories. The problem has been resolved and NovaNET properly reports when a user lacks the required access to a file or folder.
--------
9.00 SP4B --------
NovaNET has fixed a known crash bug on the Device tab of the NovaNET Administrator that affected some Windows NT 4.0 configurations.
-------- 9.00 SP4A --------
NovaNET can now be installed with predefined settings on workstations running Windows NT or later. To install NovaNET with predefined settings you launch NNwinains.exe from Windows Explorer after creating a file called autoinst.inf that includes the settings for your NovaNET installation. Follow these steps to create this file:
1. From Windows Explorer, create a new file named autoinst.inf in the directory from which NovaNET is installed (e.g., a network share).
2. Open this file with a text editor (e.g., Windows Notepad).
3. Copy the text below into the file. You can paste this information directly from these release notes.
4. Replace the text surrounded by angle brackets with your predefined settings.
· To create a zone name based on the machine name, leave zoneName= blank
· If you know the name of each machine in advance, add a section for each machine
· To prevent an older version of NovaNET from being overwritten, set ForceUpdate= to No
· To save log messages on the installation to the file NNtrace.txt, set enableDebug= to Yes
·
Set the
language in which to install NovaNET (e.g., for French set lngId= to fre, for other languages use eng for English, ita for Italian, ger for German, spa for Spanish, or jpn for Japanese)
· Customize the file for any specific locations, unique options or settings as appropriate
;----------------------------------------------------------------
;
Auto Installation Control File
;
This is the generic auto installation control file.
;----------------------------------------------------------------
;----------------------------------------------------------------
;
Configuration information
;----------------------------------------------------------------
[configuration]
zoneName=<ABC
Network Zone>
regOrg=<ABC
Company>
regUsr=<admin>
protocol=<tcp>
installPath=<c:\program
files\NovaNET>
forceUpdate=No
installAsService=Yes
isEval=No
enableDebug=No
licenseKey=<insert
license key>
lngId=<fre>
;---------------------------------------------------------------
;This
section contains settings specific to the database server.
;---------------------------------------------------------------
[configuration.<database
server machine name>]
createZone=Yes
regOrg=Yes
regUsr=<admin>
lngID=<eng>
;---------------------------------------------------------------
;This
section contains settings specific to the client machine.
;---------------------------------------------------------------
[configuration.<client
machine 2>]
createZone=No
regOrg=<ABC
Company>
regUsr=<client
user name>
;---------------------------------------------------------------
;
This section contains settings specific to another client
:
machine. Add a new section for each client machine.
;---------------------------------------------------------------
;[configuration.<client
machine 3>]
;createZone=No
;regOrg=<ABC
Company>
;regUsr=<another
client user name>
5. Save the file.
6. Launch NNwinains.exe from Windows Explorer.
7. Copy this file to other machines on which you want to install NovaNET with these settings.
-------- 9.00 SP3A --------
NovaNET Web Gateway users might have noticed that media passwords were not encrypted when they were formatting media. The problem has been corrected and passwords now appear as encrypted characters.
NovaNET Web Gateway users could not import password-protected media from the Web Gateway because NovaNET would not request the password. A field has been added to the Device page and users can now enter the password for the media.
Users might have noticed that the Run button was still active on the Job Status screen when running jobs from the Web Gateway. This would allow users to click the button while an active job was running or paused. This button is now greyed out as expected when it is unavailable.
NovaNET users running the Web Gateway might have noticed that the Diagnostics tab for a client machine connected to a server zone was blank. The problem has been corrected and users can now view diagnostics information about connected client machines through the Web Gateway.
Previously users with multi-volume systems might notice that restoring busy files did not work as expected. This would happen where the busy file resided on one volume (e.g., the C: drive) and the temporary directory resided on a different drive (e.g., the D: drive). The problem has been resolved and busy files on multi-volume systems are now restored as expected.
Previously users with systems that created short filename aliases in the registry for files with long filenames noticed that NovaNET did not restore the short filenames. This meant that the restored files could not be found by other applications that used those short filenames. The problem has been resolved and NovaNET now restores both long and short filenames.
Previously users might have noticed that NovaNET did not properly restore security information or other data streams associated with mount points as expected during a restore job when the Mount points advanced options setting was deselected. It will now restore all streams (including security) associated with the mount point when this option has been deselected.
Previously users might have noticed that NovaNET generated bad handle and busy object errors when restoring content indexing data streams created on Windows 2000 systems on which indexing services were enabled. The most common errors that NovaNET generated were Error 214 and 209. Content indexing permits users to search for and locate files in Windows Explorer or from their web browser based on advanced search criteria stored in these data streams. NovaNET now properly restores these files.
Previously NovaNET did not restore the
-------- 9.00 SP2C --------
The Web Gateway might not be enabled upon installation if the IIS server does not map correctly to .NET file extensions. This occurs if you installed the IIS server after installing the .NET framework or if you removed and reinstalled the IIS server after installing the .NET framework. To repair the IIS server mappings:
1. Open a command window.
2. At the command prompt, navigate to one of the following directories:
c:\windows\microsoft.net\framework\V1.0.3705\
(.NET framework v1.0.3)
c:\windows\microsoft\framework\v1.1.4322\
(.NET framework v1.1)
3. Type aspnet_regiis.exe –i and press Enter. This utility repairs the IIS mappings which enables the NovaNET Web Gateway.
NovaNET might cause data loss while backing up or restoring certain
configuration files. NovaNET must close these configuration files during backup
or restore operations. However, if an application does not process
“session_end” and/or “application_end” events properly, you may lose data when
it closes abruptly. NovaNET does not generate an error message or pause to let
you close the application manually.
For example, the machine.config file sends "session_end" and
“application_end” events to all open applications. Similarly, restoring
<application directory>\web.config sends “session_end” and “application_end”
events to a particular application. If one of these applications does not shut
down properly, you could lose data that has not been processed by that
application.
Session_end and application_end events are standard .NET commands. If an application on your system does not handle these commands properly, contact the application provider so that they can correct the problem.
-------- 9.00 SP2A --------
NovaNET automatically restores
read-only files in the system state. When you restore files from an SFP backup,
the read-only attributes on some files no longer prevent restoring these files.
NovaNET sometimes
failed to issue error messages if it could not restore a large Microsoft
Exchange 2000 server database (over 4GB). This problem has been fixed. NovaNET
correctly logs error messages during restore operations for larger databases.
-------- 9.00 --------
The NovaNET Disaster Recovery option
for Windows 2000 and later now supports all disk configurations including those
with dynamic disk partitions.
Note
When
performing disaster recovery with dynamic disks, you must format any new disks
with the same drive geometry as the old disks or disaster recovery may fail.
Note
On
some Windows 2000 machines with dynamic disks, it may take extra time to generate
disaster recovery media. This is due to how Windows 2000 calculates disk size.
NovaNET now backs up and restores Disk
Quota information on Windows 2000 and later systems. Disk quotas let the system
administrator limit that amount of available disk space for each user on a
volume.
NovaNET now restores the original short
path names on systems running Windows XP and later. For example, Windows might show
c:\Docume~1 for the c:\Documents and Settings directory.
Now this directory name will be restored properly.
NovaNET fully supports volume mount
points and directory junctions. During backup, NovaNET saves the basic access
control list (ACL) for each directory junction as well as the metadata. The
metadata is the descriptor block that tells Windows where the directory
junction is mounted or linked. During restore (including disaster recovery), NovaNET
uses this information to restore both volume mount points and directory
junctions.
For information on how to include or
exclude mount point data during backup and restore jobs, see Mount Points in Chapter 7 — Job Options in the NovaNET
User’s Guide and Technical Reference.
NovaNET also comes with the new Smart
Mount Points feature. This feature prevents recursion, that is, an object that
refers to itself. It also prevents multiple backups of the same data on volumes
that are referenced by different identifiers.
After successfully completing a
disaster recovery on Windows NT and later systems, the system event viewer
reports an error: “The Distributed Transaction Coordinator service terminated
with service-specific error …” This error occurs because the restored DTC log
file, which was marked as “busy” during backup, is also marked as “busy.” This
keeps the DTC service from starting.
To resolve this problem:
a. If cannot log in to Windows, reboot your system in safe mode.
b. Open
a command window.
c. Type
msdtc –resetlog from the command
prompt.
-------- 8.50 --------
Under Windows NT and later, the file
system lets you restrict user access to specific files and folders. In some
installations, individual users changed the access permissions to their own
files. As a result, the Windows administrators could not restore these files;
they did not have access rights. NovaNET now restores these files.
Note
For
legal reasons, Microsoft recommends against restricting Windows administrator
access to any file or folder in any business, corporate or other organizational
environment.
Before it continues processing, NovaNET
verifies that a user has access rights to each drive on the Windows Cluster
2000 Server. As a result, NovaNET performance has improved.
Unicode separator characters no longer
affect NovaNET operation in some non-English Windows installations.
Microsoft Exchange Server 5.5 does not support simultaneous
backup of the information store (IS) and the data store (DS). Therefore, NovaNET
no longer supports multiple streams when backing up Microsoft Exchange Server.
If an error 617 occurs when restoring Microsoft Exchange,
you have selected old instances of Exchange for restoring. By default, you
cannot automatically restore your old backups. If you selected the old
instances by mistake, simply deselect them in the restore job. Their icons are
marked with a black X on a yellow dot.
To restore the old instances:
a. Add
the following line to the [msExcServer]
section in the NNCfg.ini:
restoreOldFormat=Yes.
b. Stop and restart the NovaNET service (see Appendix E — NovaNET Service in the NovaNET Installation Guide).
c. Restore from the old tapes:
1. Access NovaNET.
2. Create a restore job.
3. Deselect the new storage group objects from the list on the Selection tab.
4. Select the old storage group objects from the list on the Selection tab.
5. Run the restore job.
6. Exit NovaNET.
d. When you finish restoring your old instances, either remove the restoreOldFormat=Yes line from the NNCfg.ini or change the line to restoreOldFormat=No. Then stop and restart the NovaNET service.
Windows Terminal Server lets you
configure individual workstation computers as terminals to the server. To
install NovaNET in this environment:
1. Log on as the administrator; otherwise, you cannot install the software.
2. Access the command prompt.
3. Type user change /install. This locks out other users during installation.
4. Install NovaNET according to the installation instructions in the NovaNET Installation Guide. Be sure to enable the NovaNET service.
5. Access the command prompt again.
6. Type user change /execute. This returns the Terminal Server to its normal mode.
Windows 2000 Small Business Server does
not support short path names during backup and restore. If you use short path
names during a restore, the Small Business Server console tools will become
unavailable. This is because Microsoft registered the short path names instead
of the long path names for the SBS program files (DLLs) in its registry.
To resolve this problem, run the
following from the command prompt immediately after performing disaster
recovery:
regsvr32 "c:\program files\microsoft
backoffice\Management\BOMsnap.dll"
regsvr32 "c:\program files\microsoft
backoffice\Management\BOHome.dll"
When you install an OnStream ADR2.60usb
tape drive, your computer may install the wrong device driver. Therefore, you
must install the OnStream USB tape driver (ADR2K.sys) before starting NovaNET.
The ADR2K driver is located in the /Drivers subdirectory on the NovaNET CD-ROM that ships with the
OnStream ADR2.60usb tape drive. You can also download the driver from the
OnStream website (http://www.onstreamdata.com/support/win_drivers.shtml).
Note
This
link may change without notice.
Before you proceed, identify the
location of the device driver. Then install and power on the tape drive.
Finally, refer to the appropriate instructions below: Windows
2000 or Windows XP.
To install the OnStream ADR USB Driver
for Windows 2000, follow the steps below.
a. If the Insert Disk screen appears, insert the NovaNET CD-ROM and click OK. After the system installs the drivers, skip to step 1 in step e below.
b. Access the Hardware tab on the System Properties screen:
1. Right-click My Computer. A popup menu appears.
2. Select Properties. The System Properties screen appears.
3. Select the Hardware tab.
c. Run the Hardware wizard:
1. Click the Hardware Wizard button. The Add/Remove Hardware Wizard screen appears.
2. Click Next. The Choose a Hardware Task screen appears.
3. Select Add/Troubleshoot a device and click Next. The system searches for the hardware and displays the Choose a Hardware Device screen.
4. Select OnStream ADR Series USB Device and click Next. The Add/Remove Hardware Wizard screen appears again.
5. Click Finish. The Add/Remove Hardware Wizard screen closes.
6. Close the Hardware Troubleshooter screen.
d. Upgrade Device Driver
1. If the Upgrade Device Driver Wizard starts automatically, skip to step 7 below.
2. Click the Device Manager button on the System Properties screen. The Device Manager screen appears.
3. If not already open, double-click Tape drives to open its category.
4. Double-click OnStream ADR Series USB Device. The Device Properties screen appears.
5. Click the Driver tab.
6. Click the Update Driver button. The Upgrade Device Driver Wizard screen appears.
7. Click Next. The Install Hardware Device Drivers screen appears.
8. Select Display a list of the known drivers… and click Next. The Select a Device Driver screen appears.
9. Select OnStream ADR Series USB.
10. Insert the NovaNET CD-ROM, a different CD or the diskette that contains the device drivers.
11. Click Have Disk. The Install From Disk screen appears.
12. Click Browse. The Locate File screen appears.
13. Select the directory location of ADR2K.INF, e.g., d:\drivers on the NovaNET CD.
14. Select the ADR2K.INF file and click Open. The Locate File screen closes.
15. Click OK. The Install From Disk screen closes.
16. Select OnStream ADR Series USB and click Next. The Start Device Driver Installation screen appears.
17. Click Next. The system installs the device driver. Then the Upgrade Device Driver Wizard screen appears.
18. Click Finish.
19. If the Device Properties screen is open, click Close to close it.
20. If the Device Manager screen is open, close it.
21. If the System Settings Change screen appears, close all applications. Then click Yes to restart your computer and complete driver installation.
e. Check the device status to make sure it is properly installed:
1. If the Hardware tab of the System Properties screen is already open, skip to step 5 below.
2. Right-click My Computer. A popup menu appears.
3. Select Properties. The System Properties screen appears.
4. Select the Hardware tab.
5. Click the Device Manager button. The Device Manager screen appears.
6. Double-click Tape drives. The Tape drives category opens.
7. Double-click OnStream ADR Series USB Device. The Device Properties screen appears.
8. Check the Device status section of the Device Properties screen. It should read: This device is working properly. If not, click Troubleshoot to open the Tape Drive Troubleshooter screen.
9. Close the Device Properties, Device Manager and System Properties screens.
To install the OnStream ADR USB Driver
for Windows XP, follow the steps below.
a. If the Found New Hardware Wizard screen appears, skip to step 7 in step d below.
b. Access the Hardware tab on the System Properties screen:
1. Right-click My Computer. A popup menu appears.
2. Select Properties. The System Properties screen appears.
3. Select the Hardware tab.
c. Run the Hardware wizard:
1. Click the Add Hardware Wizard button. The Add Hardware Wizard screen appears.
2. Click Next. The system searches for the hardware. If the Found New Hardware Wizard screen appears, skip to step 7 in step d below.
3. When the Is the hardware connected? screen appears, select Yes, I have already connected the hardware and click Next.
4. Select OnStream ADR Series USB Device and click Next. The Add Hardware Wizard screen appears again.
5. Click Finish. The Add Hardware Wizard screen closes.
6. Close the Tape Drive Troubleshooter screen if it appears.
d. Upgrade Device Driver
1. If the Hardware Update Wizard starts automatically, skip to step 7 below.
2. Click the Device Manager button on the System Properties screen. The Device Manager screen appears.
3. If not already open, double-click Tape drives to open its category.
4. Double-click OnStream ADR Series USB Device. The Device Properties screen appears.
5. Click the Driver tab.
6. Click the Update Driver button. The Hardware Update Wizard screen appears.
7. Select Install from a list…
8. Insert the NovaNET CD-ROM, a different CD or the diskette that contains the device drivers.
9. Click Next. The Install Hardware Device Drivers screen appears.
10. Select Search for the best driver…
11. Select Search removable media…
12. If installing the driver from a local or network drive location (neither diskette nor CD):
i. Select Include this location… and click Browse. The Browse For Folder screen appears.
ii. Locate the subdirectory on the drive that contains the ADR2K.INF file.
iii. Click OK. The Browse For Folder screen closes.
13. Click Next. The computer searches for the driver.
14. If two or more drivers are available, select the correct driver and click Next.
15. If a Hardware Installation warning screen appears, click Continue Anyway.
16. After the computer installs the drivers, the hardware wizard complete screen appears.
17. Click Finish. The hardware wizard complete screen closes.
18. If the Device Properties screen is open, click Close.
19. If the Device Manager screen is open, close it.
e. Check the device status to make sure it is properly installed:
1. If the Hardware tab of the System Properties screen is already open, skip to step 5 below.
2. Right-click My Computer. A popup menu appears.
3. Select Properties. The System Properties screen appears.
4. Select the Hardware tab.
5. Click the Device Manager button. The Device Manager screen appears.
6. Double-click Tape drives. The Tape drives category opens.
7. Double-click OnStream ADR Series USB Device. The Device Properties screen appears.
8. Check the Device status section of the Device Properties screen. It should read: This device is working properly. If not, click Troubleshoot to open the Tape Drive Troubleshooter screen.
9. Close the Device Properties, Device Manager and System Properties screens.
--------
9.00 SP5A --------
NovaNET reported that files were busy if a user tried to access a file to which they did not have access rights. This occurred when accessing either files or directories. The problem has been resolved and NovaNET properly reports when a user lacks the required access to a file or folder.
--------
9.00 SP3A --------
Previously NovaNET did not restore the
--------
9.00 --------
Microsoft discontinued support for Windows 95 as of
December, 2002. Therefore, NovaNET no longer supports operation under Windows
95.
-------- 8.50 --------
In some installations, logical volumes
might not appear under Windows 98/Me. This issue has been resolved.
While NovaNET supports most Windows
98/Me functionality, it has the following limitations:
·
Protected-mode 32-bit disk drivers must control all disks
and volumes. Real mode drivers are not supported. To determine if your system
uses only 32-bit drivers:
a. Right-click the My Computer icon. A popup menu appears.
b. Select the Performance tab.
If any 16-bit real mode drivers are in
use, Windows indicates that your system is not optimally configured. This is
common for most systems.
·
The tape device must use a 32-bit protected mode driver.
This is common for most SCSI and ATAPI controllers.
·
NovaNET does not support the use of disk compression
software, such as DriveSpace or Stac.
--------
9.00 SP5A --------
Users running NovaNET on NetWare 6.5 systems should be aware that the command syntax for enabling multiple LUNs might be different for some drivers. Page 34 of the NovaNET Installation Guide refers to the command “load adpt160m lun_enable=ff”. This command works for most drivers on NetWare 6.0 systems. However, on NetWare 6.5, multiple LUNs are not recognized with this command.
Refer to the manufacturer’s documentation for the correct command to enable multiple LUNs for your device driver. For example, an Adaptec Ultra160 SCSI card requires the following command to enable multiple LUNs:
load adpt160m.ham slot=x /luns
To verify that the operating system
recognizes multiple LUNs properly, run the following command:
scan all
list storage adapters
Note: The command and procedures to enable multiple LUNs with your SCSI host bus adapter might vary. Refer to the manufacturer’s documentation for the correct instructions for your operating system and device.
--------
9.00 SP3A --------
NovaNET
can now fully support backup, restore and disaster recovery operations on
NetWare version 6.5. If you would like to upgrade your Novell system to
NetWare 6.5, visit www.novell.com for
purchasing and download information.
NovaNET users on systems running NetWare 5.1 or higher might
have noticed that trustee rights for some objects were not restored properly
during a disaster recovery operation on a local machine. This has been fixed in
the current release.
--------
9.00 SP2C --------
NovaNET
now runs on NetWare 6.0 Service Pack 3. Contact Novell to obtain this service
pack.
--------
9.00 SP2A --------
Novell has identified device problems
under Netware 6.0 that use LSI SCSI adapters based on Fusion-MPT technology.
The system might hang or the device may not function properly. To resolve these
problems, contact Novell to download NWASPI.CDM version 3.25.
-------- 9.00 --------
Since Novell discontinued support for
NetWare 4.11 and 5.0, you must upgrade to NetWare 4.2 or 5.1, respectively
(refer to the Novell website for upgrade information). NovaNET no longer
supports operation under NetWare 4.11 and 5.0.
Novell has identified possible network
problems under NetWare. If you experience random lockups or slow network
throughput, we recommend that you update the AUTOEXEC.NCF file according to the
instructions in Novell Technical Information Document 10061174 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/10061174.htm).
Note
This
link may change without notice.
-------- 8.50 --------
In NetWare 6 installations, you must
install NetWare 6 SP1 to support NovaNET Disaster Recovery.
The NSS administration volume is
dynamic, being created at system startup and updated each time it is accessed.
Therefore, NovaNET does not back it up by default.
This volume’s name changed with NetWare
6, causing NovaNET to back it up by default. This has been corrected, so that NovaNET
no longer backs up either NSS administration volume by default: NSS_ADMIN under
NetWare 5, _ADMIN under NetWare 6.
Now NovaNET properly restores NSS
partitions that are larger than 4GB under NetWare 6.
In some NetWare 6 installations, NovaNET
could Abend the server during Phase 3 of Disaster Recovery. Now this phase
finishes properly in these installations.
--------
9.00 SP5B --------
When
running Disaster Recovery on some Linux systems running LILO, NovaNET restores
all files, but the system does not boot properly if the boot disc was created
with LILO. This problem does not occur on systems running GRUB. To work around
this problem, follow these instructions:
a. Start the disaster recovery operation.
b. After NovaNET restores all data, press
Alt-F2 to switch to a console screen and type the following commands:
# chroot /mnt/root
# lilo
c. Remove the boot CD from its drive and
press Ctrl-Alt-Delete to reboot the computer.
Note:
This problem has been detected on systems running Mandrake 9.2 and
SlackWare 9.1. Systems boot properly after a disaster recovery if the system
uses GRUB. If you are using LILO and would like to avoid the workaround,
install GRUB and create a new boot CD for use with future disaster recovery
operations.
--------
9.00 SP5A --------
The Oracle Connector references several libraries from Oracle version 9i. In order for the Oracle Connector to work properly with NovaNET installations running on Oracle 8i systems, you must create symbolic links to the correct libraries.
While logged on to the Oracle server as the Oracle user, run the following command:
ln
-s <target> <linkname>
where <target> is the name of the Oracle 8i library file and <linkname> is the symbolic link. You should create the following symbolic links:
target linkname
$ORACLE_HOME/lib/libclntsh.so.8.0 $ORACLE_HOME/lib/libclntsh.so.9.0
$ORACLE_HOME/lib/libwtc8.so $ORACLE_HOME/lib/libwtc9.so
Users running NovaNET from the command line on Linux systems might have noticed that NovaNET issued “Quick Erase” messages while performing a Secure Erase operation. This error has been fixed and NovaNET properly identifies the type of erase operation it is performing.
Users running the NovaNET Administrator while the NovaNET service was also running might have noticed that the nntrace.txt file would get renamed or that all logs were deleted. A problem handling locked files has been fixed and the nntrace.txt file will remain intact as expected.
Users who disabled hardware compression for a backup job might have noticed that they could not re-enable compression at a later time without deleting the job and creating a new job. The problem has been fixed and NovaNET allows users to enable hardware compression after it has been disabled.
--------
9.00 SP2D --------
Previously NovaNET
failed to complete disaster recovery operations on Linux systems with IDE tape
devices on third IDE channels. While the files remain intact on the recovery
tapes, no files would be recovered to the designated location. To recover the
files, place the disaster recovery tape in IDE channel 1 or 2 and start the
operation again. Future disaster recovery operations made with reformatted
tapes using IDE tape devices on Channel 3 will complete as expected.
-------- 9.00 SP2C --------
Previously NovaNET
failed to restore the GRUB boot loader correctly during the recovery phase of a
disaster recovery on United Linux systems. As a result administrators were
required to restart the machine using a recovery disk. NovaNET now correctly
restores the GRUB boot loader, and recovery disks are no longer required to
restart the machine.
-------- 9.00 SP2A --------
If you are
using a LUN-based autoloader or library on a Linux system, some LUNS for the
device might not be recognized at first. To verify that all LUNS are
recognized, use the following command:
“cat /proc/scsi/scsi”.
If a LUN does not appear, force the system to
recognize it with the following command:
echo "scsi add-single-device w x y
z" > /proc/scsi/scsi
Where the
parameters are set as follows:
·
w
is the host adapter ID, where the first adapter is zero (0)
·
x
is the SCSI channel on the host adaptor, where the first channel is zero (0)
·
y
is the SCSI ID of the device
·
z
is the LUN number of the missing LUN, where the first LUN is zero (0)
Once your device has been detected, stop and restart NovaNET. You must also stop and restart the NovaNET service if it is running.
If you are running NovaNET for the first time on a system
with an attached autoloader or library, NovaStor Corporation recommends that
the autoloader be empty. NovaNET might not be able to eject media from the
autoloader. If this happens, NovaNET displays an alert asking you to eject the
media manually.
-------- 9.00 --------
NovaNET now backs up and restores the extended attributes
and access control lists (ACLs) for objects. As a result, these attributes will
be available when the objects are restored.
When using Red Hat 8.0 and GNOME terminal, the F10 key is
remapped for the GNOME terminal windows. As a result, pressing F10 has no
effect within NovaNET. As an alternative:
· Use the ` (grave accent) shortcut key instead of the F10 key. These keys are equivalent in NovaNET.
· Launch the console version of NovaNET from an XTERM window.
· Use the X Window version of NovaNET.
Mandrake 7.2 and SuSE 7.0 are incorrectly listed as supported
Linux versions in Chapter 1 —
Installation Overview of the NovaNET
Installation Guide. However, NovaNET supports all other listed Linux
versions.
-------- 8.50 --------
A problem with the Linux SCSI Generic (sg) module causes it
to incorrectly determine the direction of dataflow in Symbios SCSI cards. As a
result, a message similar to the following may appear:
kernel:
sym53c1010-33-1-<3,0>: extraneous data discarded.
kernel:
sym53c1010-33-1-<3,0>: COMMAND FAILED (89 0) @dfe17000.
When the SCSI card driver tries to use this information, it
becomes confused and information is lost, which triggers the extraneous data discarded error message.
Please note that this is not a NovaNET problem. It is a
problem with the Linux SCSI Generic (sg) kernel module (sg.o).
Choose one of the following to resolve this problem:
· Install a different SCSI card that works properly with Linux.
· Find out from your Linux distributor when they will change the sg module to accommodate the latest Symbios driver.
· Compile the latest sg.o drivers for the current version of the Linux kernel yourself.
Note NovaStor Corporation
only provides this information as a service to our users. We assume no
liability for the driver or end-user failure.
To fix this problem, you must rebuild the SCSI Generic
(sg.o) driver for the Linux kernel. Your Linux distributor typically performs
this complicated procedure. If you perform this procedure, we recommend that
you test the result on a non-production machine in case if the steps are
performed incorrectly.
Access the SCSI Generic site at http://gear.torque.net/sg/.
Access the Linux kernel HOWTO at http://www.linuxhq.com/ldp/howto/Kernel-HOWTO.html. This document
describes how to compile your Linux kernel.
Note These links may
change without notice.
To apply the kernel patch:
a. Obtain your kernel source code as described in the Kernel HOWTO.
b. Apply the SCSI Generic source code to the kernel source as described under SG Device Driver downloads on the SCSI Generic site.
c. Compile the new patched kernel as described in the Kernel HOWTO.
d. Install the new kernel as described in the Kernel HOWTO.
NovaNET always scans for 26 SCSI devices. However, if you
have fewer SCSI devices, you can decrease its load time by decreasing the
number of SCSI devices it scans for.
Simply update the following line in the [configuration] section of the NNCfg.ini file:
maxScsiDevices=n
Reduce n to a lower number.
To properly manage IDE tape drives under Linux, NovaNET uses
the ide-scsi module to link the IDE device to a SCSI identifier. If the ide-cd
module is loaded, this command links the device from /dev/cdrom to /dev/scd0. As a result, you
may not be able to access the CD. To re-link the CD to /dev/cdrom, execute the
following command from the command prompt:
ln –sf /dev/scd0 /dev/cdrom
Note You only have to
execute this command once.
For NovaNET to respond correctly in
CRT, follow these steps:
a. Copy the mappings below and save them into a file called novanet.key
b. Select Session Options from the CRT’s Options menu.
c. Select the Emulation category.
d. Select vt100 for the terminal.
e. Check ANSI Color.
f. Select Custom for the keyboard and enter full path to novanet.key.
g. Select the Appearance category and use the vt100 font.
Make sure you export the variable TERM to xterm-color using the command:
export
TERM=xterm-color
If xterm-color is not available on your
system, use xterm, which only supports back and white.
You can also add export
TERM=xterm-color to the /etc/profile or ~/.bash_profile as a permanent
setting.
Key mappings placed in novanet.key:
N VK_INSERT "\e[2~"
N VK_F1 VT_PF1
N VK_F2 VT_PF2
N VK_F3 VT_PF3
N VK_F4 VT_PF4
N VK_F5 "\e[15~"
N VK_F6 "\e[17~"
N VK_F7 "\e[18~"
N VK_F8 "\e[19~"
N VK_F9 "\e[20~"
N VK_F10 "\e[21~"
E VK_INSERT "\e[2~"
S VK_F1 "\e[23~"
Notice
Information in this document is subject to change without notice. NovaStor Corporation makes no representations or warranties with respect to the contents of this document and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Further, NovaStor Corporation reserves the right to revise this publication and to make changes without obligation to notify any person or organization of such revisions or changes.
Copyright
Under copyright laws, the contents of this document may not be copied, photocopied, reproduced, translated or reduced to any electronic medium or machine-readable form, in whole or in part, without prior written consent of NovaStor Corporation.
Copyright © 1998-2003 NovaStor Corporation
www.NovaStor.com
Trademarks
NovaNET® is a registered trademark of NovaStor Corporation.
Microsoft®, Windows® and Windows NT® are registered trademarks of Microsoft Corporation. Novell® and NetWare® are registered trademarks of Novell, Inc. Linux® is a registered trademark of Linus Torvalds. Mandrake® is a registered trademark of MandrakeSoft S.A. SuSE® is a registered trademark of SuSE Linux. UNIX® is a registered trademark of The Open Group.
Netscape® is a registered trademark of Netscape Communications Corporation. Java™ is a trademark of Sun Microsystems, Inc. Adobe®, Acrobat® and Acrobat® Reader® are registered trademarks of Adobe Systems Incorporated. WinZip® is a registered trademark of WinZip Computing, Inc. OnStream™ and ADR™ are trademarks of OnStream Data b.v. Fusion-MPT™ is a trademark of LSI Logic Corporation.
Oracle® is a registered trademark of Oracle Corporation.
REV and Iomega are trademarks or
registered trademarks of Iomega Corporation in the
DLTIce™ is a trademark of Quantum Corporation. DLTSage is a product of Quantum Corporation.