US 12,007,982 B2
Method and system for identifying and deleting records on hosts
Asif Khan, Bangalore (IN); Kenneth William Owens, Burlington (CA); Adrian Dobrean, Oakville (CA); Aneesh Kumar Gurindapalli, Vijayawada (CA); Vipin Kumar Kaushal, Bangalore (IN); Yasemin Ugur-Ozekinci, Oakville (CA); Shelesh Chopra, Bangalore (IN); and Gowtham Krishna Iyengar Srinivasa Rangan, Mysore (IN)
Assigned to EMC IP HOLDING COMPANY LLC, Hopkinton, MA (US)
Filed by EMC IP Holding Company LLC, Hopkinton, MA (US)
Filed on Jan. 27, 2021, as Appl. No. 17/160,353.
Prior Publication US 2022/0237177 A1, Jul. 28, 2022
Int. Cl. G06F 16/23 (2019.01)
CPC G06F 16/2379 (2019.01) [G06F 16/2358 (2019.01)] 10 Claims
OG exemplary drawing
 
1. A system for identifying and deleting records of hosts, comprising:
local data manager persistent storage; and
a local data manager executing on a host of the hosts programmed to:
identify a discovery event associated with the host and a record type of record types, wherein the record types comprise at least host component records associated with host components executing on the host, agent records associated with agents executing on the host, asset records associated with assets of host components executing on the host, and backup records associated with backups of the assets;
obtain, in response to identifying, all previously discovered records on the host associated with the record type from a host record repository, wherein a record of the host record repository comprises record information that specifies a host component identifier corresponding to a component of the host, a topology of the component, and contents of the component;
obtain discovered records associated with the record type and associated with the host;
after obtaining all discovered records and previously discovered records:
select a first previously discovered record of the previously discovered records;
make a first determination that the first previously discovered record does not match any discovered records of the discovered records and is not tagged with a soft delete tag or a hard delete tag; and
in response to the first determination:
tag the first previously discovered record with the soft delete tag;
make a second determination that additional records are included in the previously discovered records; and
in response to the second determination:
 select a second previously discovered record of the previously discovered records;
 make a third determination that the second previously discovered record is associated with the soft delete tag and does not match any of the discovered records; and
 in response to the third determination:
 make a fourth determination that the second previously discovered record exceeds a soft delete period; and
 in response to the fourth determination:
 tag the second previously discovered record with the hard delete tag; and
 notify a data manager of modifications to the previously discovered records.