Video Screencast Help

details on media server and clients

Created: 29 Jun 2012 • Updated: 02 Jul 2012 | 14 comments
This issue has been solved. See solution.

What this details means?why only these values?what backupstart notify time and backup end notify does on media server?

 

 

Media Server

 

client connect time out 3000 sec

client read time out  3000 sec

backupstart notify time out  3000 sec

backup end notify time out 3000 sec

media server connect time out  30 sec

File browse time out 300 sec

 

Client:

client read time out   300 sec

File browse time out  300 sec

Comments 14 CommentsJump to latest comment

sazz.'s picture

It is more or less the same irrespective of how many times you ask it won't change.. Repetitive post :

http://www.symantec.com/connect/forums/client-read-timeout-and-client-connect-timeout-can-go-masters-or-medias-they-go-anything-will

 

Also administrator guide volume 1 go to Timeouts properties and it explains it all.

mph999's picture

3000 is too high for client connect/ read timeout, unless it has been changed for a specific reason - even then, I would say if a cleint needs this much time, there 'might' be some issue that  needs adressing.

Settings in NBU should not be changed just because they can, each change should be really be recorded as to when and whyit was made in the system documentation.

Martin

 

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
NIKHIL2346565959's picture

client connect time out 3000 sec   on media server means?

Marianne's picture

I wish I could understand why you keep on asking the same questions?

Or are you doing this for the sake of the 1 point you get for each post and comment?

PLEASE go check this link:

https://www-secure.symantec.com/connect/forums/cli...

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

NIKHIL2346565959's picture

Client:

client read time out   300 sec

File browse time out  300 sec

 

@Martin:What is the use of these two attributes on client?

Andy Welburn's picture

Have you seen this:

https://www-secure.symantec.com/connect/forums/cli...

& *especially* the solution on this one:

https://www-secure.symantec.com/connect/forums/cli...

.....oh, hang on a minute, that name looks remarkably familiar.....

 

NIKHIL2346565959's picture

Martin told me that on client this settings is not valid

Then why this exist on client?

Andy Welburn's picture

(a suggested read by sazz in the first response)

Specifies the number of seconds to use for the client-read timeout. This timeout can
apply to a NetBackup master, remote media server, or database-extension client (such
as NetBackup for Oracle). The default is 300 seconds.
The client-read timeout on a database-extension client is a special case. Clients can
initially require more time to get ready than other clients. More time is required
because database backup utilities frequently start several backup jobs at the same
time, slowing the central processing unit.

Note: For database-extension clients, Symantec suggests that the Client read timeout
be set to a value greater than 5 minutes. 15 minutes are adequate for many
installations. For other clients, change this property only if the client encounters
problems.
The sequence on a database-extension client is as follows:
NetBackup on the database-extension client reads the client’s client-read timeout
to find the initial value.
If the option is not set, the standard 5-minute default is
used.
■ When the database-extension API receives the server’s value, it uses it as the
client-read timeout.

Hope that helps.

mph999's picture

 

Hi NIkhail,
 
Hmm ...  looks like I might have been wrong ...
 
Specifies the number of seconds to use for the client-read timeout. This timeout can
apply to a NetBackup master, remote media server, or database-extension client (such
as NetBackup for Oracle). The default is 300 seconds.
The client-read timeout on a database-extension client is a special case. Clients can
initially require more time to get ready than other clients. More time is required
because database backup utilities frequently start several backup jobs at the same
time, slowing the central processing unit.
 
" or database-extension client (such as NetBackup for Oracle). "
 
Looks like in this case it is valid on a client - if it's running Oracle.
 
However, if you are not running Oracle on the client - I think 3000 seconds is very high and should be investigated.
 
If you are running Oracle, then 3000 may be an acceptable value - as you may have now noticed, DB backups is not an area I deal with (we have dedicated DB specialists, I'm not one of them).
 
Martin
 
 
 
 
 
 
 
 
 

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Marianne's picture

"From the Admin Guide section on "Timeouts"
(a suggested read by sazz in the first response)"

83 posts in 21 weeks...
In MOST of these posts we have recommended that you download the manuals and start reading.
Still, in most of your posts, your questions are answered with copy & paste from the manuals.....

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

NIKHIL2346565959's picture

@Martin:These are not for oracle.Just for normal OS backup.Why they are there then?

NIKHIL2346565959's picture

Client:

client read time out   300 sec

File browse time out  300 sec

 

Why this on client?

mph999's picture

OK, if Oracle is not used, then I had a lucky escape .... 

I do not know why they are on the client.  I suspect someone has added them without understanding that they are not needed.

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Marianne's picture

These timeout setting exist by default on all servers and clients when you look at Host Properties in the GUI.

They should simply be left alone unless database agents are used and evidence of client-intiated comms issues are seen.

The moment you go into Host Properties -> Clients -> Client-Name -> Timeouts, you will see two default settings. If you click OK or Apply (instead of Cancel), these settings are written to Client's bp.conf file.

As Martin (and all of us) have set previously - leave Host Properties ALONE if you are not experiencing a SPECIFIC issue that needs settings to be changed.

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION