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

Configuring required object storage permissions

Permissions setting vary depending on your cloud storage provider (CSP). Complete one of the following procedures according to your CSP’s requirements:

•
Configuring permissions for AWS storage
•
Configuring permissions for Wasabi S3 storage

Configuring permissions for AWS storage

To configure permissions for AWS storage
1
From the AWS console, go to the IAM service.
2
Create a new policy using the following set of permissions:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": [
"s3:CreateBucket",
"s3:ListBucket",
"s3:DeleteBucket"
],
"Resource": "arn:aws:s3:::*"
},
{
"Sid": "VisualEditor1",
"Effect": "Allow",
"Action": [
"s3:PutObject",
"s3:GetObject",
"s3:DeleteObject"
],
"Resource": "arn:aws:s3:::*/*"
},
{
"Sid": "VisualEditor2",
"Effect": "Allow",
"Action": "s3:ListAllMyBuckets",
"Resource": "*"
}
]
}
3
Create a new user.
4
Under Permissions, attach the policy you created in Step 2 to the user you created in Step 3.
5
When adding the container or bucket to NetVault, use the access_key and secret_key of the newly created user.

Configuring permissions for Wasabi S3 storage

To configure permissions for Wasabi S3 storage
1
From the Wasabi Console, go to the policy document section.
2
Create a new policy using the following permissions:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": [
"s3:CreateBucket",
"s3:ListBucket",
"s3:DeleteBucket"
],
"Resource": "arn:aws:s3:::<wasabi_cloud_tier_bucket>"
},
{
"Sid": "VisualEditor1",
"Effect": "Allow",
"Action": [
"s3:PutObject",
"s3:GetObject",
"s3:DeleteObject"
],
"Resource": "arn:aws:s3:::<wasabi_cloud_tier_bucket>/*"
},
{
"Sid": "VisualEditor2",
"Effect": "Allow",
"Action": "s3:ListAllMyBuckets",
"Resource": "*"
}
]
}
3
Create a sub-user.
4
Attach the newly created policy to the new sub-user.
5
When adding the container or bucket to NetVault, use the access_key and secret_key of the newly created user.

Using a proxy for direct-to-object storage

When accessing a container or bucket through a proxy, based on your operating system, define the parameters in this procedure in one of the following files:

•
For Linux: /etc/oca/aws.conf
•
For Windows: C:\ProgramData\QoreStor\aws.conf
Using a proxy for AWS and S3-compatible storage
To use a proxy for AWS and S3-compatible storage
1
When adding AWS or other S3-compatible storage to NetVault through a proxy, use the following parameters:
AWS_PROXY_HOST=<IP address of the proxy or FQDN of the proxy>
AWS_PROXY_PORT=<Proxy port number>
AWS_PROXY_USER=<Username to access the proxy>
AWS_PROXY_PASSWORD=<Password for the newly created user name>
Using a proxy for Azure storage
To use a proxy for Azure storage
1
While accessing the container or bucket through the proxy, add https_proxy as an environment variable use one of the following options depending on your environment:
•
On Linux: To restrict the proxy, define the environment in .bashrc, .bash_profile, or /etc/oca/cml_common.conf. For example: https_proxy=http://<FQDN>:<PORT>
•
On Windows: To add https_proxy as a variable, use the following URL format:
https_proxy=http://<username>:<password>@proxy.<IP address of the proxy>.com:<port number>
2
To apply the changes, restart the system.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation