Help!
We have a SQL Cluster, running Server 2003, Snapdrive 3.2r1 and Snapmanager SQL 1.5
On node one, we have an sql instance that runs that Snapshots/Snapmirrors the SQL data over to our offsite location twice a day. Works like a champ.
On node two, we have a new instance running all the same software, the backup runs and complets with no issues, but for some reason it will not snapmirror.
From the logs, it looks like it doesn't even try. There are no errors.
On the node that works, we get the following in the backuplogs:
*** REQUEST SNAPMIRROR UPDATE AFTER BACKUP ***
Starting SnapMirror update...
Querying disk list for SnapMirror update...
Requesting SnapMirror update for LUN [G:] on volume [musql2k_1_database] of filer [URBFiler2]...
Request for SnapMirror update for LUN [G:] was completed successfully.
Requesting SnapMirror update for LUN [K:] on volume [musql2k_1_logs] of filer [URBFiler2]...
Request for SnapMirror update for LUN [K:] was completed successfully.
Requesting SnapMirror update for LUN [I:] on volume [musql2k_1_snapinfo] of filer [URBFiler2]...
Request for SnapMirror update for LUN [I:] was completed successfully.
There is no such text on Node 2, even though it's set to Snapmirror:
Full database backup
Maximum databases of concurrent backup: 255
Naming convention: Generic
Run transaction log backup after full database backup: Yes
Keep the oldest 3 full backups.
Retain up-to-the-minute restore ability for older backups in other management groups: No
Leave database attached after DBCC: No
Run DBCC CHECKDB with Live Database Before Backup: No
Run DBCC CHECKDB with Live Database After Backup: No
Backup Management Group: Standard
Update SnapMirror after operation: Yes <----------------
Run Command after operation: No
I have reinstalled SMSQL, and I can even manually kick off a snapmirror from the node inside of Snapdrive so I know were talking on the right ports.
I have double checked the RSH access, and it all seems to be in order. Both the SQL instance has access as well as the Snapdrive service account.
Any suggestions? I've been fighting this for five days. Netapp support is trying to help, but we're getting no where fast.
Rod Newcomb
Dumb question, you sure there's a snapmirror license on node 2?
Thanks and regards,
Glenn (the other one)
________________________________
From: owner-toasters@mathworks.com on behalf of Rod Newcomb Sent: Fri 2/9/2007 5:14 PM To: toasters@mathworks.com Subject: Snap Manager for SQL / SnapMirror issue.
Help!
We have a SQL Cluster, running Server 2003, Snapdrive 3.2r1 and Snapmanager SQL 1.5
On node one, we have an sql instance that runs that Snapshots/Snapmirrors the SQL data over to our offsite location twice a day. Works like a champ.
On node two, we have a new instance running all the same software, the backup runs and complets with no issues, but for some reason it will not snapmirror.
From the logs, it looks like it doesn't even try. There are no errors.
On the node that works, we get the following in the backuplogs:
*** REQUEST SNAPMIRROR UPDATE AFTER BACKUP ***
Starting SnapMirror update...
Querying disk list for SnapMirror update...
Requesting SnapMirror update for LUN [G:] on volume [musql2k_1_database] of filer [URBFiler2]...
Request for SnapMirror update for LUN [G:] was completed successfully.
Requesting SnapMirror update for LUN [K:] on volume [musql2k_1_logs] of filer [URBFiler2]...
Request for SnapMirror update for LUN [K:] was completed successfully.
Requesting SnapMirror update for LUN [I:] on volume [musql2k_1_snapinfo] of filer [URBFiler2]...
Request for SnapMirror update for LUN [I:] was completed successfully.
There is no such text on Node 2, even though it's set to Snapmirror:
Full database backup
Maximum databases of concurrent backup: 255
Naming convention: Generic
Run transaction log backup after full database backup: Yes
Keep the oldest 3 full backups.
Retain up-to-the-minute restore ability for older backups in other management groups: No
Leave database attached after DBCC: No
Run DBCC CHECKDB with Live Database Before Backup: No
Run DBCC CHECKDB with Live Database After Backup: No
Backup Management Group: Standard
Update SnapMirror after operation: Yes <----------------
Run Command after operation: No
I have reinstalled SMSQL, and I can even manually kick off a snapmirror from the node inside of Snapdrive so I know were talking on the right ports.
I have double checked the RSH access, and it all seems to be in order. Both the SQL instance has access as well as the Snapdrive service account.
Any suggestions? I've been fighting this for five days. Netapp support is trying to help, but we're getting no where fast.
Rod Newcomb
Hi Ron!
On 2/9/07, Rod Newcomb rodn@dice.com wrote:
Help!
We have a SQL Cluster, running Server 2003, Snapdrive 3.2r1 and Snapmanager SQL 1.5
On node one, we have an sql instance that runs that Snapshots/Snapmirrors the SQL data over to our offsite location twice a day. Works like a champ.
On node two, we have a new instance running all the same software, the backup runs and complets with no issues, but for some reason it will not snapmirror.
From the logs, it looks like it doesn't even try. There are no errors.
A few pointers:
* For a snapmirror update to work, the volumes that you have stored your luns on, must be in a snapmirrored state to begin with. You can check that in FilerView or on the cli: snapmirror status. Remember that SnapDrive only supports VSM, not QSM. * Does the snapmirror update work when you use sdcli by hand ? You can find sdcli in c:\program files\netapp\snapdrive\sdcli.exe. When you create a snapshot using sdcli, you can force a mirror update, for instance * When you completely failover the cluster to node 1, does all work as expected? * Same for node 2
HTH & HAND!
Nils
Are you running the same version of ONTAP on both ends?
Rod Newcomb wrote:
Help!
We have a SQL Cluster, running Server 2003, Snapdrive 3.2r1 and Snapmanager SQL 1.5
On node one, we have an sql instance that runs that Snapshots/Snapmirrors the SQL data over to our offsite location twice a day. Works like a champ.
On node two, we have a new instance running all the same software, the backup runs and complets with no issues, but for some reason it will not snapmirror.
From the logs, it looks like it doesn't even try. There are no errors.
On the node that works, we get the following in the backuplogs:
*** REQUEST SNAPMIRROR UPDATE AFTER BACKUP ***
Starting SnapMirror update...
Querying disk list for SnapMirror update...
Requesting SnapMirror update for LUN [G:] on volume [musql2k_1_database] of filer [URBFiler2]...
Request for SnapMirror update for LUN [G:] was completed successfully.
Requesting SnapMirror update for LUN [K:] on volume [musql2k_1_logs] of filer [URBFiler2]...
Request for SnapMirror update for LUN [K:] was completed successfully.
Requesting SnapMirror update for LUN [I:] on volume [musql2k_1_snapinfo] of filer [URBFiler2]...
Request for SnapMirror update for LUN [I:] was completed successfully.
There is no such text on Node 2, even though it's set to Snapmirror:
Full database backup
Maximum databases of concurrent backup: 255
Naming convention: Generic
Run transaction log backup after full database backup: Yes
Keep the oldest 3 full backups.
Retain up-to-the-minute restore ability for older backups in other management groups: No
Leave database attached after DBCC: No
Run DBCC CHECKDB with Live Database Before Backup: No
Run DBCC CHECKDB with Live Database After Backup: No
Backup Management Group: Standard
Update SnapMirror after operation: Yes <----------------
Run Command after operation: No
I have reinstalled SMSQL, and I can even manually kick off a snapmirror from the node inside of Snapdrive so I know were talking on the right ports.
I have double checked the RSH access, and it all seems to be in order. Both the SQL instance has access as well as the Snapdrive service account.
Any suggestions? I've been fighting this for five days. Netapp support is trying to help, but we're getting no where fast.
Rod Newcomb
-
Glenn Dekhayser -
Nils Vogels -
Rod Newcomb -
tux79