03 TCI2743 HCP Policies and Services v4-0

Operating and Managing
Hitachi Content
Platform v8.x
Policies and Services
© Hitachi Vantara LLC 2020. All Rights Reserved.

Module Objectives
 When you complete this module, you should be able to describe:

• RetUpon completion of ention and data protection compliance features
• Purpose of all Hitachi Content Platform policies and services
• Policies included in Object Metadata
• Scheduling of all HCP Services

Policies and Services
 Policies – part of system metadata

• Settings that influence transactions and services on objects
• Set at the object or namespace levels
• DPL, indexing, retention, shredding and versioning
 Services – schedule or run from system management console

• Background processes that iterate over objects
• Services run according to service schedule
• Enable or disable, start or stop at the system level

Policy Descriptions
Retention Shredding
 Prevents file deletion before retention  Ensures no trace of file is
May
May period expires recoverable from disk after
21
21
2036
 Can be set explicitly or inherited deletion
 Deferred retention option
 Can set a Retention Hold on any file Versioning
 New object version is created
Indexing when data changes
 Determines whether an object will be  Write Seldom Read Many
indexed for search (WSRM)
Custom metadata XML checking

 Determines whether HCP allows
custom metadata to be added to a
namespace if it is not well-formed
XML

Retention Policy
 Each object has a retention policy which:

• Determines how long an object must be kept
• Influences transactions and services on the object
• Has retention methods as:
 Special value
o Deletion allowed (0) Retention
o Deletion prohibited (-1), or Object policy:
o Initially unspecified (-2) • Retention
setting
 Offset: years, months, days • Retention
 Fixed date class
• Retention class: Named retention setting
Retention Hold
= true/false
 Retention hold
Shredding Policy
 Determines whether objects are shredded by the shredding service

when they are deleted
 Each object has its own shredding policy setting

• Indicates whether the object should be shredded
 Users and applications can see and modify shredding policy settings

Indexing Policy
 Indexing policy determines how the metadata query engine indexes

objects
 Indicates whether the metadata query engine should index custom

metadata for that object
• Each object has its own indexing policy setting
 Third-party applications can use this setting for their own purposes

Versioning Policy
 Versioning policy determines whether HCP can create multiple versions

of objects
 Policy is set at the namespace level and applies only to HCP

namespaces
 The versioning policy consists of two settings:

• Versioning setting, which is either on or off
• Version pruning setting, the amount of time HCP should wait after a version is
created before automatically deleting it

Custom Metadata XML Checking Policy
 Custom metadata XML checking policy determines whether HCP allows

custom metadata to be added to a namespace if it is not well-formed
XML
• This policy is set at the namespace level
 XML checking policy can have a setting of:

• Enabled – When custom metadata is added to or replaced in a namespace,
HCP checks whether it’s well-formed XML. If the XML is not well-formed,
HCP rejects it
• Disabled – HCP accepts any data submitted as custom metadata.

Active Learning Exercise: Raise Your Hands If
You Know It!
Are all policies set on an object level?
0 © Hitachi Vantara LLC 2020. All Rights Reserved.

Services
 You can disable or start specific services using the Services panel of
the System Management Console Overview page
Disable a service
Start a service

Default Service Schedule

Schedule Create and Edit

Service Descriptions
Capacity balancing Content verification

 Ensures distribution of available Object
 Ensures integrity of object by
storage remains roughly equivalent checking cryptographic hash value;
across all storage nodes repairs object if hash does not match
 User selectable hash algorithms
include SHA-1, 256, 384 or 512; MD5
and RIPEMD-160
Compression/Encryption
 Compresses object data, freeing Disposition
space for additional storage
 Deletes expired objects, service
disabled by default – use caution if
considering enabling on an existing
HCP with data

Garbage collection Duplicate elimination

 Deletes data and metadata left by  Find and inspect duplicates
incomplete operations  Remove duplicates but maintains
G  Reclaims storage for deleted integrity
objects
Shredding Scavenging
 Shreds deleted objects marked for  Ensures objects have valid metadata
shredding by detecting and repairing violations

Protection Replication
 Maintains set level of data  Creates copies of objects to
redundancy, as specified by DPL another system for recovery
for each namespace
 Can be set to maintain 1 to 4
internal copies depending on
value of data
Replication Verification Service

Indexing
 Replication Verification Service
 Prepares objects to be indexed (RVS), checks that objects are
and found by specified criteria being properly replicated as
through the Search console specified in the service plan.
 Continually processes new
objects and metadata changes

Geographically Distributed Data Protection
 Geo-protection is implemented by the HCP replication service
 The replication service is responsible for keeping tenants and

namespaces on two or more HCP systems in sync with each other
 Geo-protection offers several benefits:

• If a system in a replication topology suffers irreparable damage, a remote
system can serve as a source for disaster recovery
• If multiple HCP systems are widely separated geographically, each system
may be able to provide faster data access for some applications than the
other systems can

Active Learning Exercise: Follow the Manual
To get detailed information about modifying or monitoring the services -

refer to the HCP System Management Help
In particular, search for “service precedence”

Module Recap
 Policies – part of system metadata

• DPL, indexing, retention, shredding and versioning
 Services – schedule or run from System Management Console

• Background processes that iterate over objects
• Weekly schedule may be customized to accommodate other production
operations
 Geo-protection is implemented by the HCP replication service

• Keep tenants and namespaces on two or more HCP systems in sync

Questions and
Discussion

Module Review
1. Retention is a service that runs on a daily schedule. (True or False)
2. Services may run manually from the Tenant Management Console. (True or False)
3. Replication Service runs in a different user configurable schedule. (True or False)
4. The following policies are applied to the namespace level, not the object:
a) Versioning
b) Custom metadata XML checking
c) Shredding
d) a and b
e) b and c

03 TCI2743 HCP Policies and Services v4-0

Uploaded by

Copyright:

Available Formats

03 TCI2743 HCP Policies and Services v4-0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

03 TCI2743 HCP Policies and Services v4-0

Uploaded by

Copyright:

Available Formats

Operating and Managing

Policies and Services

© Hitachi Vantara LLC 2020. All Rights Reserved.

 When you complete this module, you should be able to describe:

© Hitachi Vantara LLC 2020. All Rights Reserved.

 Policies – part of system metadata

 Services – schedule or run from system management console

© Hitachi Vantara LLC 2020. All Rights Reserved.

Custom metadata XML checking

© Hitachi Vantara LLC 2020. All Rights Reserved.

 Each object has a retention policy which:

 Determines whether objects are shredded by the shredding service

 Each object has its own shredding policy setting

© Hitachi Vantara LLC 2020. All Rights Reserved.

 Indexing policy determines how the metadata query engine indexes

 Indicates whether the metadata query engine should index custom

© Hitachi Vantara LLC 2020. All Rights Reserved.

 Versioning policy determines whether HCP can create multiple versions

 Policy is set at the namespace level and applies only to HCP

 The versioning policy consists of two settings:

© Hitachi Vantara LLC 2020. All Rights Reserved.

 Custom metadata XML checking policy determines whether HCP allows

 XML checking policy can have a setting of:

© Hitachi Vantara LLC 2020. All Rights Reserved.

0 © Hitachi Vantara LLC 2020. All Rights Reserved.

1 © Hitachi Vantara LLC 2020. All Rights Reserved.

2 © Hitachi Vantara LLC 2020. All Rights Reserved.

3 © Hitachi Vantara LLC 2020. All Rights Reserved.

Capacity balancing Content verification

4 © Hitachi Vantara LLC 2020. All Rights Reserved.

Garbage collection Duplicate elimination

5 © Hitachi Vantara LLC 2020. All Rights Reserved.

Replication Verification Service

6 © Hitachi Vantara LLC 2020. All Rights Reserved.

 Geo-protection is implemented by the HCP replication service

 The replication service is responsible for keeping tenants and

 Geo-protection offers several benefits:

7 © Hitachi Vantara LLC 2020. All Rights Reserved.

To get detailed information about modifying or monitoring the services -

In particular, search for “service precedence”

8 © Hitachi Vantara LLC 2020. All Rights Reserved.

 Policies – part of system metadata

 Services – schedule or run from System Management Console

 Geo-protection is implemented by the HCP replication service

9 © Hitachi Vantara LLC 2020. All Rights Reserved.

0 © Hitachi Vantara LLC 2020. All Rights Reserved.

1. Retention is a service that runs on a daily schedule. (True or False)

3. Replication Service runs in a different user configurable schedule. (True or False)

1 © Hitachi Vantara LLC 2020. All Rights Reserved.

You might also like