Chat now with support
Chat with Support

NetVault 13.0.3 - Administration Guide

Introduction Getting started Configuring clients Managing catalog search Configuring storage devices
About storage devices SAN considerations Quest DR Series systems Quest QoreStor NetVault SmartDisk EMC Data Domain Systems Snapshot Array Manager Virtual Tape Libraries Virtual standalone drives Shared Virtual Tape Libraries Physical tape devices Storage tiers
Backing up data Managing policies Restoring data Managing NetVault dashboard Managing jobs Monitoring logs Managing storage devices
Monitoring device activity Managing disk-based storage devices in list view Managing disk-based storage devices in tree view Managing the Snapshot Array Manager Managing tape libraries in list view Managing tape libraries in tree view Managing tape drives in list view Managing tape drives in tree view Adding shared devices
Managing storage media Managing user and group accounts Monitoring events and configuring notifications Reporting in NetVault Working with client clusters Configuring default settings for NetVault
About configuring default settings Configuring encryption settings Configuring plug-in options Configuring default settings for post-scripts Configuring default settings for Verify Plug-in Configuring Deployment Manager Settings Configuring Job Manager settings Configuring Logging Daemon settings Configuring Media Manager settings Configuring Network Manager settings Configuring Process Manager settings Configuring RAS device settings Configuring Schedule Manager settings Configuring Web Service settings Configuring Auditor Daemon settings Configuring firewall settings Configuring general settings Configuring security settings Synchronizing NetVault Time Configuring default settings for global notification methods Configuring the reporting utility Configuring NetVault WebUI default settings Configuring NetVault to use a specific VSS provider Configuring default settings using Txtconfig
Diagnostic tracing Managing diagnostic data Using the deviceconfig utility NetVault processes Environment variables Network ports used by NetVault Troubleshooting
Common errors
NetVault Service fails to start on Windows NetVault Service fails to start after the machine is restarted NetVault Service starts, but stops immediately on Linux Login fails after any change in the server IP address Unexpected behavior of NetVault WebUI WebUI does not run in Compatibility View in Internet Explorer NetVault installer fails during push installation VSS-based backup fails Modifying TCP/IP socket buffer size on Windows Restores using Data Copy savesets fail on clients running NetVault 10.0.1 Restore fails on Itanium platforms if the index is larger than 2GB After upgrade, Data Copy and Consolidated backup job on Linux fails After upgrade, console error is displayed on WebUI pages Deployment task hangs on target Linux machine during push installation. Unable to add package store with hostname. Deployment task fails due to network configuration issues. Domain user is unable to login NetVault Server if the workstation attribute is set. Domain user is unable to login NetVault Server on Debian 9. Adding the target machine as a client fails, after successful push installation. Unable to install, uninstall or navigate catalog search page after manually uninstalling NetVault Client Host. Unable to install, uninstall catalog search on client after NetVault Server migration with the same or different server name External Azure AD user cannot add an external Azure AD user to NetVault Server Failed to verify target Windows machine from a Linux-based NetVault Server NetVault is unable to send reports as an email attachment in PDF format on RHEL 5.x platform Restore fails on NetVault Database backup When using RDA for backups, only four streams are used at once Unable to create large VTL on Linux Browsing a folder with a large number of files times out
Safe Mode in NetVault

Backup retirement

A backup can be retained indefinitely or retired after a specified period. NetVault supports generation- and time-based retirement methods for backups. When a backup is retired, its index is deleted from the NetVault Database.

Backup retirement methods

You can specify generation- and time-based retirement methods for backups:

•
Generation-based backup retirement: This method specifies the maximum generation count for a Full Backup (that is, the maximum number of Full Backups that are retained for the same data set). Generation-based retirement can only be set for Full Backups. When the number of Full Backups exceeds the specified generation count, the oldest Full Backup is retired.
•
Time-based backup retirement: This method specifies the length of time a backup is retained. You can specify the retirement age for backups in number of days, weeks, or years. A backup is retired when the retirement age is reached. Time-based retirement can be set for all backup types (that is, Full, Incremental, and Differential).
 
* 
NOTE: When a backup stored on a disk-based storage device (such as NetVault SmartDisk, Quest DR Series system, or Data Domain system) is retired, that backup is deleted from the device. You cannot import the deleted backup by scanning the device.
NOTE: When a backup is immutable, it does not retire until it reaches the selected length of time, regardless of the backup count For more information, see Backup immutability.
Retirement rules for dependent backups

If a backup has any dependent backups, you can use the following rules to delete the backup series:

•
Retire all backups when the last backup is retired: By default, the retirement of a backup series is deferred until all backups from this series are ready for retirement. The backups from an Incremental series or a Differential series are retired when the last dependent backup from the series is retired.
•
Retire all backups when the first backup is retired: NetVault lets you modify the retirement behavior to retire a backup series when the first backup is retired. When this rule is applied, the backups from an Incremental series or a Differential Series are retired when the first backup from the series is retired.
You can choose to apply this rule in the following ways:
•
Use the Retirement Timing Control settings to change the default behavior for all backups
•
Use the saveset retirement settings to override the default behavior for selected backups

The following examples illustrate the retirement behavior for different backup series:

•
Example 1: Incremental Backup series
•
Example 2: Differential Backup series
•
Example 3: Mixed backups (Full, Incremental, and Differential Backups)
Example 1: Incremental Backup series

In this example, Full Backups are performed on Sunday and Incremental Backups are performed from Monday through Saturday. The retention period is set to seven days.

 
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7

Full Backup

Incremental Backup 1

Incremental Backup 2

Incremental Backup 3

Incremental Backup 4

Incremental Backup 5

Incremental Backup 6

The Incremental Backups depend on the most recent backup of any type (Full, Incremental, or Differential). Therefore, these backups create a single backup series:

Full Backup <- Incremental Backup 1 <- Incremental Backup 2 <- Incremental Backup 3 <- Incremental Backup 4 <- Incremental Backup 5 <- Incremental Backup 6

Depending on the retirement rule that is applied, the backups are retired as follows:

•
Retire all backups when the last backup is retired: When you apply this rule, all backups from this series are retired on Day 15.
•
Retire all backups when the first backup is retired: When you apply this rule, all backups from this series are retired on Day 8.
Example 2: Differential Backup series

In this example, Full Backups are performed on Sunday and Differential Backups are performed from Monday through Saturday. The retention period is set to seven days.

 
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7

Full Backup

Differential Backup

Differential Backup

Differential Backup

Differential Backup

Differential Backup

Differential Backup

Differential Backups depend on the recent Full Backup. Therefore, these backups create six separate backup series:

Full Backup <- Differential Backup 1

Full Backup <- Differential Backup 2

Full Backup <- Differential Backup 3

Full Backup <- Differential Backup 4

Full Backup <- Differential Backup 5

Full Backup <- Differential Backup 6

Depending on the retirement rule that is applied, the backups are retired as follows:

•
Retire all backups when the last backup is retired: When you apply this rule, the backups from this example are retired as follows:
 
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day 14
Day 15

None

None

Differential Backup 1

Differential Backup 2

Differential Backup 3

Differential Backup 4

Differential Backup 5

Full Backup and Differential Backup 6

•
Retire all backups when the first backup is retired: When you apply this rule, all backups from this example are retired on Day 8.
Example 3: Mixed backups (Full, Incremental, and Differential Backups)

In this example, Full Backups are performed on Sunday, Incremental Backups are performed on Monday, Tuesday, and Thursday, and Differential Backups are performed on Wednesday and Saturday. The retention period is set to seven days.

 
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7

Full Backup

Incremental Backup 1

Incremental Backup 2

Differential Backup 1

Incremental Backup 3

Incremental Backup 4

Differential Backup 2

The Differential Backups depend on the recent Full Backup, while the Incremental Backups depend on the most recent backup of any type (Full, Differential, or Incremental). Therefore, these backups create three separate backup series:

Full Backup <- Incremental Backup 1 <- Incremental Backup 2

Full Backup <- Differential Backup 1 <- Incremental Backup 3 <- Incremental Backup 4

Full Backup <- Differential Backup 2

Depending on the retirement rule that is applied, these backups are retired as follows:

•
Retire all backups when the last backup is retired: When you apply this rule, the backups from this example are retired as follows:
 
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day 14
Day 15

None

None

None

Incremental Backup 1 and Incremental Backup 2

None

None

Differential Backup 1, Incremental Backup 3, and Incremental Backup 4

Full Backup and Differential Backup 2

•
Retire all backups when the first backup is retired: When you apply this rule, all backups from this example are retired on Day 8.

Backup immutability

If you use QoreStor for backup storage, you can select to make RDA backups immutable. RDA immutability provides protection from overwrites and deletes on backup files. This technology is present by default for RDS containers, but not all backups are protected by default. When NetVault sends data using the RDA protocol to QoreStor, you can define whether the backup data should be immutable. After you set immutability on a backup set, you cannot modify or delete the backup data from the RDA container until the predetermined length of time expires.

 
* 
NOTE: The backup immutability feature is available beginning with NetVault 13.0.3 and QoreStor 7.1. It is not compatible with previous versions of NetVault. For more information, see the NetVault Supported Storage Targets Guide and the QoreStor Interoperability Guide.

Backup immutability is not accessible through the command line interface or REST API.

About NetVault Sets

NetVault Sets are used to create backup and restore jobs.

You can use sets to store data selections, backup and restore options, scheduling options, device and media options, and other advanced backup and restore options. Sets eliminate the need to manually select the data items or configure backup and restore options for each job, and allow you to quickly and easily apply the same data selections and options to multiple jobs.

For example, you can save the data selections in a Backup Selection Set, and use this set to create Full, Incremental, and Differential Backup jobs to ensure that the same data set is used for all jobs. Similarly, you can change the day, date, or time in a Schedule Set to automatically change the job schedule for multiple jobs, or specify a new device for backups by changing the Target Set.

Set types

The following table describes the set types that are available in NetVault.

 
Table 33. Set types
Set type
Descriptions

Backup Selection Set

This set is used to specify data selections for backup jobs. The data items that are available for selection depend on the plug-in in use.

For more information about these sets, see the relevant plug-in user's guide.

Plugin Options Set

This set is used to specify the backup method, backup type, and other backup options.

The backup options that are available to a job depend on the plug-in in use. For more information about these sets, see the relevant plug-in user's guide.

Schedule Set

This set is used to specify scheduling options for backup and restore jobs. These options define when and at what intervals a job runs.

NetVault includes the following predefined Schedule Sets:

•
Immediate
•
Daily 10 PM
•
Friday 10 PM
•
Week Night 10 PM

Source Set

This set is used to specify source device options.

A Source Set is required for the following jobs:

•
Plug-in for Consolidation jobs
•
Plug-in for Data Copy jobs
•
Secondary Copy jobs
•
Restore jobs

NetVault includes the following predefined Source Set:

•
Any Device

Target Set

This set is used to specify target device and media options for backup jobs.

NetVault includes the following predefined Target Sets:

•
Default Backup Target Options
•
Local Only
•
Reuse Old Media
•
Stand-alone

Backup Advanced Options Set

This set is used to specify backup retirement settings, Secondary Copy job definitions, user-defined events, and other advanced options.

NetVault includes the following predefined Backup Advanced Options Sets:

•
Default Advanced Backup Options
•
Keep forever (Archive)
•
Encrypt

Restore Selection Set

This set is used to specify data selections for restore jobs.

The data items that are available for selection depend on the plug-in in use. For more information, see the relevant plug-in user's guide.

Restore Advanced Options Set

This set is used to specify restore type, user-defined events, and other advanced restore options.

NetVault provides the following predefined Restore Advanced Options Set:

•
Restore from selected backup

Backup and recovery strategy

The primary objective of backing up data is to recover from the damages caused by a data loss event and resume normal operations quickly. This objective requires a good backup strategy, which maximizes data availability and minimizes data loss and downtime, while balancing your business requirements with costs, resources, and other factors.

To create a good backup plan, consider the possible failure modes, like hardware failure, data corruption, human error, or loss of a data center, and select the suitable backup methods and features to recover from these scenarios.

Typically, your backup plan should define what backup methods are used, when and at what intervals the backups are performed, how the backups are stored, how long the backups are retained, and how the backup media are re-used.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating