[Veritas-bu] Excessive Windows incrementals (Robert Griffin)

Rob,
May be try just making a copy of the policy and manually starting the
new policy after waiting like 20 to 30 minutes.

-Karim 

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of
veritas-bu-request AT mailman.eng.auburn DOT edu
Sent: Tuesday, November 20, 2007 1:00 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Veritas-bu Digest, Vol 19, Issue 39

Send Veritas-bu mailing list submissions to
        veritas-bu AT mailman.eng.auburn DOT edu

To subscribe or unsubscribe via the World Wide Web, visit
        http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
or, via email, send a message with subject or body 'help' to
        veritas-bu-request AT mailman.eng.auburn DOT edu

You can reach the person managing the list at
        veritas-bu-owner AT mailman.eng.auburn DOT edu

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Veritas-bu digest..."


Today's Topics:

   1. Excessive Windows incrementals (Robert Griffin)
   2. Re: T2000 vaulting performance with VTL/LTO3 (Marianu, Jonathan)


----------------------------------------------------------------------

Message: 1
Date: Tue, 20 Nov 2007 11:04:30 -0600
From: Robert Griffin <rmg AT ua DOT edu>
Subject: [Veritas-bu] Excessive Windows incrementals
To: veritas-bu AT mailman.eng.auburn DOT edu
Message-ID: <ED97F619-EA9B-451E-9895-0A0091804D72 AT ua DOT edu>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

I recently added a Windows client to a stable Solaris NetBackup
installation. During the window for nightly incrementals, it's
performing the incrementals over and over, unlike all the other clients,
and I'm wondering how to get it not to do that.

Master: 6.0MP4 / Solaris 10 / SL500 with LTO3 drives Most clients are
6.0MP4 / Solaris 9 or 10.
Problem client: 6.0MP4 / Windows XP
Problem client is also listed as a "SERVER" in everyone's bp.conf so it
can run the admin console.

At first, a full backup was unable to complete in reasonable time, while
the client ground to a halt, so I had to disable open-file backups /
VSP.

Backup selection on the policy is ALL_LOCAL_DRIVES, but the exclude list
contains "*" and a couple of directories are in the include list
(C:\Documents and Settings and D:\something). The idea being that other
clients added to the policy in future could have different areas they
need backed up. No files are ever backed up from System_State:\ because
of the exclude list, but including part of it didn't change the behavior
either.

The schedule is frequency-based, every "1 days", with
1 month retention. Another schedule in the same policy does weekly full
backups. Have tried all combinations of Differential & Cumulative,
date-based & archive-bit-based, all producing repetitive incrementals
about every 14 minutes during the nightly start windows. Incrementals
usually finish in about 4 minutes, so I can only assume the master's
10-minute job retry delay is being added onto that. The master also has
"Schedule backup attempts" set to 2 tries per 12 hours. Have restarted
NBU on the master, no change.

Usually the job status on the parent job and all three streams (C:\,
D:\, and System_State:\) is status 0. Occasionally C:\ produces status 1
due to a Firefox lock file, etc.
There is also usually a warning on the C:\ backup, even when it returns
status 0:

   11/20/07 00:02:29 - Warning bpbrm(pid=21835) from client
PROBLEM_CLIENT: WRN - Removable Storage Management: unable to export
database (WIN32 21: The device is not ready. )

Could this warning be related to the repeated incrementals? I think we
can try disabling Removable Storage but don't know if that will break
anything else. The client has no direct access to tape drives but may
have a zip drive and legacy backups that need to work, independent of
NBU.

Other ideas appreciated.

Robert Griffin
Unix Systems Administrator
OIT, Enterprise Technology
The University of Alabama
<rmg AT ua DOT edu> | 205-348-0177




------------------------------

Message: 2
Date: Tue, 20 Nov 2007 09:59:06 -0800
From: "Marianu, Jonathan" <JM7640 AT att DOT com>
Subject: Re: [Veritas-bu] T2000 vaulting performance with VTL/LTO3
To: <VERITAS-BU AT mailman.eng.auburn DOT edu>
Message-ID:
        
<A2F0E7B061E9A7438D37094F213F9519039FCE88 AT BD01MSXMB017.US.Cingular DOT Net>
        
Content-Type: text/plain; charset="us-ascii"

The MPX setting of the original backup can greatly influence the speed
of your duplications.

I'm not *telling* you to use a high mpx but it is something to consider
testing.

 

It is very interesting to open up two ssh sessions, put them side by
side and run a truss on both the reading and writing bptm processes of
the media server while a duplication is running and then rotate your
screen 90 degrees to the right.



That illustrates the effect MPX has much better than I could describe in
words.

 

 


__________________________________________
Jonathan Marianu (mah ree ah' nu)
AT&T Storage Planning and Design Architect
(360) 597-6896
Work Hours 0800-1800 PST M-F

Manager: David Anderson
(314) 340-9296 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20071120/
7d3be3a4/attachment-0001.html

------------------------------

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


End of Veritas-bu Digest, Vol 19, Issue 39
******************************************

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu