Tchater maintenant avec le support
Tchattez avec un ingénieur du support

NetVault 13.2 - Administration Guide

Introduction Getting started Configuring clients Managing catalog search Configuring storage devices
About storage devices SAN considerations Quest DR Series systems Quest QoreStor Object storage 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 Push installation failed on Linux
Safe Mode in NetVault

Migrating savesets and backup jobs from NetVault SmartDisk to QoreStor

Use the migration feature to move savesets and backup jobs from NetVault SmartDisk device to QoreStor. As part of migration, all saved and scheduled backup jobs are redirected from the targeted NetVault SmartDisk device to the targeted QoreStor device. This process is completed before the data from existing backups is migrated.

Important notes
•
QoreStor is only supported on Linux-based platforms.
•
All savesets associated with a specific NetVault Server and NetVault SmartDisk are migrated to the new target. You cannot select specific savesets.
•
Although migration moves the backup and saveset data to a QoreStor device, NetVault does not delete the data from NetVault SmartDisk. Additionally, you cannot use NetVault to delete the data from NetVault SmartDisk after migration is finished; you must manually delete the data.
•
The Expire All function is automatically disabled during the migration process. However, it is not disabled on the new target.
•
If migration fails or you manually stop the process, savesets that were already migrated automatically point to the new target. If you restart migration, only savesets that have not been migrated yet are addressed. Additionally, corresponding backup jobs are also automatically updated to point to the new target; they do not revert to the original target even if migration of the applicable savesets is interrupted.
If migration of a specific saveset fails, you can run migration again after the first pass is finished. Depending on the reason for the failure, the remaining savesets might complete migration on the subsequent pass.
•
If you interrupt the migration process to select a different target, you must manually update the backup jobs that have been redirected to point to the new target.
•
Although NetVault does not limit the number of migrations that you can perform simultaneously, Quest recommends that you process each migration separately.
•
You can migrate multiple savesets from different NetVault SmartDisk devices to the same QoreStor device if the target contains sufficient space. If space is not available, migration fails.
•
You can migrate the same saveset to different QoreStor devices; however, the saveset points to the last QoreStor device that you selected.
•
During the migration process, Quest strongly recommends that you avoid initiating a backup job that targets the NetVault SmartDisk device that you are migrating.
•
You can create up to five storage groups and 16 containers across all storage groups.
QoreStor does not support multi-tenancy.
•
NetVault does not support migration of a Secondary Copy from one type of RDA Device to another.
If you use a Duplicate method of a Phase 2 backup job to create a Secondary Copy that also targets a NetVault SmartDisk device, the job might fail after migration is finished. This occurs when both jobs targeted a NetVault SmartDisk device. During migration, the primary job is migrated to the new target, such as a QoreStor device, and the backup job completes successfully. The secondary job still identifies a NetVault SmartDisk device as the target, which causes it to fail.
•
You can use the Secondary Copy feature with different RDA device types, but you cannot use it with an RDA device and a NetVault SmartDisk device. You must create a new Secondary Copy that uses an RDA device as the target.

Migrating savesets and backup jobs

1
Make sure that you have added the Linux-based QoreStor device to the NetVault Server.
For more information, see Quest DR Series systems or Quest QoreStor.
2
Make sure that the NetVault SmartDisk device and the QoreStor device are online and assigned to the same NetVault Server.
a
In the Navigation pane, click Manage Devices.
b
On the Manage Devices page, note the status of the NetVault SmartDisk device and the QoreStor device.
Figure 6. Devices are online
3
Verify that the applicable backup savesets are pointing to the online NetVault SmartDisk device.
a
In the Navigation pane, click Explore Storage.
b
On the Explore Storage page, click Explore Disk Storage.
c
On the Explore Disk Storage page, select the applicable device in the repository table, and click Explore Repository.
d
On the Explore Disk Storage Repository page, review the information listed in the Saveset table.
e
To close the dialog box, click Close.
f
Repeat these steps for each saveset that you want to migrate from NetVault SmartDisk to a QoreStor device.
4
When you are ready to start the migration process, click Manage Devices in the Navigation pane.
5
Click the Manage Device icon for the NetVault SmartDisk device.
6
On the RAS Device Management page, click Start Migration.
7
In the Select target device dialog box, select the QoreStor device to which you want to migrate the NetVault SmartDisk saveset.
8
Select an existing Target Set or create a new Target Set that saved or scheduled backup jobs should target, and click Confirm.
9
To monitor the progress of the migration, click Check logs.

The View logs page displays all NetVault logs. To view only the NetVault SmartDisk, enter NVSD in the text box. The process is displayed as a percentage of the savesets that have been migrated.

EMC Data Domain Systems

This section includes the following topics:

•
About EMC Data Domain Systems
•
DD Boost/DDOS dynamic configuration
•
Data Domain System prerequisites
•
Adding a Data Domain System
•
DD Boost commands

About EMC Data Domain Systems

EMC Data Domain Systems provide disk-based storage with inline deduplication capabilities that reduce storage requirements by 10 to 30 times.

NetVault provides seamless integration with Data Domain systems through the EMC DD Boost software, allowing you to minimize your backup window and perform optimized disk-based backups while reducing your storage and network bandwidth requirements.

 
* 
NOTE: The NetVault Starter Edition does not support DD Boost.
DD Boost/DDOS dynamic configuration

To use the new DD Boost library or DDOS appliance, the configuration file “boostlayer.cfg” needs to be updated with the newer library version and supported appliance versions.

[Library]
Version= 7.7
Appliances= 6.2, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9, 7.10, 7.11, 7.12
 

Also, copy the DD Boost library in the NV install directory location “/usr/netvault/dynlib/dd_boost” with a new folder created and renaming the library as follows:

Example:

DDBoost library version: 7.7
so, created new folder name “/usr/netvault/dynlib/dd_boost/7_7” and renamed library name to libDDBoost_7_7.so
DD Boost components

The DD Boost software includes two components:

•
DD Boost Library: This component runs on the NetVault Server, and provides the interface to communicate with the DD Boost Server running on the Data Domain system.
•
DD Boost Server: This component runs on the Data Domain systems.
DD Boost features

DD Boost offers the following features:

•
Distributed segment processing: DD Boost offloads parts of the deduplication process to the backup client or server, enabling the client or server to send only unique data segments to the Data Domain system.
Distributed segment processing offers the following advantages:
•
It increases the aggregate backup throughput of the storage system and reduces the amount of data transferred over the network.
•
It decreases processor utilization on the backup server because sending data over the network is more CPU‑intensive than the distributed deduplication process.
Without this feature, the DD Boost Library sends all data (unique or redundant) to a Data Domain system for deduplication processing.
•
Advanced load balancing and link failover: This feature lets you combine multiple Ethernet links into a group, and register a single interface with the backup application. The Data Domain system automatically balances the load for backup and restore jobs on multiple interfaces, and routes the jobs to the available interfaces if one of the interfaces in the group goes down.
•
File replication: File-level replication enables transfer of deduplicated data directly between two or more DD Boost-enabled Data Domain systems, and thus reduces WAN bandwidth requirement by up to 99 percent. The Data Domain systems create and transfer the duplicate copies without using any resources on the backup server.
Replication requires optional DD Boost Replicator license. The license must be installed on all participating Data Domain systems.
If the source and target Data Domain systems are running different versions of the Data Domain OS, then for replication to be successful, the target system must be running the higher version of the OS.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation