BMR LINUX 복구

2015. 3. 13. 01:08

보호되어 있는 글입니다.
내용을 보시려면 비밀번호를 입력하세요.

반응형

 

 

Thank you for contacting Dell Software, I have taken ownership of your Service Request Number 2592836 - RDA ERROR CODE 38.

 

Looking through your logs... I see Error Code 38, which means "No buffer space available "... I also see an Error that you're Hard Drive is at 90% used... which means you're running out of disk space and NetVault will on it's own, stop running when it reaches 95% used disk space.  Also, double check your Read/Write rights... to Drive "D".

 

 

Posted by IT 사랑 :

BMR Boot System AIK ADK

2014. 1. 2. 20:49 from Data Protection
반응형

 

BMR Boot System part ~

 

 

cf) www.quest.com  

 

Quest® NetVault®
Bare Metal Recovery Plug-ins
User’s Guide

 

 

 

3.3.2.a Creating a Linux-Based Boot System

Requirements

The following items are required for this procedure:

 VaultOS ISO image (obtained via download)

 A writable DVD and CD-ROM drive

 A blank DVD and CD

 DVD- and CD-generation software

Creation Procedure

Note: Quest Software recommends that all applications running on the machine

performing this operation be shut down before starting this procedure.

1. Download Plug-in Offline Client, VaultOS from the Quest Software web site.

2. Note the name and location of this file (for example,

/home/vaultos_x86_vxxx.zip” where xxx represents the software version

number).

3. Insert a blank CD in the writable drive.

4. Create a new CD with the CD-generation software using the

vaultos_x86_vxxx.iso” file.

For details on this procedure, refer to the relevant documentation for the CDgeneration

software in use.

3.3.2.b Creating a Windows PE-Based Boot System

Requirements

You can complete this process on any Windows system for which the following

requirements are met:

 Windows Assessment and Deployment Kit (ADK) for Windows 8

(obtained via download)

 Windows 2008 R2, Windows 2012, Windows 7, or Windows 8 system

 “NetVault Bare Metal Recovery ISO Builder for Plug-in Offline Client for

Windows” file (located on the Quest NetVault Backup Installation CD or

downloaded from the Quest Software web site)

 A writable DVD and CD-ROM drive

 A blank DVD and CD

 DVD- and CD-generation software

 

Creation Procedure

Note: Quest Software recommends that all applications running on the machine

performing this operation be shut down before starting this procedure.

1. Download the Windows ADK for Windows 8 from the following link:

http://www.microsoft.com/en-us/download/details.aspx?id=39306

http://www.microsoft.com/en-us/download/confirmation.aspx?id=39982

2. Install the Windows ADK on a Windows 2008 R2, Windows 2012, Windows

7, or Windows 8 system.

You can use the default directory (C:\Program Files (x86)\Windows Kits\8.0)

or another directory of your choosing.

Important: Installation of Windows ADK also installs Microsoft .NET Framework if

it is not already installed. After .NET Framework is installed, the system is

automatically restarted.

3. Extract the “NetVault Bare Metal Recovery ISO Builder for Plug-in Offline

Client for Windows” file to the Windows ADK machine.

This creates two files, “nvbmrisocreate.exe” and “nvbmriso.pkg.”

4. Make sure that the path to where you intend to create the ISO image exists.

If the directory does not exist when you execute the next step, the ISO image

will not be created.

5. To create the Windows PE ISO image, navigate to the directory that contains

the extracted “nvbmrisocreate.exe” file, type the following at the command

prompt, and press Enter:

The following list describes what you can specify for each option:

 /TYPE – If you are working with an earlier version of the Plug-in Offline

Client, enter WAIK for Windows Automated Installation Kit (AIK). If you

are using version 6.1 or later, you can enter ADK.

 /PKG – Enter the full path and file name for the Plug-in Offline Client .pkg

file that you downloaded separately.

 /DIR – Enter the full path to the location of the Windows AIK or ADK

directory.

 /OUT – Enter the path where the bootable ISO image should be created.

Example:

6. Insert a blank CD in the writable drive.

 

C:\NVBMR\nvbmrisocreate_6.1.4>nvbmrisocreate.exe

/TYPE:WAIK

/PKG:"C:\NVBMR\nvbmrisocreate_6.1.4\nvbmriso.pkg"
/DIR:"C:\Program Files\Windows AIK" /OUT:"E:\temp\bmr.iso"

 

ImageX Tool for Windows

Copyright (C) Microsoft Corp. All rights reserved.

Version: 6.1.7600.16385

 

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

 

è  ENTER

 

 

C:\NVBMR\nvbmrisocreate_6.1.4>nvbmrisocreate.exe  /TYPE:WAIK /PKG:"C:\NVBMR\nvbmrisocreate_6.1.4\nvbmriso.pkg" /DIR:"C:\Program Files\Windows AIK" /OUT:"E:\temp\bmr.iso"

 

ImageX Tool for Windows

Copyright (C) Microsoft Corp. All rights reserved.

Version: 6.1.7600.16385

 

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

 

[ 100% ] Mounting progress

 

Successfully mounted image.

 

Total elapsed time: 16 min 36 sec

 

 

 

 

작업을 완료했습니다.

작업을 완료했습니다.

작업을 완료했습니다.

작업을 완료했습니다.

작업을 완료했습니다.

작업을 완료했습니다.

 

ImageX Tool for Windows

Copyright (C) Microsoft Corp. All rights reserved.

Version: 6.1.7600.16385

 

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

[   0% ] Committing Image progress

 

 

Posted by IT 사랑 :
반응형

Date - May 2009
Affected Product Version - NVBU 8.x
Affected Module & Version - NA
OS Version - All
Application Information - NA

Description:
You may be requested to run this utility by support. This command performs an integrity check of the NetVault Media database, which include checks on:

a) Raw file structure
b) Database table integrity
c) Inter-table references and dependencies:

Solution/Workaround/Procedure:

On the Netvault server:
1) Run a NetVault database backup without the check database option selected.
2) Stop the Netvault services
3) Open a command prompt and navigate ~netvault/util
4) Run the command:

nvmedddbcheck check
you can also redirect the output to a file:
nvmeddbcheck check > nvmedcheck.log

The nvmeddbcheck command can take one of the following arguments:
- check: Just performs database checks
- compact: Performs the database checks, fixes faults identified during the check phase, and compacts the database
- Force: Checks, fixes and compacts the database regardless of the last
successful backup.
- list: Prints a line of output for every backup record, new stream, old stream, session, segment, media, and backup index in the database. This is particularly useful in order to determine what records should be deleted.

 

www.quest.com

'Data Protection > NetVault Backup' 카테고리의 다른 글

RDA PLUGIN  (0) 2015.03.13
N MEDIA :=  (0) 2014.09.23
[APM:ORACLE] ORACLE ONLINE BACKUP FAILURE  (0) 2013.12.03
[BMR]] Error "Failed to launch STORIX stmakeboot command"  (0) 2013.12.01
[BMR] LINUX mkisofs  (0) 2013.11.29
Posted by IT 사랑 :
반응형

First

 

Thanks a lot. You're been a big help!!

 

very good! Michael g...^^ 

 

 

 

Hello Rich,

 

Its not possible to run the same exact instance of SmartDisk on two systems, like copy all files from A machine to B machine. Internal datastructures in SmartDisk are unique to the machine.

 

The best option for what you want to do is SmartDisk replication function. This is controled by NetVault Backup. It is basically an intelligent DataCopy job from SmarDisk A machine to SmartDisk B machine. It understands data is deduplicated smartdisk, so only copies the unique chunks. Its very fast. See section 5.5.7, pg 117. "Use Optimised Replication between Devices that Support this Feature"

 

http://us-downloads.quest.com/Repository/support.quest.com/NetVault%20Backup/9.2/Documentation/NetVaultBackup_9.2_AdministratorsGuide.pdf

 

Even better is DR4100. THese things are great.

 

 

 

 

 

Posted by IT 사랑 :
반응형

NVBU ORACLE APM 백업 실패 .

 

파일 백업 문제 없으나 오라클 온라인 백업은 실패 됨.

 

의심 1!

 

 

 

 

ACTIVE 를 -- >  NOT ACTIVE   변경해 주자!

 

 

'Data Protection > NetVault Backup' 카테고리의 다른 글

N MEDIA :=  (0) 2014.09.23
nvmeddbcheck  (0) 2013.12.18
[BMR]] Error "Failed to launch STORIX stmakeboot command"  (0) 2013.12.01
[BMR] LINUX mkisofs  (0) 2013.11.29
[BMR] VSS provider VS acronis VSS provider  (0) 2013.11.29
Posted by IT 사랑 :
반응형

"  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 사랑 :
반응형

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The “mkisofs” utility installed and available on all Linux NVBMR
Clients – The plug-in requires that this component be installed to allow for
the creation of “.iso” CD creation files from any potential Linux NVBMR
Clients. This component may not be automatically available with all
installations of Linux.
The following command can be issued from a terminal session launched from
most versions of Linux to verify that this component is installed:
rpm -qa | grep mkisofs
If the component does not exist on an intended Linux NVBMR Client, it can
be obtained and installed as follows:

a. Access your copy of the Linux installation media, and locate the
mkisofs*.rpm” file.
b. With this file available on the NVBMR Client (that is, via copying the file or
direct download), open a terminal session, and navigate to the location of
the file.
c. Input the following command to initiate the installation, and follow the
install prompts as they appear:
rpm -i <installation_file_name>

 

 

 

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 사랑 :
반응형

 

Posted by IT 사랑 :