Skip to main content
NetApp Knowledge Base

CSNAPC-11480: Using Powershell to clone an SQL Database from secondary storage does not apply all logs as requested

  1. Last updated
  2. Save as PDF
Views:
6
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Issue

To clone a database, it is normally possible to include all transaction logs since the backup to be applied automatically, even for restoring from secondary.
This either applies the current logs when cloning a single database locally, or by cloning the Log Directory disk (HLD) when the destination is on a different Host/instance from its last backup.
This works fine when done from the GUI, who will output this in the SCSQL job log:
// Some comments here
<NUMBER_OF> Log backups of database [<DATABASE>] are successfully restored....

However, when attempting from Powershell, even with including the ArchivedLocators, fails to clone the Log Directory, since it doesn't pick up all that information from the repository (unlike GUI usage), and thereby fails to apply any extra logs. That example line will be missing from the SCSQL job log.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.