Creating Image from multiple file SQL Backups

• 
  Not sure if it comes into play, but could file zeroing be a thing here? Would Instant File Initialization be helpful if so?
  
  Other than that, I would say it is VERY dependent on your IO read, network, IO write capabilities and latencies - which can each be a HUGE impediment to throughput.

  TheSQLGuru August 08, 2017 22:45

  - 0 +
• 
  Hi, We have good IO performance on this server, we run ETL processes with large data throughput without problem. The backups I use is local on the server, so not a network problem. I have now also tried creating a image from a 100GB local database, but it also shows "checking for compatibility.." for the last 2 hours.
  Is there anyone that use SQLClone for larger databases 100GB plus?
  Maybe there is an issue with the evaluation version?
  
  Jaco

  JacoNZ August 08, 2017 23:02

  - 0 +
• 
  I've been running it on a 200gb backup and it takes around 40 minutes (on very weak hardware) to create an image. However, it's a single file backup. I haven't tested it on a multi-file backup yet.

  Grant August 09, 2017 12:12

  - 0 +
• 
  Hi Grant. Restoring the database takes 3 hours on this server. When trying to create a image from the same backup it does not get past the "checking for compatibility.."
  I also tried creating a image directly from a 100Gb database, this also does not get past the "checking for compatibility.." There are no errors.

  JacoNZ August 09, 2017 21:27

  - 0 +
• 
  It does work when I create an image from a database with no data.
  We are using SQL Server 2016 and the backups are made using Redgate SQL Backup 7
  OS: Windows Server 2012 R2
  Processor: Intel Xeon CPU E5-2650 0 @ 2.00GhZ (2 processors)
  RAM: 224Gb
  Storage: SAN
  

  JacoNZ August 09, 2017 21:42

  - 0 +
• 
  That's odd behavior. I'll see if someone from the team can look into it.

  Grant August 09, 2017 22:55

  - 0 +

Add comment

Please sign in to leave a comment.