|
| ||||||||||
| Tags: backup, cvsswriter, databaselogfiles, initialization, virtual machines, vss_backup |
![]() |
| | Thread Tools | Search this Thread |
|
#1
| |||
| |||
| Overview of Backup Initialization of VM
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
| ||||
| ||||
| 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
| ||||
| ||||
| 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 :
__________________ "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
| ||||
| ||||
| 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
| |||
| |||
| 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
| ||||
| ||||
| 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 :
|
|
#7
| ||||
| ||||
| 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. |
![]() |
|
| Thread Tools | Search this Thread |
| |
Similar Threads for: "Overview of Backup Initialization of VM" | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Overview of AMD L3 cache | Botan | Motherboard Processor & RAM | 7 | 26-11-2010 04:48 AM |
| DVD Initialization Error | Anirvinya | Portable Devices | 4 | 23-04-2010 05:36 AM |
| Overview of MS-DOS commands | 2ndChance | Operating Systems | 5 | 27-03-2010 05:30 PM |
| Initialization problems with P45 USB | Solaris | Operating Systems | 3 | 03-11-2009 10:46 AM |
| DLL Initialization Failed | Tahseen Shahzad | Windows XP Support | 3 | 17-08-2009 01:51 PM |