Skip to main content
All CollectionsKnowledge BaseEnterprise WorkloadsTroubleshooting - Enterprise Workloads
VM backup stalled with the error "got exception while parsing LCN and size from ntfscluster command” after a successful snapshot
VM backup stalled with the error "got exception while parsing LCN and size from ntfscluster command” after a successful snapshot
Updated over a week ago

This article applies to:

  • OS: Windows server

  • Product edition: Phoenix

Problem description

Virtual Machine (VM) backup stops progressing after a successful snapshot creation and gives error “Got exception while parsing LCN and size from ntfscluster command”. The scheduled backups fail as "Backup Window Expired" and Manual (Backup Now) backups will be successful.

Cause

This can occur when the backup job takes long time to parse and process pagefile.sys and hiberfil.sys files.

Traceback

[ERROR] Got exception while parsing LCN and size from ntfscluster command: invalid literal for int() with base 10: '0x80'
[ERROR] Got exception while parsing LCN and size from ntfscluster command: invalid literal for int() with base 10: 'VCN'

Resolution

Let the Phoenix backup proxy back up the entire hiberfil.sys and pagefile.sys as is. To allow that, set VMWARE_EXCLUDE_FILTER to False in the Phoenix.cfg file using the below steps.

  1. Open the terminal and stop Agent Client Service.

    Agent Version 6.x.x: /etc/init.d/Phoenix stop

    ​Agent Version 7.x.x: service Druva-EnterpriseWorkloads stop

  2. Verify if any Druva or Phoenix related processes.

    Agent Version 6.x.x: ps -ef| grep -i Phoenix

    Agent Version 7.x.x: ps -ef | grep -i EnterpriseWorkloads

  3. If any process is still found running, kill the process with the following command:

    Kill -9 <process id>

  4. Take a backup of the Configuration File

    Agent Version 6.x.x: /etc/Phoenix/FS/Phoenix.cfg

    Agent Version 7.x.x: /etc/Druva/EnterpriseWorkloads/vmware/VMwareConfig.yaml

  5. Edit Phoenix.cfg/VMwareConfig.yaml file using vi editor using below command

    Agent Version 6.x.x:

    vi Phoenix.cfg

    Type ‘ i ‘ to activate insert mode

    Add the following line to the configuration file:

    VMWARE_EXCLUDE_FILTER = False

    Agent Version 7.x.x:

    vi VMwareConfig.yaml

    Type ‘ i ‘ to activate insert mode

    change the value of parameter from

    vmware_exclude_filter = true

    To
    vmware_exclude_filter = false

  6. Type esc key followed by :wq to save and exit file.

  7. Then again Open the terminal and start Agent Client Service.

    Agent Version 6.x.x: /etc/init.d/Phoenix start

    Agent Version 7.x.x: service Druva-EnterpriseWorkloads start

  8. Initiate the backup job.


💡 Tip

When you set VMWARE_EXCLUDE_FILTER to False in the Phoenix.cfg file, back up the pagefile.sys and hiberfil.sys files as it is without compression and deduplication. Otherwise, if Phoenix is able to parse the files then they are compressed and further deduplicated to save the storage space. Storage utilization for this resource is expected to increase a bit with the above steps.


Verification

Again trigger the backup job and it should complete successfully.

See also

Did this answer your question?