Hi Toasters,
I have a number of volumes running from a common snapshot and would like to split them out.
All these volumes are snapmirrored to our DR site.
However, when I try to perform a vol clone split, it complains about an in-use snapshot.
Reading further, it appears that the split will delete all snapshots, so doesn't like the snapmirror snap.
What is the best way to split these volumes? Ideally without having to re-baseline \ lose my snapmirror destination volume \ snaps.
ONTAP v9.1P2
Error below;
Time Node Severity Event
------------------- ---------------- ------------- ---------------------------
8/30/2017 09:02:17 filer1 INFORMATIONAL mgmtgwd.jobmgr.jobcomplete.failure: Job "Clone Split" [id 6716] (Split vol1) completed unsuccessfully: Volume has locked snapshots (1).
8/30/2017 09:02:17 filer1 DEBUG wafl.config.req.error: Config request 'VV_CONFIG_REQ_CLONE_SPLIT_START' by WAFL for volume vol1 is not being processed because of the error: '387 - CR_VV_VOLUME_SNAPSHOTS'.
8/30/2017 09:02:17 filer1 NOTICE wafl.vv.clone.splitBusySnap: Volume 'vol1 has locked snapshots, not splitting.
KR,
Chris.
Hi All,
We have been using Foreign LUN Import to migrate 3rd party storage systems into CDOT.
So far, we have been shutting down servers to perform the cutover.
However we are now due to migrate some multiple node SQL clusters and looking at the possibility of using windows failover cluster manager to make these migrations non-disruptive.
i.e.
Failover node 1 resources to node 2
FLI node 1 LUN's & re-zone
Failover node 2 resources to node 1
FLI node 2 LUN's & re-zone
We are worried that if we fail over each windows node, migrate it's disks using FLI and change the zoning. When we failover the next node which still has direct access to the 3rd party storage, any writes made will not go through the LUN import relationship on CDOT and potentially cause corruption.
Can anyone offer any advice on this?
Many Thanks,
Chris.
This email is being sent by a subsidiary of Arthur J. Gallagher Holdings (UK) Limited, part of the Arthur J. Gallagher & Co. global group of companies. For details of the registered office, company number and, where applicable, regulated status of our subsidiaries, please visit https://www.ajginternational.com/legal-regulatory-information/.
We are the data controller of any personal information you provide to us or personal information that has been provided to us by a third party. We collect and process information about you in order to arrange insurance policies and to process claims. Your information is also used for business purposes such as fraud prevention and detection and financial management. This may involve sharing your information with third parties such as insurers, reinsurers, other brokers, claims handlers, loss adjusters, credit reference agencies, service providers, professional advisors, our regulators, police and government agencies or fraud prevention agencies.
We may record telephone calls to help us monitor and improve the service we provide. For further information on how your information is used and your rights in relation to your information please see our privacy notice at https://www.ajginternational.com/Privacy-Policy/. If you are providing personal data of another individual to us, you must tell them you are providing their information to us and show them a copy of this notice.
Where you are obtaining a non-consumer policy of (re)insurance, or cover for additional risks or renewal under an existing policy, you are required to make a fair presentation of the risk to a (re)insurer which discloses every material circumstance which you know or ought to know relating to the risk to be insured. A circumstance is material if it would influence the judgment of a prudent insurer in determining whether to provide insurance for the risk and, if so, on what terms. Disclosure must be reasonably clear and accessible to a prudent insurer and made in good faith. The aforementioned duty of disclosure is the applicable duty under the laws of England and Wales. If your policy is not subject to English law you are expected to disclose risk information in accordance with the requirements of the applicable law. In such circumstances we expect you will disclose risk information at least equal to the standard required under English law and where the applicable law requires you to disclose information over and above the level required under English law you will provide such information in accordance with that law.
Where you are obtaining a consumer policy of insurance, you must read each question and answer honestly and fully and must take reasonable care to not make a misrepresentation.
Failure to comply with the above disclosure requirements, as they apply to you, could mean that your policy of (re)insurance is void, its terms are materially altered or that (re)insurers are not liable to pay all or part of your claim(s). If you are in any doubt as to your obligations you should ask your usual contact.
This e-mail and any attachments are CONFIDENTIAL and may contain legally privileged information. If you are not the intended recipient of this e-mail message, please telephone or e-mail us immediately, delete this message from your system and do not read, copy, distribute, disclose or otherwise use this e-mail message and any attachments. Although the above company has taken reasonable precautions to ensure this e-mail and any attachments are free of any virus or other defect that may affect your computer, it is the responsibility of the recipient to ensure that it is virus free and the above company does not accept any responsibility for any loss or damage arising in any way from its use.
Hi All,
Do you have list of alerts which are eligible for P1, P2, P3, P4
If we talk in alerts - > Critical, Fatal, Error, Warning.types of alerts,
is any one has got any Excel sheet ?
please let me on the same..
Regards
Yuvaraja
Hi all,
Can we add new NTP servers to 7 mode and C-mode on Fly without disrupting
any protocols...
infact NTP servers are being decommissioned in future, so wanted to add the
new NTP servers before decommissioned...so what is the best practise to add
the same....
is there any disconnects happens to cifs protocols...?
Regards
Yuvaraja
Hi
We’re migrating some data from Windows file servers to CIFS shares on a 9.1p13 cluster (NTFS security style on the vols). We’re getting errors on some files and folders using Robocopy and the common thread seems to be objects with orphaned SIDs for the owner or DACL entries. We’ve tried other tools with the same results. Robocopy to another Windows file share works fine.
Has anyone else seen this behaviour? We’re assuming that the CIFS server is stopping the copy because it can’t resolve the SID. Is there any way to control that behaviour and just wrtie the DACL with the unresolved SID?
Thanks
Steve
Replying to an old post; I am just now hitting the same issue.
Steve - did you ever find a solution to this issue? (ABE not working on junction paths).
9.1P14 here.
-jeff
----------------------------------------------------------------------
Message: 1
Date: Thu, 7 Dec 2017 12:50:05 +0000
From: Stephen Stocke <scstocke(a)gmail.com>
To: "<Toasters(a)teaparty.net>" <toasters(a)teaparty.net>
Subject: CIFS Access Based Enumeration for Volume in Namespace
Message-ID:
<CAEGA2qbHgFzNEvKpLa688Syt-197quPEJNz941eYvar3PHKgZg(a)mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hello
I have a need to use access-based enumeration within a CIFS share that contains volumes mounted as junction paths within the share volume. ABE is working for normal files and folders but volumes mounted as junction paths are visible even if the user does not have permissions to see the folder representing the junction.
Has anyone done this? Or can anyone point to any documentation on whether this is possible?
ONTAP 9.1p5, ntfs security style on all volumes.
Many thanks
Steve
Hi toasters
We recently upgraded all our netapps to 9.4, from 9.3
Now we see something. The volumes we previously flagged as unprotected
under SVM-DR are now displaying as "protected". The only volumes
which show as "unprotected" are the root volumes.
In reality, the volumes we had previously flagged as "unprotected"
still seem to be unprotected, that is they are not being
snapmirrored to the destination SVM.
This is causing a few issues with our monitoring of our protection
status.
Has anybody seen this or know something about it?
Also, the "volume show" man page does not mention the protection
flag, but does display it when asked. I do not know if
the man page on 9.3 documented the flag or not. I assume it did
else I would not know about it.
Regards,
pdg
Peter Gray Ph (direct): +61 2 4221 3770
Information Management & Technology Services Ph (switch): +61 2 4221 3555
University of Wollongong Fax: +61 2 4229 1958
Wollongong NSW 2522 Email: pdg(a)uow.edu.au
Australia URL: http://pdg.uow.edu.au
Hi All,
i have configured new alert setup through OCUM 7.2p1, we are receiving
alerts but it is not showing OCUM host name , instead it shows as Local
host whenever we receive alerts to our email id's, is anyone aware how to
resolve this issue..
here in below statement itstead of localhost , it should reflect OCUM
name(oncommand unified manager)
"An incident was generated by localhost that requires your attention"
Regards
Yuvaraj
Hi Everyone,
Any one has got all the commands to setup new cluster in Dataontap C-mode
environment...9.xx version...
if it is in Best Standard would be fine....
Example steps:
Cluster mode setup
Joining cluster
Creating Vlan
Creating Interface Groups
Creating Lifs
Creating all the roles of cluster , data , node-mgmt ,intercluster
cluster-mgmt
Creating aggregates (both DP and Raidtec)
Creating Vservers (NFS, CIFS, ISCSI)
Creating failovergroups
Creating volumes
Creating Export-policy and rule set...
Regards
Yuvaraj
Just going through an experience I figured I would share with the list: we
ordered a small Snaplock cluster, sized so that all disks would be used for
the Snaplock aggregate. Well, as it turns out, you must always size enough
disk for one regular aggregate: SVM root volumes are not supported on root
aggregates nor on Snaplock aggregates.