Prerequisites In order for a VSS backup to function correctly, all of the following steps should be fulfilled. Tablespace or datafile component Verifies that the database must be mounted or the specified datafiles or tablespaces must be offline.
If only the control file needs to be recovered, then the VSS requestor application can ask the Oracle writer to perform complete recovery. Restoring the Server Parameter File This section explains how to restore the server parameter file.Start the instance and mount the standby control file. SQL Server instance not running Troubleshooting Follow step-by-step instructions below to troubleshoot the issue. Restore the component containing the lost datafiles. If issue occurs on Workstation OS, skip this step. If it did not help, follow step-by-step instructions below to troubleshoot the issue. To recover all datafiles: Ensure that the database is mounted. Performs complete recovery of these tablespaces or datafiles. Quit Registry Editor. In order to check that the volume has enough space for the shadow copy, create a shadow copy using the tools integrated in Windows and make sure the shadow copy is created successfully. Performing Disaster Recovery This section explains how to recover from the loss of the server parameter file, control file, and all datafiles. Run cmd and enter ntbackup. Specify the volumes to be included in the backup, e. If the archived redo logs are required for recovery of the datafiles or tablespaces, then restore the archived redo logs. The Oracle VSS writer automatically mounts the database with the restored control files.
Bring the offline datafiles or tablespaces back online. To create a nonstandby database from shadow copies: Restore the database on the new host by following the procedure in "Performing Disaster Recovery".
The Oracle VSS writer automatically mounts the database with the restored control files. Performs complete recovery of these tablespaces or datafiles.
Server Parameter File Verifies that the database instance is not started.Recovering from the Loss of All Control Files This section explains how to recover from the loss of all multiplexed control files. Duplicating a Database If your VSS shadow copies are transportable, then you can use these shadow copies can be used to duplicate the primary database. Bring the offline datafiles or tablespaces back online. Restore the component containing the lost datafiles. Specify the writers that should be verified during the shadow copy creation: specify the ID of VSS writer s from the error message that you receive, e. If you do not want to grant the sysadmin role to the agent, you will need to specify the sysadmin credentials in every backup plan. Error troubleshooting Analyze VSS errors to resolve the issue. Creating a Nonstandby Database from Shadow Copies This section assumes that you are duplicating the database on a host with the same file system structure as the primary database.
Increase the size of such volume up to MB and more or exclude it from the backup source. The Oracle VSS writer automatically restores the datafiles and mounts the database.Do the following to check if the issue is with metadata: Open the TIB archive using any file viewer e. Recovering All Tablespaces This section explains how to recover from the loss of all tablespaces. TOL: Failed to execute the command. If you do not want to grant the sysadmin role to the agent, you will need to specify the sysadmin credentials in every backup plan. Does not perform default recovery of this component. Server Parameter File Verifies that the database instance is not started. Far Manager ; Scroll down to the very bottom of the file contents and check if there is a line with metadata. Complete prerequisites step before proceeding to error troubleshooting step. Go to known issues part and check for known solutions. To recover from the loss of all tablespaces or datafiles: Ensure that the database is either mounted or open.
These credentials are required to grant the sysadmin role to the agent service account.