http://docs.stoneram.com/api.php?action=feedcontributions&user=Sachin&feedformat=atomTranzman Documentation - User contributions [en]2024-03-28T19:08:31ZUser contributionsMediaWiki 1.28.0http://docs.stoneram.com/index.php?title=Install_TZM_Server_Using_OVA&diff=2713Install TZM Server Using OVA2021-09-01T16:29:00Z<p>Sachin: </p>
<hr />
<div><br />
==Headline== <br />
<br />
This section explains how to install the Tranzman Server from an <b>OVA</b>. OVA will be shared with Customers though a fileshare from where Customers can download and follow the below steps to install<br />
the Tranzman Appliance.<br />
<br />
VMware admins or System admins shoule be efficiently able to deploy the OVA. Below is just an example of deploying OVA using vSphere client.<br />
<br />
===Step 1===<br />
Login to host using vSphere client and click on <b>File->Deploy OVF</b> to deploy the Deploy OVF Template wizard and select the downloaded OVA.<br />
<br />
<br />
[[File:OVAWizard.JPG | border|600x600px]]<br />
<br />
<br />
===Step 2===<br />
Review the OVF Template , Read and Accept the License and complete the steps to deploy the template.<br />
Make sure to select <b>Thick Provision Lazy zeroed</b> in <b>Disk Format</b><br />
<br />
<br />
<br />
[[File:Overview.JPG | border|600x600px]]<br />
<br />
<br />
<br />
[[File:AcceptLicense.JPG | border|600x600px]]<br />
<br />
<br />
<br />
===Step 3===<br />
Select <b>Power on after deployment</b> and finish the installation.Wait for the Tranzman Appliance to be deployed.<br />
<br />
<br />
[[File:FinishDeployment.JPG | border|600x600px]]<br />
<br />
<br />
===Step 4===<br />
Once the machine is deployed and powered on, the machine will look on the network for an available NTP and DHCP server.<br />
If you have a DHCP enabled environment and machine is able to get an IP from DHCP Server it will be displayed like in below image. Please login to the web using that IP and proceed with [[ Configuration | Configuration ]] otherwise go to [[ Configure IP Network | Configure IP Network ]] to manually set an appliance IP before jumping on to configuration.<br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
|<br />
Tranzman V3.0 <br />
(c) Stone Ram Ltd 2014 - 2017 <br />
The network was configured with DHCP, this is not recommended!! <br />
you can connect to the web interface using the following URL in your browser <br />
<br />
http://192.168.50.97/<br />
<br />
You can connect to the console using "admin" to configure the network. <br />
All other access is denied <br />
tzm_appliance login: _ <br />
|}<br />
<br />
<br />
[[ Configuration | Jump to Configuration ]]<br />
<br />
[[ Installation | Return to Installation ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=File:FinishDeployment.JPG&diff=2712File:FinishDeployment.JPG2021-09-01T16:27:24Z<p>Sachin: Sachin uploaded a new version of File:FinishDeployment.JPG</p>
<hr />
<div></div>Sachinhttp://docs.stoneram.com/index.php?title=Install_TZM_Server_Using_OVA&diff=2711Install TZM Server Using OVA2021-09-01T16:25:42Z<p>Sachin: </p>
<hr />
<div><br />
==Headline== <br />
<br />
This section explains how to install the Tranzman Server from an <b>OVA</b>. OVA will be shared with Customers though a fileshare from where Customers can download and follow the below steps to install<br />
the Tranzman Appliance.<br />
<br />
VMware admins or System admins shoule be efficiently able to deploy the OVA. Below is just an example of deploying OVA using vSphere client.<br />
<br />
===Step 1===<br />
Login to host using vSphere client and click on <b>File->Deploy OVF</b> to deploy the Deploy OVF Template wizard and select the downloaded OVA.<br />
<br />
<br />
[[File:OVAWizard.JPG | border|600x600px]]<br />
<br />
<br />
===Step 2===<br />
Review the OVF Template , Read and Accept the License and complete the steps to deploy the template.<br />
Make sure to select <b>Thick Provision Lazy zeroed</b> in <b>Disk Format</b><br />
<br />
<br />
<br />
[[File:Overview.JPG | border|600x600px]]<br />
<br />
<br />
<br />
[[File:AcceptLicense.JPG | border|600x600px]]<br />
<br />
<br />
<br />
===Step 3===<br />
Select <b>Power on after deployment</b> and finish the installation.Wait for the Tranzman Appliance to be deployed.<br />
<br />
<br />
[[File:FinishDeployment.JPG | border|600x600px]]<br />
<br />
<br />
===Step 4===<br />
Once the machine is deployed and powered on, the machine will look on the network for an available NTP and DHCP server.<br />
If you have a DHCP enabled environment and machine is able to get an IP from DHCP Server it will be displayed like in below image. Please login to the web using that IP and proceed with [[ Configuration | Configuration ]] otherwise go to [[ Configure IP Network | Configure IP Network ]] to manually set an appliance IP before jumping on to configuration.<br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
|<br />
Tranzman V2.0 <br />
(c) Stone Ram Ltd 2014 - 2017 <br />
The network was configured with DHCP, this is not recommended!! <br />
you can connect to the web interface using the following URL in your browser <br />
<br />
http://192.168.50.97/<br />
<br />
You can connect to the console using "admin" to configure the network. <br />
All other access is denied <br />
tzm_appliance login: _ <br />
|}<br />
<br />
<br />
[[ Configuration | Jump to Configuration ]]<br />
<br />
[[ Installation|Return to Installation ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=File:AcceptLicense.JPG&diff=2710File:AcceptLicense.JPG2021-09-01T16:25:21Z<p>Sachin: </p>
<hr />
<div></div>Sachinhttp://docs.stoneram.com/index.php?title=Install_TZM_Server_Using_OVA&diff=2709Install TZM Server Using OVA2021-09-01T16:24:59Z<p>Sachin: </p>
<hr />
<div><br />
==Headline== <br />
<br />
This section explains how to install the Tranzman Server from an <b>OVA</b>. OVA will be shared with Customers though a fileshare from where Customers can download and follow the below steps to install<br />
the Tranzman Appliance.<br />
<br />
VMware admins or System admins shoule be efficiently able to deploy the OVA. Below is just an example of deploying OVA using vSphere client.<br />
<br />
===Step 1===<br />
Login to host using vSphere client and click on <b>File->Deploy OVF</b> to deploy the Deploy OVF Template wizard and select the downloaded OVA.<br />
<br />
<br />
[[File:OVAWizard.JPG | border|600x600px]]<br />
<br />
<br />
===Step 2===<br />
Review the OVF Template , Read and Accept the License and complete the steps to deploy the template.<br />
Make sure to select <b>Thick Provision Lazy zeroed</b> in <b>Disk Format</b><br />
<br />
<br />
[[File:Overview.JPG | border|600x600px]]<br />
<br />
<br />
[[File:AcceptLicense.JPG | border|600x600px]]<br />
<br />
<br />
<br />
===Step 3===<br />
Select <b>Power on after deployment</b> and finish the installation.Wait for the Tranzman Appliance to be deployed.<br />
<br />
<br />
[[File:FinishDeployment.JPG | border|600x600px]]<br />
<br />
<br />
===Step 4===<br />
Once the machine is deployed and powered on, the machine will look on the network for an available NTP and DHCP server.<br />
If you have a DHCP enabled environment and machine is able to get an IP from DHCP Server it will be displayed like in below image. Please login to the web using that IP and proceed with [[ Configuration | Configuration ]] otherwise go to [[ Configure IP Network | Configure IP Network ]] to manually set an appliance IP before jumping on to configuration.<br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
|<br />
Tranzman V2.0 <br />
(c) Stone Ram Ltd 2014 - 2017 <br />
The network was configured with DHCP, this is not recommended!! <br />
you can connect to the web interface using the following URL in your browser <br />
<br />
http://192.168.50.97/<br />
<br />
You can connect to the console using "admin" to configure the network. <br />
All other access is denied <br />
tzm_appliance login: _ <br />
|}<br />
<br />
<br />
[[ Configuration | Jump to Configuration ]]<br />
<br />
[[ Installation|Return to Installation ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=File:Overview.JPG&diff=2708File:Overview.JPG2021-09-01T16:24:06Z<p>Sachin: </p>
<hr />
<div></div>Sachinhttp://docs.stoneram.com/index.php?title=Install_TZM_Server_Using_OVA&diff=2707Install TZM Server Using OVA2021-09-01T16:23:46Z<p>Sachin: </p>
<hr />
<div><br />
==Headline== <br />
<br />
This section explains how to install the Tranzman Server from an <b>OVA</b>. OVA will be shared with Customers though a fileshare from where Customers can download and follow the below steps to install<br />
the Tranzman Appliance.<br />
<br />
VMware admins or System admins shoule be efficiently able to deploy the OVA. Below is just an example of deploying OVA using vSphere client.<br />
<br />
===Step 1===<br />
Login to host using vSphere client and click on <b>File->Deploy OVF</b> to deploy the Deploy OVF Template wizard and select the downloaded OVA.<br />
<br />
<br />
[[File:OVAWizard.JPG | border|600x600px]]<br />
<br />
<br />
===Step 2===<br />
Review the OVF Template , Read and Accept the License and complete the steps to deploy the template.<br />
Make sure to select <b>Thick Provision Lazy zeroed</b> in <b>Disk Format</b><br />
<br />
<br />
[[File:Overview.JPG | border|600x600px]]<br />
<br />
<br />
[[File:License.JPG | border|600x600px]]<br />
<br />
<br />
<br />
===Step 3===<br />
Select <b>Power on after deployment</b> and finish the installation.Wait for the Tranzman Appliance to be deployed.<br />
<br />
<br />
[[File:FinishDeployment.JPG | border|600x600px]]<br />
<br />
<br />
===Step 4===<br />
Once the machine is deployed and powered on, the machine will look on the network for an available NTP and DHCP server.<br />
If you have a DHCP enabled environment and machine is able to get an IP from DHCP Server it will be displayed like in below image. Please login to the web using that IP and proceed with [[ Configuration | Configuration ]] otherwise go to [[ Configure IP Network | Configure IP Network ]] to manually set an appliance IP before jumping on to configuration.<br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
|<br />
Tranzman V2.0 <br />
(c) Stone Ram Ltd 2014 - 2017 <br />
The network was configured with DHCP, this is not recommended!! <br />
you can connect to the web interface using the following URL in your browser <br />
<br />
http://192.168.50.97/<br />
<br />
You can connect to the console using "admin" to configure the network. <br />
All other access is denied <br />
tzm_appliance login: _ <br />
|}<br />
<br />
<br />
[[ Configuration | Jump to Configuration ]]<br />
<br />
[[ Installation|Return to Installation ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Planning&diff=2706Planning2021-09-01T16:14:21Z<p>Sachin: </p>
<hr />
<div><br />
{|style="font-size: 15px;"<br />
|<br />
== <b>Headline</b> ==<br />
|}<br />
To help determine the correct sizing for a Tranzman Appliance, it is recommended that the [[Recorder|Tranzman Recorder]] is used to help better understand the current environment.<br />
<br />
A single Tranzman Appliance can be used to convert many environments, the following considerations need to be taken into account when sizing it.<br />
<br />
{|style="font-size: 15px;"<br />
|<br />
===RAM===<br />
|}<br />
{| class="wikitable" style="text-align:center; font-size:14px; font-family:Arial, Helvetica, sans-serif !important;;"<br />
|- style="font-weight:bold; font-size:16px;"<br />
! RAM Size<br />
! Use Case<br />
|-<br />
| Minimum 2G<br />
| style="text-align:left;" | Using appliance only for assessments<br />
|-<br />
| Minimum 8GB<br />
| style="text-align:left;" | Migrating Same Vendor<br />
|- style="text-align:left;"<br />
| Minimum 8GB<br />
| Migrating Cross Vendor<br />
|}<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Additional 1GB of RAM is required for every tape drive connected to the Appliance<br />
| <br />
|}<br />
<br />
{|style="font-size: 15px;"<br />
|<br />
===CPU===<br />
|}<br />
{| class="wikitable" style="font-size:14px; font-family:Arial, Helvetica, sans-serif !important;;"<br />
|- style="font-weight:bold; font-size:16px;"<br />
! CPU Core<br />
! Use Case<br />
|- style="text-align:center;"<br />
| Minimum 4 core Intel CPU<br />
| style="text-align:left;" | Migrating Same Vendor<br />
|-<br />
| Minimum 8 core Intel CPU<br />
| Migrating Cross Vendor<br />
|}<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Additional 1 core for every tape drive connected to the Appliance<br />
* ONLY INTEL processors have been tested and are supported.<br />
| <br />
|}<br />
<br />
{|style="font-size: 15px;"<br />
|<br />
===Network===<br />
|}<br />
* 1Gbit minimum connection required (for Same Vendor migration and recovery on Demand).<br />
* 10Gbit connection recommended for Cross Vendor to ensure that tape drive are kept running at a reasonable speed.<br />
* If multiple links are used, aggregation is needed to provide maximum throughput. <br />
* Multiple connections may be required if there are multiple tape drives.<br />
<br />
{|style="font-size: 15px;"<br />
|<br />
===Ports===<br />
|}<br />
The appliance needs to communicate over the network. If you have internal firewalls, you must allow the following connections or the appliance cannot function.<br />
<br />
{|style="font-size: 16px;"<br />
|<br />
====Backup Servers (Clients of Tranzman)====<br />
|}<br />
<br />
=====All servers=====<br />
{| class="wikitable"<br />
|-<br />
|INBOUND || TCP 443 from ANY<br />
|-<br />
|OUTBOUND || to Tranzman Appliance TCP 55560<br />
|}<br />
<br />
=====Destination servers=====<br />
* Windows<br />
{| class="wikitable"<br />
|-<br />
|OUTBOUND || to the Tranzman Appliance TCP 139 and 445 and UDP 137 and 138<br />
|}<br />
* Unix/Linux<br />
{| class="wikitable"<br />
|-<br />
|OUTBOUND || to the Tranzman Appliance TCP 111,4045 and 2049 and UDP 111,4045 and 2049<br />
|}<br />
<br />
<br />
{|style="font-size: 16px;"<br />
|<br />
====Tranzman Appliance (Server)====<br />
|}<br />
{| class="wikitable"<br />
|-<br />
|INBOUND || TCP 443 from ANY<br />
|-<br />
|INBOUND || TCP 22 from ANY<br />
|-<br />
|INBOUND || TCP 80 from ANY<br />
|-<br />
|INBOUND || TCP 55560 from all origin and destination backup servers<br />
|-<br />
|INBOUND || TCP 139 and 445 and UDP 137 and 138 from destination Windows servers<br />
|-<br />
|INBOUND || TCP 111,4045 and 2049 and UDP 111,4045 and 2049 from destination *nix servers<br />
|-<br />
|INBOUND || TCP 139 and 445 and UDP 137 and 138 from Administration PC(s) Windows Only<br />
|-<br />
|OUTBOUND|| TCP 53 and UDP 53 to the DNS servers<br />
|-<br />
|OUTBOUND|| UDP 123 to the NTP servers<br />
|-<br />
|INBOUND || UDP 123 to the NTP servers.<br />
|-<br />
|OUTBOUND || TCP 25, 587 to the Email server<br />
|}<br />
<br />
<br />
{|style="font-size: 16px;"<br />
|<br />
====Administration PC====<br />
|}<br />
{| class="wikitable"<br />
|-<br />
|OUTBOUND || to Tranzman Appliance TCP 443 <br />
|-<br />
|OUTBOUND || to Tranzman Appliance TCP 80 <br />
|-<br />
|OUTBOUND || to Tranzman Appliance TCP 22<br />
|-<br />
|OUTBOUND || to the Tranzman Appliance TCP 139 and 445 and UDP 137 and 138<br />
|}<br />
<br />
<br />
{|style="font-size: 16px;"<br />
|<br />
===Storage===<br />
|}<br />
* Minimum 3GB local disk for OS Installation.<br />
* Local/SAN attached disks needed for temporary staging of converted images, sized according to volume of recoveries to accommodate at any one time. The following is for guidance only, it would be recommended that you use the [[Recorder|Tranzman Recorder]] and Stone Ram Consulting Services to correctly size the volumes.<br />
{|style="font-size: 15px;"<br />
|<br />
<br />
{| class="wikitable" style="font-weight:bold;"<br />
|+Table for Guidance<br />
|- style="font-size:16px; font-family:Arial, Helvetica, sans-serif !important;;"<br />
! Assessment Only<br />
! Same Vendor<br />
! Cross Vendor<br />
|- style="font-weight:normal;"<br />
| style="text-align:center; font-size:16px; font-family:Arial, Helvetica, sans-serif !important;;" | Additional disk of Minimum 20GB<br />
| Additional disk(s) of Minimum ((2.5 * Size of combined catalogs) + (2 * Total Memory))<br />
| Additional disk(s) of Minimum ((2.5 * Size of combined catalogs) + (2 * Total Memory) + Largest of either<br />3 x Largest image size <br />Number of Drives * max size of compressed tape<br />
|}<br />
<br />
<br />
[[ Installation | Jump to Installation ]]<br />
<br />
[[ Tranzman| Return to Overview ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Planning&diff=2705Planning2021-09-01T16:12:49Z<p>Sachin: </p>
<hr />
<div><br />
{|style="font-size: 15px;"<br />
|<br />
== <b>Headline</b> ==<br />
|}<br />
To help determine the correct sizing for a Tranzman Appliance, it is recommended that the [[Recorder|Tranzman Recorder]] is used to help better understand the current environment.<br />
<br />
A single Tranzman Appliance can be used to convert many environments, the following considerations need to be taken into account when sizing it.<br />
<br />
{|style="font-size: 15px;"<br />
|<br />
===RAM===<br />
|}<br />
{| class="wikitable" style="text-align:center; font-size:14px; font-family:Arial, Helvetica, sans-serif !important;;"<br />
|- style="font-weight:bold; font-size:16px;"<br />
! RAM Size<br />
! Use Case<br />
|-<br />
| Minimum 2G<br />
| style="text-align:left;" | Using appliance only for assessments<br />
|-<br />
| Minimum 8GB<br />
| style="text-align:left;" | Migrating Same Vendor<br />
|- style="text-align:left;"<br />
| Minimum 8GB<br />
| Migrating Cross Vendor<br />
|}<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Additional 1GB of RAM is required for every tape drive connected to the Appliance<br />
| <br />
|}<br />
<br />
{|style="font-size: 15px;"<br />
|<br />
===CPU===<br />
|}<br />
{| class="wikitable" style="font-size:14px; font-family:Arial, Helvetica, sans-serif !important;;"<br />
|- style="font-weight:bold; font-size:16px;"<br />
! CPU Core<br />
! Use Case<br />
|- style="text-align:center;"<br />
| Minimum 4 core Intel CPU<br />
| style="text-align:left;" | Migrating Same Vendor<br />
|-<br />
| Minimum 8 core Intel CPU<br />
| Migrating Cross Vendor<br />
|}<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Additional 1 core for every tape drive connected to the Appliance<br />
* ONLY INTEL processors have been tested and are supported.<br />
| <br />
|}<br />
<br />
{|style="font-size: 15px;"<br />
|<br />
===Network===<br />
|}<br />
* 1Gbit minimum connection required (for Same Vendor migration and recovery on Demand).<br />
* 10Gbit connection recommended for Cross Vendor to ensure that tape drive are kept running at a reasonable speed.<br />
* If multiple links are used, aggregation is needed to provide maximum throughput. <br />
* Multiple connections may be required if there are multiple tape drives.<br />
<br />
{|style="font-size: 15px;"<br />
|<br />
===Ports===<br />
|}<br />
The appliance needs to communicate over the network. If you have internal firewalls, you must allow the following connections or the appliance cannot function.<br />
<br />
{|style="font-size: 16px;"<br />
|<br />
====Backup Servers (Clients of Tranzman)====<br />
|}<br />
<br />
=====All servers=====<br />
{| class="wikitable"<br />
|-<br />
|INBOUND || TCP 443 from ANY<br />
|-<br />
|OUTBOUND || to Tranzman Appliance TCP 55001-55555 <br />
|}<br />
<br />
=====Destination servers=====<br />
* Windows<br />
{| class="wikitable"<br />
|-<br />
|OUTBOUND || to the Tranzman Appliance TCP 139 and 445 and UDP 137 and 138<br />
|}<br />
* Unix/Linux<br />
{| class="wikitable"<br />
|-<br />
|OUTBOUND || to the Tranzman Appliance TCP 111,4045 and 2049 and UDP 111,4045 and 2049<br />
|}<br />
<br />
<br />
{|style="font-size: 16px;"<br />
|<br />
====Tranzman Appliance (Server)====<br />
|}<br />
{| class="wikitable"<br />
|-<br />
|INBOUND || TCP 443 from ANY<br />
|-<br />
|INBOUND || TCP 22 from ANY<br />
|-<br />
|INBOUND || TCP 80 from ANY<br />
|-<br />
|INBOUND || TCP 55001-55555 from all origin and destination backup servers<br />
|-<br />
|INBOUND || TCP 139 and 445 and UDP 137 and 138 from destination Windows servers<br />
|-<br />
|INBOUND || TCP 111,4045 and 2049 and UDP 111,4045 and 2049 from destination *nix servers<br />
|-<br />
|INBOUND || TCP 139 and 445 and UDP 137 and 138 from Administration PC(s) Windows Only<br />
|-<br />
|OUTBOUND|| TCP 53 and UDP 53 to the DNS servers<br />
|-<br />
|OUTBOUND|| UDP 123 to the NTP servers<br />
|-<br />
|INBOUND || UDP 123 to the NTP servers.<br />
|-<br />
|OUTBOUND || TCP 25, 587 to the Email server<br />
|}<br />
<br />
<br />
{|style="font-size: 16px;"<br />
|<br />
====Administration PC====<br />
|}<br />
{| class="wikitable"<br />
|-<br />
|OUTBOUND || to Tranzman Appliance TCP 443 <br />
|-<br />
|OUTBOUND || to Tranzman Appliance TCP 80 <br />
|-<br />
|OUTBOUND || to Tranzman Appliance TCP 22<br />
|-<br />
|OUTBOUND || to the Tranzman Appliance TCP 139 and 445 and UDP 137 and 138<br />
|}<br />
<br />
<br />
{|style="font-size: 16px;"<br />
|<br />
===Storage===<br />
|}<br />
* Minimum 3GB local disk for OS Installation.<br />
* Local/SAN attached disks needed for temporary staging of converted images, sized according to volume of recoveries to accommodate at any one time. The following is for guidance only, it would be recommended that you use the [[Recorder|Tranzman Recorder]] and Stone Ram Consulting Services to correctly size the volumes.<br />
{|style="font-size: 15px;"<br />
|<br />
<br />
{| class="wikitable" style="font-weight:bold;"<br />
|+Table for Guidance<br />
|- style="font-size:16px; font-family:Arial, Helvetica, sans-serif !important;;"<br />
! Assessment Only<br />
! Same Vendor<br />
! Cross Vendor<br />
|- style="font-weight:normal;"<br />
| style="text-align:center; font-size:16px; font-family:Arial, Helvetica, sans-serif !important;;" | Additional disk of Minimum 20GB<br />
| Additional disk(s) of Minimum ((2.5 * Size of combined catalogs) + (2 * Total Memory))<br />
| Additional disk(s) of Minimum ((2.5 * Size of combined catalogs) + (2 * Total Memory) + Largest of either<br />3 x Largest image size <br />Number of Drives * max size of compressed tape<br />
|}<br />
<br />
<br />
[[ Installation | Jump to Installation ]]<br />
<br />
[[ Tranzman| Return to Overview ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Planning&diff=2704Planning2021-09-01T16:12:26Z<p>Sachin: </p>
<hr />
<div><br />
{|style="font-size: 15px;"<br />
|<br />
== <b>Headline</b> ==<br />
|}<br />
To help determine the correct sizing for a Tranzman Appliance, it is recommended that the [[Recorder|Tranzman Recorder]] is used to help better understand the current environment.<br />
<br />
A single Tranzman Appliance can be used to convert many environments, the following considerations need to be taken into account when sizing it.<br />
<br />
{|style="font-size: 15px;"<br />
|<br />
===RAM===<br />
|}<br />
{| class="wikitable" style="text-align:center; font-size:14px; font-family:Arial, Helvetica, sans-serif !important;;"<br />
|- style="font-weight:bold; font-size:16px;"<br />
! RAM Size<br />
! Use Case<br />
|-<br />
| Minimum 2G<br />
| style="text-align:left;" | Using appliance only for assessments<br />
|-<br />
| Minimum 8GB<br />
| style="text-align:left;" | Migrating Same Vendor<br />
|- style="text-align:left;"<br />
| Minimum 8GB<br />
| Migrating Cross Vendor<br />
|}<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Additional 1GB of RAM is required for every tape drive connected to the Appliance<br />
| <br />
|}<br />
<br />
{|style="font-size: 15px;"<br />
|<br />
===CPU===<br />
|}<br />
{| class="wikitable" style="font-size:14px; font-family:Arial, Helvetica, sans-serif !important;;"<br />
|- style="font-weight:bold; font-size:16px;"<br />
! CPU Core<br />
! Use Case<br />
|- style="text-align:center;"<br />
| Minimum 4 core Intel CPU<br />
| style="text-align:left;" | Migrating Same Vendor<br />
|-<br />
| Minimum 8 core Intel CPU<br />
| Migrating Cross Vendor<br />
|}<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Additional 1 core for every tape drive connected to the Appliance<br />
** ONLY INTEL processors have been tested and are supported.<br />
| <br />
|}<br />
<br />
{|style="font-size: 15px;"<br />
|<br />
===Network===<br />
|}<br />
* 1Gbit minimum connection required (for Same Vendor migration and recovery on Demand).<br />
* 10Gbit connection recommended for Cross Vendor to ensure that tape drive are kept running at a reasonable speed.<br />
* If multiple links are used, aggregation is needed to provide maximum throughput. <br />
* Multiple connections may be required if there are multiple tape drives.<br />
<br />
{|style="font-size: 15px;"<br />
|<br />
===Ports===<br />
|}<br />
The appliance needs to communicate over the network. If you have internal firewalls, you must allow the following connections or the appliance cannot function.<br />
<br />
{|style="font-size: 16px;"<br />
|<br />
====Backup Servers (Clients of Tranzman)====<br />
|}<br />
<br />
=====All servers=====<br />
{| class="wikitable"<br />
|-<br />
|INBOUND || TCP 443 from ANY<br />
|-<br />
|OUTBOUND || to Tranzman Appliance TCP 55001-55555 <br />
|}<br />
<br />
=====Destination servers=====<br />
* Windows<br />
{| class="wikitable"<br />
|-<br />
|OUTBOUND || to the Tranzman Appliance TCP 139 and 445 and UDP 137 and 138<br />
|}<br />
* Unix/Linux<br />
{| class="wikitable"<br />
|-<br />
|OUTBOUND || to the Tranzman Appliance TCP 111,4045 and 2049 and UDP 111,4045 and 2049<br />
|}<br />
<br />
<br />
{|style="font-size: 16px;"<br />
|<br />
====Tranzman Appliance (Server)====<br />
|}<br />
{| class="wikitable"<br />
|-<br />
|INBOUND || TCP 443 from ANY<br />
|-<br />
|INBOUND || TCP 22 from ANY<br />
|-<br />
|INBOUND || TCP 80 from ANY<br />
|-<br />
|INBOUND || TCP 55001-55555 from all origin and destination backup servers<br />
|-<br />
|INBOUND || TCP 139 and 445 and UDP 137 and 138 from destination Windows servers<br />
|-<br />
|INBOUND || TCP 111,4045 and 2049 and UDP 111,4045 and 2049 from destination *nix servers<br />
|-<br />
|INBOUND || TCP 139 and 445 and UDP 137 and 138 from Administration PC(s) Windows Only<br />
|-<br />
|OUTBOUND|| TCP 53 and UDP 53 to the DNS servers<br />
|-<br />
|OUTBOUND|| UDP 123 to the NTP servers<br />
|-<br />
|INBOUND || UDP 123 to the NTP servers.<br />
|-<br />
|OUTBOUND || TCP 25, 587 to the Email server<br />
|}<br />
<br />
<br />
{|style="font-size: 16px;"<br />
|<br />
====Administration PC====<br />
|}<br />
{| class="wikitable"<br />
|-<br />
|OUTBOUND || to Tranzman Appliance TCP 443 <br />
|-<br />
|OUTBOUND || to Tranzman Appliance TCP 80 <br />
|-<br />
|OUTBOUND || to Tranzman Appliance TCP 22<br />
|-<br />
|OUTBOUND || to the Tranzman Appliance TCP 139 and 445 and UDP 137 and 138<br />
|}<br />
<br />
<br />
{|style="font-size: 16px;"<br />
|<br />
===Storage===<br />
|}<br />
* Minimum 3GB local disk for OS Installation.<br />
* Local/SAN attached disks needed for temporary staging of converted images, sized according to volume of recoveries to accommodate at any one time. The following is for guidance only, it would be recommended that you use the [[Recorder|Tranzman Recorder]] and Stone Ram Consulting Services to correctly size the volumes.<br />
{|style="font-size: 15px;"<br />
|<br />
<br />
{| class="wikitable" style="font-weight:bold;"<br />
|+Table for Guidance<br />
|- style="font-size:16px; font-family:Arial, Helvetica, sans-serif !important;;"<br />
! Assessment Only<br />
! Same Vendor<br />
! Cross Vendor<br />
|- style="font-weight:normal;"<br />
| style="text-align:center; font-size:16px; font-family:Arial, Helvetica, sans-serif !important;;" | Additional disk of Minimum 20GB<br />
| Additional disk(s) of Minimum ((2.5 * Size of combined catalogs) + (2 * Total Memory))<br />
| Additional disk(s) of Minimum ((2.5 * Size of combined catalogs) + (2 * Total Memory) + Largest of either<br />3 x Largest image size <br />Number of Drives * max size of compressed tape<br />
|}<br />
<br />
<br />
[[ Installation | Jump to Installation ]]<br />
<br />
[[ Tranzman| Return to Overview ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Planning&diff=2703Planning2021-09-01T16:11:01Z<p>Sachin: </p>
<hr />
<div><br />
{|style="font-size: 15px;"<br />
|<br />
== <b>Headline</b> ==<br />
|}<br />
To help determine the correct sizing for a Tranzman Appliance, it is recommended that the [[Recorder|Tranzman Recorder]] is used to help better understand the current environment.<br />
<br />
A single Tranzman Appliance can be used to convert many environments, the following considerations need to be taken into account when sizing it.<br />
<br />
{|style="font-size: 15px;"<br />
|<br />
===RAM===<br />
|}<br />
{| class="wikitable" style="text-align:center; font-size:14px; font-family:Arial, Helvetica, sans-serif !important;;"<br />
|- style="font-weight:bold; font-size:16px;"<br />
! RAM Size<br />
! Use Case<br />
|-<br />
| Minimum 2G<br />
| style="text-align:left;" | Using appliance only for assessments<br />
|-<br />
| Minimum 8GB<br />
| style="text-align:left;" | Migrating Same Vendor<br />
|- style="text-align:left;"<br />
| Minimum 8GB<br />
| Migrating Cross Vendor<br />
|}<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Additional 1GB of RAM is required for every tape drive connected to the Appliance<br />
| <br />
|}<br />
<br />
{|style="font-size: 15px;"<br />
|<br />
===CPU===<br />
|}<br />
{| class="wikitable" style="font-size:14px; font-family:Arial, Helvetica, sans-serif !important;;"<br />
|- style="font-weight:bold; font-size:16px;"<br />
! CPU Core<br />
! Use Case<br />
|- style="text-align:center;"<br />
| Minimum 2 core Intel CPU<br />
| style="text-align:left;" | Migrating Same Vendor<br />
|-<br />
| Minimum 4 core Intel CPU<br />
| Migrating Cross Vendor<br />
|}<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Additional 1 core for every tape drive connected to the Appliance<br />
** ONLY INTEL processors have been tested and are supported.<br />
| <br />
|}<br />
<br />
{|style="font-size: 15px;"<br />
|<br />
===Network===<br />
|}<br />
* 1Gbit minimum connection required (for Same Vendor migration and recovery on Demand).<br />
* 10Gbit connection recommended for Cross Vendor to ensure that tape drive are kept running at a reasonable speed.<br />
* If multiple links are used, aggregation is needed to provide maximum throughput. <br />
* Multiple connections may be required if there are multiple tape drives.<br />
<br />
{|style="font-size: 15px;"<br />
|<br />
===Ports===<br />
|}<br />
The appliance needs to communicate over the network. If you have internal firewalls, you must allow the following connections or the appliance cannot function.<br />
<br />
{|style="font-size: 16px;"<br />
|<br />
====Backup Servers (Clients of Tranzman)====<br />
|}<br />
<br />
=====All servers=====<br />
{| class="wikitable"<br />
|-<br />
|INBOUND || TCP 443 from ANY<br />
|-<br />
|OUTBOUND || to Tranzman Appliance TCP 55001-55555 <br />
|}<br />
<br />
=====Destination servers=====<br />
* Windows<br />
{| class="wikitable"<br />
|-<br />
|OUTBOUND || to the Tranzman Appliance TCP 139 and 445 and UDP 137 and 138<br />
|}<br />
* Unix/Linux<br />
{| class="wikitable"<br />
|-<br />
|OUTBOUND || to the Tranzman Appliance TCP 111,4045 and 2049 and UDP 111,4045 and 2049<br />
|}<br />
<br />
<br />
{|style="font-size: 16px;"<br />
|<br />
====Tranzman Appliance (Server)====<br />
|}<br />
{| class="wikitable"<br />
|-<br />
|INBOUND || TCP 443 from ANY<br />
|-<br />
|INBOUND || TCP 22 from ANY<br />
|-<br />
|INBOUND || TCP 80 from ANY<br />
|-<br />
|INBOUND || TCP 55001-55555 from all origin and destination backup servers<br />
|-<br />
|INBOUND || TCP 139 and 445 and UDP 137 and 138 from destination Windows servers<br />
|-<br />
|INBOUND || TCP 111,4045 and 2049 and UDP 111,4045 and 2049 from destination *nix servers<br />
|-<br />
|INBOUND || TCP 139 and 445 and UDP 137 and 138 from Administration PC(s) Windows Only<br />
|-<br />
|OUTBOUND|| TCP 53 and UDP 53 to the DNS servers<br />
|-<br />
|OUTBOUND|| UDP 123 to the NTP servers<br />
|-<br />
|INBOUND || UDP 123 to the NTP servers.<br />
|-<br />
|OUTBOUND || TCP 25, 587 to the Email server<br />
|}<br />
<br />
<br />
{|style="font-size: 16px;"<br />
|<br />
====Administration PC====<br />
|}<br />
{| class="wikitable"<br />
|-<br />
|OUTBOUND || to Tranzman Appliance TCP 443 <br />
|-<br />
|OUTBOUND || to Tranzman Appliance TCP 80 <br />
|-<br />
|OUTBOUND || to Tranzman Appliance TCP 22<br />
|-<br />
|OUTBOUND || to the Tranzman Appliance TCP 139 and 445 and UDP 137 and 138<br />
|}<br />
<br />
<br />
{|style="font-size: 16px;"<br />
|<br />
===Storage===<br />
|}<br />
* Minimum 3GB local disk for OS Installation.<br />
* Local/SAN attached disks needed for temporary staging of converted images, sized according to volume of recoveries to accommodate at any one time. The following is for guidance only, it would be recommended that you use the [[Recorder|Tranzman Recorder]] and Stone Ram Consulting Services to correctly size the volumes.<br />
{|style="font-size: 15px;"<br />
|<br />
<br />
{| class="wikitable" style="font-weight:bold;"<br />
|+Table for Guidance<br />
|- style="font-size:16px; font-family:Arial, Helvetica, sans-serif !important;;"<br />
! Assessment Only<br />
! Same Vendor<br />
! Cross Vendor<br />
|- style="font-weight:normal;"<br />
| style="text-align:center; font-size:16px; font-family:Arial, Helvetica, sans-serif !important;;" | Additional disk of Minimum 20GB<br />
| Additional disk(s) of Minimum ((2.5 * Size of combined catalogs) + (2 * Total Memory))<br />
| Additional disk(s) of Minimum ((2.5 * Size of combined catalogs) + (2 * Total Memory) + Largest of either<br />3 x Largest image size <br />Number of Drives * max size of compressed tape<br />
|}<br />
<br />
<br />
[[ Installation | Jump to Installation ]]<br />
<br />
[[ Tranzman| Return to Overview ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2702Recovery as Normal Files(MS-SharePoint)2021-07-14T12:23:37Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files(FileSystem)|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ('' As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named '''SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4'''<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|900x600px]]<br />
<br />
<br />
===Step 1===<br />
<br />
Login to SSMS(SQL Server Management Studio) and connect to the SQL Server Instance.<br />
<br />
<br />
[[File:SQL_SharePoint_Connect.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 2===<br />
<br />
Right Click and select Restore Database.<br />
<br />
<br />
[[File:SQL_Restore_Database.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 3===<br />
<br />
From Device , select the data file to restore.<br />
<br />
<br />
[[File:SQL_Select_DataFile.JPG | border|900x600px]]<br />
<br />
<br />
<br />
<br />
===Step 4===<br />
<br />
Click on OK and start the restore. Your data should start restoring.<br />
<br />
<br />
[[File:SQL_Restore_Progress.JPG | border|900x700px]]<br />
<br />
<br />
You might have to take the database offline in case there are any existing connections.<br />
<br />
===Step 5===<br />
<br />
Verify the restored data,once restore has been successful<br />
<br />
<br />
[[File:SQL_Data_Restored.JPG | border|900x700px]]<br />
<br />
<br />
<br />
[[ VERITAS NetBackup Recovery | Return to VERITAS NetBackup Recovery ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2701Recovery as Normal Files(MS-SharePoint)2021-07-14T12:11:00Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ('' As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named '''SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4'''<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|900x600px]]<br />
<br />
<br />
===Step 1===<br />
<br />
Login to SSMS(SQL Server Management Studio) and connect to the SQL Server Instance.<br />
<br />
<br />
[[File:SQL_SharePoint_Connect.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 2===<br />
<br />
Right Click and select Restore Database.<br />
<br />
<br />
[[File:SQL_Restore_Database.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 3===<br />
<br />
From Device , select the data file to restore.<br />
<br />
<br />
[[File:SQL_Select_DataFile.JPG | border|900x600px]]<br />
<br />
<br />
<br />
<br />
===Step 4===<br />
<br />
Click on OK and start the restore. Your data should start restoring.<br />
<br />
<br />
[[File:SQL_Restore_Progress.JPG | border|900x700px]]<br />
<br />
<br />
You might have to take the database offline in case there are any existing connections.<br />
<br />
===Step 5===<br />
<br />
Verify the restored data,once restore has been successful<br />
<br />
<br />
[[File:SQL_Data_Restored.JPG | border|900x700px]]<br />
<br />
<br />
<br />
[[ VERITAS NetBackup Recovery | Return to VERITAS NetBackup Recovery ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2700Recovery as Normal Files(MS-SharePoint)2021-07-14T12:09:13Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named '''SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4'''<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|900x600px]]<br />
<br />
<br />
===Step 1===<br />
<br />
Login to SSMS(SQL Server Management Studio) and connect to the SQL Server Instance.<br />
<br />
<br />
[[File:SQL_SharePoint_Connect.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 2===<br />
<br />
Right Click and select Restore Database.<br />
<br />
<br />
[[File:SQL_Restore_Database.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 3===<br />
<br />
From Device , select the data file to restore.<br />
<br />
<br />
[[File:SQL_Select_DataFile.JPG | border|900x600px]]<br />
<br />
<br />
<br />
<br />
===Step 4===<br />
<br />
Click on OK and start the restore. Your data should start restoring.<br />
<br />
<br />
[[File:SQL_Restore_Progress.JPG | border|900x700px]]<br />
<br />
<br />
You might have to take the database offline in case there are any existing connections.<br />
<br />
===Step 5===<br />
<br />
Verify the restored data,once restore has been successful<br />
<br />
<br />
[[File:SQL_Data_Restored.JPG | border|900x700px]]<br />
<br />
<br />
<br />
[[ VERITAS NetBackup Recovery | Return to VERITAS NetBackup Recovery ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2699Recovery as Normal Files(MS-SharePoint)2021-07-14T12:07:52Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named ==SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4==<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|900x600px]]<br />
<br />
<br />
===Step 1===<br />
<br />
Login to SSMS(SQL Server Management Studio) and connect to the SQL Server Instance.<br />
<br />
<br />
[[File:SQL_SharePoint_Connect.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 2===<br />
<br />
Right Click and select Restore Database.<br />
<br />
<br />
[[File:SQL_Restore_Database.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 3===<br />
<br />
From Device , select the data file to restore.<br />
<br />
<br />
[[File:SQL_Select_DataFile.JPG | border|900x600px]]<br />
<br />
<br />
<br />
<br />
===Step 4===<br />
<br />
Click on OK and start the restore. Your data should start restoring.<br />
<br />
<br />
[[File:SQL_Restore_Progress.JPG | border|900x700px]]<br />
<br />
<br />
You might have to take the database offline in case there are any existing connections.<br />
<br />
===Step 5===<br />
<br />
Verify the restored data,once restore has been successful<br />
<br />
<br />
[[File:SQL_Data_Restored.JPG | border|900x700px]]<br />
<br />
<br />
<br />
[[ VERITAS NetBackup Recovery | Return to VERITAS NetBackup Recovery ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2698Recovery as Normal Files(MS-SharePoint)2021-07-14T12:07:15Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named **SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4**<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|900x600px]]<br />
<br />
<br />
===Step 1===<br />
<br />
Login to SSMS(SQL Server Management Studio) and connect to the SQL Server Instance.<br />
<br />
<br />
[[File:SQL_SharePoint_Connect.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 2===<br />
<br />
Right Click and select Restore Database.<br />
<br />
<br />
[[File:SQL_Restore_Database.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 3===<br />
<br />
From Device , select the data file to restore.<br />
<br />
<br />
[[File:SQL_Select_DataFile.JPG | border|900x600px]]<br />
<br />
<br />
<br />
<br />
===Step 4===<br />
<br />
Click on OK and start the restore. Your data should start restoring.<br />
<br />
<br />
[[File:SQL_Restore_Progress.JPG | border|900x700px]]<br />
<br />
<br />
You might have to take the database offline in case there are any existing connections.<br />
<br />
===Step 5===<br />
<br />
Verify the restored data,once restore has been successful<br />
<br />
<br />
[[File:SQL_Data_Restored.JPG | border|900x700px]]<br />
<br />
<br />
<br />
[[ VERITAS NetBackup Recovery | Return to VERITAS NetBackup Recovery ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2697Recovery as Normal Files(MS-SharePoint)2021-07-14T12:07:06Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named *SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4*<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|900x600px]]<br />
<br />
<br />
===Step 1===<br />
<br />
Login to SSMS(SQL Server Management Studio) and connect to the SQL Server Instance.<br />
<br />
<br />
[[File:SQL_SharePoint_Connect.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 2===<br />
<br />
Right Click and select Restore Database.<br />
<br />
<br />
[[File:SQL_Restore_Database.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 3===<br />
<br />
From Device , select the data file to restore.<br />
<br />
<br />
[[File:SQL_Select_DataFile.JPG | border|900x600px]]<br />
<br />
<br />
<br />
<br />
===Step 4===<br />
<br />
Click on OK and start the restore. Your data should start restoring.<br />
<br />
<br />
[[File:SQL_Restore_Progress.JPG | border|900x700px]]<br />
<br />
<br />
You might have to take the database offline in case there are any existing connections.<br />
<br />
===Step 5===<br />
<br />
Verify the restored data,once restore has been successful<br />
<br />
<br />
[[File:SQL_Data_Restored.JPG | border|900x700px]]<br />
<br />
<br />
<br />
[[ VERITAS NetBackup Recovery | Return to VERITAS NetBackup Recovery ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2696Recovery as Normal Files(MS-SharePoint)2021-07-14T12:06:59Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named *SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4.*<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|900x600px]]<br />
<br />
<br />
===Step 1===<br />
<br />
Login to SSMS(SQL Server Management Studio) and connect to the SQL Server Instance.<br />
<br />
<br />
[[File:SQL_SharePoint_Connect.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 2===<br />
<br />
Right Click and select Restore Database.<br />
<br />
<br />
[[File:SQL_Restore_Database.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 3===<br />
<br />
From Device , select the data file to restore.<br />
<br />
<br />
[[File:SQL_Select_DataFile.JPG | border|900x600px]]<br />
<br />
<br />
<br />
<br />
===Step 4===<br />
<br />
Click on OK and start the restore. Your data should start restoring.<br />
<br />
<br />
[[File:SQL_Restore_Progress.JPG | border|900x700px]]<br />
<br />
<br />
You might have to take the database offline in case there are any existing connections.<br />
<br />
===Step 5===<br />
<br />
Verify the restored data,once restore has been successful<br />
<br />
<br />
[[File:SQL_Data_Restored.JPG | border|900x700px]]<br />
<br />
<br />
<br />
[[ VERITAS NetBackup Recovery | Return to VERITAS NetBackup Recovery ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(Oracle)&diff=2695Recovery as Normal Files(Oracle)2021-07-14T12:06:37Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore Oracle data after it has been recovered as normal files using steps as shown in [[ Recovery as Normal Files(FileSystem) | Recovery as Normal Files ]].<br />
Please recover the Oracle files (dbf's). Once you have the files, please follow the steps to restore.<br />
<br />
The restore of Oracle data can be done from within '''RMAN''' and we restore the backup files from NetBackup to a temporary location on the Oracle server. <br />
<br />
To log in to '''RMAN''', type the command below into a Command Line window. <br />
<br />
{| class="wikitable" style="padding-left: 20px; color:#FFFFFF; background-color: black; width: 900px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap; "<br />
|<br />
rman target /<br />
|}<br />
As soon as you log in to the database, the DBID currently in use will be displayed.<br />
<br />
{| class="wikitable" style="padding-left: 20px; color:#FFFFFF; background-color: black; width: 900px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap; "<br />
|<br />
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Nov 9 11:53:46 2018<br />
<br />
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.<br />
<br />
connected to target database: ORCL (DBID=1490584423)<br />
<br />
RMAN> <br />
|}<br />
__NOTOC__<br />
<br />
<br />
==='''Step 1'''===<br />
{| class="wikitable" style="padding-left: 20px; color:#FFFFFF; background-color: black; width: 900px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap; "<br />
|<br />
RMAN> STARTUP NOMOUNT;<br />
|}<br />
<br />
==='''Step 2'''===<br />
Restore the control file.<br />
<br />
{| class="wikitable" style="padding-left: 20px; color:#FFFFFF; background-color: black; width: 900px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap; "<br />
|<br />
RMAN> REPLICATE CONTROLFILE FROM "C:\Backup\Oracle\ctrl_ORCL_2924.dbf";<br />
|}<br />
<br />
Restore of control file changes the DBID to the target DBID. Run a select DBID from v$database; from SQL to verify that.<br />
<br />
==='''Step 3'''===<br />
Mount the database.<br />
<br />
{| class="wikitable" style="padding-left: 20px; color:#FFFFFF; background-color: black; width: 900px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap; "<br />
|<br />
RMAN> ALTER DATABASE MOUNT;<br />
|}<br />
<br />
==='''Step 4'''===<br />
Configure sbt device.<br />
<br />
{| class="wikitable" style="padding-left: 20px; color:#FFFFFF; background-color: black; width: 900px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap; "<br />
|<br />
RMAN> CONFIGURE DEVICE TYPE sbt_tape PARALLELISM 1;<br />
RMAN> CONFIGURE CHANNEL DEVICE TYPE sbt_tape PARMS='SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=C:\Backup\Oracle)';<br />
|}<br />
<br />
==='''Step 5'''===<br />
Catalog each of the dbf files in turn.<br />
<br />
{| class="wikitable" style="padding-left: 20px; color:#FFFFFF; background-color: black; width: 900px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap; "<br />
|<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_10%3A962806106%3A1%3E.dbf';<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_11%3A977481621%3A1%3E.dbf';<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_12%3A977481656%3A1%3E.dbf';<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_16%3A977491557%3A1%3E.dbf';<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_17%3A977491557%3A1%3E.dbf';<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_18%3A977491557%3A1%3E.dbf';<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_19%3A977491557%3A1%3E.dbf';<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_2%3A962805087%3A1%3E.dbf';<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_20%3A977491575%3A1%3E.dbf';<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_21%3A977491602%3A1%3E.dbf';<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_22%3A977491602%3A1%3E.dbf';<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_23%3A977492038%3A1%3E.dbf';<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_24%3A977492038%3A1%3E.dbf';<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_25%3A977492038%3A1%3E.dbf';<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_26%3A977492046%3A1%3E.dbf';<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_27%3A977492058%3A1%3E.dbf';<br />
RMAN> catalog device type 'SBT_TAPE' backuppiece 'B_ORA_All_Full_BS068%3CORCL_9%3A962806071%3A1%3E.dbf';<br />
|}<br />
<br />
==='''Step 6'''===<br />
Do a crosscheck backup files on disk with entries in the catalog or controlfile.<br />
<br />
{| class="wikitable" style="padding-left: 20px; color:#FFFFFF; background-color: black; width: 900px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap; "<br />
|<br />
RMAN> CROSSCHECK BACKUP;<br />
|}<br />
<br />
==='''Step 7'''===<br />
Restore the database.<br />
<br />
{| class="wikitable" style="padding-left: 20px; color:#FFFFFF; background-color: black; width: 900px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap; "<br />
|<br />
RMAN> RESTORE DATABASE;<br />
|}<br />
<br />
==='''Step 8'''===<br />
Perform this step if redo of all online datafiles needs to be applied.<br />
<br />
{| class="wikitable" style="padding-left: 20px; color:#FFFFFF; background-color: black; width: 900px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap; "<br />
|<br />
RMAN> RECOVER DATABASE;<br />
|}<br />
<br />
<br />
<br />
[[ VERITAS NetBackup Recovery | Return to VERITAS NetBackup Recovery ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2694Recovery as Normal Files(MS-SharePoint)2021-07-14T12:05:54Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4.<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|900x600px]]<br />
<br />
<br />
===Step 1===<br />
<br />
Login to SSMS(SQL Server Management Studio) and connect to the SQL Server Instance.<br />
<br />
<br />
[[File:SQL_SharePoint_Connect.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 2===<br />
<br />
Right Click and select Restore Database.<br />
<br />
<br />
[[File:SQL_Restore_Database.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 3===<br />
<br />
From Device , select the data file to restore.<br />
<br />
<br />
[[File:SQL_Select_DataFile.JPG | border|900x600px]]<br />
<br />
<br />
<br />
<br />
===Step 4===<br />
<br />
Click on OK and start the restore. Your data should start restoring.<br />
<br />
<br />
[[File:SQL_Restore_Progress.JPG | border|900x700px]]<br />
<br />
<br />
You might have to take the database offline in case there are any existing connections.<br />
<br />
===Step 5===<br />
<br />
Verify the restored data,once restore has been successful<br />
<br />
<br />
[[File:SQL_Data_Restored.JPG | border|900x700px]]<br />
<br />
<br />
<br />
[[ VERITAS NetBackup Recovery | Return to VERITAS NetBackup Recovery ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=File:SQL_Data_Restored.JPG&diff=2693File:SQL Data Restored.JPG2021-07-14T12:04:36Z<p>Sachin: </p>
<hr />
<div></div>Sachinhttp://docs.stoneram.com/index.php?title=File:SQL_Restore_Progress.JPG&diff=2692File:SQL Restore Progress.JPG2021-07-14T12:04:11Z<p>Sachin: </p>
<hr />
<div></div>Sachinhttp://docs.stoneram.com/index.php?title=File:SQL_Select_DataFile.JPG&diff=2691File:SQL Select DataFile.JPG2021-07-14T12:03:41Z<p>Sachin: Sachin uploaded a new version of File:SQL Select DataFile.JPG</p>
<hr />
<div></div>Sachinhttp://docs.stoneram.com/index.php?title=File:SQL_Select_DataFile.JPG&diff=2690File:SQL Select DataFile.JPG2021-07-14T12:03:14Z<p>Sachin: Sachin uploaded a new version of File:SQL Select DataFile.JPG</p>
<hr />
<div></div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2689Recovery as Normal Files(MS-SharePoint)2021-07-14T11:17:48Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4.<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|900x600px]]<br />
<br />
<br />
===Step 1===<br />
<br />
Login to SSMS(SQL Server Management Studio) and connect to the SQL Server Instance.<br />
<br />
<br />
[[File:SQL_SharePoint_Connect.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 2===<br />
<br />
Right Click and select Restore Database.<br />
<br />
<br />
[[File:SQL_Restore_Database.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 3===<br />
<br />
From Device , select the data file to restore.<br />
<br />
<br />
[[File:SQL_Select_DataFile.JPG | border|900x600px]]<br />
<br />
<br />
<br />
<br />
===Step 4===<br />
<br />
Click on OK and start the restore. Your data should start restoring.<br />
<br />
<br />
[[File:SQL_Restore_Progress.JPG | border|900x700px]]<br />
<br />
<br />
You might have to take the database offline in case there are any existing connections.<br />
<br />
===Step 5===<br />
<br />
Verify the restored data,once restore has been successful<br />
<br />
<br />
[[File:SQL_Data_Restored.JPG | border|900x700px]]<br />
<br />
<br />
<br />
[[ DP/DataProtector Recovery | Return to DP/DataProtector Recovery ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=File:SQL_Select_DataFile.JPG&diff=2688File:SQL Select DataFile.JPG2021-07-14T11:14:54Z<p>Sachin: Sachin uploaded a new version of File:SQL Select DataFile.JPG</p>
<hr />
<div></div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2687Recovery as Normal Files(MS-SharePoint)2021-07-14T11:14:37Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4.<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|900x600px]]<br />
<br />
<br />
===Step 1===<br />
<br />
Login to SSMS(SQL Server Management Studio) and connect to the SQL Server Instance.<br />
<br />
<br />
[[File:SQL_SharePoint_Connect.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 2===<br />
<br />
Right Click and select Restore Database.<br />
<br />
<br />
[[File:SQL_Restore_Database.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 3===<br />
<br />
From Device , select the data file to restore.<br />
<br />
<br />
[[File:SQL_Select_DataFile.JPG | border|900x600px]]<br />
<br />
<br />
<br />
<br />
===Step 4===<br />
<br />
Click on OK and start the restore. Your data should start restoring.<br />
<br />
<br />
[[File:SQL_Restore_Progress.JPG | border|900x700px]]<br />
<br />
<br />
<br />
===Step 5===<br />
<br />
Verify the restored data,once restore has been successful<br />
<br />
<br />
[[File:SQL_Data_Restored.JPG | border|900x700px]]<br />
<br />
<br />
<br />
[[ DP/DataProtector Recovery | Return to DP/DataProtector Recovery ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2686Recovery as Normal Files(MS-SharePoint)2021-07-14T11:13:27Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4.<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|900x600px]]<br />
<br />
<br />
===Step 1===<br />
<br />
Login to SSMS(SQL Server Management Studio) and connect to the SQL Server Instance.<br />
<br />
<br />
[[File:SQL_SharePoint_Connect.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 2===<br />
<br />
Right Click and select Restore Database.<br />
<br />
<br />
[[File:SQL_Restore_Database.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 3===<br />
<br />
From Device , select the data file to restore.<br />
<br />
<br />
<br />
[[File:SQL_Select_DataFile.JPG | border|900x600px]]<br />
<br />
<br />
<br />
After that , optionally you can click on Verify Backup Media too.<br />
<br />
<br />
===Step 4===<br />
<br />
Click on OK and start the restore. Your data should start restoring.<br />
<br />
<br />
[[File:SQL_Restore_Progress.JPG | border|900x700px]]<br />
<br />
<br />
<br />
===Step 5===<br />
<br />
Verify the restored data,once restore has been successful<br />
<br />
<br />
[[File:SQL_Data_Restored.JPG | border|900x700px]]<br />
<br />
<br />
<br />
[[ DP/DataProtector Recovery | Return to DP/DataProtector Recovery ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=File:SQL_Select_DataFile.JPG&diff=2685File:SQL Select DataFile.JPG2021-07-14T11:13:02Z<p>Sachin: </p>
<hr />
<div></div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2684Recovery as Normal Files(MS-SharePoint)2021-07-14T11:10:36Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4.<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|900x600px]]<br />
<br />
<br />
===Step 1===<br />
<br />
Login to SSMS(SQL Server Management Studio) and connect to the SQL Server Instance.<br />
<br />
<br />
[[File:SQL_SharePoint_Connect.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 2===<br />
<br />
Right Click and select Restore Database.<br />
<br />
<br />
[[File:SQL_Restore_Database.JPG | border|900x600px]]<br />
<br />
<br />
<br />
===Step 3===<br />
<br />
From Device , select the data file to restore.<br />
<br />
<br />
[[File:SQL_Select_DataFile.JPG | border|900x600px]]<br />
<br />
<br />
After that , optionally you can click on Verify Backup Media too.<br />
<br />
<br />
===Step 4===<br />
<br />
Click on OK and start the restore. Your data should start restoring.<br />
<br />
<br />
[[File:SQL_Restore_Progress.JPG | border|900x700px]]<br />
<br />
<br />
<br />
===Step 5===<br />
<br />
Verify the restored data,once restore has been successful<br />
<br />
<br />
[[File:SQL_Data_Restored.JPG | border|900x700px]]<br />
<br />
<br />
<br />
[[ DP/DataProtector Recovery | Return to DP/DataProtector Recovery ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=File:SQL_Restore_Database.JPG&diff=2683File:SQL Restore Database.JPG2021-07-14T11:10:00Z<p>Sachin: </p>
<hr />
<div></div>Sachinhttp://docs.stoneram.com/index.php?title=File:SQL_SharePoint_Connect.JPG&diff=2682File:SQL SharePoint Connect.JPG2021-07-14T10:57:56Z<p>Sachin: </p>
<hr />
<div></div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2681Recovery as Normal Files(MS-SharePoint)2021-07-14T10:56:14Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4.<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|900x700px]]<br />
<br />
<br />
===Step 1===<br />
<br />
Login to SSMS(SQL Server Management Studio) and connect to the SQL Server Instance.<br />
<br />
<br />
[[File:SQL_SharePoint_Connect.JPG | border|900x700px]]<br />
<br />
<br />
<br />
===Step 2===<br />
<br />
Right Click and select Restore Database.<br />
<br />
<br />
[[File:SQL_Restore_Database.JPG | border|900x700px]]<br />
<br />
<br />
<br />
===Step 3===<br />
<br />
From Device , select the data file to restore.<br />
<br />
<br />
[[File:SQL_Select_DataFile.JPG | border|900x700px]]<br />
<br />
<br />
After that , optionally you can click on Verify Backup Media too.<br />
<br />
<br />
===Step 4===<br />
<br />
Click on OK and start the restore. Your data should start restoring.<br />
<br />
<br />
[[File:SQL_Restore_Progress.JPG | border|900x700px]]<br />
<br />
<br />
<br />
===Step 5===<br />
<br />
Verify the restored data,once restore has been successful<br />
<br />
<br />
[[File:SQL_Data_Restored.JPG | border|900x700px]]<br />
<br />
<br />
<br />
[[ DP/DataProtector Recovery | Return to DP/DataProtector Recovery ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2680Recovery as Normal Files(MS-SharePoint)2021-07-14T10:54:30Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4.<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|900x700px]]<br />
<br />
<br />
<br />
===Step 1===<br />
<br />
<br />
===Step 2===<br />
<br />
<br />
===Step 3===<br />
<br />
<br />
===Step 4===</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2679Recovery as Normal Files(MS-SharePoint)2021-07-14T10:54:20Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4.<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|700x600px]]<br />
<br />
<br />
<br />
===Step 1===<br />
<br />
<br />
===Step 2===<br />
<br />
<br />
===Step 3===<br />
<br />
<br />
===Step 4===</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2678Recovery as Normal Files(MS-SharePoint)2021-07-14T10:54:11Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4.<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|600x400px]]<br />
<br />
<br />
<br />
===Step 1===<br />
<br />
<br />
===Step 2===<br />
<br />
<br />
===Step 3===<br />
<br />
<br />
===Step 4===</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2677Recovery as Normal Files(MS-SharePoint)2021-07-14T10:54:02Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4.<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|500x400px]]<br />
<br />
<br />
<br />
===Step 1===<br />
<br />
<br />
===Step 2===<br />
<br />
<br />
===Step 3===<br />
<br />
<br />
===Step 4===</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2676Recovery as Normal Files(MS-SharePoint)2021-07-14T10:53:47Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4.<br />
<br />
<br />
<br />
[[File:SharePoint1.JPG | border|700x600px]]<br />
<br />
<br />
<br />
===Step 1===<br />
<br />
<br />
===Step 2===<br />
<br />
<br />
===Step 3===<br />
<br />
<br />
===Step 4===</div>Sachinhttp://docs.stoneram.com/index.php?title=File:SharePoint1.JPG&diff=2675File:SharePoint1.JPG2021-07-14T10:53:28Z<p>Sachin: </p>
<hr />
<div></div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2674Recovery as Normal Files(MS-SharePoint)2021-07-14T10:53:14Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. ( As the steps are similar to normal SQL database restores so it's up to users preference whether they prefer SQL Server Management Studio, SQL Query or the command line). <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
We are demonstrating restore of database named SharePoint_AdminContent_3cad2f2b-76a6-4621-93bf-cd2668d18eb4.<br />
<br />
<br />
[[File:SharePoint1.JPG | border|700x600px]]<br />
<br />
<br />
===Step 1===<br />
<br />
<br />
===Step 2===<br />
<br />
<br />
===Step 3===<br />
<br />
<br />
===Step 4===</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2673Recovery as Normal Files(MS-SharePoint)2021-07-14T10:19:30Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
===Step 1===<br />
<br />
<br />
===Step 2===<br />
<br />
<br />
===Step 3===<br />
<br />
<br />
===Step 4===</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2672Recovery as Normal Files(MS-SharePoint)2021-07-14T10:19:19Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. <br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
<br />
__NOTOC__<br />
<br />
===Step 1===<br />
<br />
<br />
===Step 2===<br />
<br />
<br />
===Step 3===<br />
<br />
<br />
===Step 4===</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2671Recovery as Normal Files(MS-SharePoint)2021-07-14T10:19:06Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. <br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
__NOTOC__<br />
<br />
===Step 1===<br />
<br />
<br />
===Step 2===<br />
<br />
<br />
===Step 3===<br />
<br />
<br />
===Step 4===</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2670Recovery as Normal Files(MS-SharePoint)2021-07-14T10:18:43Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. <br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}<br />
<br />
<br />
===Step 1===<br />
<br />
<br />
===Step 2===<br />
<br />
<br />
===Step 3===<br />
<br />
<br />
===Step 4===</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2669Recovery as Normal Files(MS-SharePoint)2021-07-14T10:17:22Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. <br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress for SharePoint Farm configuration restore.<br />
| <br />
|}</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2668Recovery as Normal Files(MS-SharePoint)2021-07-14T10:17:09Z<p>Sachin: </p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.<br />
<br />
Below we have demonstrated the restore steps along with the example. <br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note currently work has been done for the SharePoint farm content data restore. Work is still in progress<br />
| for SharePoint Farm configuration restore.<br />
| <br />
|}</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(MS-SharePoint)&diff=2667Recovery as Normal Files(MS-SharePoint)2021-07-14T09:19:25Z<p>Sachin: Created page with "Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in Recovery as Normal Files|Recovery as Normal File..."</p>
<hr />
<div>Below documentation shows how to restore SharePoint data after it has been recovered as normal files using steps as shown in [[Recovery as Normal Files|Recovery as Normal Files]]. Please recover the SharePoint database files as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
Since SharePoint sits on top of SQL Server, which is a relational database management system so eventually we will be doing SQL database restores.<br />
For more information about database types and descriptions please read https://docs.microsoft.com/en-us/sharepoint/technical-reference/database-types-and-descriptions.</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(SAP_R3)&diff=2666Recovery as Normal Files(SAP R3)2021-07-05T14:34:50Z<p>Sachin: </p>
<hr />
<div><br />
Below documentation shows how to restore SAP R3 data after it has been recovered as normal files using steps as shown in [[ Recovery as Normal Files(FileSystem) | Recovery as Normal Files ]]. Please recover the SAP R3 data files, control file and backup id file as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
sap-ora:orats2 62> ls -ltr<br />
total 22445512<br />
-rw-r--r-- 1 orats2 dba 18605 Oct 22 16:16 bezoagvv.anf<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 10:51 sr3.data1<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 10:57 sr3.data2<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:04 sr3.data3<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:10 sr3.data4<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:17 sr3.data5<br />
-rw-r--r-- 1 orats2 dba 1614815232 Oct 21 11:23 sr3.data6<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:30 sr3740.data1<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:37 sr3740.data2<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:44 sr3740.data3<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:50 sr3740.data4<br />
-rw-r--r-- 1 orats2 dba 1059069952 Oct 21 11:53 sr3740.data5<br />
-rw-r--r-- 1 orats2 dba 20979712 Oct 21 11:53 sr3usr.data1<br />
-rw-r--r-- 1 orats2 dba 734011392 Oct 21 11:55 undo.data1<br />
-rw-r--r-- 1 orats2 dba 209723392 Oct 21 11:56 sysaux.data1<br />
-rw-r--r-- 1 orats2 dba 450895872 Oct 21 11:57 system.data1<br />
-rw-r--r-- 1 orats2 dba 20267008 Oct 21 11:57 cntrlTS2.dbf<br />
<br />
|}<br />
<br />
<br />
===Step 1===<br />
<br />
Copy/Move the backup id file (file with extension of .anf or .pff ) to default SAP backup location on the SAP R3 server.<br />
i.e. /oracle/<SID>/sapbackup<br />
<br />
e.g. bezoagvv.anf is the backup id file in our case and we have restored it to our sapbackup location which is /oracle/TS2/sapbackup/bezoagvv.pff<br />
<br />
<br />
===Step 2===<br />
<br />
Copy/Move the other files(data file, control file) to the SAP R3 client under a folder with the name of a backup id without the extension.<br />
<br />
e.g. We have created a folder under /oracle/TS2/sapbackup named bezoagvv. And we have copied the files already there as shown below. <br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
sap-ora:orats2 66> pwd<br />
/oracle/TS2/sapbackup<br />
sap-ora:orats2 67> cd bezoagvv/<br />
sap-ora:orats2 68> ls -ltr<br />
total 22445512<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 10:51 sr3.data1<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 10:57 sr3.data2<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:04 sr3.data3<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:10 sr3.data4<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:17 sr3.data5<br />
-rw-r--r-- 1 orats2 dba 1614815232 Oct 21 11:23 sr3.data6<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:30 sr3740.data1<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:37 sr3740.data2<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:44 sr3740.data3<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:50 sr3740.data4<br />
-rw-r--r-- 1 orats2 dba 1059069952 Oct 21 11:53 sr3740.data5<br />
-rw-r--r-- 1 orats2 dba 20979712 Oct 21 11:53 sr3usr.data1<br />
-rw-r--r-- 1 orats2 dba 734011392 Oct 21 11:55 undo.data1<br />
-rw-r--r-- 1 orats2 dba 209723392 Oct 21 11:56 sysaux.data1<br />
-rw-r--r-- 1 orats2 dba 450895872 Oct 21 11:57 system.data1<br />
-rw-r--r-- 1 orats2 dba 20267008 Oct 21 11:57 cntrlTS2.dbf<br />
-rw-r--r-- 1 orats2 dba 18605 Oct 22 16:16 bezoagvv.anf<br />
|}<br />
<br />
<br />
===Step 3===<br />
<br />
Edit the file and update the backup_dev_type to disk under PARAMETERS section.<br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
BR0101I Parameters<br />
<br />
Name Value<br />
<br />
oracle_sid TS2<br />
oracle_home /oracle/TS2/112_64<br />
oracle_profile /oracle/TS2/112_64/dbs/initTS2.ora<br />
sapdata_home /oracle/TS2<br />
sap_profile /oracle/TS2/112_64/dbs/initTS2.sap<br />
backup_mode PSAPSR3<br />
backup_type offline<br />
backup_dev_type disk<br />
system_info orats2/orats2 sap-ora Linux 3.12.49-11-default #1 SMP Wed Nov 11 20:52:43 UTC 2015 (8d714a0) x86_64<br />
oracle_info TS2 11.2.0.3.0 8192 32 1836601 sap-ora UTF8 UTF8 1850097416 &TS2<br />
sap_info 740 SAPSR3<br />
|}<br />
<br />
<br />
<br />
===Step 4===<br />
<br />
Modify the #SAVED path in the backup id file pointing to the location where your restored files are.<br />
e.g. In our case the files are in /oracle/TS2/sapbackup/bezoagvv/ , so we replaced the path under #SAVED to the path where our files are i.e. /oracle/TS2/sapbackup/bezoagvv/<br />
<br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
BR0280I BRBACKUP time stamp: 2018-10-09 16.59.21<br />
#FILE..... /oracle/TS2/sapdata3/sr3740_1/sr3740.data1<br />
#SAVED.... /oracle/TS2/sapbackup/bezoagvv/sr3740.data1<br />
|}<br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note that this method will overwrite the existing data files. In case you want to avoid overwrite #FILE section of the backupid file could be modified. Please follow the SAP documentation for more details on this.<br />
| <br />
|}<br />
<br />
<br />
===Step 5===<br />
Run brrestore on SAP Oracle Client and feed it the backup id file. Command is : brrestore -b <backup id> -d disk <br />
where d is to read the data from disk.<br />
It has to be run under the database user.<br />
<br />
e.g. In our case we ran the command as below.<br />
brrestore -b bezoagvv.anf -d disk<br />
<br />
You would this warning if you have chose to overwrite the existing data files and other notifications as per your selections.<br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
BR0428W File /oracle/TS2/sapdata2/sr3_1/sr3.data1 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata2/sr3_2/sr3.data2 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata2/sr3_3/sr3.data3 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata2/sr3_4/sr3.data4 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata2/sr3_5/sr3.data5 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata2/sr3_6/sr3.data6 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata3/sr3740_1/sr3740.data1 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata3/sr3740_2/sr3740.data2 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata3/sr3740_3/sr3740.data3 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata3/sr3740_4/sr3740.data4 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata3/sr3740_5/sr3740.data5 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata4/sr3usr_1/sr3usr.data1 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata1/undo_1/undo.data1 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata1/sysaux_1/sysaux.data1 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata1/system_1/system.data1 will be overwritten<br />
<br />
BR0280I BRRESTORE time stamp: 2020-10-30 15.26.10<br />
BR0407I Restore of database: TS2<br />
BR0408I BRRESTORE action ID: rffaewrc<br />
BR0409I BRRESTORE function ID: rsb<br />
BR0449I Restore mode: ALL<br />
BR0419I Files will be restored from backup: bezoagvv.anf 2018-10-09 16.43.11<br />
BR0416I 15 files found to restore, total size 21900.117 MB<br />
BR0424I Files will not be decompressed<br />
BR0421I Restore device type: disk<br />
BR0420I Files will be restored from directory: /oracle/TS2/sapbackup/bezoagvv<br />
<br />
R0280I BRRESTORE time stamp: 2020-10-30 15.26.10<br />
BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRRESTORE:<br />
c<br />
BR0280I BRRESTORE time stamp: 2020-10-30 15.27.08<br />
BR0257I Your reply: 'c'<br />
BR0259I Program execution will be continued...<br />
<br />
BR0351I Restoring /oracle/TS2/sapdata2/sr3_1/sr3.data1<br />
BR0355I from /oracle/TS2/sapbackup/bezoagvv/sr3.data1 ...<br />
|}<br />
<br />
<br />
A successful restore would give notifications like below.<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
BR0351I Restoring /oracle/TS2/sapdata2/sr3_1/sr3.data1<br />
BR0355I from /oracle/TS2/sapbackup/bezoagvv/sr3.data1 ...<br />
<br />
#FILE..... /oracle/TS2/sapdata2/sr3_1/sr3.data1<br />
#RESTORED. /oracle/TS2/sapbackup/bezoagvv/sr3.data1 #0/1<br />
<br />
BR0280I BRRESTORE time stamp: 2020-10-30 15.27.57<br />
BR0418I 1 of 15 files restored - 2000.008 of 21900.117 MB done<br />
BR0204I Percentage done: 9.13%, estimated end time: 15:36<br />
BR0001I *****_____________________________________________<br />
|}<br />
<br />
<br />
<br />
[[ DP/DataProtector Recovery | Return to DP/DataProtector Recovery ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(SAP_R3)&diff=2665Recovery as Normal Files(SAP R3)2021-07-05T14:34:22Z<p>Sachin: </p>
<hr />
<div><br />
Below documentation shows how to restore SAP R3 data after it has been recovered as normal files using steps as shown in [[ Recovery as Normal Files(FileSystem) | Recovery as Normal Files ]]. Please recover the SAP R3 data files, control file and backup id file as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
sap-ora:orats2 62> ls -ltr<br />
total 22445512<br />
-rw-r--r-- 1 orats2 dba 18605 Oct 22 16:16 bezoagvv.anf<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 10:51 sr3.data1<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 10:57 sr3.data2<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:04 sr3.data3<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:10 sr3.data4<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:17 sr3.data5<br />
-rw-r--r-- 1 orats2 dba 1614815232 Oct 21 11:23 sr3.data6<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:30 sr3740.data1<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:37 sr3740.data2<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:44 sr3740.data3<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:50 sr3740.data4<br />
-rw-r--r-- 1 orats2 dba 1059069952 Oct 21 11:53 sr3740.data5<br />
-rw-r--r-- 1 orats2 dba 20979712 Oct 21 11:53 sr3usr.data1<br />
-rw-r--r-- 1 orats2 dba 734011392 Oct 21 11:55 undo.data1<br />
-rw-r--r-- 1 orats2 dba 209723392 Oct 21 11:56 sysaux.data1<br />
-rw-r--r-- 1 orats2 dba 450895872 Oct 21 11:57 system.data1<br />
-rw-r--r-- 1 orats2 dba 20267008 Oct 21 11:57 cntrlTS2.dbf<br />
<br />
|}<br />
<br />
<br />
===Step 1===<br />
<br />
Copy/Move the backup id file (file with extension of .anf or .pff ) to default SAP backup location on the SAP R3 server.<br />
i.e. /oracle/<SID>/sapbackup<br />
<br />
e.g. bezoagvv.anf is the backup id file in our case and we have restored it to our sapbackup location which is /oracle/TS2/sapbackup/bezoagvv.pff<br />
<br />
<br />
===Step 2===<br />
<br />
Copy/Move the other files(data file, control file) to the SAP R3 client under a folder with the name of a backup id without the extension.<br />
<br />
e.g. We have created a folder under /oracle/TS2/sapbackup named bezoagvv. And we have copied the files already there as shown below. <br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
sap-ora:orats2 66> pwd<br />
/oracle/TS2/sapbackup<br />
sap-ora:orats2 67> cd bezoagvv/<br />
sap-ora:orats2 68> ls -ltr<br />
total 22445512<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 10:51 sr3.data1<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 10:57 sr3.data2<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:04 sr3.data3<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:10 sr3.data4<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:17 sr3.data5<br />
-rw-r--r-- 1 orats2 dba 1614815232 Oct 21 11:23 sr3.data6<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:30 sr3740.data1<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:37 sr3740.data2<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:44 sr3740.data3<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:50 sr3740.data4<br />
-rw-r--r-- 1 orats2 dba 1059069952 Oct 21 11:53 sr3740.data5<br />
-rw-r--r-- 1 orats2 dba 20979712 Oct 21 11:53 sr3usr.data1<br />
-rw-r--r-- 1 orats2 dba 734011392 Oct 21 11:55 undo.data1<br />
-rw-r--r-- 1 orats2 dba 209723392 Oct 21 11:56 sysaux.data1<br />
-rw-r--r-- 1 orats2 dba 450895872 Oct 21 11:57 system.data1<br />
-rw-r--r-- 1 orats2 dba 20267008 Oct 21 11:57 cntrlTS2.dbf<br />
-rw-r--r-- 1 orats2 dba 18605 Oct 22 16:16 bezoagvv.anf<br />
|}<br />
<br />
<br />
===Step 3===<br />
<br />
Edit the file and update the backup_dev_type to disk under PARAMETERS section.<br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
BR0101I Parameters<br />
<br />
Name Value<br />
<br />
oracle_sid TS2<br />
oracle_home /oracle/TS2/112_64<br />
oracle_profile /oracle/TS2/112_64/dbs/initTS2.ora<br />
sapdata_home /oracle/TS2<br />
sap_profile /oracle/TS2/112_64/dbs/initTS2.sap<br />
backup_mode PSAPSR3<br />
backup_type offline<br />
backup_dev_type util_file<br />
system_info orats2/orats2 sap-ora Linux 3.12.49-11-default #1 SMP Wed Nov 11 20:52:43 UTC 2015 (8d714a0) x86_64<br />
oracle_info TS2 11.2.0.3.0 8192 32 1836601 sap-ora UTF8 UTF8 1850097416 &TS2<br />
sap_info 740 SAPSR3<br />
|}<br />
<br />
<br />
<br />
===Step 4===<br />
<br />
Modify the #SAVED path in the backup id file pointing to the location where your restored files are.<br />
e.g. In our case the files are in /oracle/TS2/sapbackup/bezoagvv/ , so we replaced the path under #SAVED to the path where our files are i.e. /oracle/TS2/sapbackup/bezoagvv/<br />
<br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
BR0280I BRBACKUP time stamp: 2018-10-09 16.59.21<br />
#FILE..... /oracle/TS2/sapdata3/sr3740_1/sr3740.data1<br />
#SAVED.... /oracle/TS2/sapbackup/bezoagvv/sr3740.data1<br />
|}<br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note that this method will overwrite the existing data files. In case you want to avoid overwrite #FILE section of the backupid file could be modified. Please follow the SAP documentation for more details on this.<br />
| <br />
|}<br />
<br />
<br />
===Step 5===<br />
Run brrestore on SAP Oracle Client and feed it the backup id file. Command is : brrestore -b <backup id> -d disk <br />
where d is to read the data from disk.<br />
It has to be run under the database user.<br />
<br />
e.g. In our case we ran the command as below.<br />
brrestore -b bezoagvv.anf -d disk<br />
<br />
You would this warning if you have chose to overwrite the existing data files and other notifications as per your selections.<br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
BR0428W File /oracle/TS2/sapdata2/sr3_1/sr3.data1 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata2/sr3_2/sr3.data2 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata2/sr3_3/sr3.data3 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata2/sr3_4/sr3.data4 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata2/sr3_5/sr3.data5 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata2/sr3_6/sr3.data6 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata3/sr3740_1/sr3740.data1 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata3/sr3740_2/sr3740.data2 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata3/sr3740_3/sr3740.data3 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata3/sr3740_4/sr3740.data4 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata3/sr3740_5/sr3740.data5 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata4/sr3usr_1/sr3usr.data1 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata1/undo_1/undo.data1 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata1/sysaux_1/sysaux.data1 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata1/system_1/system.data1 will be overwritten<br />
<br />
BR0280I BRRESTORE time stamp: 2020-10-30 15.26.10<br />
BR0407I Restore of database: TS2<br />
BR0408I BRRESTORE action ID: rffaewrc<br />
BR0409I BRRESTORE function ID: rsb<br />
BR0449I Restore mode: ALL<br />
BR0419I Files will be restored from backup: bezoagvv.anf 2018-10-09 16.43.11<br />
BR0416I 15 files found to restore, total size 21900.117 MB<br />
BR0424I Files will not be decompressed<br />
BR0421I Restore device type: disk<br />
BR0420I Files will be restored from directory: /oracle/TS2/sapbackup/bezoagvv<br />
<br />
R0280I BRRESTORE time stamp: 2020-10-30 15.26.10<br />
BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRRESTORE:<br />
c<br />
BR0280I BRRESTORE time stamp: 2020-10-30 15.27.08<br />
BR0257I Your reply: 'c'<br />
BR0259I Program execution will be continued...<br />
<br />
BR0351I Restoring /oracle/TS2/sapdata2/sr3_1/sr3.data1<br />
BR0355I from /oracle/TS2/sapbackup/bezoagvv/sr3.data1 ...<br />
|}<br />
<br />
<br />
A successful restore would give notifications like below.<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
BR0351I Restoring /oracle/TS2/sapdata2/sr3_1/sr3.data1<br />
BR0355I from /oracle/TS2/sapbackup/bezoagvv/sr3.data1 ...<br />
<br />
#FILE..... /oracle/TS2/sapdata2/sr3_1/sr3.data1<br />
#RESTORED. /oracle/TS2/sapbackup/bezoagvv/sr3.data1 #0/1<br />
<br />
BR0280I BRRESTORE time stamp: 2020-10-30 15.27.57<br />
BR0418I 1 of 15 files restored - 2000.008 of 21900.117 MB done<br />
BR0204I Percentage done: 9.13%, estimated end time: 15:36<br />
BR0001I *****_____________________________________________<br />
|}<br />
<br />
<br />
<br />
[[ DP/DataProtector Recovery | Return to DP/DataProtector Recovery ]]</div>Sachinhttp://docs.stoneram.com/index.php?title=Recovery_as_Normal_Files(SAP_R3)&diff=2664Recovery as Normal Files(SAP R3)2021-07-05T14:32:57Z<p>Sachin: </p>
<hr />
<div><br />
Below documentation shows how to restore SAP R3 data after it has been recovered as normal files using steps as shown in [[ Recovery as Normal Files(FileSystem) | Recovery as Normal Files ]]. Please recover the SAP R3 data files, control file and backup id file as shown below. Once you have the files, please follow the steps to restore.<br />
<br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
sap-ora:orats2 62> ls -ltr<br />
total 22445512<br />
-rw-r--r-- 1 orats2 dba 18605 Oct 22 16:16 bezoagvv.anf<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 10:51 sr3.data1<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 10:57 sr3.data2<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:04 sr3.data3<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:10 sr3.data4<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:17 sr3.data5<br />
-rw-r--r-- 1 orats2 dba 1614815232 Oct 21 11:23 sr3.data6<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:30 sr3740.data1<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:37 sr3740.data2<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:44 sr3740.data3<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:50 sr3740.data4<br />
-rw-r--r-- 1 orats2 dba 1059069952 Oct 21 11:53 sr3740.data5<br />
-rw-r--r-- 1 orats2 dba 20979712 Oct 21 11:53 sr3usr.data1<br />
-rw-r--r-- 1 orats2 dba 734011392 Oct 21 11:55 undo.data1<br />
-rw-r--r-- 1 orats2 dba 209723392 Oct 21 11:56 sysaux.data1<br />
-rw-r--r-- 1 orats2 dba 450895872 Oct 21 11:57 system.data1<br />
-rw-r--r-- 1 orats2 dba 20267008 Oct 21 11:57 cntrlTS2.dbf<br />
<br />
|}<br />
<br />
<br />
===Step 1===<br />
<br />
Copy/Move the backup id file (file with extension of .anf or .pff ) to default SAP backup location on the SAP R3 server.<br />
i.e. /oracle/<SID>/sapbackup<br />
<br />
e.g. bezoagvv.anf is the backup id file in our case and we have restored it to our sapbackup location which is /oracle/TS2/sapbackup/bezoagvv.pff<br />
<br />
<br />
===Step 2===<br />
<br />
Edit the file and update the backup_dev_type to disk under PARAMETERS section.<br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
BR0101I Parameters<br />
<br />
Name Value<br />
<br />
oracle_sid TS2<br />
oracle_home /oracle/TS2/112_64<br />
oracle_profile /oracle/TS2/112_64/dbs/initTS2.ora<br />
sapdata_home /oracle/TS2<br />
sap_profile /oracle/TS2/112_64/dbs/initTS2.sap<br />
backup_mode PSAPSR3<br />
backup_type offline<br />
backup_dev_type util_file<br />
system_info orats2/orats2 sap-ora Linux 3.12.49-11-default #1 SMP Wed Nov 11 20:52:43 UTC 2015 (8d714a0) x86_64<br />
oracle_info TS2 11.2.0.3.0 8192 32 1836601 sap-ora UTF8 UTF8 1850097416 &TS2<br />
sap_info 740 SAPSR3<br />
|}<br />
<br />
<br />
===Step 3===<br />
<br />
Copy/Move the other files(data file, control file) to the SAP R3 client under a folder with the name of a backup id without the extension.<br />
<br />
e.g. We have created a folder under /oracle/TS2/sapbackup named bezoagvv. And we have copied the files already there as shown below. <br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
sap-ora:orats2 66> pwd<br />
/oracle/TS2/sapbackup<br />
sap-ora:orats2 67> cd bezoagvv/<br />
sap-ora:orats2 68> ls -ltr<br />
total 22445512<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 10:51 sr3.data1<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 10:57 sr3.data2<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:04 sr3.data3<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:10 sr3.data4<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:17 sr3.data5<br />
-rw-r--r-- 1 orats2 dba 1614815232 Oct 21 11:23 sr3.data6<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:30 sr3740.data1<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:37 sr3740.data2<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:44 sr3740.data3<br />
-rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:50 sr3740.data4<br />
-rw-r--r-- 1 orats2 dba 1059069952 Oct 21 11:53 sr3740.data5<br />
-rw-r--r-- 1 orats2 dba 20979712 Oct 21 11:53 sr3usr.data1<br />
-rw-r--r-- 1 orats2 dba 734011392 Oct 21 11:55 undo.data1<br />
-rw-r--r-- 1 orats2 dba 209723392 Oct 21 11:56 sysaux.data1<br />
-rw-r--r-- 1 orats2 dba 450895872 Oct 21 11:57 system.data1<br />
-rw-r--r-- 1 orats2 dba 20267008 Oct 21 11:57 cntrlTS2.dbf<br />
-rw-r--r-- 1 orats2 dba 18605 Oct 22 16:16 bezoagvv.anf<br />
|}<br />
<br />
<br />
<br />
===Step 3===<br />
Modify the #SAVED path in the backup id file pointing to the location where your restored files are.<br />
e.g. In our case the files are in /oracle/TS2/sapbackup/bezoagvv/ , so we replaced the path under #SAVED to the path where our files are i.e. /oracle/TS2/sapbackup/bezoagvv/<br />
<br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
BR0280I BRBACKUP time stamp: 2018-10-09 16.59.21<br />
#FILE..... /oracle/TS2/sapdata3/sr3740_1/sr3740.data1<br />
#SAVED.... /oracle/TS2/sapbackup/bezoagvv/sr3740.data1<br />
|}<br />
<br />
<br />
{|style="padding: 5px; width: 85%;"<br />
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Please note that this method will overwrite the existing data files. In case you want to avoid overwrite #FILE section of the backupid file could be modified. Please follow the SAP documentation for more details on this.<br />
| <br />
|}<br />
<br />
<br />
===Step 4===<br />
Run brrestore on SAP Oracle Client and feed it the backup id file. Command is : brrestore -b <backup id> -d disk <br />
where d is to read the data from disk.<br />
It has to be run under the database user.<br />
<br />
e.g. In our case we ran the command as below.<br />
brrestore -b bezoagvv.anf -d disk<br />
<br />
You would this warning if you have chose to overwrite the existing data files and other notifications as per your selections.<br />
<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
BR0428W File /oracle/TS2/sapdata2/sr3_1/sr3.data1 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata2/sr3_2/sr3.data2 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata2/sr3_3/sr3.data3 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata2/sr3_4/sr3.data4 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata2/sr3_5/sr3.data5 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata2/sr3_6/sr3.data6 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata3/sr3740_1/sr3740.data1 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata3/sr3740_2/sr3740.data2 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata3/sr3740_3/sr3740.data3 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata3/sr3740_4/sr3740.data4 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata3/sr3740_5/sr3740.data5 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata4/sr3usr_1/sr3usr.data1 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata1/undo_1/undo.data1 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata1/sysaux_1/sysaux.data1 will be overwritten<br />
BR0428W File /oracle/TS2/sapdata1/system_1/system.data1 will be overwritten<br />
<br />
BR0280I BRRESTORE time stamp: 2020-10-30 15.26.10<br />
BR0407I Restore of database: TS2<br />
BR0408I BRRESTORE action ID: rffaewrc<br />
BR0409I BRRESTORE function ID: rsb<br />
BR0449I Restore mode: ALL<br />
BR0419I Files will be restored from backup: bezoagvv.anf 2018-10-09 16.43.11<br />
BR0416I 15 files found to restore, total size 21900.117 MB<br />
BR0424I Files will not be decompressed<br />
BR0421I Restore device type: disk<br />
BR0420I Files will be restored from directory: /oracle/TS2/sapbackup/bezoagvv<br />
<br />
R0280I BRRESTORE time stamp: 2020-10-30 15.26.10<br />
BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRRESTORE:<br />
c<br />
BR0280I BRRESTORE time stamp: 2020-10-30 15.27.08<br />
BR0257I Your reply: 'c'<br />
BR0259I Program execution will be continued...<br />
<br />
BR0351I Restoring /oracle/TS2/sapdata2/sr3_1/sr3.data1<br />
BR0355I from /oracle/TS2/sapbackup/bezoagvv/sr3.data1 ...<br />
|}<br />
<br />
<br />
A successful restore would give notifications like below.<br />
{| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap;<br />
| <br />
BR0351I Restoring /oracle/TS2/sapdata2/sr3_1/sr3.data1<br />
BR0355I from /oracle/TS2/sapbackup/bezoagvv/sr3.data1 ...<br />
<br />
#FILE..... /oracle/TS2/sapdata2/sr3_1/sr3.data1<br />
#RESTORED. /oracle/TS2/sapbackup/bezoagvv/sr3.data1 #0/1<br />
<br />
BR0280I BRRESTORE time stamp: 2020-10-30 15.27.57<br />
BR0418I 1 of 15 files restored - 2000.008 of 21900.117 MB done<br />
BR0204I Percentage done: 9.13%, estimated end time: 15:36<br />
BR0001I *****_____________________________________________<br />
|}<br />
<br />
<br />
<br />
[[ DP/DataProtector Recovery | Return to DP/DataProtector Recovery ]]</div>Sachin