STORAGE

QtreeCreation

This document contains proprietary information of Wipro Infotech MIT. No part of this publication may
be reproduced, stored in a retrieval system or transmitted in any form or by any means, whether
electronic, mechanical, photocopying, recording or otherwise, without the prior written permission of
Wipro Infotech MIT. The information contained herein is confidential to Wipro Infotech MIT and
<Customer Name> and shall not be distributed to any persons other than those involved in the
assessment and delivery of services. Wipro Infotech MIT reserves the right to revise and update this
document as and when required. Wipro Infotech MIT reserves the right to withdraw the document
excluding customer specific information at the time of termination of services.
All product names referenced herein are trademarks of their respective companies.

Document Management Information

Document Title

: QTreeCreation

Document Status

: Draft / Review / Approval / Final

Document Publication History

(All revisions made to this document must be listed in chronological order)
Version

Date

1.0

Author(s)

Remarks

Praveen Motupalle

Draft Document

Document Review and Approval History

(All revisions must be approved. Review and Approval can be done by an internal
source or by the customer)
Version

Date

Reviewer & Approver

Document Distribution List

S.No
1
2

Name and Company

Purpose

Remarks

TABLE OF CONTENT

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.

Purpose....................................................................................................1
Scope.......................................................................................................1
Definition..................................................................................................1
Procedure\ Process.....................................................................................1
Metric / Acceptable Limits...........................................................................8
Defect Definition........................................................................................8
Incident Handing Process............................................................................8
Escalation Matrix........................................................................................8
Exceptions.................................................................................................8
Ownership and Responsibilities....................................................................8
Compliance...............................................................................................8
Enforcement..............................................................................................8
Changes to Policy.......................................................................................9
Frequency of Review...................................................................................9
Reference..................................................................................................9

Qtree Creation
STORAGE

DOCUMENT ID

CN.STR_NETAPP.7.15

VERSION NO.

1.0

EFFECTIVE
DATE

1. Purpose
This SOP would give clear and complete steps required for Creation of Qtree on
gefilers on INDGE Domain

2. Scope
All filer of Genpact on INDGE Domain

3. Definition
None

4. Procedure\ Process

Approvals:

Activity
Share folder creation
Share folder creation more than 50GB

CN

First Level
Approval
IT CoE
Vivek Gupta

Confidential

Second
Level
Approval
FP&A
FP&A

Third Level
Approval
N/A
ITCOE

Page 1 of 9

Qtree Creation
STORAGE

DOCUMENT ID

CN.STR_NETAPP.7.15

VERSION NO.

1.0

EFFECTIVE
DATE

Step 1: Go to Filerview click on Volume Qtree Add

Step 2: Select the volume name form the drop down list on which you want to
create the qtree
Step 3: Give the qtree name (check for the naming convention)
Step 4: Security style should be NTFS as we only have CIFS (windows) shares in
Genpact
Step 5: Click Add button to finish creating the qtree

Note on Oplocks:
Oplocks (opportunistic locks) enable the redirector on a CIFS client in certain filesharing scenarios to perform client-side caching of read-ahead, write-behind, and

CN

Confidential

Page 2 of 9

Qtree Creation
STORAGE

DOCUMENT ID

CN.STR_NETAPP.7.15

VERSION NO.

1.0

EFFECTIVE
DATE

lock information. A client can then work with a file-read or write it) without regularly
reminding the server that it needs access to the file in question, which improves
performance by reducing network traffic.
By default, oplocks are enabled for each qtree. If you disable oplocks for the entire
filer, oplocks are not sent even if you enable oplocks on a per-qtree basis

After creating the qtree we need to assign the quota to that qtree to restrict the
space usage on the quota tree/volume.
Go to Quota Add and you see the following screen.
We are going to assign the quota to qtree. Select the quota type as tree. Select
quota volume and click next:

CN

Confidential

Page 3 of 9

Qtree Creation
STORAGE

DOCUMENT ID

CN.STR_NETAPP.7.15

VERSION NO.

1.0

EFFECTIVE
DATE

On the following screen provide the soft limit and the hard limit for the quota and
threshold as well.

Once done just click on the commit button and the quota is applied. We need to
restart the quota to enable the quota limit on the following screen. (Quota Manage)

CN

Confidential

Page 4 of 9

Qtree Creation
STORAGE

CN

DOCUMENT ID

CN.STR_NETAPP.7.15

VERSION NO.

1.0

EFFECTIVE
DATE

Confidential

Page 5 of 9

Qtree Creation
STORAGE

CN

DOCUMENT ID

CN.STR_NETAPP.7.15

VERSION NO.

1.0

EFFECTIVE
DATE

Confidential

Page 6 of 9

Qtree Creation
STORAGE

DOCUMENT ID

CN.STR_NETAPP.7.15

VERSION NO.

1.0

EFFECTIVE
DATE

It is mandatory to update the share Description here. Update the Description with
the SR Ticket Number.

CN

Confidential

Page 7 of 9

Qtree Creation
STORAGE

DOCUMENT ID

CN.STR_NETAPP.7.15

VERSION NO.

1.0

EFFECTIVE
DATE

5. Metric / Acceptable Limits

Adherence to the process will be considered as acceptable limits.

6. Defect Definition
Non adherence to the process will be considered as defect definition.

7. Incident Handing Process

For all incidents, team will follow the incident handling process (Clarify System)
(Wherever Applicable)

8. Escalation Matrix
All escalation will follow-up the laid down ITIL escalation matrix.

9. Exceptions
None.

10.

Ownership and Responsibilities

It is the responsibility of the CST SR team to keep the document updated at all
times.

11.

Compliance

It is the responsibility of the CST SR team to adhere to this policy and ensure
compliance with the standards setup in this policy.

12.

Enforcement

Any employee found to have violated this policy may be subject to disciplinary
action, up-to and including termination of employment

CN

Confidential

Page 8 of 9

Qtree Creation
STORAGE

13.

DOCUMENT ID

CN.STR_NETAPP.7.15

VERSION NO.

1.0

EFFECTIVE
DATE

Changes to Policy

Any change in the above policy should be approved by Change Control Board of
Genpact as they are the final authority for making changes in the policy document.

14.

Frequency of Review

The policy documents needs to be reviewed by the functional leader at least once in
a year.

15.

CN

Reference

Confidential

Page 9 of 9