The answer to your question depends on the specific backup tool and datastore configuration, but in general, there are two possible scenarios:

1. Backups remain, but are unavailable:

    If the datastore was simply removed as a location for storing backups, but the backups themselves were not explicitly deleted, they might still exist on another datastore used by the backup tool. However, you wouldn't be able to access or restore them unless the datastore is reconnected or the backup tool allows for finding backups across different locations.

2. Backups are also deleted:

    If the backup tool is configured to automatically remove backups associated with deleted datastores, then the VM backups might also be deleted along with the datastore. This is more likely if the datastore was an integral part of the backup job configuration.

The terms "backup section" and "backup repositories" can have different meanings depending on the specific software or context you're referring to. However, here's a general explanation of the potential differences:

Backup section:

    Typically refers to a user interface or menu within a system where you manage backup settings and operations.
    This section might allow you to:
        Configure backup jobs, specifying what data to back up, how often, and where to store it.
        Schedule backup tasks and view past backup runs.
        Monitor the status of backups and review logs.
        Manage backup retention policies, deciding how long to keep backup copies.

Backup repositories:

    Define the physical or virtual locations where backup data is actually stored.
    These repositories can be various types, including:
        Local disks on the system itself.
        Network-attached storage (NAS) devices.
        Cloud storage services.
        Tape drives or other offline media.

Relationship between the two:

    The backup section usually lets you define and configure one or more backup repositories.
    You specify which repository each backup job should use to store its data.
    The backup section communicates with the selected repositories to perform backup and restore operations.

The answer to your question depends on the specific backup tool and datastore configuration, but in general, there are two possible scenarios:

1. Backups remain, but are unavailable:

    If the datastore was simply removed as a location for storing backups, but the backups themselves were not explicitly deleted, they might still exist on another datastore used by the backup tool. However, you wouldn't be able to access or restore them unless the datastore is reconnected or the backup tool allows for finding backups across different locations.

2. Backups are also deleted:

    If the backup tool is configured to automatically remove backups associated with deleted datastores, then the VM backups might also be deleted along with the datastore. This is more likely if the datastore was an integral part of the backup job configuration.

The terms "backup section" and "backup repositories" can have different meanings depending on the specific software or context you're referring to. However, here's a general explanation of the potential differences:

Backup section:

    Typically refers to a user interface or menu within a system where you manage backup settings and operations.
    This section might allow you to:
        Configure backup jobs, specifying what data to back up, how often, and where to store it.
        Schedule backup tasks and view past backup runs.
        Monitor the status of backups and review logs.
        Manage backup retention policies, deciding how long to keep backup copies.

Backup repositories:

    Define the physical or virtual locations where backup data is actually stored.
    These repositories can be various types, including:
        Local disks on the system itself.
        Network-attached storage (NAS) devices.
        Cloud storage services.
        Tape drives or other offline media.

Relationship between the two:

    The backup section usually lets you define and configure one or more backup repositories.
    You specify which repository each backup job should use to store its data.
    The backup section communicates with the selected repositories to perform backup and restore operations.