Netbackup interview Questions

Questions set-1

1. If you have a SCSI attached robot and in device monitor you see the drives marked as AVR, what does that mean and how would you fix it?
2. If I asked you to tell me if a client has Netbackup on it just by using a telnet command what would you do?
3. If you wanted to know what IP address netbackup was using to perform backups what command would you run and where would you run it?
4. What is flash backup?
5. How is image stored in netbackup
6. If a media ID A04567 comes back and it is frozen, what are the steps to unfreeze it and move it back to scratch from the command line?
7. If you wanted to bypass netbackup commands and move a tape from slot 1 to drive 3 how would you do that?
8. What is the client version supported by NBU 6.x and 5.x masters
9. If your last catalog backup was two days ago and the master server crashed what would you have to do to bring your environment back up to present time?
10. How do you find a disk based image via the command line and then delete it?
11. How do you import an NBU image that has been written to a disk storage unit?
12. What are the critical catalogs or databases on a Media Server?
13. How would you tune NetBackup to increase backup performance?
In which location(path) the temp files located in Netbackup for Windows/Unix?
14.What is the process of importing images and why do we import images?
15.How to Importing and expiring images?
16.What does it mean by inventoring a robot?
17.What is SAN media server?
18. How to check tape is bad?
19. How to check the tape is already expired or not?
20. How to check volume pool?
21 Media has been already expired, How to find out?
22. How to check tape is in cap?
53. How to see log entries, how to create log directories?
24.SQL Script.. in to create?
25. How to install media server(with device configuration steps)?
26.what is avr mode

27. There is a Tape library with 10 drives …Can we able to create 2 Storage units…..?

28.There are 1000 Client machines , 999 machines are transferring datas in good speed but one client machine is taking too long to transfer a datas ….. That is …backup should complete within 2 hours ..but after 12 hours and more …the data transfer is still happening…. why?

Questions set 2

1. What is User Backup,User Archive & How to take?
2. Difference between 5.x, 6.x VNB
3 .In which location(path) the temp files located in Netbackup for Windows/Unix?
4. How do you configure a client for automatic backups?
5. What’s the difference between diff incr and cumulative incr? What happens when I mix them on Windows client… Unix client?
6. How is a changed file determined on Unix?
7. When would I, or would I not, use cross mount points?
8. What is the difference between a Volume Group and a Volume Pool?
9. How do you back up the catalog? Why is this important? What do you have todo if you don’t have a catalog backup?
10. How do you recover the catalog?
11. How do you configure retention levels for a backup?
12. If I install the Admin client on an NT workstation, what else has to be done for it to work… be an authorized server?
13. What is multiplexing? What is multiple data streams? Are they the same?
14 .how can I recover an corrupted image?
15. How can we assign barcode rules?
16. What is OTM? TIR?
17. What format does NetBackup write the tape in?
18. How does NetBackup tie together with Media Manager?
19. How do I create a Storage Unit that will only be used by one client?
20. What is the difference between the expiration date for a volume in NetBackup’s media catalog and Media Manager’s volume database?
22. What is the difference between a frozen volume and a suspended volume?
23. How many Robot Control Hosts can a DLT tape library have?
24. What does the bpbkar process do? bpsched? bpbrm? bpdbm? ltid? What process controls a DLT tape library… a DLT tape drive? What is the AVRD process?
25. Why is the catalog the most important component of Netbackup?
26. What does status 59 mean in the activity monitor?
27. Installation process for NBU 5.x, 6.x?
28. what is AVR mode?
29. Why is a binary catalog more efficient than an ASCII catalog?
30. What are NBU daemons and how to process

10 Free Server & Network Monitoring Tools

1. Monit


Monit not only monitors your server, but also attempts to remedy problems by taking predefined actions for certain situations. For example, if your database server crashes, Monit can automatically restart the service if this is the action that you want to take (hint: it usually is).

If you have more than one server that you need to monitor, then you can use M/Monit– an extended version of Monit that provides a simple way to monitor multiple machines.

There’s also an iPhone app available for M/Monit to help you conveniently check on your network without lugging around a laptop around.

2. Ganglia


When you have a cluster of machines, it’s difficult to see how the whole cluster is doing all at once. Ganglia, instead, presents an overview of the whole cluster. This is a great tool to have set up when you’re working with a server cluster; with that said, it may be overkill for single-machine set-ups.

3. Munin


Munin monitors and graphs system performance metrics. It can automatically produce daily/weekly/monthly/yearly performance graphs and reports of many important metrics. It comes with the ability to monitor core system resources, such as memory, disk space, CPU usage, server applications such as MySQL, Apache, and Squid.

One of Munin’s greatest strengths is how simple it is to extend. With just a few lines of code, you can write a plugin to monitor almost anything. Being so easy to extend means that Munin is also a good choice for graphing things unrelated to server performance, such as the number of user signups or website popularity.

4. Cacti


Cacti is similar to Munin in many ways. What is makes Cacti different though–and where it stands out in relation to Munin–is that it allows you to resize your graphs and view data for an arbitrary range. Whereas Munin has fixed daily, weekly, monthly and yearly graphs (unless you write a custom extension), Cacti lets you view your data however you want to: last 2 hours, last 4 days, last 6 months, out of the box. You can even visually select and zoom into regions on your graphs.

5. Nagios


Nagios is “the industry standard in IT infrastructure monitoring,”–well, at least that’s what it says on their website. Nagios can be complicated to install and configure, but its wealth of features are unmatched by any tool out in the market and is geared for the experienced IT network administrator. Nagios supports monitoring of multiple hosts and can send out alerts via email, pager (if you still use this ancient technology) or SMS/text messaging. Like Monit, it can also be configured to automatically respond to problems.

6. Zabbix


Zabbix is a feature-packed monitoring tool. It has great visualization support including user-defined views, zooming, and mapping. It can send out alerts via email, SMS or instant message. It also provides audible alerts, which can be useful when you’re physically near the monitoring machine.

7. Observium


Observium is geared towards Linux, BSD and Cisco networks. It supports auto discovery of your network infrastructure, finding the networks that you’re likely interested in monitoring; this feature can be compared to how your Wi-Fi software automatically finds signals in range that you can jack into. Observium provides detailed graphs, and can be set up alongside Nagios to provide alerts. It also integrates well with Collectd (featured below) for a more robust interface.

8. Zenoss


Zenoss is an open source version of the commercial server monitoring tool Zenoss Enterprise, written entirely in Python. It supports the Nagios plugin format, so many existing Nagios plugins can be used in Zenoss. One of the main highlights of Zenoss is its powerful yet simple to use user interface.

9. Collectd


Collectd is similar to Munin and Cacti in that it focuses on graphing system metrics. Where it excels in is that it is designed specifically for performance and portability; this ultimately means it’s great on rugged systems, low-end systems, and embedded systems. Being designed for performance and low-system resource use means that Collectd can gather data every 10 seconds without interfering with your server processes, providing extremely high-resolution statistics. You can write extensions for it in C, Perl or Java.

10. Argus


Argus focuses on the monitoring of network services, and supports IPv4 and IPv6. It has a nice alert escalation procedure: after sending out an alert and the problem still isn’t resolved within a fixed amount of time (because the systems admin is at home enjoying his sleep), another alert will be sent out to someone else.

%d bloggers like this: