2011-07-21
04:59 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Lsmaint indexing question
I have a client who purchased a secondary NAS. We are able to map to this NAS just like the Primary.
They would like to have any data older than X months on the Secondary, and not on the Primary.
I proposed doing this with a LSMaint -move command, and adding the secondary NAS directories as read-only, not writable using the GUI.
My question is this..... Once I move the data, will enVision know to access the information on the secondary NAS, and not the Primary? Will the location of the data be updated by the locator service?
How long does this usually take to update the pointers? Is there an extra step(s) I need to take in addition to the LSMaint -move command?
1 Reply
2011-08-02
09:44 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Once the data is moved and the NAS added as a secondary storage location, you should be able to run the locator service in discovery mode (pi_locator –t –v). This should discover the data that was moved and allow you to query. This may take some time depending on the amount of data. Hope this helps...
