Forum Discussion

Rajesh_s1's avatar
Rajesh_s1
Level 6
11 years ago

V-Ray backups are impacting on SAP jobs

Hi friends,   Does anyone experience network connectivy issues on V-Ray backups. We have found that during snapshot quiesce time SAP jobs are getting failed. That is when ever V-Ray backups are...
7.6
Backup and Recovery
NetBackup
Troubleshooting
Windows Server (2003-2008)
  • Anonymous's avatar
    Anonymous
    11 years ago

    Let's rule out NetBackup...

     

    Perform a snapshot in the vSphere Client against the VM's in question.

    Wait 10-15 mins, just to assume some datachange in the VM and some data been written to the deltas.

    Then consolidate the snapshot - Delete ALL.

    During all this monitor SAP on the server.

    When do the jobs fail. Is it at the snapshot removal part. ie the VM could be getting stunned.

    Check the Event Viewer of the Windows box also.

    So if happens in the vSphere Client not a NetBackup issue.

     

    Interesting Note in VMware KB: A snapshot removal can stop a virtual machine for long time (1002836)

    Note: Beginning in ESXi 5.0, the snapshot stun times are logged. Each virtual machine's log file (vmware.log) will contain messages similar to:

    2013-03-23T17:40:02.544Z| vcpu-0| Checkpoint_Unstun: vm stopped for 403475568 us

    In this example, the virtual machine was stunned for 403475568 microseconds (1 second = 1 million microseconds).

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

    Some other considerations

    1. Make sure VM does not have any other snapshots (including hidden).
    2. Increase CPU reservations in the VM settings.
    3. Move snapshot location to a different datastore (via workingDir parameter), preferably backed by faster storage (for example, SSD disk).

     

    It is strange when this is an App server and not the DB so would not expect high I/O.

Anonymous's avatar
Anonymous
11 years ago

Let's rule out NetBackup...

 

Perform a snapshot in the vSphere Client against the VM's in question.

Wait 10-15 mins, just to assume some datachange in the VM and some data been written to the deltas.

Then consolidate the snapshot - Delete ALL.

During all this monitor SAP on the server.

When do the jobs fail. Is it at the snapshot removal part. ie the VM could be getting stunned.

Check the Event Viewer of the Windows box also.

So if happens in the vSphere Client not a NetBackup issue.

 

Interesting Note in VMware KB: A snapshot removal can stop a virtual machine for long time (1002836)

Note: Beginning in ESXi 5.0, the snapshot stun times are logged. Each virtual machine's log file (vmware.log) will contain messages similar to:

2013-03-23T17:40:02.544Z| vcpu-0| Checkpoint_Unstun: vm stopped for 403475568 us

In this example, the virtual machine was stunned for 403475568 microseconds (1 second = 1 million microseconds).

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

Some other considerations

1. Make sure VM does not have any other snapshots (including hidden).
2. Increase CPU reservations in the VM settings.
3. Move snapshot location to a different datastore (via workingDir parameter), preferably backed by faster storage (for example, SSD disk).

 

It is strange when this is an App server and not the DB so would not expect high I/O.