Skip to main content

Hi,

we were in SP26, to save the new Vms we used XML by specifying the VmguidNo need to launch a first backup to generate the IndexV2 client.Do you have an idea ?Since SP28, our XML no longer works

For exemple

<?xml version="1.0" encoding="utf-8" standalone="no"?>
<TMMsg_CreateTaskReq>
    <taskInfo>
        <associations>
            <subclientName>subclient</subclientName>
            <backupsetName>backupset</backupsetName>
            <instanceName>VMware</instanceName>
            <appName>Virtual Server</appName>
            <clientName>vcenter</clientName>
            <consumeLicense>true</consumeLicense>
            <clientSidePackage>true</clientSidePackage>
        </associations>
        <subTasks>
            <options>
                <backupOpts>
                    <dataOpt>
                        <createNewIndex>false</createNewIndex>
                        <enforceTransactionLogUsage>true</enforceTransactionLogUsage>
                        <followMountPoints>true</followMountPoints>
                        <skipConsistencyCheck>false</skipConsistencyCheck>
                        <useCatalogServer>true</useCatalogServer>
                    </dataOpt>
                    <vsaBackupOptions>
                        <quiesceGuestFileSystemAndApplications> false </quiesceGuestFileSystemAndApplications>
                        <backupFailedVMsOnly>false</backupFailedVMsOnly>
                        <selectiveVMInfo>
                            <vmGuid>XXXXXXXXXX-XXXX-XXXXX-XXXXX</vmGuid>
                        </selectiveVMInfo>
                        <backupCWEVMsWithFailedVMs>false</backupCWEVMsWithFailedVMs>

 

Thanks for your reply
                    </vsaBackupOptions>
                    <collectMetaInfo>false</collectMetaInfo>

Hi @sauvegarde,

The XML format most likely has changed between versions. If you run a save as script now, you should be able to compare or use the new XML format to do what you need to do.


Reply