Highlighted

Does Backup Exec have a way to do Hierarchical storage management or Tiered storage?

Does Backup Exec 2014 have a way to do Hierarchical storage management or Tiered storage? I have a Dicom server that needs to archive files to a single storage space, that then needs to have the older files migrated to tape, while maintaining a stub file in the original location for the Dicom server to see and retrieve if necessary.

Thank you,

scrow

1 Solution

Accepted Solutions
Accepted Solution!

BE does not have the facility

BE does not have the facility that you are looking for.  The closest would be the File Archive option, but that option is nearing its EOL.

View solution in original post

3 Replies

Hi Scrow, You can try

Hi Scrow,

You can try creating a new backup job for the required files/folders which will backup the data to the tape.

And you can configure that backup job with best suitable "include files" option mentioned below.

Files dated

Select this option to include the files that were created or modified during a specific time period. You must select the beginning and ending dates for the time period.

Files not accessed in X days

Select this option to include any files that have not been accessed in a specific number of days. You must enter the number of days.

* More options are mentioned in the article mentioned below.

Please refer: http://www.symantec.com/docs/HOWTO99702

You can also try it the other way around by using "exclude files" option to exclude the recently modified files from the backup and the job will only backup older files.

Please refer: http://www.symantec.com/docs/HOWTO99632

Hope it helps.

Thanks!!

Accepted Solution!

BE does not have the facility

BE does not have the facility that you are looking for.  The closest would be the File Archive option, but that option is nearing its EOL.

View solution in original post

The file archive option does

The file archive option does not provide an automated placeholder (retrieval stub file) for every file that is archived.  This is because it is the cut down version of Enterprise Vault where the end user will find a link in any folder that has archived files which takes them to a web based search tool (as a manual process) As such it would not be transparent to an application trying to open the archived files.

Of course the fact that it is end of life is also a good reason to not use it.

 

Enterprise Vault might do what the original customer wants as it as least does leave placeholders for every file, the only concern I have with this is whether or not what sounds like a database application that creates the files would cause problems against the design that might expect file change activity from individual user applications (and therefore credentials) and not a database using a servcie account.