Randy Manchester wrote:

I have a client that was running Linux and backing up sucessfully for
several months. Two weeks ago the owner wiped the system disk and
installed WinXP and the Win32_x86 client (version 7.0)

Now that's a downgrade in my book. ;-)

Watching nwadmin, her system seems to back up, I see several hundred MB
backed up for SYSTEM FILES and C drive, but I keep getting failure
notices.

It would probably help if you let us know what messages these are.

I've tried deleting the client and re-adding it (I noticed it used the
same client-id after adding it back in).

I suppose this is something that NetWorker doesn't expect. The media
database knows about this client and the fact that it is a Linux client.
It probably doesn't expect it suddenly to become a Wintel box. I assume
the machine has the same name? I think in this case you don't want it to
 keep the same client ID. The reason for keeping the client ID is so
that you can recover old data, but in this case it won't be possible
since the client now has an OS that's incompatible with the old data.

I think you have two options to fix this.
(1) Rename the new client and define a new client resource for it. It
should get a new client ID.
(2) Rename the old client in the media database taking care to preserve
the old client ID as per TB138, then redefine the new client with the
original name. It should get a new client ID.

Any way to get more verbose error messages? All I see is that it failed
and retried once. No explanation of what caused the failure.

Use an increased verbosity on save/savegrp. You can use one or more v
options, e.g. -vvv.

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=