Veritas CloudPoint Administrator's Guide
- Getting started with CloudPoint
- Section I. Installing and configuring CloudPoint
- Preparing for installation
- Deploying CloudPoint
- Deploying CloudPoint in the AWS cloud
- Using plug-ins to discover assets
- Configuring off-host plug-ins
- AWS plug-in configuration notes
- Google Cloud Platform plug-in configuration notes
- Microsoft Azure plug-in configuration notes
- HPE RMC plug-in configuration notes
- NetApp plug-in configuration notes
- Hitachi plug-in configuration notes
- InfiniBox plug-in configuration notes
- About CloudPoint plug-ins and assets discovery
- Configuring the on-host agents and plug-ins
- Oracle plug-in configuration notes
- Protecting assets with CloudPoint's agentless feature
- Preparing for installation
- Section II. Configuring users
- Section III. Protecting and managing data
- User interface basics
- Indexing and classifying your assets
- Protecting your assets with policies
- Tag-based asset protection
- Replicating snapshots for added protection
- Managing your assets
- About snapshot restore
- Single file restore requirements and limitations
- Additional steps required after a SQL Server snapshot restore
- Monitoring activities with notifications and the job log
- Protection and disaster recovery
- Section IV. Maintaining CloudPoint
- CloudPoint logging
- Troubleshooting CloudPoint
- Working with your CloudPoint license
- Managing CloudPoint agents and plug-ins
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Section V. Reference
Using the Job Log
The CloudPoint Job Log allows you to keep a track of all the activities that are happening in your CloudPoint environment. These include manual and policy-driven tasks such as snapshot creation and deletion, as well as plug-in configuration and removal operations. On the right-hand side of the CloudPoint dashboard, you will see the Last 24 Hours pane that shows a preview of the most recent activities that have occurred.
The Last 24 Hours pane also displays the following information:
Number of running tasks
Number of successfully completed tasks
Number of tasks that are pending
Number of tasks that have failed
Towards the bottom of the pane is a link that takes you to the Job Log page where you can see more detailed information about all the tasks.
To use the Jog Log
- On the CloudPoint dashboard, in the Last 24 Hours panel, click Explore Job Log.
- Review the Job Log page.
The Job Log page displays a tabular list of all the tasks. Each log entry includes the following:
An icon that indicates the job status--whether completed successfully, completed with errors, failed, or in progress
The job name, includes details about the assets that are involved in the task
The job type
The job start time and the end time (if applicable)
- Use the filter and sorting tools as needed to locate the job you are interested in. You can filter the jobs based on the job type, job name, or job status.
- Click anywhere in a job row to see detailed information about that job. The Job Details pane on the right displays additional details.
A successful job appears as follows:
Depending on the type of job, the Job Details pane displays the following information:
The job type
A description of the job
A task ID that uniquely identifies the job
Job start time
Job end time (applicable only if the job has completed)
The time it took for the job to complete (applicable only if the job has completed)
A summary of the underlying tasks
The type of snapshot that was involved in the job (applicable only for create snapshot operations)
A failed job appears as follows:
For jobs that have failed, the Job Details pane also displays an error summary that indicates why a particular job has failed.
Note:
You may notice that the Job Log page displays several "delete snapshots of asset" messages on a regular basis. The frequency of such messages is higher especially during a policy run. However, do not be alarmed.
During every policy run, CloudPoint performs the delete snapshots task to verify and ensure that the retention count specified in the policy configuration is maintained. These messages do not indicate a user-initiated snapshot deletion case.