• Locked Locked
  • Replies 6 replies
  • Subscribers 12 subscribers
  • Views 7549 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Litespeed "nice to have" future enhancement suggestions 2017

susan.mcloughlin
over 7 years ago

1. With SQL Server 2012+ and Availability Groups, it would be nice to have the restore option in an automated restore to restore with "No Recovery" so you can restore multiple databases to the secondary for adding to Availability Groups. I had a specific instance where I had to restore 150 databases to the secondary with No Recovery and had to restore them one at a time. ugh. 

2. Backup Templates: Really need an option to schedule differential backups when not using "Fast Compression". There is only the option for scheduling the full and log backups. So you have to create a separate job for each instance outside of the template for diff backups when not using Fast Compression type backups.

 

Parents
  • over 7 years ago
    Hi Alexander,

    It's a long story with multiple factors for the decision, but in short we want to ensure that a full backup is taken every Sunday and only differential and log backups during the week. In a perfect world, it would be nice to use fast compression with all days but Sunday selected not to run a full UNLESS a full didn't exist. We are trying to determine the best way to implement this but also account for when a new database gets added to an instance that the initial full backup is taken accordingly.

    Do you have any suggestions?

    Susan
Reply
  • over 7 years ago
    Hi Alexander,

    It's a long story with multiple factors for the decision, but in short we want to ensure that a full backup is taken every Sunday and only differential and log backups during the week. In a perfect world, it would be nice to use fast compression with all days but Sunday selected not to run a full UNLESS a full didn't exist. We are trying to determine the best way to implement this but also account for when a new database gets added to an instance that the initial full backup is taken accordingly.

    Do you have any suggestions?

    Susan
Children
No Data