Moving FSA place holders and files not yet archived
Hi all, I need to move files and placeholders to a new volume on same server. (13TB) My understanding is that if I use the fsautility -pm -s "\\fileserver\fileshare" -d "\\fileserver\newfileshare" the placeholders will be moved, however what will happen to the files that are yet to be archived? are they also moved or do I need to run another process to do this? Cheers Changes made: "Disk" to "server"
Delete archived file when placeholder is delete with Pass-Throught enable
Hi ! I need enable Pass-Throught option, but the setting "Delete archived file when placeholder is delete" is ignored on NTFS volumes if pass-through recall is enabled on the volume. How can I delete archived file when placeholder is deleted ? Is there a command line to automate the deletion of archive file with placeholder deleted? Thanks !
Can you set size on Vault store partition?
Hi, I have large volumes 8TB+ and was looking at setting Vault store partion to Tape size of 2.35TB, however there appers to be no option to set the rollover for Vault partion size just the Disk volume size. I would prefer this to be auto rather then me doing it manualy since we have over 80TB to archive So the idea is that for each Disk Volume I have 3 Partions (Ptn1,Ptn2 and Ptn3) of 2.35TB each leaving 16% for operations disk volume, and get them to roll over to the next automaticaly once prtitions are filled up. cheers
Enterprise Vault as standalone archive (removing connections with Exchange mailbox)
My organization currently uses the Enterprise Vault 11.0.1 The business requirements are 1. Users are required to manage their archiving (3 month Exchange mailbox policy, multi-year Archive policy), this is achieved by having the user manually move items to the archive 2. Users typically use a drag and drop method to place items into the vault (for which we use vault cache) There are a few situations where this becomes problematic. There are several users who have multiple folders in their archive that do not exist in their mailbox or vice versa. When users attempt to move items between folders or delete folders, they may get error messages stating that they are unable to do so because the folder exists in exchange. I have also observed in a few cases a user will move an item in the vault cache and Enterprise vault will move it back to its original location. Under the Exchange mailbox policy, under the Moved Items tab, Update archive location for items moved in the mailbox is checked, however since we are not using shortcuts and delete the item after archiving, I don't think this is having any affect. The simplist solution for me would be to sever the tie between Enterprise Vault and Exchange and have the vault exist independently of Exchange. I have been reading up on zapping mailboxes, (and if anyone has a good write up on it, it would be appreciated) as a possible solution, but from what I understand, this will reset the permissions on the archive, not sure if it will clear info on what folder an email item came from. Has anyone had similar business requirements and does anyone know of a way to allow users to edit their vault independantly of their Exchange mailbox?
