-
- Veteran
- Posts: 391
- Liked: 56 times
- Joined: Feb 03, 2017 2:34 pm
- Full Name: MikeO
- Contact:
SQL Explorer issue
Setup:
Production server that is protected by Veeam is a 2008 SP4 SQL instance
Staging SQL server is SQL 2014 (a virtual machine)
Veeam B&R is physical v9.5
When performing a restore export to folder the 2008 database is first restored to the staging server (2014). Once its done replaying the transaction logs the export proceeds. The DB and log file are exported to my destination folder of choice.
Issue:
When attempting to mount the exported database on any SQL 2008 instance I get a version is greater then error. No downgrade is possible. This is because the staging server is SQL 2014. The only way around this issue is to make the staging server SQL 2008 and repeat the process.
Production server that is protected by Veeam is a 2008 SP4 SQL instance
Staging SQL server is SQL 2014 (a virtual machine)
Veeam B&R is physical v9.5
When performing a restore export to folder the 2008 database is first restored to the staging server (2014). Once its done replaying the transaction logs the export proceeds. The DB and log file are exported to my destination folder of choice.
Issue:
When attempting to mount the exported database on any SQL 2008 instance I get a version is greater then error. No downgrade is possible. This is because the staging server is SQL 2014. The only way around this issue is to make the staging server SQL 2008 and repeat the process.
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: SQL Explorer issue
Hi Mike, this is expected behavior. Database is upgraded upon being attached to SQL 2014, so cannot be then attached to an earlier version.
-
- Veteran
- Posts: 391
- Liked: 56 times
- Joined: Feb 03, 2017 2:34 pm
- Full Name: MikeO
- Contact:
Re: SQL Explorer issue
OK, however I was doing some practice runs on a SQL 2005 server restoring to "Other server" so I can rename the database. I used the 2014 Staging instance and was able to recover back to 2005. That being the case I think doing a database export should leave the DB in its original version, in this case (100).
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: SQL Explorer issue
Staging server is not used in case of restore, the database was mounted directly to the target server.
-
- Veteran
- Posts: 391
- Liked: 56 times
- Joined: Feb 03, 2017 2:34 pm
- Full Name: MikeO
- Contact:
Re: SQL Explorer issue
Gotcha. Thank you sir
Who is online
Users browsing this forum: Bing [Bot], Google [Bot], Majestic-12 [Bot], restore-helper and 141 guests