NovaNet-Web 6.8.17.0 has been released

NovaNet-WEB v6.8.17
Maintenance Release (v6.8.17.0)
May 16, 2007

This is NOT unsolicited e-mail. You can add/remove yourself as a member of our List at any time.

***CAUTION STATEMENT***
IMPORTANT NOTE - PLEASE READ!

Upgrading your server: NovaNet-WEB v6.8 will successfully upgrade a v5.x and v6.x NovaNet-WEB Server. If you are running v4.x of NovaNet-WEB Server, you cannot perform a direct upgrade. You will be required to upgrade the server to v5.x first, and then perform another upgrade to v6.x
Clients running v5.x or v6.x of NovaNet-WEB Client can connect to a v6.8 NovaNet-WEB Server and successfully upgrade.
If you upgrade to v6.8 of NovaNet-WEB Server/Client you cannot roll back the server or client to a previous 5.X version of the software.
Clients running v6.8 cannot connect to lower server versions.

Instructions on installing/upgrading your current NovaNet-WEB

In order to install or upgrade your backup server to v6.8, you MUST already have MSDE/SQL 2000/SQL 2005 installed on an available network or local system. For testing purposes, you may use Microsoft SQL 2005 Express available from the following link: http://www.microsoft.com/downloads/details.aspx?FamilyID=220549b5-0b07-4448-8848-dcc397514b41&DisplayLang=en (NOTE: If you are using SQL 2005 Express, you must enter .\SQLEXPRESS as the server name when installing the NovaNet-WEB Backup Server software)
This release includes support for Open File Backup using Microsoft's Volume Shadow Copy Service (VSS). However, In order to utilize Open File Backup, the NovaNet-Web Client must be run on either Windows XP or 2003.

Note: Open File Backup option requires at least one NTFS drive to operate and Logged-in User must have Administrative rights.

You may download the software from the following link:

NovaNet-WEB v6.8.17.0
Client: http://www.novastor.com/pub/demos/NOVANETWEB/Version68/6.8.17.0/NovaNet-WEBBackupClient.exe
Server: http://www.novastor.com/pub/demos/NOVANETWEB/Version68/6.8.17.0/NovaNet-WEBBackupServer.exe

Release Notes - What's New/Fixed/Known Issues

Please note that installing v6.8 on top of your existing installation will also install a client upgrade. Any client connecting to your backup server will automatically (unless you have disabled that option) be upgraded to a v6.8 Client level.

New Features:
====================

Fixes/Updates in NovaNet-WEB (Client/Server) Version 6.8.17.0
====================

- server: restarting the backup server service clears the masterlog.txt file.
- server: work directory set to use the account data directory as the work directory does not save/work.
- server: after a restore/rollup the work directory is not being deleted

- client: if a disconnect happens when a file is being prepared for fastbit the fastbit cache can be deleted.
- client: specific case of fastbit hard closing/hanging the application.
- client: possibility to corrupt the secret key on the server during an uninstall/reinstall of the client software making data unrestorable.

Errata-Known Issues:
====================

Client Issues:

The Backup Client scheduler service installation option has been removed from Windows NT4 due to NTLM authentication errors.
The client installer will no longer provide an option to install the client scheduler as a Windows NT4 service. During a Windows NT4 scheduled backup, the client fails to acquire the correct authentication token to validate against the server.

Other Important Items

New options in (v6.8)

-BackupClient.ini
The BackupClient.ini will be installed in the full install and during a patched upgrade. This file replaces the reg hack for the debugging and gives more flexibility. The debugging in this version of the software has also been enhanced by the engineers.

a) The zDiag.txt and possible zvdb.txt This PREVIOUSLY was enabled by setting a reg value "DiagnosticLevel" to a value, typically 2. The reg setting will now have NO EFFECT.
The benefit is basically vdb/file selection diags.

b) The newer 'TraceLog.txt'.
Never implemented via registry setting (brand new feature).
It's purpose is to peek at client guts...
Level 1 is mostly a copy of the standard client logs.
Level 2 is a trace of all kinds of client lines, mostly having to do with SendPDU lines.

All that's a background and fyi.
The important thing to know is how NOW to enable it if desired.
So we now use BackupClient.ini which by default looks like:

[Configuration]
#
# comments pending
#
DiagnosticLevel = 0
#
# comments pending
#
TraceLevel = 0

#
# comments pending
#

TraceTimed = 0
#
# comments pending
#
SkipResend = 0

========================================
To turn on the zDiag stuff, use DiagnosticLevel = n like you would if set in the registry.

Use Tracelevel to enable creation of TraceLog.txt Use TraceTimed if you want time stamping in TraceLog.txt

Here's an example of a full blown diagnostic enabled setup:
============================================================
[Configuration]
#
# comments pending
#
DiagnosticLevel = 2

#
# comments pending
#
TraceLevel = 2

#
# comments pending
#
TraceTimed = 1

#
# comments pending
#
SkipResend = 0

-New BackupServer.ini Options

Load Balance Support=1
1 turns it on, 0 turns it off. This option signals that this server is part of a load balanced server cluster. Auto configured during the install/upgrade of the servers

Interlock File Directory=\\storage01\interlock
This directory is needed when Load Balance Support=1. This needs to be a shared directory between all of the server cluster. This directory contains 'lock' files for the servers so that there is no potential of a user backing up on 2 servers at the same time. This option is auto configured during the install/upgrade of the servers.

Defrag Limit=7 (default which is not listed in the backupserver.ini)
When a rollup occurs, the versions rolled out get marked for deletion within the structure storage file. The deletions get processed when the delete count reaches the defrag limit which is set to 7 by default. The ini value that can change this limit." Defrag Limit" under "Configuration" can be set to 1 to immediate results.

So say a user is backing up one single file a day with a restore window of 1 day.

first day - one version stored
second day - one version stored; 1 stream version marked for deletion
third day - one version stored; 2 stream versions marked for deletion
fourth day - one version stored; 3 stream versions marked for deletion
..
..
8th day - one version stored; 7 streams marked for deletion --> defrag kicks in and all streams marked for deletion are removed; storage file is therefore reduced in size. Streams stored file version data (patches or full). Versions that are marked for deletion cannot be recovered.

NovaStor Products
http://www.novastor.com/products.html

Special Deals
http://www.novastor.com/nova_store/specials2.asp

How To Provide Us With Feedback

Best Regards,

NovaStor QA Team

NovaStor
80-B West Cochran Street
Simi Valley, CA 93065
PH: 805.579.6700
FX: 805.579.6510
QAteam@novastor.com

Notice
Information in this document is subject to change without notice. NovaStor 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 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.

Copyright © 2007 NovaStor
www.novastor.com

Trademarks
NovaNet-WEB® & FastBIT® are a registered trademarks of NovaStor
Windows® is a registered trademark of Microsoft Corporation.