Depending on what version of ontap your running depends.. if you are before a certain version in 8.0.x it just fails, but netapp added in predictive failures into their code that will test the drive based on a set of thresholds, once it falls before it will fail out the drive. In my opinion, it's irrelevant unless you are consistently getting failed drives
... View more
That usually happens in 7-mode if someone is on the cli.. But for the SP it will prompt you for disonnect. Can you make sure the remote support person isn't on the SP
... View more
Ok, so you are running cdot with 8.3rc1. Can you log into cluster over mgmt lif if so type - system service-processor ssh show and system service-process show -instance
... View more
Also, i'm not sure how old your systems are, but you really should upgraded to a newer code. you are on code thats very old. at the cli just type hostname newfilername but it's best to reboot or source rc file srouce -v /etc/rc if you know how to do that
... View more
edit /etc/rc file and change this entry hostname (currentname) to newname you should reboot to take effect. If you dont' want to reboot you can just type that name on the cli
... View more
It sounds like you need to understand the basics a little. Please read the TR guide for snapmirro as well as the data-protection guide for the platform you are on to get a better understanding of how things work. Unless QSM is required, we steer away from it and do volume based replication (VSM) with snapmirror. You do not need snap restore, you just need to understand the concepts of snapmirror . And if you are using vfilers, you should focus on using vfiler-dr
... View more
No worries, i'm battling some other things with a/v So, we have the SVM in round-robin DNS. Let's say svm.domain.com (round robin with two lifs) The vscan server is setup to talk to those lifs... We also have lifs with no failover group assigned for our backup to do node scoped backup, but they aren't in DNS. Now, from the packet trace tcp packets are going over our backup lif.. I can't figure out how this is possible if the LIFS assigned in a/v are the other lifs and not those.. So, i'm perplexed at the traffic flow...
... View more
In a snapmirrored state you cannot change the setting. Did you not get this error message when you tried Warning: Volume "filer:volume" is a SnapMirror destination volume. The Filesystem Size for this volume is derived from its source and cannot be changed. The specified size will be used as the Volume Size. I just ran this in my lab. I'm running 8.3.1rc1
... View more
A couple of comments on this thread as i've been spending some time on this. FYI - resetting the vscan cache fixed this as i must have had some corrupted cache. i've enabled and disabled vscan and created new policies without issue One comment, i've also disabled all on-access policies for the SVM. We are still scanning the files and deleting files that contain viruses (EICAR). So the documentation appears off, it says you "MUST" create an on-access policy. I've seemed to prove that wrong. Anyone else seeing this
... View more
We are working on getting a/v setup correctly, and i'm trying to determine if the issue is on the SVM configuration side or on the Vscan connector side. I've read the best practices guide and the setup guide for 8.3.. (I happen to be running 8.3.1rc), but i think it's irrellevant at this point. The simple question is that on our on-access policy we set the filters to "" This is a snippit frm TR-4286 By default, the scan-mandatory filter is enabled if other filters are not specified. Use double quotes ("" or "-") to disable filters. For information about the parameters that you can use with the vserver vscan on-access-policy create command, see the command’s man page. Essentially, we want to disable on-access filters. All our shares are created with standard vscan op profile in cifs. What happens is once we set the filters to "" (basically disabling it), we can create a file, but we can't read any files or write to any files... I'm thoroughly confused at this point b/c the reality is i don't see an issue on the svm side. what are we missing.. Here's our policy Vserver: svm-name Policy: vscan_scan Policy Status: on Policy Config Owner: vserver File-Access Protocol: CIFS Filters: - Max File Size Allowed for Scanning: 5MB File Paths Not to Scan: - File Extensions Not to Scan: URL, LNK, MDB, PST, NSF, 7Z, CAB, ISO, JAR, RAR, TAR, TGZ, VHD, ZIP, VMDK File Extensions to Scan: * Scan Files with No Extension: true
... View more
