立即与支持人员聊天
与支持团队交流

NetVault 12.2 - Administration Guide

Introduction Getting started Configuring clients Managing catalog search Configuring storage devices Backing up data Managing policies Restoring data Managing NetVault Backup 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 Backup Working with client clusters Configuring default settings for NetVault Backup
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 Backup WebUI default settings Configuring NetVault Backup to use a specific VSS provider Configuring default settings using Txtconfig
Diagnostic tracing Managing diagnostic data Using the deviceconfig utility NetVault Backup processes Environment variables Network ports used by NetVault Backup Troubleshooting

Limitations

Following are the limitations when you push the NetVault Backup Client from a Linux to Windows machine.

•
Mention the target machine in FQDN format and not in an IP format, as Kerberos requires the hostname with FQDN for authentication.
•
Local user is not supported, as Kerberos does not authenticate a local user, hence domain admin user account must be provided to connect to target machine.
•
During Push installation specify the domain suffix (For example: domain.com or domain.local) for the samaccountname or DL format.

Managing package stores

This section includes the following topics:

•
Configuring a package store
•
Modifying a package store
•
Removing a package store

Configuring a package store

A package store is a shared location used for storing NetVault Backup Client and plug-in binary files for push installations. Only CIFS shares (including Linux Samba shares) are currently supported as package stores. You can set up a package store in NetVault Backup by providing the path and user credentials for the CIFS share.

To configure a package store:
1
In the Navigation pane, click Guided Configuration, and then on the NetVault Configuration Wizard page, click Install Software/Add Clients.
2
On the Select Software/Add Clients page, select Install NetVault software on remote machines.
3
Click Manage Stores, and provide the following details.
 
Option
Description

Store Name

Provide a display name for the package store.

You cannot change the store name after it is configured.

Type

Select CIFS.

Location

Provide the UNC (uniform naming convention) path of the CIFS (Common Internet File System) share.

The format for specifying the path for Windows-based server is:

\\<server>\<share name>

The format for specifying the path for Linux-based server is:

//<server>/<share name>

Verify that the path is accessible to the NetVault Backup Server and all target machines where you want to install the packages.

NOTE: On the Windows-based server, if the server IP address is used to configure a local package store (for example, \\10.11.12.3\PkgStore), the user credentials are not validated when the package store is added or updated. If you specify invalid credentials, no errors are reported. However, the deployment task fails if the authentication fails and the packages cannot be retrieved from the store. Therefore, Quest recommends that you use the server name when configuring the path to a local store (for example, \\WinServer1\PkgStore).

User Name

Specify a user account that can be used to access the CIFS share.

Password

Specify the password for the user account.

4
Click Add to add the store, and then click Done.

Modifying a package store

You can update the UNC path or user credentials for an existing package store.

To modify a package store:
1
In the Navigation pane, click Guided Configuration, and then on the NetVault Configuration Wizard page, click Install Software/Add Clients.
2
On the Select Software/Add Clients page, select Install NetVault software on remote machines.
3
Click Manage Stores, and in the package store list, select the applicable package store.
4
Under the package details section, type new values for the options that you want to change.
For more information about the options, see Configuring a package store.
5
Click Update, and in the confirmation dialog box, click OK.
 
* 
NOTE: When you edit a package store, it affects the existing deployment tasks that use the package store.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级