– found an EEB for NetBackup upgrade from 8.1.2 to 8.3 for similar issue. – stopped Netbackup services and tried upgrading NetBackup to 8.3 and it was successful. – Further we tried to proceed for NetBackup upgrade to 10.2 and it was giving db related error. Since the relational database is migrated in NBU 10.2 we need the RDBMS service up and running during upgrade to 10.2 , started the same. Finally, the NetBackup was upgraded successfully to 10.2 and Catalog backup was successfully completed as well
Software lifecycle:- upgrading the appliance has always been a time-consuming task with the help of the container platform upgrade can be done in 6 mins and 6 mins to roll back.
NetBackup provisioning :- Wizard base NetBackup provisioning, 1 min to provision including start-up, create mix version netbackup within single appliance (test purpose, you can have latest netbackup in few mins)
smaller footprint :- It supports single appliance for everything, serverless architecture
Multi-tenancy:- Multi-tenancy support, segregated netbackup domain can be created in single appliance
storage saving :- Highly scalable, fastest dedupe appliance in the market with highest dedupe ratio
OpsCenter is a web-based software application that helps organizations by providing visibility into their data protection environment. By using OpsCenter, you can track the effectiveness of backup operations by generating comprehensive reports.
OpsCenter is available in the following two versions:
This OpsCenter version does not require any license.OpsCenter provides single deployment configuration and user interface for monitoring, alerting, and reporting functionality.
OpsCenter Analytics is the licensed version of OpsCenter.In addition to the features available in the unlicensed OpsCenter version, Analytics offers report customization, and chargeback reporting.
open VERITAS licensing portal
copy license from VERITAS NETBACKUP 8.2 PLATFORM BASE COMPLETE EDITION LICENSE as below highlighted
The answer is pretty simple. An air-gapped backup, as part of your backup and recovery strategy, is a copy of your organization’s data that’s offline and inaccessible. Without an internet or other network connection, it’s impossible for your backup device to be remotely hacked or corrupted. That leaves only a direct physical attack as a means to getting to your data. Traditionally, air gapping has been referred to in the context of tape backups, but today’s options for backing up to the cloud offer a virtual equivalent of air-gapped tape. But, while the cloud’s object-based storage defenses are incredibly powerful, a physically air gapped backup is your absolutely final line of defense.
Updating the 3-2-1 Rule
This ties back to our recent post about StorageCraft’s take on the traditional 3-2-1 rule. There we discuss how you should store one copy of your backups in a secure, offsite location. If that offsite copy is disconnected, it’s protected from malicious software, direct cyberattacks, and other threats. It also protects your backups even if ransomware compromises admin passwords or other data. If everything else fails, your air-gapped backups should be capable of restoring your entire network system.
Air Gapping Challenges
Although air gapping is your ultimate defense against disaster, it can also be costly in terms of labor. When your backup device is completely disconnected from your network, the only way to access it is with direct physical contact. That limits your ability to automate backups, and, while there are automated solutions available, any device that is connected from a network could become compromised. That means going to the device and physically transferring data is your best bet.
Ultimately, whether you choose to include air-gapped backups in your strategy depends on your unique situation. What matters most is that you have a solid backup and recovery plan in place and that you keep it up to date. StorageCraft offers solutions for organizations of every size that simplify backup and recovery and ensure your data is always protected.
ExaGrid is a new generation storage device that is built and designed for the backup solution. ExaGrid Doesn’t have a lock-in with one specific backup vendor and it’s supported with the most of backup software.
We all are very well aware of the data Tiered concept mainly for HOT and Cold data, ExaGrid is Tiered backup storage but with more advanced logic which is really fixing major challenges and providing robust protection against a ransomware attack.
Ransomware stories are very common these days and many organizations had faced tuff times and have lost very critical and important data. Ransomware is really scary.
The most Terrifying thing is hackers manage to delete data from the primary storage and backup storage as well and the organization is left with no option to get the data back
Let us understand how protection works
ExaGrid’s have unique approach is called Retention Time-Lock (RTL). It prevents the threat actors/ hackers from deleting the backups and allows for retention points to be purged.
ExaGrid is Tiered Backup Storage with a front-end disk-cache Landing Zone and separate Repository Tier containing all retention data. Data is written directly to the “network facing”ExaGrid disk-cache Landing Zone. hen it is tiered into a “non-network-facing” long-term retention repository where it is stored as deduplicated data objects to reduce the storage cost of long-term retention data. As data is tiered to the Repository Tier, it is deduplicated and stored in a series of objects and metadata. As with other object storage systems, the ExaGrid objects and metadata never change allowing only for the creation of new objects or deletion of old objects when retention is reached.
Any deletion requests are delayed by the number of days in the protection policy
Encrypted data written to ExaGrid does not delete or change previous backups in the repository
Landing Zone data that is encrypted does not delete or change previous backups in the repository
Set delayed deletion in 1-day increments from 0 days to 30 days
Protects against loss of any and all retained backups including monthlies and yearlies
Two-Factor Authentication (2FA) protects changes to the Time-Lock setting
Separate password for primary site versus second site ExaGrid
Separate backup staff and security staff roles and passwords
Microsoft Exchange is a popular business email server that runs on top of Windows Server OS. It stores the user data, such as emails, attachments, contacts, notes, calendar, tasks, etc., in a mailbox database file or EDB.
Exchange server also creates and stores transaction logs (.log) and Checkpoint file (.chk), along with the EDB file. It uses the Write-Ahead Logging method to record all the transactions made on the Exchange server in log files. Once the transaction is complete, the transaction log files are committed to the database file and the changes are applied to the database. Exchange server does this to maintain the database integrity, reduce disk writes, high availability, and prevent data loss.
However, if an uncommitted log file is deleted or the server crashes/reboots before committing the transaction log to the database file, it can lead to an inconsistent database and cause database corruption.
Exchange server database may also get damaged or corrupt due to the following factors:
Software or hardware failure
Damaged storage media
Unstable or poor network connection
Virus or malware intrusion
Abrupt shutdown or server crash
In such a case, the database state changes to Dirty Shutdown state and the database does not mount, which leads to downtime as users who have their mailboxes on the damaged database can’t access their emails.
This is a common issue in a standalone Exchange server environment that could lead to financial loss, productivity loss, and may tarnish the organization’s reputation. Thus, it is critical to fix the database immediately and restore mailbox connectivity.
Recover Corrupt Exchange Database
The most reliable and quick way to restore databases and mailboxes is to use the last backup. However, if the backup is not available, obsolete, or does not work, administrators can use built-in Exchange database recovery tools, such as EseUtil, to recover corrupt Exchange databases.
One can use EseUtil to perform Soft Recovery or Hard Recovery (when Soft Recovery fails) to recover the inconsistent or corrupt database.
Although EseUtil helps recover inconsistent databases via Hard Recovery, it does that by purging irrecoverable mailboxes and data from the EDB file that can lead to significant data loss.
Thus, it’s recommended to use a third-party Exchange recovery software, such as Stellar Repair for Exchange. The software can repair and recover corrupt or inconsistent Exchange databases with complete integrity and without any risk of data loss.
Stellar Repair for Exchange – An Overview
Stellar Repair for Exchange is a powerful and advanced Exchange recovery software to repair corrupt, inconsistent, inaccessible, or damaged Exchange database files. It repairs the Exchange EDB files, extracts the user mailboxes, and saves them to PST and other multiple portable file formats, such as HTML, RTF, EML, MSG, and PDF.
In addition, administrators can also export the recovered mailboxes from corrupt database files directly to a live Exchange server and Office 365. The software comes in handy when built-in Exchange repair utilities and PowerShell cmdlets fail to repair the damaged Exchange database. Also, it can repair EDB files created in MS Exchange 2019, 2016, 2013, 2010, 2007, 2003, and 5.5.
System Requirements and Installation
Stellar Repair for Exchange is a highly optimized software. You can install and use the software on any system that meets the following minimum system requirements:
Processor: Intel-compatible (x86, x64)
Memory: 4 GB minimum (8 GB recommended)
Hard Disk: 250 MB hard disk space
Operating System: Windows 10, 8.1, 8, 7, & Windows Server 2016, 2012, 2008
Stellar Repair for Exchange is available in three editions:
The Corporate edition is licensed for single users. It can repair and recover up to 100 mailboxes from corrupt or inaccessible database files to PST, live Exchange server, or Office 365 accounts. Following are some features that Corporate edition offers:
Repairs corrupt EDB files without file size limit
Dual scan modes (Quick Scan and Extensive Scan)
4x faster recovery with Parallel Processing
Option to prioritize mailbox recovery
Recovers and restores mailboxes and mail items, such as email, contacts, calendars, tasks, and notes with 100% integrity
Restores mailboxes from repaired EDB file to PST, EML, MSG, RTF, HTML, and PDF file formats
Exports the recovered mailboxes, mail items, and public folders directly to live Exchange or Office 365.
In addition to the features available in the Corporate edition, the Technician edition comes with multiple user license support, which allows you to install and use the Technician edition on more than one machine. Plus, it can repair and recover unlimited mailboxes.
The Toolkit is a 5-in-1 software suite to repair corrupt EDB files, extract mailboxes, convert OST to PST, recover mailboxes from Exchange Backup, and recover lost or forgotten Windows Server passwords. The Toolkit edition is also licensed for multiple users and offers all the features of Corporate and Technician editions.
All three editions are available for free download. You can download the free demo version to evaluate the software. The free version allows you to repair corrupt or inaccessible Exchange databases and preview recovered mailboxes and mail items. To save the recovered mailboxes to a supported format, you need to activate the software using a valid license key.
Repairing Exchange Database File
Repairing and recovering Exchange database files (EDB) is easier with Stellar Repair for Exchange. Unlike the built-in EseUtil and PowerShell cmdlets, the software features a rich graphical user interface that makes it much easier to use. In addition, with Parallel Processing, the software can repair and save up to 4 mailboxes simultaneously to PST, Office 365, or live Exchange server. You also get an option to set mailbox priority that allows you to recover and export critical mailboxes first than the others.
Also, it performs operations on the EDB file in read-only mode, ensuring maximum mailbox recovery without any data loss. During the recovery process, it also recovers accidentally deleted and lost mailboxes and mail items.
To repair a corrupt or inaccessible Exchange database file, follow these steps:
Step 1: Install and launch Stellar Repair for Exchange on any system that meets the minimum system requirements. Ensure MS Outlook is also installed on the system.
Step 2: Click ‘Browse’ to choose the damaged EDB file or use the ‘Find’ button if you don’t know the EDB file location. After selecting the EDB file, choose the ‘Temp path’ (or keep it default) and click ‘Next.’
NOTE: ‘Temp path’ should have free storage equivalent or more than the size of the EDB file.
Step 3: Then choose ‘Quick Scan’ or ‘Extensive Scan’ to start the repair process.
Step 4: After the repair, it displays an enhanced preview of mailboxes and mail items. This helps verify recovered mailboxes and mail items before saving them to PST or other formats.
Step 5: Once satisfied, you can select the mailboxes for recovery and then click the ‘Save’ button under the ‘Home’ menu.
Step 6: You can choose any saving option based on your need, such as live Exchange server, Office 365 account, PST, Public Folder, .EML, .MSG, .RTF, .PDF, or .HTML format. For this review, we chose ‘Export to PST.’
Step 7: Click ‘Browse’ to choose a save location and then click ‘OK’ to save.
NOTE: You may also ‘Apply Filter’ to include/exclude Junk/Deleted items or mail items based on the email address and date range.
Similarly, you may choose other saving options and follow the wizard to save the recovered mailboxes.
To Wrap Up
Stellar Repair for Exchange is a highly recommended tool by MVPs and IT administrators across the globe for Exchange recovery. It’s a lifesaver tool for all administrators as it comes in handy during disaster recovery when the backup isn’t available and built-in utilities fail. In addition, it helps prevent permanent data loss situations and restores mailbox connectivity and business activities.
It is a must-have tool for every IT and Exchange Server Admin as it reduces downtime and gets the business up and running with minimal effort and downtime.
Netbackup job failing to write data on the tape media with following error message
NBU status: 96, EMM status: No media is available
unable to allocate new media for backup, storage unit has none available (96)
Things to check :–
–> status on tape library management console , make sure all green,
–> make you have empty tape available to write the data or add new tape media
–> make sure scratch pool was created correctly
–> make sure driver was up from Netbackup console
–> make you tape drivers are able to performed move operation or clean-up job
—> restart the service if required.
–> run the netbackup tape library configuration wizard.
–> most of the time issue is mainly related to tape media so make sure you have correct media available or run the expire of media
bpmedialist -U -m (media ID) — to check the media status
VERITAS access appliance is built for primary purpose for replacing tape with Veritas’ software-defined Access scale-out network attached storage—a storage solution optimized for unstructured data use cases, Access appliance is appliance is cost-optimized and tuned for high-capacity workloads like long-term retention (LTR), tape replacement and backup archiving
Supported Protocal :-
Amazon S3, CIFS, NFS, SMB for file and object access, and iSCSI target support for block storage.
Deeply integrated with Veritas NetBackup andNetBackup CloudCatalyst, providing a turnkey, cost-optimized LTR solution for large-scale (PB) deployments where Veritas NetBackup is the primary backup utility. Integration with CloudCatalyst deduping
capability reduces storage and media transfer costs. NetBackup’s proven, enterprise-hardened deduplication saves space,
Use Cases :-
Long-term retention for Veritas NetBackup and other backup applications
IT infrastructure is rapidly increasing as a different kind of the number of applications are also increasing, each application required special skills set to manage so the number of application admins is also increasing and these the cycle has increased challenges for backup admin to keep testing backup and restore and that just to make sure that backup is valid or to meet compliance requirements. For such a task application stack holder are always highly depended on the backup admin
With the help of Netbackup self-service option dependancy on the backup, the administrator can be minimized by providing tenant access to the application stack holder to test the backup and restore it.
NetBackup Self Service 8.2 empowers users to self-serve common backup and restore requests while providing automation and control to IT. Self Service’s multi-tenant, role-based access, and dashboard features provide visibility over what’s protected and ongoing backup usage. Self Service’s request forms put complex policy management tasks safely in the h
For Enterprises Managing backups and restores for many thousands of endpoints across multiple locations and data centers is a task that typically requires a team of specialists. Effecting changes to policies can be a time consuming, an error-prone, manual activity that can leave vital resources unprotected. Enabling an intuitive self-service portal reduces complexity and errors, and automates a significant number of manual policy change activities. It also enables non-backup specialists to carry out backup and recovery-related tasks in a controlled and audited environment.
For Service providers Providing backup and restore services to multiple tenants across mixed platforms is a challenge for many service providers. Service providers can enable self-service
and automate tenant requests for backups and restores. This action puts the tenant in control and significantly reduces provisioning costs. NetBackup Self Service allows multiple tenants to access a tailored, self-service portal through which requests to back up and restore infrastructure are made intuitively. The status of their protected environments is tracked and reported. Service providers gain from automation while ensuring strict separation and security between tenant environments. Tenants gain control and visibility over what is protected.