Go to main content

Contents

Title and Copyright Information

Preface

1 Introduction

2 Installing and Configuring SPM

3 Storage Plan Manager Operations

4 Frequently Asked Questions

What should be done if no SPM actions are being generated?
What should be done if only Storage actions are being generated?
What should be done if SPM actions are generated but are never executed (they stay in the Scheduled state)?
What should be done if SPM actions always Fail Long?
Why are SPM actions removed from the SPM Actions List?
Why does the Start At time not update when an SPM action is rescheduled?
Why are copies being recreated on the disk after a Delete Instance?
What are the different components of SPM?
It appears that sometimes not all components start as part of SPM. What, if anything, controls whether a given component starts, and how do I tell if the DSM Controller is started since it is now integrated with SPM?
SPM appears to communicate only with the Oracle Database and the Manager (through DIVArchive API calls). Does SPM interact with any other processes?
Is SPM event driven, or does it purely repeat some looped processing of slots and rules or database query results?
Is SPM stateful across restarts?
An archived object can only belong to a single Storage Plan. When an object is first archived, DIVArchive Manager appears to archive to the default media for the corresponding Storage Plan, or the next-best media if the default media is not available for some reason. Is this correct?
What are the meanings of the DATARCHIVED, DATELASTUPDATE, and DATENEXTUPDATE properties for objects under SPM?
A newly archived object appears to have its DATELASTUPDATE and DATENEXTUPDATE fields set to the same value as DATEARCHIVED automatically by DIVArchive independent of SPM. Is this correct?

A DIVArchive Options and Licensing

B Default SPM Configuration Files and Parameters

Glossary