Hello @Commvault Engineer
Commvault is agnostic to whether the MediaAgent is physical or virtual. It all depends on what the customer wants to implement.
If you are concerned about High Availability, if something happens to the MediaAgent, whether physical or virtual, it cannot be used until it is repaired. You can have multiple MediaAgents configured to use the tape library so in the event something happens with one MediaAgent, another can load balance the work.
Thank you,
Collin
Hello @Commvault Engineer
Commvault is agnostic to whether the MediaAgent is physical or virtual. It all depends on what the customer wants to implement.
If you are concerned about High Availability, if something happens to the MediaAgent, whether physical or virtual, it cannot be used until it is repaired. You can have multiple MediaAgents configured to use the tape library so in the event something happens with one MediaAgent, another can load balance the work.
Thank you,
Collin
Thanks, Collin, for your usual support.
I had one more question regarding Tape Library integration with Commvault. The main purpose of using the Tape Library is for Secondary Copies. Since primary copies data will be saved on their backup disk library and want to create a secondary copy on the tape library for longer retention.
Our concern is that the primary copy will be hosted on deduped storage pool, does deduplication cause any issue with secondary copies with Tapes ? We read somewhere that dedup is not supported for Tapes, maybe that's the case only for primary copies on Tapes.
Regards.
CommVault will read from the disk storage rehydrating the data to copy the backup jobs to the tape media.
You are right, you can no use deduplication if your backup target in the primary copy is tape media but here you have disk storage
in case you are wondering what is “ rehydrating “ , it it simply the conversation from dedup to non-dedup data.
You can have the secondary copy configured without deduplication irrespective of the storage (Disk, tape,cloud) , data will always gets rehydrated and stored in the secondary copy in form of non-dedup data
Thanks a lot @SMD and @Ledoesp.
If I’m understanding right, basically, we’re going to configure our primary copy to Disk with dedup and secondary copy to tape as source the primary copy and CommVault will automatically rebuild “rehydrating” the data from the source copy which is deduped as a non-deduped data to be stored on the tape library.
Kind regards.
