Let's talk about Backup and Recovery! Engage with other data protection experts about NetApp's SnapManager, SnapDrive, SnapProtect and SnapCenter, Ransomware Protection, etc.
Let's talk about Backup and Recovery! Engage with other data protection experts about NetApp's SnapManager, SnapDrive, SnapProtect and SnapCenter, Ransomware Protection, etc.
For example, if snapshot is set for the share of \\ svm01 \ smb02, the \\ svm01 \ smb02 \ ~ snapshot folder will be displayed for FAS. (When show snapshot is set) -exclude path (‘* \ ~ snapshot \ *’) was able to exclude at scan time. I wanted to exclude the regular folder \\ svm01 \ smb02 \ test, but I didn't exclude it without -exclude path (‘* \\ test \\ *’).(Two \) It seems that some folders can be excluded with -exclude path (‘* \ <$ name> \ *’), but what is the condition for having to add two \s? Or is it better to always have two \s attached?
... View more
> version NetApp Release 9.15.1P5 1. I have a snapmirror relationship and I manually mirrored a snapshot "test5" from source to destination using the below command. Dest > snapmirror -update -destination-path <> -snapshot test5 2. I created a flexclone at the destination using the snapshot test5 > vol clone show Parent Parent Parent Vserver FlexClone Vserver Volume Snapshot State Type ------- ------------- ------- ------------- -------------------- --------- ---- dest vol_dest_clone dest vol_dest test5 online RW 3. Now, I deleted(accidentally) the test5 snapshot at the source forcefully *> snap delete -vserver source -volume vola -snapshot test5 -ignore-owners true 4. The snapmirror relationship is not affected by this even after an update: >snapmirror update -destination-path dest:vol_dest > snapmirror show Progress Source Destination Mirror Relationship Total Last Path Type Path State Status Progress Healthy Updated - ---------- ---- ------------ ------- -------------- --------- ------- -------- SourceLocal:vola XDP dest:vol_dest Snapmirrored Idle - true - Question: - From the past experience I have noted that this type of action affects the snapmirror relationship. As mentioned in a 3rd party article: ~~~ If a FlexClone volume is created from a Snapshot copy that is not the most recent Snapshot copy, and that Snapshot copy no longer exists on the source volume, then every update will need to delete the Snapshot copy on the destination. In this case, all SnapMirror updates to the destination volume fail until the clone is destroyed or split. ~~ What has changed on a newer version of Netapp that deleting the source snapshot does not affect snapmirror? Or it only affects if snapshot deleted is a baseline snapshot?
... View more
Hi! I am thinking of installing the snapcenter plugin for vSpherere in an environment where the main datacenter storage is served via FC and the DR site would have iSCSI connectivity. The question is if in this scenario, Snapcenter would be able to mount snapshots on the DR site being the protocol different from the production site. Thanks
... View more
Hello All, We are using an archiving (HSM) solution where the archiving application uses NetApp Fpolicy. After migrating files off a NetApp smb share to s3 storage, the fpolicy engine leaves a stub at the original location. This "stub" is used to recall the file back to the original location when it is accessed. These stubs cause problems when backing up through veeam. When using "flat" fileshare backup the stubs are not backed up, it causes a recall from the archive. (This is not what you want). There is no functionality in veeam to skip the stubs. When using the NetApp storage integration in Veeam. (eg. Snapshot). The stubs are then skipped on the basis of an access denied. (Skiping is what you want, not how it is done) The Fpolicy server rejects stub backup/ restore from a Snapshot. [SNAPSHOT_ACCESS_BLOCKED]. We tested this with Ontap release 9.12.1 P4 and 9.13.1 P4. Are there any best-practices to integrate Veeam with NetApp Fpolicy stub backup? NDMP is not an option as it is very basic within veeam. Thanks in advance. Pieter van de Burg
... View more
Hello Community, we have a working Netapp Setup with 3 different size Disks. Recerntly I noticed that there is a disk failure and the system already replaced it with one of the Spare disks. I wish to now insert a disk of the same size as spare for future. Unfortunately I only have higher range disks in stock. Questions , 1. I think I can add higher sized disk into spare and when one of the lower sized disks fails , it will still get replaced with the higher ones. Correct me if I am wrong. But the documentation says its possible without disturbing the RAID structure. Only drawback is that the extra space will get wasted. Thats ok with me. But please confirm that its possible. 2. Secondly I do have same sized disks as well but they are not new. They are taken out from older Netapp which is not in use anymore. So first , am I allowed to add such disks straightaway as spare in existing Netapp? If yes , will the procedure be same? Normally we just take out the failed disk and insert a new one in the same slot. And using command <disk assign disk-id> I would add the new disk to spare. Will this procedure remain same or I should be deleting existing data from the disk first? I assume there could be data on these disks, as they were in use in older Netapp. Kindly point me in right direction. Thanks in advance. Regards, Sachin
... View more
