Search results for query: *

I have seen this before too. Most often the scheduler was hung up on something. We have seen this for example when several hundred jobs are queued and clients are shutdown for maintenance without the jobs being canceled first. If they are then selected and canceled the scheduler must time out on...

Has anyone developed any scripts or other "anything" that can get a better insight into the space currently allocated on a disk staging storage unit? 1) I would like to know how many images have been migrated to tape. 2) I would like to know how many total images are on it. 3) Of the images...

Interesting. I would think a setting with a short interval would overload the scheduler. How many clients do you have?

Or you could get the vault option.

Anyone?

Hmmm.. I found this for the UNIX environments. It may be usefull. It explains in depth how the scheduler works and what could cause it to hang. http://support.veritas.com/docs/274559

I am curious to see what other people have this set to. The help file seems to suggest it is better to have a smaller try number in there.

What is the best setting for "CLIENT_CONNECT_TIMEOUT" ?

The software includes the extra 1k so adding it is no longer necessary.

I am having the exact same issue in on a Windows 2003 master server with NetBckup 5.1 MP3. bpsched process goes to 100% utilization and no new jobs will run. Jobs complete but stay in the active state. I have seen this issue since 4.5FP6.

yep, the scheduler needs to pick up the new storage unit. You could try this: ...\Program Files\VERITAS\NetBackup\bin\admincmd\bpschedreq.exe -read_stu_config It will re-read the storage units and should pick up the new storage unit without stoping and restarting.

Also, If you use inline tape copy you will not see a graph for the second and subsequent copies.

I would like to start archiving everything over 1 year. If anyone is doing this please let us know how things are going.

I have used it but do not do so any longer because of multiple issues. - The clients at risk report is a joke. The report will show a client at risk if any client in that same policy has a failure. I called Veritas and asked about it and they said that yes it is by design. - Our catalog is...

Okay, I broke down and contacted support on this issue. Here is what they said... ----(paste from email)---- 1) Although many customers have reported success launching NetBackup CLI, VERITAS does not officially support the use of sudo with NetBackup product. In NetBackup installation guides...

I don't know if this is much help but we use in-line tape copy and it seems to work fine. We like the fact that the backup continues even if one copy fails. I don't know what your environment is but if you are using any flavor of UNIX then you really need to use TIR. If you do not use TIR w/...

We use sudo for root access. This is done so user activity can be logged. The AIX client installs have been performed using a standard user to login with but then using sudo to get root permissions. Is this an acceptable thing to do? What account does NetBackup run under? Does it have to be...

We did this recently and things went smoothly. We were running AIX 5.2 and NB 4.5FP6. We are now at 5.1MP1.

We are receiving the error below when trying to to a synthetic backup using NetBackup 5.1. The policy has 3 schedules in it, full, diff-inc, and synth-full. I run the full manual backup and it completes with no errors. I then run a diff-inc manual backup and it completes with no errors. I then...

I have servers in a test environment and need them to be restored from production servers. The test environment has it's own network and cannot be connected to the production environment. In the past I have used a backupexec server to backup the production machine and switch the network to the...