Results 1 to 7 of 7

Thread: Overview of Backup Initialization of VM

  1. #1
    Join Date
    May 2009
    Posts
    2,865

    Overview of Backup Initialization of VM

    Hi everyone,
    I have recently started learning with the virtual machines. So I am not having much knowledge about it. I want to know about the back up process that takes place in virtual machines. So I am expecting some help about an overview of backup initialization of virtual machines. Please provide some detailed information about the same.!!

  2. #2
    Join Date
    Aug 2006
    Posts
    122

    Re: Overview of Backup Initialization of VM

    An IVssBackupComponents object can Be Used for only one backup. Therefor, a requester must-through shall proceed to the end of the backup, Including IVssBackupComponents releasing the interface. If the backup Needs to terminate prematurely, the requester Needs to Call IVssBackupComponents: AbortBackup And Then release the IVssBackupComponents object. Do Not Attempt to resume the IVssBackupComponents interface. Typically, a requester's Backup Components Document IS initialized as empty. A Stored Backup Components Document can Be When loaded IVssBackupComponents: InitializeForBackup IS called, in support of portable Typically Windows clipboard shadow volumes. In this case, the writer-requester Communication Will Be Somewhat different.
    In the end, we will remember not the words of our enemies, but the silence of our friends.
    -Martin Luther King Jr.

  3. #3
    Join Date
    Aug 2006
    Posts
    173

    Re: Overview of Backup Initialization of VM

    To add to the volume shadow copy set, a requester must first set the context for the shadow copy by calling transaction IVssBackupComponents: setContext . If This Is Not Called method, the default context for shadow copies, VSS_CTX_BACKUP, IS used. To begin the completion of Its setup Prior to backup, a requester must call IVssBackupComponents: SetBackupState . By doing this, a requester Indicates to the writers :
    • The type of backup (as defined \ in VSS_BACKUP_TYPE )
    • Whether the backup system includes a bootable state
    • Whether the requester supports the selection of components or individual "backs up CF firefighters volumes.
    "Let us remember that our interest is in concord, not conflict, and that our real eminence rests in the victories of peace, not those of war." -McKinley

  4. #4
    Join Date
    Aug 2006
    Posts
    121

    Re: Overview of Backup Initialization of VM

    All requesters participantes en backup and restore operations must Always call IVssBackupComponents: GatherWriterMetadata . This method initials requester communication by writer-Generating a VSS Identify event, in response to Which Creates a writer ITS metadata document. Prior to calling IVssBackupComponents: GatherWriterMetadata , a requester year Has Opportunity to enable or disable certain Explicitly Specifying writers and writer classes using IVssBackupComponents: EnableWriterClasses , IVssBackupComponents: DisableWriterInstances , and IVssBackupComponents: DisableWriterClasses (by default, all classes are Enabled). After IVssBackupComponents: GatherWriterMetadata IS called, thesis calls Have No Effect.
    Whats my name again? I spend so much time looking at code i fogot my own name ahhh!

  5. #5
    Dr. V Guest

    Re: Overview of Backup Initialization of VM

    In response to Identify the event, EACH calls VSS writer's virtual handler method, CVssWriter: OnIdentify . A Writer Creates ITS Writer Metadata Document by Overriding the default implementation of CVssWriter: OnIdentify and using the IVssCreateWriterMetadata interface. Note That Other applications Than the current requester (for instance, system applications) can generate events Identify That Must Be Handled By The Writer. In addition, There is No way for a writer to determine From Within CVssWriter: OnIdentify Which Has application generated the Identify event.

  6. #6
    Join Date
    Nov 2005
    Posts
    1,203

    Re: Overview of Backup Initialization of VM

    Instead, CVssWriter: OnIdentify Perform a "should consist algorithm to create the writer's Writer Metadata Document, particularly after a writer Because Create the document, the requester Neither the writer nor can modify it. From this point forward, it Is a read-only document. This Means That the number and type of components associated with a writer, Which files are part of Each component, and the explicit exclusion of files from backup or restore operations Can not Be changed after a writer returns from processing Identify the event. All writers participante with VSS are required to do the Following :
    • Indicate a restore method for all components managed by the writer using IVssCreateWriterMetadata: SetRestoreMethod .
    • Add at least one component using IVssCreateWriterMetadata: AddComponent.

  7. #7
    Join Date
    Nov 2005
    Posts
    3,026

    Re: Overview of Backup Initialization of VM

    A writer Indicates the files to Participate in a backup or restore operation by Adding file sets -a combination of a path, file specification, and a flag-to recursion to Given component using IVssCreateWriterMetadata: AddFilesToFileGroup , IVssCreateWriterMetadata: AddDatabaseFiles , gold IVssCreateWriterMetadata: : AddDatabaseLogFiles , DEPENDING ON type. A Writer May Have Also one or more empty components, components to Which Have Been No files added. These Are Very useful in Organizing the writer's components. A writer uses IVssCreateWriterMetadata: AddExcludeFiles Explicitly to Prevent files from Being included in the backup. This explicit exclusion IS Useful wildcard characters can Because Be Used to specify files for inclusion. IVssCreateWriterMetadata: AddAlternateLocationMapping IS Used to create alternate rental mappings for specified file sets That Have Been added to one of the writer's components. These mappings are Used DURING file restore When restoring to a file's original location is not possible or desirable.

Similar Threads

  1. Overview of AMD L3 cache
    By Botan in forum Motherboard Processor & RAM
    Replies: 7
    Last Post: 26-11-2010, 05:48 AM
  2. DVD Initialization Error
    By Anirvinya in forum Portable Devices
    Replies: 4
    Last Post: 23-04-2010, 05:36 AM
  3. Overview of MS-DOS commands
    By 2ndChance in forum Operating Systems
    Replies: 5
    Last Post: 27-03-2010, 05:30 PM
  4. Initialization problems with P45 USB
    By Solaris in forum Operating Systems
    Replies: 3
    Last Post: 03-11-2009, 11:46 AM
  5. DLL Initialization Failed
    By Tahseen Shahzad in forum Windows XP Support
    Replies: 3
    Last Post: 17-08-2009, 01:51 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,714,314,913.31899 seconds with 17 queries