We have a " 2 node SQL D/B cluster ( active - passive)" which I need to backup.
We have I Virtual Server defined in this evn.
Here is what I understand from PDF, please let me know if I am doing any thing wrong.
1. Install "NW Client & NW Module for SQL" on both the P-Nodes.
2. Add 1 instance of each P-Node to backup server , mentioning "ALL" the drives
in the saveset list.
3. Add 2 instances of V-Node to backup server
i) In one instance mention "MSSQL:" in saveset list and ¿nsrsqlsv¿ in command.
ii) And in other specify names of all File systems ( Drive Letters ) as saveset and in command ¿save ¿c
Thanks for your reply. In our case SQL DBA wants to kick off the backups from his side using "nsrsqlsv". In this case I want know as how many instances should I have exactly add to accomplish this task ?
if you're using your virtual node to backup your MSSQL databases backup command must be ¿nsrsqlsv -a ¿ instead of "nsrsqlsv" (this is similar to save's -c option for fs backup). If you're running a dedicated database cluster (meaning no other stuff running on the servers) the file system backup of your virtual node may be obsolete as all database files (that are normaly stored on cluster shared disks) are already backed up with NMSQL...
if you're using your virtual node to backup your MSSQL databases backup command must be ¿nsrsqlsv -a ¿ instead of "nsrsqlsv" (this is similar to save's -c option for fs backup). If you're running a dedicated database cluster (meaning no other stuff running on the servers) the file system backup of your virtual node may be obsolete as all database files (that are normaly stored on cluster shared disks) are already backed up with NMSQL...
regards.
Hi bkppkb,
if you're using your virtual node to backup your MSSQL databases backup command must be ¿nsrsqlsv -a ¿ instead of "nsrsqlsv" (this is similar to save's -c option for fs backup). If you're running a dedicated database cluster (meaning no other stuff running on the servers) the file system backup of your virtual node may be obsolete as all database files (that are normaly stored on cluster shared disks) are already backed up with NMSQL...
regards.
Hi,
I have added 2 P-Nodes for regular OS backup and added V-Node to backup the shared-drives of the cluster.
And SQL DBA is running the initiating the backups from SQL agent ( I suppose this is a like SQL schedular ) using the following command. nsrsqlsv -s -C -c -g
So I am not using nsrsqlsv in the command attributes on V-node configuraiton.
So far I see the backups are going well and I see that the D/B backups are updating the CFI of the V-Node that I defined on NW server.
All the 3 clients that I defined on NW server are going to a diffrent pool and the SQL DBA initiated backups are going to different pool. I dont see any thing wrong in this.
If any one has any suggestions or corrections regarding the above it would be great.
you can schedule MSSQL backups as well. You'd need a separate V-node client created with nsrsqlsv command set as backup command attribute. Another suggestion: Perform a recover test to verify that your backup is working and that you're familiar with recover procedures.
dpinink_silva
2 Intern
•
724 Posts
653
0
Posted November 9th, 2007 18:00
Take a look at the Nw module for SQL manual about users and permissions you may need to set to do the backup.
After that, go ahead!