Hi All
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..
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??
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.. And when i check the error log, most of the
access denial e and share violation errors are coming from
windows systems files which in my opinion does not need
backup.
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???
Is there a list of recomanded windows folders to exclude
in order to get a successful full backup?? I am getting
too many access denial and share violation error that they
are making me paranoid abt my backups.. =)
---------------------------------
Real people. Real questions. Real answers. Share what you know.-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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/
