Move / split FSA archiving?

[VersEV1]

have 5 file servers targeted. one task archiving all, one vault store with 5 partitions. have a new ev server that is not doing anything. would like to have three of the file servers use a task on the new server.

what's the best way to split up?

could you update the taskentryid in dbo.fileservervolumeentry?

[VersEV1]

any thoughts on this?

would the folders and volumes need to be removed through the admin console and then added back selecting the new vault store and task? but the archive points would need to be deleted in order to use a new vault store and task, and there would be multiple archives with the same name. any other methods?

[plaudone1 · Accepted solution]

Hi VersEV1,

Since the vault store for the task has to be local to the task you will not be able to just move the targets. As you stated you would have to remove the current archive points and re-configure but this will leave archived data split between the two archives.  

The data would need to be moved from one vault store to another and this can be accomplished using fsautility -m. Since the file server path is not changing, as it would when moving to a new file server, this option will not work.  

The only other option is to recall all the data to the file server and remove the original archive point. Then re-target the path from the new EV server so that it can process the any new data.   You could do this in stages by enalbing the new archive and then scripting recalls of data in chunks to the file server so that it could be re-archived to new store.   Any files that are recalled and not in the new store would be archived in full.  Any items that have already been archived to the new store would be converted to shortcuts and not re-archived.  This would not account for items that have had the placeholder deleted, but still have a copy of the item in the archive.  These would only be in original archive.   

The FSAUtility -b command could be used to recall the items and threads for this can be increased by implenting a DWORD value of FSAUtilityFolderProcessThreads under Enterprise Vault\FSA in the registry with a value of 20...max of 40.  This could be done in stages to process the data from one archive to the other by recalling the data and then re-archiving to the new archive.  

It may be best to open a Support case to discuss the option further. 

Regards,

Patrick