Backup Central

Hi,

In upgrading our Networker from v6.1.3 to v7.1.3, I was reminded by way
of the feature not being available that a Windows NT 4 server (yes I
know its old) cannot be a storage node, only a client.

We have one such Windows NT 4 server which is running Exchange 5.5, and
is a storage node (currently it only backs up data from itself).

While it will be replaced by the end of 2005 with Windows 2003 and
Exchange 2003, we are not quite there yet. But we can wait no longer to
upgrade to Networker v7.x.

Is it possible to keep the NT 4 server running Networker 6.1.4 (which
would allow the NT 4 server to be a storage node) and have the Networker
server be v7.1.3? Will this introduce problems with restores, the on-
line indexes, the media database, etc?

I know that from a functional standpoint from my testing that at least
backups will work okay. I haven't tried a recover though.

The only other option we currently have is to backup this client over a
T1 during off-hours to another storage node located in the same
city/country.

--
Craig Ruefenacht
UNIX Systems Administrator
USANA Health Sciences
http://www.usana.com

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Craig Ruefenacht wrote:
Hi,

In upgrading our Networker from v6.1.3 to v7.1.3, I was reminded by way
of the feature not being available that a Windows NT 4 server (yes I
know its old) cannot be a storage node, only a client.

We have one such Windows NT 4 server which is running Exchange 5.5, and
is a storage node (currently it only backs up data from itself).

While it will be replaced by the end of 2005 with Windows 2003 and
Exchange 2003, we are not quite there yet. But we can wait no longer to
upgrade to Networker v7.x.

Is it possible to keep the NT 4 server running Networker 6.1.4 (which
would allow the NT 4 server to be a storage node) and have the Networker
server be v7.1.3? Will this introduce problems with restores, the on-
line indexes, the media database, etc?


This should work, and should be a supported configuration, other than
the fact that 6.1.x is now officially out of support.

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Thanks to those who replied either to me personally or to the list about
this topic.

A few have verified that a Networker 6.1.x client will work with a
Networker 7.1.x server and there shouldn't be any issues. As for the
storage node question, I found a one-line note in the release supplement
for Networker 7.1.3 that says that a Networker server release 7.1.x
supports release 6.x storage nodes.

Another interesting note on the same page in the documentation says that
a Networker 7.1.x storage node is not compatible with a Networker server
earlier than v6.0, so it appears that you can have a v7.x storage node
and a v6.x server and be okay as well.

On Wed, 2005-03-09 at 11:10 -0700, Craig Ruefenacht wrote:
Hi,

In upgrading our Networker from v6.1.3 to v7.1.3, I was reminded by way
of the feature not being available that a Windows NT 4 server (yes I
know its old) cannot be a storage node, only a client.

We have one such Windows NT 4 server which is running Exchange 5.5, and
is a storage node (currently it only backs up data from itself).

While it will be replaced by the end of 2005 with Windows 2003 and
Exchange 2003, we are not quite there yet. But we can wait no longer to
upgrade to Networker v7.x.

Is it possible to keep the NT 4 server running Networker 6.1.4 (which
would allow the NT 4 server to be a storage node) and have the Networker
server be v7.1.3? Will this introduce problems with restores, the on-
line indexes, the media database, etc?

I know that from a functional standpoint from my testing that at least
backups will work okay. I haven't tried a recover though.

The only other option we currently have is to backup this client over a
T1 during off-hours to another storage node located in the same
city/country.

--
Craig Ruefenacht
UNIX Systems Administrator
USANA Health Sciences
http://www.usana.com

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu