Hi Jean-Baptiste Do you have a Solution for this founded? We have the same challange at our site. TIA Thomas ... View more

Hi Wei Thanks for your quick answer and your explanantions.. I Know its a small detail, but sometimes such things can have a significant impact. Thats why I wanna be sure I set the right values.. regards and a nice weekend Thomas ... View more

Hi Wei Its over a year you make following statement: with SMB2 the size is 2MB (2097152) In the TR-3869 the value is 2096560. Which one is now correct or it doesn't matter which value I take? Thanks Thomas ... View more

Hi jan Thanks for your answer. This is also the reason, why it doesn't happen on my Simulator (Beacuse is a Workgroup and so the setup doesnt ask for DNS related things) regards Thomas ... View more

Hi You can enable login tracing for investigate what happend during accessing c$ Options cifs trace_login on Regards Thomas ... View more

Hi Stephanie Befor this Error happen I have did following Steps: - Because an other Issue, I have removed the Mirror Nodes from the dataset. - Provisioning Manager has made New Mirror Volumes - Because of Bad calculating the Mirror Size the creation of snapmirror Relationsships has failed - Over the Hosts/Aggregate/Manage Space I have resized the Backup Node - After the resizing the Relationship was created successfully, but since Then I Have the Behavior, which I have described above: - Since I have resize The Mirror Node (over the Controller CLI) to a big Value (20TB) the snapmirror update works and only the Resize Error happen: regards Thomas ... View more

Hi - I would recommend you to install DSM-MPIO also. Since Version 3.5 you dont need anymore the Host Utilities, because DSM MPIO set the recommended Values:      New features in this Host Utilities release      Windows Host Utilities 6.0 includes several new features and support for additional configurations.      Host Utilities 6.0 includes the following changes from 5.3:      •    The Host Utilities are no longer required if the Windows host is running the Data ONTAP DSM      3.5 for Windows MPIO or later. - Best Practise --> http://media.netapp.com/documents/tr-4001.pdf - Snapdrive Dokus --> http://support.netapp.com/NOW/download/software/snapdrive_win/6.4.2/ - I recommend to setup the iscsi sessions/LUNs within snapdrive. The Volumes and the Qtrees you have to create on the Filer (System Manager/CLI). - When you add a shared LUN in a Cluster, snapdrive connect the Disk on both node and create the Cluster Ressource group also (Or add a Disk to a existing Cluster Ressource Group. Only the iscsi Sessions you have to establish on both nodes as First Step. regards Thomas ... View more

Hi The same Problem here (Do you have you received a Solution from Netapp in the Meantime?) : OCUM5.1 Primary-->Snapvault-->Snapmirror - My Dataset U:\>dfpm dataset list -R 96671 Id         Name                        Protection Policy           Provisioning Policy Relationship Id State        Status  Hours Source                       Destination ---------- --------------------------- --------------------------- ------------------- --------------- ------------ ------- ----- ---------------------------- ---------------------------- 96671 Dataset1      Standard                                           96678 snapvaulted  idle 9.9 vfilerprod:/vfilerprod_cifs_share2/- vfilerSV:/Standard_backup/cifs_share2 96671 Dataset1      Standard                                           96680 snapvaulted  idle    9.9 vfilerprod:/vfilerprod_cifs_share1/- vfilerSV:/Standard_backup/cifs_share1 96671 Dataset1      Standard                                           96682 snapvaulted  idle    9.9 vfilerprod:/vfilerprod_cifs_share2/dbbackuppf vfilerSV:/Standard_backup/dbbackuppf 96671 Dataset1      Standard                                           96684 snapvaulted  idle 9.9 vfilerprod:/vfilerprod_cifs_share1/dbbackupab1 vfilerSV:/Standard_backup/dbbackupab1 96671 Dataset1      Standard                                           96688 snapmirrored idle    46.7  vfilerSV:/Standard_backup filerSM:/Standard_mirror - Snapvault Volume Size reported by DFM Report U:\>dfm report view volumes-capacity 96674 Object ID Volume           Aggregate Storage Server                               Used        Total       Used (%) --------- ----------------------------- --------- ------------------------------- ----------- ----------- -------- 96674     Standard_backup aggr3     vfilerSV.domain                               10256589560 16066582712     63.8 Totals                                                                            10256589560 16066582712     63.8 - Snapvault Volume Size on Controller filerSV> df -V Standard_backup Filesystem kbytes       used      avail capacity  Mounted on /vol/Standard_backup/ 16066582712 10256890328 5809692384      64% /vol/Standard_backup/ /vol/Standard_backup/.snapshot 0 8882897080          0     ---% /vol/Standard_backup/.snapshot - The Remote Backup DSS Job report a current Total Size of 2TB (instead of 14TB). In the Past Every Job report this 2 TB and resize to 14TB, but on the controller its already 14TB . Fact is DSS read the wrong Value of 2TB every Time DSS runs. - Snapmirror Volume Size on Controller filerSM> df -V Standard_mirror Filesystem kbytes       used      avail capacity  Mounted on /vol/Standard_mirror/ 15350455768 9670474332 5679981436 63%  /vol/Standard_mirror/ /vol/Standard_mirror/.snapshot          0 8288095364          0 ---%  /vol/Standard_mirror/.snapshot - The Mirror Backup DSS Job try to resize to 2TB (I Think its because the wrong 2TB is reported as current Size from Backup DSS Job and the resize fails.Then the snapmirror Job fails because the current Size of the snapmirror Volume is a few Bytes   smaller (16066582712-15350455768=716126944B~683MB). - We have 76 Datasets (Oracle_Snapcreator/SMSQL (Backup only)/CIFS/NFS)and this happen only on 1 Datasets since few Weeks and on 2 other Dataset sporadically. regards Thomas ... View more

Hi All FYI: Since Yesterday we running snapcreator 3.6p1 with oncommand 5.1. Till a few Minutes all looks good, but now a Job has failed with the error "in Zapi::invoke, cannot connect to socket" errno="13001"></results>" :-(.. the scheduler work like expected (No Scheduled Jobs get lost ) ... Now I have to open a Case.... regards Thomas ... View more

First you have to stop your current Relationship (snapvault stop). This will delete the qtree on the destination System (The qtree will be still available in the snapshots). Then you have to Start the Relationship (New Baseline Transfer) and the qtree will be created and your snapvault for this source qtree is back again.. Regards Thomas ... View more

Hi Nayab It looks like you have loose your snapvault Base snapshot (This snapshot reside on both sides and will be used for snapvault updates or resynchronisation). You have to do a new Baseline (snapvault start)... regards Thomas ... View more

Hi Pls try to disable certificate revocation (You have do this setting with your snapdrive Service Account --> Internetexplorer runAs <snapdriveuser>) regards Thomas ... View more

Hi fe: -  7G: netbsd, 8: freebsd - 64bit aggr - Compression - Better Multicore support ..... regards Thomas ... View more

Hi When its possible, every raidgroup in a aggr should have the same amount of disks. In your case 15 Disks... Regards Thomas ... View more

Hi Joe Could you run a vfiler status -r on both Filers and put the output in this thread? Does all vfiers Fails (unconfigured) during a takeover or only a few? regards Thomas ... View more

Hi Adai Like you have suggested, I have open a Case for a RFE. The Number ist 2004125420.... Thanks for your help Thomas ... View more

Hi Paul When its NFS: Do you have exported the Qtree or the Volume? In the Past it was a Problem, when you export the Qtree. I dont know, wether its still a Problem. regards Thomas  ... View more

Hi Adai Thanks for your response... Sometimes the Issue happens sometimes not. I think everytime the Backup Node gets resized down, the warning on the Mirror Node comes Back. My last question in this thread is: Where do I open a RFE? Thanks a lot for your explanation Thomas ... View more

Hi Adai I have read a discussion about the hidden option resize_up_only. In my Case set to 1 would be a solution, Because Mirror Node would not try to make snapmirror destination smaller than the source Volumen (because no resize down happen), correct? Are there different Sizing Settings for DSS Backup Node and DSS Mirror Node. When yes I could set different Values to avoid the "smaller than" Issue Regards Thomas ... View more

Hi Adai Do you have Solution yet for this "little Problem" regards Thomas ... View more

Hi You have to type "partner" on the console, then you are on the failovered Filer... Regards Thomas ... View more

Hi Adai Case is open since 7 hours (Case No. 2004037295) 🙂 regards Thomas ... View more

Hi Adai I know about the DSS feature in 5.1, But the message I see is a warning. Its this warning expected? Server_AllDBs_arch: Could not resize secondary volume Nearstore:/Server_AllDBs_arch_mirror_1 (33160) to 363 GB. The new volume size would be less than that of the replica file system The Problem is, that this warning markes my snapcreator Job Status as yellow (normally green). Can I disable this warning (like the "processHostPrimaryAddress" Option)? I have solved the problem, before you have send me your workaround. So I couldn't test your workaround.. regards Thomas ... View more