Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Veritas Exam VCS-278 Topic 8 Question 90 Discussion

Actual exam question for Veritas's VCS-278 exam
Question #: 90
Topic #: 8
[All VCS-278 Questions]

A NetBackup master server has many backups running each night to an MSDP pool that take a long time to complete. While these backups are running, replication jobs are queued.

Which action should the administrator perform to ensure replications can occur without waiting for the backups to complete?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Fausto
5 months ago
Option B seems like the most straightforward solution. Increase the max concurrent jobs on the storage server and let those backups and replications play nice together.
upvoted 0 times
Barbra
3 months ago
I've had a similar issue before, and increasing the max concurrent jobs really made a difference in the overall performance.
upvoted 0 times
...
Matthew
3 months ago
I agree, that should help with the queue of replication jobs waiting for the backups to complete.
upvoted 0 times
...
Otis
3 months ago
Option B seems like the most straightforward solution. Increase the max concurrent jobs on the storage server and let those backups and replications play nice together.
upvoted 0 times
...
Princess
3 months ago
I think increasing the maximum concurrent jobs in the storage server properties is the way to go. It will definitely help with the queue for replication jobs.
upvoted 0 times
...
Ocie
3 months ago
I agree, that should help prioritize the replication jobs without waiting for the backups to complete.
upvoted 0 times
...
Jeanice
4 months ago
Option B seems like the most straightforward solution. Increase the max concurrent jobs on the storage server and let those backups and replications play nice together.
upvoted 0 times
...
...
Fairy
5 months ago
I believe increasing the 'Maximum I/O Streams' for the disk pool could also help in ensuring replications can occur smoothly.
upvoted 0 times
...
Shaunna
5 months ago
Haha, gotta love those backup bottlenecks! I'd say C is the way to go - crank up those disk storage unit jobs and let those replications fly!
upvoted 0 times
...
Annmarie
5 months ago
Hmm, I'm not sure. Maybe increasing the priority for secondary operations in the SLP would be the way to go? That's my guess.
upvoted 0 times
...
Colette
5 months ago
I'd go with D. Increasing the max I/O streams for the disk pool seems like the best way to handle this bottleneck.
upvoted 0 times
Kris
4 months ago
Agreed, that should help with the bottleneck.
upvoted 0 times
...
Karol
4 months ago
I think increasing the max I/O streams for the disk pool is the way to go.
upvoted 0 times
...
...
Nidia
5 months ago
I agree with Dierdre, increasing the 'Maximum concurrent jobs' would allow replications to occur without waiting for backups to complete.
upvoted 0 times
...
Dierdre
5 months ago
I think the administrator should increase the 'Maximum concurrent jobs' in the storage server properties.
upvoted 0 times
...
Hubert
5 months ago
Option B looks good to me. Increasing the max concurrent jobs on the storage server should let the replication jobs run without waiting for the backups.
upvoted 0 times
Isadora
4 months ago
Let's go ahead and make that change then. It should improve the overall efficiency of our backups and replications.
upvoted 0 times
...
Cyndy
4 months ago
Agreed, increasing the max concurrent jobs will prevent the replication jobs from waiting for the backups to complete.
upvoted 0 times
...
Theola
4 months ago
That sounds like a good idea. It should help the replication jobs run smoothly.
upvoted 0 times
...
Roosevelt
4 months ago
I think we should increase the 'Maximum concurrent jobs' in the storage server properties.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77