The transition to NetApp MS Azure AD B2C is complete. If you missed the pre-registration, you will be invited to reigister at next log in.Please note that access to your NetApp data may take up to 1 hour.To learn more, read the FAQ and watch the video.Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.
Before I reinvent the wheel here, has anyone created a SQL Job that polls sys.sysdatabases, and creates the BACKUP statement for NETApp on the fly. In most cases, this shouldn't be needed because we know which databases are on the server, but we do have a few servers where the application actually creates new databases based on size of the previous database. It would be great to be able to make sure those databases are being backed up, too, without having to go in and recreate the backup in SnapManager.
So, for example, a database server has SnapManager installed and is currently backing up appdb1, appdb2, and appdb3. Based on some configuration of the application, it is determined that there is a need for appdb4, so it is created. The job script I am looking for would run every time there is a scheduled backup, and in this case, would see the list of databases, including the new database, and incorporate that into a new backup statement to be executed.
I know this is an old post, but in case somebody else stumbles up on this with similar requirements here's an easy way to solve this. SMSQL will create consistent backup of ANY database as long as it shares the same volume (and is connected to the same SQL instance) as the 'known' database. This means you just need to specify the name of the database you know exist and all other databases, created on the fly by your application, will benefit from this by sharing the same NetApp storage. Hope this makes sense.