The impact of deleting client resource; when saveset records are deleted; index backup

It is pretty straight ...

1.  the impact of deleting a client resource.

a. When a client resource is deleted, will it cause any changes on its saveset tracking information in media database and CFI?

   No - simply because there could still be some valid save sets.

b. If the client ID of the deleted client resource is recorded, the deletion of the client resource will not cause any data loss, is it correct?

   This is impossible as you cannot delete the client ID by itself - it is a read-only variable being part of the client resource.

   Assuming that the client ID could be deleted, you could still recover the client resource from the bootstrap.

c. If the client ID is lost, is there anyway to restore the client ID?

   In fact if you scan the save set NW would also tell you the client ID found and if it differs from the client name/ID

   which probably does exist as client resource.

d. If a host system is decommissioned and its DNS entry is removed and its client resource is deleted from NMC, is it possible to restore file from its savesets which are still browsable thanks to long browse and retention policy?  If yes, what is the procedure?

   Simply fake NW by specifying an unused IP address in the hosts file.

   Worst case you need to scan the save sets if they still exist.

------------------------

2. How Networker deletes saveset records in the media database

We only use ddboost devices.  As stated in networker training material, nsrim would do the following things:

* Enforce browse and retention policy on the savesets

* Delete tracking information from CFI when a saveset changes from browsable to recoverable (or recyclable)

* Remove recycable savesets on file type devices.

a. Will nsrim delete tracking information from media database when nsrim removes recycable savesets?

    Of course - it does not make sense keep metadata if the save set is not available any longer.

b. If yes, is there any other process that delete saveset tracking information from media database?

    There a several processes commands which will/might impact the media index information, either directly or indirectly.

        - nsrck

        - nsrim

        - nsrmm -d -S

     the most important ones i just remember.

-----------------------

3. The retention for the Index backup

a. If client A generates one saveset in daily backup and the browse policy is 30 days, there will be 30 htime folders under clientA's CFI folder.  Is it correct?

    Not necessarily as these folders do not really represent a time stamp.

    The directory names depend on part of the ssid. But yes, it is most likely one directory per day.

b. When Index backup runs, it will back up clientA's CFI for all of 30 savesets.  Is it correct?

     No. Usually, CFI backups will have the same level as the data backups.

     Except for incremental backups. Here the CFI will be backed up with level 9 (differential).

c. Although a and b are not related to this one, it is my real question.  How does networker determine the retention for the index backup?  What is the default value of the index backup retention?

      As the index backup 'belong' to the NW server's client resource, the index retention is specified by its retention policy.

      Usually all clients should have the same values.

      However, NW will automatically never delete a single (index) save set but a whole backup cycle.

Thanks for your insight, bingo!