Highlighted
3 Silver

What is the best way re-inflate VNX filesystem archived by CTA?

Jump to solution

Hi!

I have filesystem on VNX and would like to stop archiving it altogether. What is the best way to return all archived files back to file system? Is it still just reading all the files by likes of Windows Explorer with full recall configured or there is nicer way?

Thanks!

0 Kudos
Reply
1 Solution

Accepted Solutions
Highlighted
Not applicable

Re: What is the best way re-inflate VNX filesystem archived by CTA?

Jump to solution

Run the following command with the appropriate values (after checking this is what you want to do of course) against the DHSM enabled file system....

fs_dhsm - connection - delete -recall_policy

More info is provided in the "VNX Command Line Reference for File" docs.

View solution in original post

0 Kudos
Reply
3 Replies
Highlighted
Not applicable

Re: What is the best way re-inflate VNX filesystem archived by CTA?

Jump to solution

Run the following command with the appropriate values (after checking this is what you want to do of course) against the DHSM enabled file system....

fs_dhsm - connection - delete -recall_policy

More info is provided in the "VNX Command Line Reference for File" docs.

View solution in original post

0 Kudos
Reply
Highlighted

Re: What is the best way re-inflate VNX filesystem archived by CTA?

Jump to solution

small part is missing here...You want to add "yes" at the end of the command:

fs_dhsm -connection <fsname> -delete <CID> -recall_policy yes

You will get the fs listed with

fs_dhsm -l

And you will get the CID (Connection ID) with the following command:

fs_dhsm -connection <fsname> -info

0 Kudos
Reply
Highlighted
2 Bronze

Re: What is the best way re-inflate VNX filesystem archived by CTA?

Jump to solution

Hello Raimonds,

If the CTA is on 10.0 SP2 there is a recall task feature built into the CTA.  You can set a policy and define your source share you would like to have the files recalled from and run the task to perform the recall.  You will also get a task log and recalled files list.  You can also run a simulation using the task method to get an idea of how much data will be recalled.

You can use the method of deleting the DHSM connection, but that method may be slower and and some versions of Celerra or VNX, deleting the DHSM connection may cause a file system extension to occur even if there is enough space to perform the recall without the extension.

Deleting the DHSM connection is a single threaded process, while the task is multi-threaded.

Whenever you perform a full file system recall you should always delete the DHSM connection with the recall_policy yes option to ensure all files have been recalled before removing the secondary storage.

Regards,

JP

0 Kudos
Reply