Hi,
Hwee Yiap wrote on 12.11.2007 at 13:18:06 [[BackupPC-users]
NT_STATUS_BAD_NETWORK_NAME]:
>
> I got a question regarding the NT_STATUS_BAD_NETWORK_NAME.
> I have read the archives and understand that as long as
> backuppc cannot connect to a share, it will label the
> error as bad network name..
well, that's what the error means: the network share you specified does not
exist. In untrusted networking environments (i.e. if you need authentication
in the first place), it is generally not advisable to say "well, the account
information was correct, keep trying other passwords and you will eventually
succeed" ;-).
> I have currectly set up backuppc running, using the
> generic config.pl with slight change to backup the C and D Drive
> of a few windows client. But not all clients has D drive, so is
> the NT_STATUS_BAD_NETWORK_NAME due to this??
Yes.
> As backuppc finish running, i will get a backup fail
> NT_STATUS_BAD_NETWORK_NAME error but with a partial
> backup in place.. When i check the partial backup, i found
> that everything that i find important is already
> backup-ed..
BackupPC can't decide that for you. If you tell it to backup a share D$ on
a host "foobar", and either the host or the share does not exist, should
BackupPC assume that you, naturally, were just kidding, so it's ok it
didn't work out? It's a configuration error, either in the BackupPC
configuration or on the target host (or the network). BackupPC could not
successfully back up what you asked it to. Without the missing information,
the whole backup may be worthless (consider backing up only the index files
but not the data of a database).
You want to use individual config files either for the clients that have a D
drive or those that do not. You don't need to override (i.e. set) anything
except $Conf {SmbShareName} if all other settings are identical.
> My questions are, when everytime backuppc encounter such
> a situation, it will skip the file and continue to go thu
> the rest of the hdd for files it can backup right?? then
> failed the backup with a partial backup status when in
> fact most of the user's files are backup-ed already???
I believe that depends on the severity of the errors. Again, BackupPC has no
way of determining how much it could *not* backup or how important those
files would have been to you. Is this unreadable D drive empty temp space,
or does it contain your most treasured photo album? Even a human cannot
guess alone from the fact that it was unreadable.
> Is there a list of recomanded windows folders to exclude
> in order to get a successful full backup??
I don't use Windoze, so I don't know. There have been suggestions on the
list previously.
Hope that helps.
Regards,
Holger
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
