# Common Storage
To handle high traffic volume, you might end up running multiple instances of yCrash servers. In such circumstances all the yCrash server instances should be using the common storage. You have following options to enable common storage:
# 1. Remote/Cloud Storage
You can configure yCrash server instances to use remote cloud storage type of solutions. If you are running on public cloud infrastructure, you can use AWS S3 or Google Cloud Storage.
If you are running on a private data center, you can use Pure Storage, Min.io type of storage solutions.
# 2. Distributed File System
You can also use distributed file system type of solutions like: NFS (Network File System) AFS (Andrew File System), DFS (Distributed File Sytem) and RFS (Remote File Sharing),...
yCrash server stores all the captured artifacts in the upload directory. This upload directory is specified in the '-DuploadDir' system property of launch-yc-server.sh (if you are running yCrash server in Linux) or 'launch-yc-server.bat' (if you are running yCrash server in Windows). Say suppose your NFS is mounted on '/opt/ycrash-uploads' directory, then you need to specify this value in all the yCrash server instances as shown below:
java ... -DuploadDir=/opt/ycrash-uploads ...
# 3. Local Disk
Suppose you are going to run multiple of instances of yCrash server on the same device, then you can use your local disk itself as your common storage solution.
yCrash server stores all the captured artifacts in the upload directory. This upload directory is specified in the '-DuploadDir' system property of launch-yc-server.sh (if you are running yCrash server in Linux) or 'launch-yc-server.bat' (if you are running yCrash server in Windows). Say suppose you want to store all the artifacts in '/opt/ycrash-uploads' directory, then you need to specify this value in all the yCrash server instances as shown below:
java ... -DuploadDir=/opt/ycrash-uploads ...
Note: This solution will not work, if in future you decide to run yCrash servers on different devices.