Skip to main content

Inventory and Catalog in Backup Exec

What is an Inventory?
An Inventory is the process of mounting media in the drive and reading the media label, which is then displayed in the Devices view. If this is the first time that Backup Exec ™ has encountered this media, the media label is also added to the Media view.
Note: Each time new tape is introduced in the tape drive or robotic library, it must be inventoried so that the Backup Exec database gets updated with the new tape Information.
To Inventory a Tape/Robotic Library:
1. Insert the tape
2. Click the Devices tab
3. Select the correct tape drive/robotic library slot
4. Right-click on the tape drive/robotic library slot and select Inventory (Figure 1)
Figure 1

The inventory will complete and should display the correct tape name.
What is a Catalog?
When cataloging a tape, Backup Exec reads the header information from the tape and stores it in a file on the hard drive.
The information contained in the catalog includes, but is not limited to:
  • Tape number/label/name (something to identify that tape from all others)
  • Date and time of the backup
  • Type of backup
  • What directories/files were backed up
·
Inventorying All Drives When Backup Exec Services Start:
A default can be set so that all drives are inventoried whenever the Backup Exec services are started.
An inventory of all drives on startup is recommended if media is often moved between robotic libraries, but Backup Exec may take longer to start.
To have Backup Exec perform an inventory each time Backup Exec starts:
1. On the Tools menu, click Options
2. In the Properties pane, under Job Defaults, click Preferences
3. Click Inventory all drives on Backup Exec services startup (Figure 2)
Figure 2
 
To Catalog a tape:
1. Click on the tape drive/robotic library
2. Select the tape from the right pane
3. Right-click the tape and select Catalog (Figure 3)
Figure 3

This will add the directory structure of the data on the tape to the restore tree. An inventory and catalog must be performed on all tapes to be included in a search.
Note:  The process to inventory and catalog Backup-to-Disk (B2D) Files is similar to what is shown above, with the exception that these files use a virtual tape library on the designated source or target hard disk.

Popular posts from this blog

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...

Troubleshooting vSAN Storage Policy Migration Failures in VMware Cloud Foundation 9.0

Recently I had a customer who migrated their VMware infrastructure from vSphere 7.0 to VMware Cloud Foundation 9.0. After the migration, they wanted to update their vSAN storage policies to take advantage of the new vSAN ESA (Express Storage Architecture) features. However, when they tried to change the storage policy for their production VMs, the operation kept failing with a cryptic error message. The error they were getting was: "Cannot complete operation due to insufficient resources to satisfy current storage policy." This was strange because they had plenty of disk space available. The vSAN cluster was only at 45% capacity, and all the hosts were healthy. Let me walk through how we troubleshooted and fixed this issue. Understanding the Problem First, let's understand what was happening in their environment: They had a 6-node vSAN cluster running VCF 9.0 vSAN was configured with the new ESA architecture They were trying to migrate VMs fro...

Unlocking VMware Cloud Foundation 9.0: A Strategic Blueprint for Enterprise Transformation

The evolution of VMware under Broadcom represents not disruption, but clarification—a focused vision toward unified private cloud excellence. As organizations navigate this transformation, the opportunity has never been greater to build truly modern, efficient, and powerful infrastructure with VMware Cloud Foundation. After architecting VMware solutions across diverse enterprise environments, I've observed a pattern: organizations that embrace VMware Cloud Foundation (VCF) strategically—rather than viewing the transition as a burden—emerge with significantly more capable, cost-effective, and future-ready infrastructure. This post shares a practical framework for successfully modernizing your VMware environment, maximizing your investment, and positioning your organization for the AI-driven, cloud-native future. Understanding the VMware Cloud Foundation Vision Let's start with clarity about what Broadcom and VMware are building: VMware Cloud Foundati...