Forum Discussion

printf7's avatar
printf7
Level 2
7 years ago

Issue with Netbackup and Windows server 2000 VM

Hello,

I'm an engineer about VMware.
I am wondering about Netbackup.

 

One of my clients use Netbackup and VMware system.

1 weeks ago, One of VMs (especially windows svr 2000) had an issue.

When Backup process was run, CPU was increased up to 95~100% on Windows svr 2000 VM.

However, Other VMs were okay at the same time. Windows Svr 2000 VM only had a problem.

 

Are there any case or solution that is related to my issue ?

 

Thanks

  • By the sounds of if, it seems that that agent-based backup is used.

    W2K has not been supported by Symantec/Veritas for many years. 

    Extract from  : Statement of Support for NetBackup 7.x and 8.x in a Virtual Environment:     
    Supported guest operating systems for VMware
    NetBackup for VMware supports virtual machine backup and recovery on all guest
    operating systems supported by VMware. To check VMware support for a particular
    operating system, consult the VMware Compatibility Guide.

    The only backup type that is supported for legacy Operating Systems is using the VMware policy type.
    This backup type is agentless. 
    All it requires is for vmtools to be installed so that a VMware-based snapshot can be taken at the beginning of the backup.

    Here is a good overview of how NBU for VMware works: 
    http://www.settlersoman.com/symantec-netbackup-for-vmware-features-and-integration/

    Please speak to your NBU admin to ensure that the correct backup method is used for VMs.

6 Replies

  • Which process is using the CPU ?

    As always the most important questrion is: Was changed from working to not working conditions

    • printf7's avatar
      printf7
      Level 2


      Backup isn't run everyday, so I couldn't check the Process.
      I should have checked process but I forgot when issue was happened.

      Okay, I'll try to find manual and tech notes.
      (But It was hard to find about WIN2000 issue)

      thanks,

      • Marianne's avatar
        Marianne
        Level 6

        By the sounds of if, it seems that that agent-based backup is used.

        W2K has not been supported by Symantec/Veritas for many years. 

        Extract from  : Statement of Support for NetBackup 7.x and 8.x in a Virtual Environment:     
        Supported guest operating systems for VMware
        NetBackup for VMware supports virtual machine backup and recovery on all guest
        operating systems supported by VMware. To check VMware support for a particular
        operating system, consult the VMware Compatibility Guide.

        The only backup type that is supported for legacy Operating Systems is using the VMware policy type.
        This backup type is agentless. 
        All it requires is for vmtools to be installed so that a VMware-based snapshot can be taken at the beginning of the backup.

        Here is a good overview of how NBU for VMware works: 
        http://www.settlersoman.com/symantec-netbackup-for-vmware-features-and-integration/

        Please speak to your NBU admin to ensure that the correct backup method is used for VMs.

  • More info please...
    Is this agentless VMware backup or MS-Windows policy using NBU agent in the VM?
    Which NBU version and ESX/vCentre version?
    Have you tried to take a VMware quiescent snapshot (outside of NBU)? What is the effect on the VM?
    • printf7's avatar
      printf7
      Level 2

       

      I'm a field engineer so It's hard to check all of things.

      On today, I checked the VM and Other some information.

      NBU Version : 7.5
      VM Version : 7
      VM CPU : 4 vCPU
      VM RAM : 4096 MB
      Guest OS : Windows Server 2000

      ESXi Version : 6.0 3620759
      vCenter Version : 6.0 3634794


      CPU Process is increased up to 95~100% while Backup process run.

      Win2000 VM looks high cpu usage in the vCenter.
      However, If I connect the VM by using console, CPU usage looks normal in the VM.

      I'm not sure whether it was Quiesce snapshot or not.

      It is MS-Windows policy using NBU agent in the VM