toasters

toasters@lists.teaparty.net

1 participants
13528 discussions

Unable to terminate re-startable dumps
by John Adams 22 Jun '16

22 Jun '16

Hi All, We backup from a 3rd party product via NDMP. The past couple of days, SOME the backups have been failing on this filer with: There are no backup contexts available in the system. Delete some of the unwanted restartable backup contexts and retry the operation. DUMP: Maximum number of allowed dumps/restores (16) in progress. NDMP_OP_ERRORCODE is 'EMAXBACKUPS' DUMP: Dump failed to initialize. And looking at the filer: hostname*> backup status ID State Type Device Start Date Level Path -- ----------- ---- ------ ------------ ----- --------------- 2 RESTARTABLE dump 0 3 RESTARTABLE dump 0 4 RESTARTABLE dump 0 5 RESTARTABLE dump 0 6 RESTARTABLE dump 0 7 RESTARTABLE dump 0 8 RESTARTABLE dump 0 9 RESTARTABLE dump 0 10 RESTARTABLE dump 0 11 RESTARTABLE dump 0 12 RESTARTABLE dump 0 13 RESTARTABLE dump 0 14 RESTARTABLE dump 0 15 RESTARTABLE dump 0 16 RESTARTABLE dump 0 So I thought I had an accumulation of old backup sessions over time. hostname*> backup terminate 2 Unable to read from registry. There are no snapshots on the system that were created by backups right now. hostname*> version NetApp Release 8.2.3P3 7-Mode: Tue Apr 28 14:48:22 PDT 2015 Any ideas of what I could try here? Its strange that it shows dump as the device instead of NDMP. And its strange that the Start Date and Path's are blank. Thanks.

1 0

Raid disk layout - the ability to lose a shelf.
by jordan slingerland 22 Jun '16

22 Jun '16

Hello, I am deploying a new 8040 and it was requested that the aggregates / raid groups are laid out in such a way that no more than 2 disks in any raid group are within the same shelf. At first this sounds like it reduces single points of failure and could protect availability from the failure of a full disk shelf. I argue against this strategy and was wondering if anyone in this list had any feedback. My thought is that this configuration is marginally increasing availability at the sacrifice of additional risk to data integrity. With this strategy, each time a disk failed we would endure not only the initial rebuilt to spare, but a second rebuild when a disk replace is executed to put the original shelf/slot/disk back into the the active raid group. Additional, if a shelf failure were encountered, I question whether it would even be possible to limp along. In an example configuration, we would be down 24 disks, 4 or 5 would rebuild to the remaining spares available. Those rebuilds along should require significant cpu to occur concurrently and I expect would impact data services significantly. Additionally, at least 10 other raid groups would be either single or double degraded. I expect the performance degradation at this point would be so great that the most practical course of action would be to shutdown the system until the failed shelf could be replaced. Thanks for any input. I would like to know if anyone has any experience thinking through this type of scenario. Is considering this configuration interesting or perhaps silly? Are any best practice recommendations being violated? Thanks in advance. --Jordan

13 14

Netappdjenga
by Bert Kiers 21 Jun '16

21 Jun '16

Hi, A collegue fell off his chair when I proposed this game so I share the idea. Take a working Netapp metro cluster (preferably non-production). Players take turns to disconnect one connector until the cluster stops functioning. The player that disconnected the last one, loses. Grtnx, -- Bert

2 1

adding new SAS loop
by Peter D. Gray 17 Jun '16

17 Jun '16

Hi people, anybody know if adding hot adding new SAS loop onto an 8000 series with ontap 8.3 cluster mode is supported? If yes, where is this fact documented? (as opposed to added a new shelf into an existing loop which I know is supported) Regards, pdg

3 2

7-mode snap list with year
by Basil 16 Jun '16

16 Jun '16

Hi, I'm trying to write a module into a home-grown management tool that will alert us when snapshots are kept longer than their retention target. It works fine for CDOT, but I'm having trouble with the time stamps in 7-mode. They omit the year. I need to use cli to get this, I can't use powershell or the api. Does anyone have an idea?

2 2

High CPU
by Sayla, Mustafa 10 Jun '16

10 Jun '16

Is there a way to find out why in a CDOT cluster controller A is always between 50 and 55% CPU usage and controller B is less than 25%. Storage wise data is evenly balance but seem like some volumes are used more heavily than others and if I can identify them I would balance them to that CPU usage is even between the controllers. Thank you Mustafa Sayla Visit us on the Web at mesirowfinancial.com This communication may contain privileged and/or confidential information. It is intended solely for the use of the addressee. If you are not the intended recipient, you are strictly prohibited from disclosing, copying, distributing or using any of this information. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Confidential, proprietary or time-sensitive communications should not be transmitted via the Internet, as there can be no assurance of actual or timely delivery, receipt and/or confidentiality. This is not an offer, or solicitation of any offer to buy or sell any security, investment or other product.

4 3

Risk of assigning disks in a loop to two controllers
by BERNTSEN Basil 10 Jun '16

10 Jun '16

Hi folks, I have a CDOT 8.2 system (in prod) where new shelves were installed on a SAS stack on the wrong node. I want to create an aggregate on node1, but the disks are on node2. Based on the guidelines<https://library.netapp.com/ecmdocs/ECMP1196912/html/GUID-99C1AA7C-79D9-4E4F…>, I'm thinking of delaying the aggregate creation and changing the shelves. My question is whether it's worth the delay. What are the risks of just assigning the disks to the partner of the node they're currently assigned to? The documentation says to "Always assign all disks on the same loop or stack to the same system." Why? Thanks! Basil ************************************************************************* This message and any attachments (the "message") are confidential, intended solely for the addressee(s), and may contain legally privileged information. Any unauthorized use or dissemination is prohibited. E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. Please visit http://sgasdisclosure.com for important information regarding SG Americas Securities, LLC (“SGAS”). Please visit http://swapdisclosure.sgcib.com for important information regarding swap transactions with SOCIETE GENERALE. *************************************************************************

6 5

Closing cifs sessions by id in 8.2
by Basil 31 May '16

31 May '16

Hi, I'm running 8.2.3 and need to close a specific cifs session by ID for troubleshooting and taking a trace. The command cifs session close appears to have been introduced in 8.3... Is there another way, maybe from node or system shell, to kill a specific session?

1 1

Support Bulletin 7010246
by Philbert Rupkins 27 May '16

27 May '16

Toasters, Does anybody have more information on support bulletin 7010246? I just received an email urging us to upgrade to ONTAP 8.1.4 P9 as earlier versions of 8.1.4 are "more susceptible to potential system disruptions and/or data loss due to drive failures exceeding the two drive failure protection offered by RAID-DP." We've been planning to upgrade to P9 so this isn't that big of a deal. However, I'm just curious if this is a new development or has this always been a problem with pre-P9 releases of 8.1.4? The support bulletin is light on background information. If this hasn't always been an issue, the only logical conclusion I can come to is NetApp is shipping new replacement drives that don't play well with pre-P9 releases of 8.1.4. Thank you all very much. Phil

1 0

(no subject)
by Yuvaraja Shivaram 20 May '16

20 May '16

hi, Anyone has any idea of resolving the below things for snapvault issue.. would like to fix this issue, stopping and restarting might work, but is that going start once again from beginning, is there any way to start with update command rather than starting from beginning.. Transfer aborted: destination qtree is not coalesced regards raj

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters