mssql

3 Topics

SQL Metadata DB job
Hello All, this is really driving me crazy. I recently noticed some extra jobs under SQL SIP backups with file list as *md.<DBname>* which runs in the end . I thinks its a Metadata job which tracks of all DBs ranunder tht policy schd but i couild not find any documentation which explains its working. I see md.master md.msdb and on many servers i can see md.(any application DB). so how does it woks, any one please share some insight
Azhar4
3 years ago Place NetBackup
1.1KViews
0likes
4Comments
MSSQL Policy - how to configure an exclude list
I am trying to figure out how to add an exclude list to an MS-SQL-Server Policy. The Backup Selection List is WHOLE_DATABASE with multiple instances and the Database Name directive of $ALL (I know I can manually select which databases to backup but I don't want to be responsible if a new database is added to the environment and it isn't added to the selection list). Any help will be greatly appreciated. The master server is running 7.7.3 on Solaris 11, the media server is also 7.7.3 running on Solaris 11 and the client is running 7.7.3 on Windows 2012 and the Windows 2016 edition of MSSQL.
Solved
HPosenRU
6 years ago Place NetBackup
1.8KViews
0likes
4Comments
SQL 2014 Mirror on VMware
Backing up SQL 2014 Mirrored VMs on VMware. Netbackup 7.7.1. The backups are always partially successful with a status 1. The Application State Capture job on the passive node returns the following results: Warning ascc (pid=29156) MSSQL: Skipping database MSSQLSERVER\DB_NAME. The database is in the RESTORING state and cannot be protected. Just want to confirm this is normal behaviour since it's the secondary node. I find it odd that it would return a status 1 for this reason. I would think that the parent job would be able to determine whether the DBs that are in a "restoring state" were picked up in the child job that runs on the primary node.
Solved
arctics2
9 years ago Place NetBackup
2.1KViews
0likes
8Comments