Recommended backup practices — NetBackup 11.1 | Cohesity Documentation

Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist

Recommended backup practices — NetBackup 11.1 | Cohesity Documentation

Recommended backup practices

The following backup practices are recommended:

Selecting files to back up	In addition to backing up files on a regular basis, it is important to select the correct files to back up. Include all files with records that are critical to users and the organization. Back up system and application files, so you can quickly and accurately restore a system to normal operation if a disaster occurs. Include all Windows system files in your backups. In addition to the other system software, the Windows system directories include the registry, which is needed to restore the client to its original configuration. If you use a NetBackup exclude list for a client, do not specify any Windows system files in that list. Do not omit executables and other application files. You may want to save tape by excluding these easy-to-reinstall files. However, backing up the entire application ensures that it is restored to its exact configuration. For example, if you have applied software updates and patches, restoring from a backup eliminates the need to reapply them.
Bare Metal Restore	NetBackup Bare Metal Restore (BMR) protects client systems by backing them up with a policy configured for BMR protection. A complete description of BMR backup and recovery procedures is available. See the NetBackup Bare Metal Restore Administrator's Guide: http://www.veritas.com/docs/DOC5332
Critical policies	When you configure a policy for online catalog backup, designate certain NetBackup policies as critical. Critical policies back up systems and data deemed critical to end-user operation. During a catalog recovery, NetBackup verifies that all of the media that is needed to restore critical policies are available.
Full backup after catalog recovery	If the configuration contains Windows clients that have incremental backup configurations set to Perform Incrementals Based on Archive Bit, run a full backup of these clients as soon as possible after a catalog recovery. The archive bit resets on the files that were incrementally backed up after the catalog backup that was used for the catalog recovery. If a full backup of these clients is not run after a catalog recovery, these files could be skipped and not backed up by subsequent incremental backups.
Online catalog backups	Online, hot catalog backup is a policy-driven backup that supports tape-spanning and incremental backups. Online catalog backups may be run while other NetBackup activity occurs, which provides improved support for environments in which continual backup activity is typical.
Online catalog backup disaster recovery files	Cohesity recommends saving the disaster recovery files that are created by the online catalog backup to a network share or removable device. Do not save the disaster recovery files to the local computer. Catalog recovery from an online catalog backup without the disaster recovery image file is a more complex procedure and time-consuming procedure.
Automated recovery	The catalog disaster recovery file (created during an online catalog backup) is intended to automate the process of NetBackup recovery. If you recover a system other than the one that originally made the backups, it should be identical to the original system. For example, the system that performs the recovery should include NetBackup servers with identical names to those servers where the backups were made. If not, the automated recovery may not succeed.
Online catalog disaster recovery information email	Configure the online catalog backup policy to email a copy of the disaster recovery information to a NetBackup administrator in your organization. Configure this policy as part of every catalog backup. Do not save the disaster recovery information emails to the local computer. Catalog recovery without the disaster recovery image file or the disaster recovery information email available is exceedingly complex, time consuming, and requires assistance. NetBackup emails the disaster recovery file when the following events occur: The catalog is backed up. A catalog backup is duplicated or replicated. The primary catalog backup or any copy of a catalog backup expires automatically or is expired manually. The primary copy of the catalog backup is changed as follows: By using the bpchangeprimary command. By using the option to change the primary copy when the catalog backup is duplicated manually. You may tailor the disaster recovery email process by using the mail_dr_info notify script. More details are available. See the NetBackup Administrator's Guide, Volume II: http://www.veritas.com/docs/DOC5332 If you are not able to receive the disaster recovery packages over emails even after you have configured your email, then ensure the following: Your email exchange server is configured to have the attachment size equal to or greater than the disaster recovery package size. You can check the size of the package (.drpkg file size) on the disaster recovery file location that you have specified in the catalog backup policy. The firewall and antivirus software in your environment allow the files with the .drpkg extension (which is the extension for a disaster recovery package file). If BLAT is used as email notification application, it is of v2.4 or later version.
Identifying the correct catalog backup	Ensure that you identify and use the appropriate catalog backup for your recovery. For example, if you recover from your most recent backups, use the catalog from your most recent backups. Similarly, if you recover from a specific point in time, use the catalog backup from that specific point in time.
Catalog recovery time	System environment, catalog size, location, and backup configuration (full and incremental policy schedules) all help determine the time that is required to recover the catalog. Carefully plan and test to determine the catalog backup methods that result in the desired catalog recovery time.
Primary and media server backups	The NetBackup catalog backup protects your configuration data and catalog data. Set up backup schedules for the primary servers and media servers in your NetBackup installation. These schedules protect the operating systems, device configurations, and other applications on the servers. Primary or media server recovery procedures when the system disk has been lost assume that the servers are backed up separately from the catalog backup. Backups of primary and media servers should not include NetBackup binaries, configuration or catalog files, or NetBackup database data.

Feedback

Was this page helpful?

Feedback

Was this page helpful?