Backup Data Security Classification via Role-Based Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current backup solutions lack a scalable and flexible approach to data security classification, failing to accommodate diverse user roles and data types within organizations, and do not leverage global cloud-hosted backup options effectively.

Innovation Solution

An Information Handling System (IHS) that receives a backup policy with multiple profiles based on user roles, routing data to different storage locations according to specific backup rules, including on-premises and cloud storage, with the ability to configure backup strategies based on risk factors such as data criticality and sensitivity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a single backup configuration is used for all users, then device complexity is reduced, but adaptability to different user roles and data types deteriorates

Engineering Contradiction:
Improvebackup configuration complexityVSAvoidbackup strategy adaptability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The backup system segments users into different roles (executive, non-executive, service account) and applies different backup profiles to each role. This segmentation allows the system to handle diverse backup requirements without requiring complex individual configurations for each user, resolving the contradiction between simplicity and adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different backup profiles are assigned to different user roles based on their specific needs. Executive users receive profiles with enhanced security and availability settings, while non-executive users receive standard profiles. This local quality approach allows customization where needed while maintaining simplicity elsewhere.

Inventive Principle:
Principle #3Local quality

2Device complexity

If backup data is stored in a single location, then device complexity is reduced, but reliability of data recovery deteriorates

Engineering Contradiction:
Improvestorage architecture complexityVSAvoiddata recovery reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system segments backup storage into multiple locations including local storage and cloud-based storage. Different user roles are assigned to different storage locations based on their data criticality requirements, enabling reliable data recovery without overly complex storage architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A routing engine acts as an intermediary that automatically directs backup data to appropriate storage locations based on user role and data type. This intermediary simplifies the storage architecture by providing automated routing logic, while still achieving reliable data recovery through multi-location storage.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If extensive backup control options are provided, then adaptability to different user needs is improved, but ease of operation deteriorates

Engineering Contradiction:
Improvebackup configuration flexibilityVSAvoidbackup setup ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system provides universal backup profiles that serve multiple user roles within an organization. Each profile is designed to handle the common requirements of its target user group, providing adaptability without requiring complex individual configurations. This multi-functionality approach maintains ease of operation while meeting diverse backup needs.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Reliability

If multiple copies of data are stored across different locations, then reliability is improved, but loss of substance increases

Engineering Contradiction:
Improvedata availabilityVSAvoidstorage resource consumption
Core Design Contradiction:
ReliabilityVSLoss of substance

Solution Approach 1:

The system applies different replication strategies to different user roles based on their data criticality. Executive users whose data requires high availability receive multiple copies across different locations, while non-executive users receive fewer copies. This local quality approach optimizes storage resource consumption while maintaining necessary reliability levels.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10365975B2Backup data security classifcation
Publication Date: 2019.07.30 DELL PROD LP
  • US10365975B2 patent drawing
  • US10365975B2 patent drawing
  • US10365975B2 patent drawing

AI summary

Systems and methods for backup data security classification. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include one or more processors and a memory coupled to the one or more processors, the memory including program instructions stored thereon that, upon execution by the one or more processors, cause the IHS to: receive a backup policy that includes a plurality of backup profiles, where each of the plurality of backup profiles corresponds to a different user within an organization, and store a copy of electronic data associated with a given one of the different users according to a backup profile.