반응형

"  Failed to launch STORIX stmakeboot command "



 

 

 

 

NVBU BMR Plugin 설치 시 (only Linux) 후 백업 실패 " Failed to launch STORIX stmakeboot command "

 

genisoimage package 를 설치해 준다~.  cf) mkisofs

 

#yum install -y genisoimage*

 

End.

 

Posted by IT 사랑 :
반응형

 

 

cf ) http://support.unitrends.com/ikm/questions.php?questionid=806 

 

 

VSS Writer Failures Due To Multiple VSS Providers

Purpose

To help support engineers identify and rectify failures which occur in VSS due to another VSS provider being present in the system.

Description

VSS errors are common when investigating the failure of a backup/restore process.  Errors which arise due to an additional VSS provider being present will often be indicated by one or more of the following errors:

System shows errors such as:

(VSS_E_SNAPSHOT_SET_IN_PROGRESS) Another shadow copy creation is already in progress. Please wait a few moments and try again.
Please check Windows Events Log that Volume Shadow Copy Service and VSS Writers are operating properly.

USnapCreate: USNAPError! Could not create snapshot, error -1.
: Unitrends agent was not able to create Volume Shadow Copy.
: To resolve this issue review the Event logs for any potential VSS errors and application specific Writer failures.

 

When initiating a check of the Windows Event Viewer Logs, further evidence may be demonstrated by the following:

Event Type:     Error
Event Source:     VSS
Event Category:     None
Event ID:     1
Date:          9/12/2012
Time:          1:56:29 PM
User:          N/A
Computer:     SQL-SERVER
Description:
Volume Shadow Copy Service initialization error: the control dispatcher cannot be started [0x80070427].


 

 

Event Type:     Error
Event Source:     VSS
Event Category:     None
Event ID:     12292
Date:          9/14/2012
Time:          12:42:45 PM
User:          N/A
Computer:     SQL-SERVER
Description:
Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {5fc845eb-f299-40f0-9725-34045f7ea8ba} [0x80040154].

Event Type:     Error
Event Source:     VSS
Event Category:     None
Event ID:     20
Date:          9/14/2012
Time:          12:42:45 PM
User:          N/A
Computer:     SQL-SERVER
Description:
Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered.  This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider.  The error returned from CoCreateInstance on class with CLSID {5fc845eb-f299-40f0-9725-34045f7ea8ba} and Name HWPRV is [0x80040154].

Cause

This particular combination of errors from the RRC logs and from the Windows System Event Viewer Logs support the fact that an additional VSS provider may be present on the system in question.  This can be further substantiated by checking the Windows system by using vssadmin list providers.  


 

 

The report should show more than one provider, such as:

C:\Documents and Settings\administrator.LIGHTHOUSE>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

Provider name: 'Acronis VSS HW Provider'
   Provider type: Hardware
   Provider Id: {f5dbcc43-b847-494e-8083-f030501da611}
   Version: 1.0

This indicates that at one time or another, the system had an Acronis product installed.  Even though the product may have been removed, some of Acronis' registry keys are known to linger on systems indefinitely.  The keys MUST be removed in order to remove the additional provider from the system.  This particular combination of errors from the RRC logs and from the Windows System Event Viewer Logs support the fact that an additional VSS provider may be present on the system in question.  This can be further substantiated by checking the Windows system by using vssadmin list providers.  The report should show more than one provider, such as:

C:\Documents and Settings\administrator.LIGHTHOUSE>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

Provider name: 'Acronis VSS HW Provider'
   Provider type: Hardware
   Provider Id: {f5dbcc43-b847-494e-8083-f030501da611}
   Version: 1.0

This indicates that at one time or another, the system had an Acronis product installed.  Even though the product may have been removed, some of Acronis' registry keys are known to linger on systems indefinitely.  The keys MUST be removed in order to remove the additional provider from the system.  This particular combination of errors from the RRC logs and from the Windows System Event Viewer Logs support the fact that an additional VSS provider may be present on the system in question.  This can be further substantiated by checking the Windows system by using vssadmin list providers.  The report should show more than one provider, such as:

C:\Documents and Settings\administrator.LIGHTHOUSE>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

Provider name: 'Acronis VSS HW Provider'
   Provider type: Hardware
   Provider Id: {f5dbcc43-b847-494e-8083-f030501da611}
   Version: 1.0

This indicates that at one time or another, the system had an Acronis product installed.  Even though the product may have been removed, some of Acronis' registry keys are known to linger on systems indefinitely.  The keys MUST be removed in order to remove the additional provider from the system.  

Resolution

To accomplish this, the following steps may be used:

  1. Using the first character string of the Provider Id (i.e. f5dbcc43 from the above example), perform a search in Windows Registry (regedit.exe) for keys showing the full ID string.
  2. Delete each of those keys as they are discovered.
  3. Close registry, reboot if desired


Once the key deletions are complete, re-run vssadmin list providers.  Microsoft Software Shadow Copy Provider should be the only provider showing.  This will then allow the Unitrends system to perform backups and restores without complication from an additional VSS provider.

Posted by IT 사랑 :
반응형

www.quest.com

Title

  • How to build a VaultOS 6.0 boot CD
  • Description

    How to build a VaultOS 6.0 boot CD

  • Resolution

    The VaultOS boot CD is required in order to do offline backups and restores. Whilst backups can be online, restores will not be and the installation requires that the boot CD is created and tested before online backups commence.

    The VaultOS CD can be built on any machine running Windows and that machine does not have to be involved in the BMR backup (some restrictions on versions exist, see the Microsoft AIK requirements).

    1)  When you install the NetVault Bare Metal Recovery 4.0.9 Plug-in Server for Windows, the two files nvbmrisocreate.exe and nvbmriso.pkg are installed on the Netvault\util directory of the NetVault server machine . (these two files get installed when installing the Plug-in Server).   Or you may have received an nvbmrisocreate.zip file that contains these files. Note that nvbmrisocreate.zip does not include Microsoft code that is required which is why step 2 is...

    2) Download the Microsoft AIK from http://www.microsoft.com/download/en/details.aspx?id=5753 The AIK ISO can be burned to a DVD or if a virtual machine is used to build the disk image, the ISO can be mounted in the cd drive of the virtual machine. At this point install the AIK on the machine where the VaultOS ISO is going to be built.
     

    3) On the same machine, unpack the nvbmrisocreate.zip to get "nvbmrisocreate.exe" and "nvbmriso.pkg"

    4) To combine the Quest and Microsoft code to produce a bootable CD iso image in the C:\ dir, run the following command...
    c:\...\> nvbmrisocreate.exe nvbmriso.pkg "C:\Program Files\Windows AIK" C:\VaultOS_Boot.iso

    The VaultOS ISO can now be burned to CD or moved to a safe location if it is to only be used to start virtual machines and the Microsoft AIK can be uninstalled if necessary.

 

Installed it. -->  NetVault Bare Metal Recovery 4.0.9 Plug-in Server for Windows,

 

 

 

 

 

 

 

 

 

 

C:\Program Files\Quest Software\NetVault Backup\util>nvbmrisocreate.exe nvbmriso.pkg "C:\Program Files\Windows AIK" "C:\bmr_output.is
Argv [1]: nvbmriso.pkg
Argv [2]: C:\Program Files\Windows AIK
Argv [3]: C:\bmr_output.iso

ImageX Tool for Windows
Copyright (C) Microsoft Corp. All rights reserved.
Version: 6.1.7600.16385

Mounting: [C:\quest_bmr\output\ISO\sources\boot.wim, 1] -> [C:\quest_bmr\mp]...

[ 100% ] Mounting progress

Successfully mounted image.

Total elapsed time: 26 sec

 


작업을 완료했습니다.
작업을 완료했습니다.
작업을 완료했습니다.
작업을 완료했습니다.
작업을 완료했습니다.
작업을 완료했습니다.

ImageX Tool for Windows
Copyright (C) Microsoft Corp. All rights reserved.
Version: 6.1.7600.16385

Committing: [C:\quest_bmr\mp]...

[ 100% ] Committing Image progress

Successfully committed image.

Unmounting: [C:\quest_bmr\mp]...


[ 100% ] Mount cleanup progress

Successfully unmounted image.

Total elapsed time: 25 sec

 

 

OSCDIMG 2.55 CD-ROM and DVD-ROM Premastering Utility
Copyright (C) Microsoft, 1993-2007. All rights reserved.
Licensed only for producing Microsoft authorized content.


Scanning source tree
Scanning source tree complete (4 files in 3 directories)

Computing directory information complete

Image file is 137322496 bytes

Writing 4 files in 3 directories to C:\bmr_output.iso

100% complete

Final image file is 137322496 bytes

Done.

C:\Program Files\Quest Software\NetVault Backup\util>

 

 

Done.. After created iso file.

 


Posted by IT 사랑 :