APAR status
Closed as documentation error.
Error description
Starting with version 10.1.6, On-demand production restore with database and log files renaming of a Microsoft SQL database is possible with IBM Spectrum Protect Plus. Such a restore to the original location when the original database is still present might fail with the following messages. In the Job Log : SUMMARY,,<timestamp>,,CTGGA2398,Starting job for policy onDemandRestore_<RestoreID> (ID:<SLA_ID>). id -> <JobID>. IBM Spectrum Protect Plus version 10.1.6-2040. ... DETAIL,,<timestamp>,2,CTGGE0003,[<SQLServerFQDN>] Restoring database [<DBNewName>] (original database [<DBOriginalName>]) to instance [<InstanceName>]. ... DETAIL,,<timestamp>,2,CTGGA3031,[<SQLServerFQDN>] Set the restore locations and database name for database [<DBNewName>] instance [<InstanceName>]. WARN,,<timestamp>,2,,agent_win_host.ENABLE_FILE_RENAME_OPTION ... ERROR,,<timestamp>,2,CTGGA1608,[<SQLServerFQDN>] Failed to restore databases (<DBOriginalName>) on server (<SQLServerFQDN>) (The file [<PathDBFile>\<DBOriginalName> .mdf] exists on the destination location). in virgo log, we see the selected restore options : [<timestamp>] INFO .. policy added { "id" : "<SLA_ID>", "name" : "onDemandRestore_<RestoreID>", "type" : "recovery", "subType" : "sql", "serviceId" : "serviceprovider.recovery.application", "displayName" : "DB/FS Restore", "description" : "", "version" : "3.1", "spec" : { "source" : [ { "href" : "http://localhost:8082/api/application/sql/ instance/<InstanceID>/database/<DB_ID>?from= recovery", "resourceType" : "database", "include" : true, "version" : { "href" : "http://localhost:8082/api/application/version /database.<DB_ID>.<SourceJobTimeStamp>?from= recovery&embedCopies=true&omitIfNoCopies=true" "copy" : { "href" : "http://localhost:8082/api/application/ version/database.<DB_ID>. <SourceJobTimeStamp>/copy/2000.snapshot. 102_2000.snapshot.101?from=recovery& embedCopies=true&omitIfNoCopies=true" }, "metadata" : { "useLatest" : false, "protectionTime" : <SourceJobTimeStamp> } }, "metadata" : { "name" : "<DBOriginalName>", "osType" : "windows", "instanceVersion" : "<SQLVersion>", "instanceId" : "<InstanceID>", "useLatest" : false }, "id" : "<DB_ID>" } ], "subpolicy" : [ { "type" : "restore", "mode" : "production", "destination" : { "mapdatabase" : { "http://localhost:8082/api/application/sql/instance/ <InstanceID>/database/<DB_ID>?from=recovery" : { "name" : "<DBNewName>", "paths" : [ { "source" : "<PathDBFile>", "destination" : "<PathDBFile>", "mountPoint" : "<x>:", "fileType" : "DATA" }, { "source" : "<PathLogFile>", "destination" : "<PathLogFile>", "mountPoint" : "<Y>:", "fileType" : "LOGS" } ] } }, "targetLocation" : "original" }, "option" : { "autocleanup" : true, "allowsessoverwrite" : true, "continueonerror" : true, "applicationOption" : { "overwriteExistingDb" : false, "recoveryType" : "recovery", "maxParallelStreams" : 1 } }, "source" : null, "name" : "onDemandRestore_<RestoreID>" } ], "view" : "applicationview" }, "specType" : "JSON", "applicationType" : null, "sysObj" : null, "script" : { "preScript" : null, "postScript" : null, "preSnap" : null, "postSnap" : null, "preGuest" : null, "postGuest" : null, "preGuestSnap" : null, "postGuestSnap" : null, "continueScriptsOnError" : false }, "tenantId" : 1000, "creationTime" : <timestamp>, "lastUpdated" : 0, "logicalDelete" : false, "cleanupOptions" : null, "systemPolicy" : false } So that is a restore of DB "<DBOriginalName>" to the original location : data files in "<PathDBFile>" log files in "<PathLogFile>" just renaming it to "<DBNewName>". Looking into the command.log file found in the Job Log bundle, the restore stops with : ERROR sqlvdiwrapper - The file [<PathDBFile>\<DBOriginalName> .mdf] exists on the destination location This happens because, by default, renaming existing database and log files is not permitted. The On-Demand restore Wizard does not display any warning or option to allow renaming of the new restored Database *.mdf and *.ldf files when the original ones still are present in the target location. The needed option, that is unselected by default, does exist but is located using the GUI in : 'System Configuration' ->'Global Preferences' -> 'Application' -> 'Rename SQL data and log files when database is restored in production mode with new name'. IBM Spectrum Protect Plus Versions Affected: IBM Spectrum Protect Plus 10.1.6 Initial Impact: Low Additional Keywords: SPP, SPPLUS, TS004242917, restore
Local fix
Before running the restore select the option : 'System Configuration' ->'Global Preferences' -> 'Application' -> 'Rename SQL data and log files when database is restored in production mode with new name'.
Problem summary
**************************************************************** * USERS AFFECTED: * * IBM Spectrum Protect Plus Knowledge Center and User's Guide * * in version 10.1.5, 10.1.6 and 10.1.7. * **************************************************************** * PROBLEM DESCRIPTION: * * See ERROR DESCRIPTION. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
This
Temporary fix
Comments
APAR Information
APAR number
IT34458
Reported component name
SP PLUS
Reported component ID
5737SPLUS
Reported release
A15
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-10-06
Closed date
2020-12-04
Last modified date
2020-12-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSNQFQ","label":"IBM Spectrum Protect Plus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A15","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
31 January 2024