2011-08-29 02:22 AM
Yes you are correct, one could easily turn SMHV into a Snap Creator plugin however nobody is working on this just yet. Why is SMHV not a decent solution or proving a solution, or is it more about just getting support for HV into Snap Creator?
2012-07-03 06:32 AM
I'm searching this Snap creator plugins in my context because SMHV can't be linked to Protection manager to execute Snapvault Relationship and store "application consistent" backup on secondary (backup) Filer.
Please let me know If you are aware of a solution to adress my problem.
I will share any information I can get too!
Many thanks in advance.
2012-07-03 07:17 AM
Snap Creator 3.6 can help. Although SC does not (yet) have Hyper-V plugin, starting with 3.6 release (available on NOW July 19th) you can have SC manage external snapshots, menaing those created from SM products. This means you could have SC run SMHV and then register SMHV snapshot in protection manager through SC. You would be able to fully automate the backup however restore from secondary would be a manual effort since it isnt integrated in SMHV and SC is not shipping plugin for Hyper-V.
The options you would look at setting in SC are:
# NTAP_USE_EXTERNAL_SNAPSHOT - (Y|N) Setting which allows for import of non Snap Creator snapshot, most recent #
# snapshot is matched #
# NTAP_EXTERNAL_SNAPSHOT_REGEX - A regular expression for matching imported snapshots, requires the #
# NTAP_USE_EXTERNAL_SNAPSHOT option #
Hope this helps
2012-07-03 09:04 AM
thanks for your answer,
to be sure that i've weel understand what i can do with Snapcreator :
1) command SMHV Snapshot (app consistent),
2) command Snapvault to update relationship using the snapshot (app consistent) created in step 1,
3) command Snapvault to create snapshot on the secondary Filer if step 2 well performed,
4) command Protection Manager to register snapshot on secondary Filer into PM database if step 3 well performed,
Am I correct?
Thanks in advance,
2012-07-03 11:40 AM
No you simply run SMHV, point SC at volume where SMHV snapshots are and then SC will register snapshot with PM. Then PM will do snapvault update. Steps should be:
1. SMHV backup
2. SC register SMHV snapshot with PM
3. PM do snapvault transfer
4. PM create secondary snapshot on snapvault destination
2012-07-04 01:15 AM
finaly for being totaly sure your solution fits my needs :
in step 3 : PM will do snapvault tranfert using the "application consistent" snapshot => is it correct?
Thanks in advance,
2012-07-04 06:43 AM
Thanks for your help Keith,
This solution give me a way to my goal, while waiting the behavior of SnapCreator be included in SMHV options (or maybe in OnCommand Host Package for Hyper-V).
to conclude :
this will work event if i use the command line : "dfpm backup start -n <secondary_filer> <dataset_name> <backup_retention> " to start the PM backup to secondary?
Many Thanks for your time.