サポートと今すぐチャット
サポートとのチャット

DR Series Software 4.0.3 - Administration Guide

Introducing the DR Series system documentation Introducing the DR Series system Setting up the DR Series system Configuring the DR Series system settings Managing containers Managing replications Monitoring the DR Series system Using GlobalView Configuring and using Rapid NFS and Rapid CIFS Configuring and using Rapid Data Access with NetVault Backup and with vRanger Configuring and using RDA with OST
Understanding RDA with OST Guidelines Terminology Supported RDA with OST software and components Best Practices: RDA with OST and the DR Series System Setting client-side optimization Configuring an LSU Installing the RDA with OST plug-in Configuring DR Series system information using NetBackup Backing up data from a DR Series system with NetBackup Using Backup Exec with a DR Series system (Windows) Understanding the OST CLI commands Understanding RDA with OST Plug-In Diagnostic Logs Collecting diagnostics by using a Linux utility Guidelines for gathering media server information
Configuring and using VTL Configuring and Using Encryption at Rest Support, maintenance, and troubleshooting Supported Ports in a DR Series system About us

Collecting diagnostics by using a Linux utility

Rotating RDA with OST plug-in logs for Linux

You can use a Linux utility called ocaDRDiags to collect diagnostics from Linux-only clients. This Linux utility is installed by the OST plug-in installer in the /opt/oca directory. The tool collects the following types of information:

•
var/log/libstspioca.log.*
•
usr/openv/netbackup/logs
•
usr/openv/logs/nbemm/
•
usr/openv/logs/nbrmms/

The diagnostics file is written to the following location: /var/log/diags_client location.

The following example shows the process for collecting the RDA with OST diagnostic logs (the root user account shown represents one that resides on the media server, and is not to be confused with a root user account on the DR Series system):

[root@QA-OST-rh6-64 admincmd]# cd /opt/oca
[root@QA-OST-rh6-64 oca]# ./ocaDRDiags --collect
Collecting diagnostics...Done
Diagnostics location: /var/log/diags_client//QA-OST-rh6-64_2017-11-01_03-20-56.tgz

The default log level can be modified via the DR Series system CLI or GUI.

* 
NOTE: For backward compatibility the /opt/dell folder also exists on the client.

Rotating RDA with OST plug-in logs for Linux

If you set the RDA with OST plug-in log level to Debug, this can cause the plug-in log to grow in size quickly. The best practice for preventing any issues with log sizes is to rotate the plug-in logs using the logrotate utility that is commonly available on Linux-based systems.

To configure log rotation, complete the following:

1.
Create a file in /etc/logrotate.d/, name it “ost”, and add the following entries:
/var/log/libstspioca.log {
rotate 10
size 10M
copytruncate
}
2.
Create a file in /etc/cron.hourly/, name it “ost_logrotate.cron”, and add the following entries:
#!/bin/bash
/usr/sbin/logrotate /etc/logrotate.d/ost

The logrotate utility runs every hour, and rotates the logs whenever the log file size exceeds 10 megabytes (MB). This procedure is automated as part of the plug-in installation.

Guidelines for gathering media server information

In addition to the DR Series system diagnostics log file bundles and core files that you can collect for history and troubleshooting purposes, if you have run any RDA with OST operations, Quest recommends that you also gather some important media server-related files. This topic introduces some of these key media server files that reside on Linux and Windows platforms .

NetBackup on Linux Media Servers

For NetBackup running on a Linux media server, Quest recommends gathering the following files:
•
RDA with OST plug-in configuration files and log files from the media server
◦
Location: /var/log/libstspioca.log.*
•
NetBackup backup job logs and command logs from the media server:
◦
Location: NetBackup log files reside in /usr/openv/netbackup/logs/. For each process in NetBackup, there is a subdirectory in the logs directory. Quest is interested in the following process-related logs: bptm, bpdm, bprd, bpcd, bpbrm.
◦
Be aware that these five directories may not exist by default, so only collect these logs if they exist on your media server. If they were created, the locations where these log files reside are as follows: /usr/openv/netbackup/logs/bptm, /usr/openv/netbackup/logs/bpdm, /usr/openv/netbackup/logs/bpcd, /usr/openv/netbackup/logs/bprd, and /usr/openv/netbackup/logs/bpbrm.
◦
Quest recommends that you collect logs from the following directories: /usr/openv/logs/nbemm and /usr/openv/logs/nbrmms/.
•
Check for any core files that were generated on the NetBackup media server or on the DR Series system that can include:
◦
Core files on a Linux NetBackup media server reside in the /usr/openv/netbackup/bin directory. Most of the NetBackup binaries that link with the RDA with OST plug-in are in this directory.
◦
The location of the core files on the client is not a fixed location. Verify if the core files reside in following directories: /, /root/, or the directory mentioned in the /proc/sys/kernel/core_pattern. For example, if the following is a core_pattern from a DR Series system (/var/cores/core.%e.%p.%t), then all the core files would reside in /var/cores.

Quest recommends that if core_pattern on the client is set by NAT to a specific directory, then the diagnostics script has to look into that directory for any related cores.

NetBackup on Windows Media Servers

For NetBackup running on a Windows media server, Quest recommends gathering the following files:
•
RDA with OST plug-in configuration files and log files from the media server:
◦
Location: %ALLUSERSPROFILE%\Quest\OST\log\libstspioca.log*
•
NetBackup job logs and command logs from the media server, with log files from following directories:
◦
C:\Program Files\Veritas\NetBackup\logs\bptm (if it exists)
◦
C:\Program Files\Veritas\NetBackup\logs\bpdm (if it exists)
◦
C:\Program Files\Veritas\NetBackup\logs\bpbrm (if it exists)
◦
C:\Program Files\Veritas\NetBackup\logs\bprd (if it exists)
◦
C:\Program Files\Veritas\NetBackup\logs\bpcd (if it exists)
◦
C:\Program Files\Veritas\NetBackup\logs\nbemm
◦
C:\Program Files\Veritas\NetBackup\logs\nbrmms
•
Any core files generated on the NetBackup media server or on the DR Series system.
•
If a server failure is involved (which could be an inapparent or silent failure), the Windows media server event log for the application could be collected by using Administrative Tools → Event Viewer. Next, check the Windows Logs → Application. Typically, the last entry marked with Error is the one for which you are searching.
◦
Copy and paste this text in the window, as shown in the following example:
Faulting application bptm.exe, version 7.0.2010.104, time stamp 0x4b42a78e, faulting module libstspiocaMT.dll, version 1.0.1.0, time stamp 0x4f0b5ee5, exception code 0xc0000005, fault offset 0x000000000002655d, process id 0x12cc, application start time 0x01cccf1845397a42.
◦
If the system is unresponsive, force the crash of bptm.exe and complete the following:
1.
Click to open Task Manager.
2.
Locate the process.
3.
Right-click, and select Create Dump File.
4.
Retrieve the dump file from the location specified in the dialog that displays after the dump file is created.

Backup Exec on Windows Media Servers

For Backup Exec running on a Windows media server, Quest recommends gathering the following files:
•
RDA with OST plug-in configuration files and log files from the media server:
◦
Location: %ALLUSERSPROFILE%\Quest\OST\log\libstspioca.log*
•
Backup Exec job logs and command logs from the media server.
•
Any core files generated on the Backup Exec media server or on the DR Series system.
•
If a crash is involved, collect any mini-dump file(s) that reside in %ProgramFiles%\Veritas\Backup Exec\BEDBG.
•
If the system is unresponsive, force the crash of pvlsvr.exe and bengine.exe, and complete the following:
1.
Open Task Manager.
2.
Locate the process.
3.
Right-click, and select Create Dump File.
4.
Retrieve the dump file from the location specified in the dialog that displays after the dump file is created.

Configuring and using VTL

Configuring and using VTL

Understanding VTL
Terminology
Supported virtual tape library access protocols
VTL and DR Series specifications
Guidelines for configuring VTL

This topic introduces Virtual Tape Libraries (VTLs) and related concepts and tasks. Refer to the subsequent topics and procedures in this section for more information.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択