Forum Discussion

philt's avatar
philt
Level 5
15 years ago

Share permissions on Partitions question - moving Vault store partitions.

Hi All,

I'd like to know what the share permissions on Vault partitions are used for. The reason I need to know is I'm looking to move (via copy) all Vault stores to a different physical drive, with more storage, on same server. I'm following http://seer.entsupport.symantec.com/docs/273271.htm but it doesn't mention anything about the share permissions.

Cheers,
Phil
Enterprise Vault
Information Governance
  • Wayne_Humphrey's avatar
    Wayne_Humphrey
    15 years ago
    Hi Phil,

    You spot on.  I would Even consider opening  a new partition to your new storage. Then copy both  closed partition to the new storage, then simply update the PartitionEntry and restart storage ;)

    So to recap:
    Today, you have:
    1 Closed partition (OLD Storage)
    Open Partition (OLD Storage)

    Then you could do the following:
    • Open a new Partition (New Storage)
    • Copy both Closed Partitions to (New Storage)
    • Update PartitionEntry Table
    • Restart Storage

    Therefor minimal amount of downtime, no need for Read Only mode....
  • Wayne_Humphrey's avatar
    Wayne_Humphrey
    Level 6
    15 years ago
    Phil,

    The VSA (Vault Service Account) will need full permissions on a UNC , that's all :)

  • philt's avatar
    philt
    Level 5
    15 years ago
    Thanks Wayne,

    Should I be removing the shares before I delete the old vault stores after we've succesfully moved the vault stores.

    Cheers,
    Phil
  • Wayne_Humphrey's avatar
    Wayne_Humphrey
    Level 6
    15 years ago
    Phill,

    I am an idiot, did not read "different physical drive" so there fore you will not need share permissions, just the VSA needs full access to that folder.
  • philt's avatar
    philt
    Level 5
    15 years ago

    Hi Wayne,

    I wouldn't go that far and understood what you meant so no worries from here.

    I do have one last question on the subject. As you can imagine the moving (via copy) of the partitions will take some time so I'm thinking about copying the CLOSED Journal Vault partitions over the course of a couple of days before updating the PartitionEntry table with the new locations. Then on a weekend put EV into read-only and copy the open partitions and make the updates to the PartitionEntry table. Just wondering what your advice might be on this approach.

    Thanks in advanced.
    Cheers,
    Phil

  • Wayne_Humphrey's avatar
    Wayne_Humphrey
    Level 6
    15 years ago
    Hi Phil,

    You spot on.  I would Even consider opening  a new partition to your new storage. Then copy both  closed partition to the new storage, then simply update the PartitionEntry and restart storage ;)

    So to recap:
    Today, you have:
    1 Closed partition (OLD Storage)
    Open Partition (OLD Storage)

    Then you could do the following:
    • Open a new Partition (New Storage)
    • Copy both Closed Partitions to (New Storage)
    • Update PartitionEntry Table
    • Restart Storage

    Therefor minimal amount of downtime, no need for Read Only mode....
  • philt's avatar
    philt
    Level 5
    15 years ago
    Thanks Wayne,

    Now for the last questions :-)

    What are your thoughts on using the same approach for the CLOSED Mailbox partitions?

    Please be aware we do allow users to delete from their Vault.

    I'm thinking it wouldn't be a good idea because if I move a Mailbox partition to new storage, then user does a delete, then I update PartitionEntry table to point to new storage. I'm thinking the deleted item would still be physcially on the new storage but wouldn't have an entry in the Databases resulting in an inconsistent system.

    I guess I answered my own question but I do appreciate your advice again if you don't mind.

    Thanks again.
    Cheers,
    Phil
  • Wayne_Humphrey's avatar
    Wayne_Humphrey
    Level 6
    15 years ago
    Phil,

    Yes that would be correct... but hay we speaking about a hand-full of orphaned items apposed to downtime.  And once are on v8 you can use EVSVR to go and delete the orphaned items on disk :)

    Its your call, I personally would go with the new partition route, its quicker and has no end user impact.  You could just disable deletions for the time the data takes to copy....

    --wayne