{"_id":"5a7b5ce0c5400800129f895a","project":"55d535ca988e130d000b3f5c","version":{"_id":"55d535cb988e130d000b3f5f","__v":13,"project":"55d535ca988e130d000b3f5c","hasDoc":true,"hasReference":false,"createdAt":"2015-08-20T02:04:59.052Z","releaseDate":"2015-08-20T02:04:59.052Z","categories":["55d535cc988e130d000b3f60","55d6b238d2a8eb1900109eef","55d6b4f3250d7d0d004274cd","55d7967960fc730d00fc2852","55da9804e835f20d009fc5d0","55e75b1de06f4b190080dbfd","55e75b39e06f4b190080dbfe","55e75b7ae06f4b190080dbff","564f5a4e33082f0d001bb709","570fb64aa38d470e0060cbff","586d0dd89a854123001acd65","586d0e3b9a854123001acd66","5a613b28da07540012e8ca4a"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"category":{"_id":"55e75b7ae06f4b190080dbff","__v":10,"project":"55d535ca988e130d000b3f5c","version":"55d535cb988e130d000b3f5f","pages":["5637e17197666c0d008656a5","569591a4fcb1032d0089e037","569622eafe18811700c9c19b","5696c9588560a60d00e2c1e0","569709ca0b09a41900b2442b","5697129ac8ded91700307b77","5697190a59a6692d003fad6a","5697192969393517000c8280","569f11908f6d4b0d00f13bb2","56a0030b5b981c2b00383df0"],"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-02T20:26:34.258Z","from_sync":false,"order":4,"slug":"frame-platform","title":"Frame Platform"},"user":"5910f1a2657bf91b00bf9d41","githubsync":"","__v":0,"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2018-02-07T20:09:04.078Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":26,"body":"Frame has built and integrated a variety of storage options into our platform to fit a multitude of unique use-cases. This article covers the Frame Personal Drive feature which provides persistent storage on a per-user basis. This storage space can be used as a cache to store frequently used files that will persist between a user’s sessions. Note that this Personal Drive, is not intended as a long-term or primary storage location for these files, users should use cloud storage options for this purpose.\n\nThe specific implementation of the Frame Personal Drive depends on which cloud infrastructure provider you've chosen (Azure or AWS); however, the end-user experience is the same regardless. For more information about all our available storage options, you can reference our Storage Solution Guide [here](https://fra.me/solutionguides/storage-solution-guide.pdf). \n\n###Overview\nFrame's Personal Drive (P: Drive) is a storage solution that provides each authenticated user with 10 GB of individually allocated storage space. The drive is accessible from \"My Computer\" within the session and appears as the \"P\" drive letter.  Drives are automatically provisioned as new users are added to the account. When users return to their accounts and launch sessions, their stateless instances mount their unique P: drives. When the user's session ends, the P: drive is disconnected from the stateless instance.\n\nNote that the Personal Drive is only available to the authenticated user and is not shared with any other user.  See the article on shared drives for teams or the Solution Guide referenced above if you are looking for a collaboration solution. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/fee8298-explorerPdrive.png\",\n        \"explorerPdrive.png\",\n        266,\n        203,\n        \"#cfe1e7\"\n      ]\n    }\n  ]\n}\n[/block]\n###Personal Drive on Azure\nWhen using Azure as your IaaS choice, we leverage Azure Files for the Frame Personal Drive feature. Azure Files is a native Azure service that enables a high-performance connection between the session and the data being accessed. Azure Files data is encrypted at rest in most Azure regions today with encryption planned for all regions in the near future. See [this article](https://azure.microsoft.com/en-us/blog/announcing-default-encryption-for-azure-blobs-files-table-and-queue-storage/) for more details. Azure Files uses [Locally Redundant Storage](https://docs.microsoft.com/en-us/azure/storage/common/storage-introduction) (LRS) to backup your data with 11 9's (99.999999999%) durability of objects over a given year.\n\n###Personal Drive on AWS\nWhen using AWS as your IaaS choice, Frame sets up the Personal Drive feature by provisioning a managed Linux server contained within the VPC of your Frame account. This \"managed\" server runs 24x7 and is not visible within your Frame dashboard because Frame takes care of all of the management (unlike a Utility Server which you have access to and manage on your own). This managed server dynamically allocates more space on its network drive for each new user that connects to a session. Data is encrypted at rest using industry-standard AES-256 encryption for maximum security. The Personal Drives are also automatically backed up daily and retained for a rolling seven day window.\n\nThe amount of storage will scale automatically based on a predefined free space threshold and a predefined system storage size.  The default threshold is 90% utilization and the default system storage size is 100 GB. When the storage threshold (e.g. 90%) is reached additional storage will be provisioned at that time.  The storage can be automatically expanded this way a maximum of 15 times. \n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/305d33b-Pdrive2.jpg\",\n        \"Pdrive2.jpg\",\n        1200,\n        910,\n        \"#0b0b0c\"\n      ],\n      \"caption\": \"The Personal Drive feature gives each user their own storage space\"\n    }\n  ]\n}\n[/block]\n###Summary of key features\n\n* Automatic drive creation for new users\n* Drive automatically mounted as P:\\ (“Personal Drive”) on session start\n* Fixed drive size (quota) per user\n* Per user quota defined per account (all users on the account have the same size) - default of 10 GB\n* User files are encrypted at rest (by default on AWS and in most Azure regions - see Azure documentation for encryption support in your region)\n* Data backup (rolling snapshots on AWS, LRS on Azure)\n* Storage auto-scales based on admin defined free space threshold and defined disk size\n* All communication between workload machines and file server is done through a private network\n\nTo enable the Personal Drive feature for your account, speak with your Frame Account manager first to get a price quote for your specific use case.  Then Frame Support will enable the feature for your account(s).","excerpt":"Persistent file storage for end users","slug":"personal-drive","type":"basic","title":"Personal Drives"}

Personal Drives

Persistent file storage for end users

Frame has built and integrated a variety of storage options into our platform to fit a multitude of unique use-cases. This article covers the Frame Personal Drive feature which provides persistent storage on a per-user basis. This storage space can be used as a cache to store frequently used files that will persist between a user’s sessions. Note that this Personal Drive, is not intended as a long-term or primary storage location for these files, users should use cloud storage options for this purpose. The specific implementation of the Frame Personal Drive depends on which cloud infrastructure provider you've chosen (Azure or AWS); however, the end-user experience is the same regardless. For more information about all our available storage options, you can reference our Storage Solution Guide [here](https://fra.me/solutionguides/storage-solution-guide.pdf). ###Overview Frame's Personal Drive (P: Drive) is a storage solution that provides each authenticated user with 10 GB of individually allocated storage space. The drive is accessible from "My Computer" within the session and appears as the "P" drive letter. Drives are automatically provisioned as new users are added to the account. When users return to their accounts and launch sessions, their stateless instances mount their unique P: drives. When the user's session ends, the P: drive is disconnected from the stateless instance. Note that the Personal Drive is only available to the authenticated user and is not shared with any other user. See the article on shared drives for teams or the Solution Guide referenced above if you are looking for a collaboration solution. [block:image] { "images": [ { "image": [ "https://files.readme.io/fee8298-explorerPdrive.png", "explorerPdrive.png", 266, 203, "#cfe1e7" ] } ] } [/block] ###Personal Drive on Azure When using Azure as your IaaS choice, we leverage Azure Files for the Frame Personal Drive feature. Azure Files is a native Azure service that enables a high-performance connection between the session and the data being accessed. Azure Files data is encrypted at rest in most Azure regions today with encryption planned for all regions in the near future. See [this article](https://azure.microsoft.com/en-us/blog/announcing-default-encryption-for-azure-blobs-files-table-and-queue-storage/) for more details. Azure Files uses [Locally Redundant Storage](https://docs.microsoft.com/en-us/azure/storage/common/storage-introduction) (LRS) to backup your data with 11 9's (99.999999999%) durability of objects over a given year. ###Personal Drive on AWS When using AWS as your IaaS choice, Frame sets up the Personal Drive feature by provisioning a managed Linux server contained within the VPC of your Frame account. This "managed" server runs 24x7 and is not visible within your Frame dashboard because Frame takes care of all of the management (unlike a Utility Server which you have access to and manage on your own). This managed server dynamically allocates more space on its network drive for each new user that connects to a session. Data is encrypted at rest using industry-standard AES-256 encryption for maximum security. The Personal Drives are also automatically backed up daily and retained for a rolling seven day window. The amount of storage will scale automatically based on a predefined free space threshold and a predefined system storage size. The default threshold is 90% utilization and the default system storage size is 100 GB. When the storage threshold (e.g. 90%) is reached additional storage will be provisioned at that time. The storage can be automatically expanded this way a maximum of 15 times. [block:image] { "images": [ { "image": [ "https://files.readme.io/305d33b-Pdrive2.jpg", "Pdrive2.jpg", 1200, 910, "#0b0b0c" ], "caption": "The Personal Drive feature gives each user their own storage space" } ] } [/block] ###Summary of key features * Automatic drive creation for new users * Drive automatically mounted as P:\ (“Personal Drive”) on session start * Fixed drive size (quota) per user * Per user quota defined per account (all users on the account have the same size) - default of 10 GB * User files are encrypted at rest (by default on AWS and in most Azure regions - see Azure documentation for encryption support in your region) * Data backup (rolling snapshots on AWS, LRS on Azure) * Storage auto-scales based on admin defined free space threshold and defined disk size * All communication between workload machines and file server is done through a private network To enable the Personal Drive feature for your account, speak with your Frame Account manager first to get a price quote for your specific use case. Then Frame Support will enable the feature for your account(s).