Forum Discussion

Riadh_R17's avatar
Riadh_R17
Level 5
4 months ago
Solved

invalid filelist specification(status 69) when backup vmware VM

Hi all

after migrating some VMs to a new 100To datastore (configured as same as the existing datastores and from the same array) we got the error message on the snapshot jobs of the migrated VMs 

 invalid filelist specification(status 69)

the VMs which been kept in original datastore continue backup successfully.

VMs are selected by tag query in the policy

we have deleted the vcenter than added it again in the credential but always the same issue

when we try to backup one of these VM with a test policy (manually selected) we got the error message 

The scheduler found that no backups are due (200)

netbackup version = 10

any help please, thanks in advance

  • Riadh_R17's avatar
    Riadh_R17
    7 days ago

    It was observed that the new datastore was configured with limits that prevented NetBackup from creating a snapshot and starting the backup.
    The limitation enforced a maximum file size within the datastore.
    When NetBackup attempted to create a snapshot prior to the backup, the snapshot creation failed because its size exceeded the configured limit.

    RESOLUTION: The limits were removed, and the backup is now functioning correctly.

7 Replies

  • Riadh_R17's avatar
    Riadh_R17
    Level 5
    7 days ago

    It was observed that the new datastore was configured with limits that prevented NetBackup from creating a snapshot and starting the backup.
    The limitation enforced a maximum file size within the datastore.
    When NetBackup attempted to create a snapshot prior to the backup, the snapshot creation failed because its size exceeded the configured limit.

    RESOLUTION: The limits were removed, and the backup is now functioning correctly.

  • kiyan's avatar
    kiyan
    Level 6
    4 months ago

    create a new policy and instead of tag, select one of the VMs's manually, does it work ?
    when you are validating the query, is it able to validate your query for migrated VM's (be specific for that datastore) is it finding migrated VMs?
    the 69 file list error is a general error(which ususally you will get on VMware jobs),what quebek​  provide you will get you more details on the root cause of the issue.

  • quebek's avatar
    quebek
    Moderator
    4 months ago

    Hey,

    What is your transport type? Is it SAN - did you discover these new LUNs of the new datastores on the vmware backup host?
    Try to rescan devices on the vmware backup host. You can tell in the policy to use NBD if SAN is not available...

     

    • Riadh_R17's avatar
      Riadh_R17
      Level 5
      4 months ago

      Hi quebek​ 

      Thanks for your answer.

      we use NBD

      we use the media server as a backup host  (appliance 5250 master/media)  could you please provide the commands to discover the new luns from netbackup media server?

      Thanks in advance :))

      • quebek's avatar
        quebek
        Moderator
        4 months ago

        Hello

        If you are using NBD than there is no need to discover LUNs as these are needed on SAN transport mode.
        In this situation I would have enabled VxMS logging, below are TN how to do it.

        https://www.veritas.com/support/en_US/doc/166027891-166028774-0/v23649764-166028774

        https://www.veritas.com/support/en_US/doc/21902280-127283730-0/v19546272-127283730