Best Practices: Exclusive access to Storage Location
Summary
This article describes the Best Practices regarding the DS-System storage location(s).
- The DS-System should have exclusive access to the storage locations(s) at all times when it is running.
Known issues regarding exclusive access
The following issues are known to occur if DS-System does not have exclusive access to the storage location(s):
Issue 1: Renaming a customer or DS-Client
1. When renaming a customer or DS-Client, if Windows Explorer (or any other application) opens that customer's (or DS-Client's) folder on the storage location(s):
- The customer / DS-Client folder cannot be renamed to the new customer / DS-Client folder number.
- However, the database is already modified to the renamed customer / DS-Client.
- In this situation, you cannot find the backup sets belonging to this customer /DS-Client.
2. The workaround is to close the Windows Explorer (or other application), and rename the customer/DS-Client folder manually from the storage location itself.
Issue 2: Retiring a storage location
1. When retiring a storage location, if Windows Explorer (or other application) opens any of the folders in that storage, those folders cannot be moved to the other storage locations and the retired storage will not be empty.
2. The workaround is to close the Windows Explorer (or other application), and re-run the retire storage process for that storage location.
There might be other issues related to exclusive storage access, however the best practice is to prevent any other application from accessing the DS-System online storage during normal operation of the DS-System (i.e. whenever the service/daemon is running).
See Also
- "Retire Storage Locations"
- "Storage Balancing (Extensible Storage)"
- "Storage Scalability (Extensible Storage)"
- "Retiring the DS-System Primary Storage Location (Backup Root)"
The information provided in this document is provided "AS IS", without warranty of any kind. ASIGRA Inc. (ASIGRA) disclaims all warranties, either express or implied. In no event shall ASIGRA or its business partners be liable for any damages whatsoever, including direct, indirect, incidental, consequential, loss of business profits or special damages, even if ASIGRA or its business partners have been advised of the possibility of such damages. © Asigra Inc. All Rights Reserved. Confidential.
![]() ![]() |