I have found it helpfull to report all incomplete backups older than say
8 hours to me by mail
as well as any incomplete clones.
that way I can have some idea what is failing and correlate that with
messages that may or may not have been generated in the log files.
listing the incomplete backups is easy:
mminfo -av -q'incomplete'
listing any incomplete clones is not posstible without scripting as
there is no incomplete flag for clones at all. a grep in the i character
of a certain field is the only way to go.
we have by now gone over from 5.5.2 to 6.1.1 since then we see less bad
file numbers, they used to interfere mainly with cloning though.
I also delete any incomplete backup automatically if it is older than
say 1 or 2 days. they are not retrievalbe anyway.
Maarten
Nicole Skyrca wrote:
>
> Hello,
> I'm running Solstice Backup 5.5.3 on Solaris 7. I have some Solaris
> clients that say they have successful backups, but within the
> email, I see some "bad file number" and "aborted due to inactiviy"
> messages. This doesn't happen with every backup.
>
> Here is an example of the output:
> Solstice Backup Savegroup: (notice) daytime_atc completed, 2 client(s) (All
> Succeeded)
> Start time: Sat Oct 12 17:10:00 2002
> End time: Sat Oct 12 18:49:49 2002
>
> - --- Successful Save Sets ---
>
> jason-web1: / level=full, 799 MB 00:16:00 42089 files
> * jason-web1:/ 10/12/02 18:32:38 nsrexec: Attempting a kill on remote save
> * jason-web1:/ write: Bad file number
> * jason-web1:/ aborted due to inactivity
> jason-web1: /var level=full, 63 MB 00:03:29 3558 files
> jason-web1: /clients level=full, 3373 MB 00:35:21 100733 files
> * jason-web1:/clients 10/12/02 18:47:39 nsrexec: Attempting a kill on remote
> save
> * jason-web1:/clients write: Bad file number
> * jason-web1:/clients aborted due to inactivity
> jason-web1: /usr/local level=full, 548 MB 00:11:26 10615 files
> * jason-web1:/usr/local 10/12/02 18:27:38 nsrexec: Attempting a kill on
> remote save
> * jason-web1:/usr/local write: Bad file number
> * jason-web1:/usr/local aborted due to inactivity
> mack: /nsr/index/jason-web1 level=full, 208 MB 00:02:10 5 files
>
> Has anyone seen this before? Do you know if my backups are still good?
> Why does the backup report as successful? How do I fix this?
>
> The machines that I'm seeing this problem are behind a firewall.
> The neccessary ports on the firewall are open (Since I do get a "good"
> backup sometimes). I've tried increasing the inactivity timeout of the
> groups. That helps for level1 backups on some of the machines, but
> not for others.
>
> Thanks!
>
> Nicole Skyrca
> ClearBlue Technologies Phone: 315-453-2912 x5861
> 125 Elwood Davis Road Fax: 315-453-4594
> Syracuse, New York 13212
>
> ------- End of Forwarded Message
>
> --
> Note: To sign off this list, send a "signoff" 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.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Maarten.Boot _at_ nl.compuware.com
One of the problems with Java is that they swept a bit too much
of the innate complexity of life under the carpet of the libraries.
And so now they've had to replace the carpets several times.
(Larry
Wall,http://interviews.slashdot.org/article.pl?sid=02/09/06/1343222)
--
Note: To sign off this list, send a "signoff" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
