1. create new LUNs (RAW not VMDK) for DB, logs & SnapInfo
2. migrate all the DB & log to new LUNs (downtime require)
3. setup SnapInfo directory on new LUN
4. create new LUNs in the destination FAS
5. create SnapVault relieatonship between source & destination LUN
6. configure SMSQL for backup setting
7. Test and confirm the backup and SnapVault image in destination storage
As a simple way for snapvault we use only 2 Volumes for sql server
We have one volume for Datastore for SQL Server and Splitt System Windows, SQL Server Programm, SystemDB, TEMPDB, SnapInfo as seperate vmdk diks on this datastore.
User DBs an User Logs on extra Volume as RAW Lun.
Configure an SnapVault with the right policy and snapmirror labels for datastore volume and raw lun volume
Configure SnapManager
as result: UserDB ist snapvault as RAW LUN an can esay mount to any other server.
The snapinfo snapshot on volume level will automaticly transfer the rest of the sql server volume without use of VSC to secondary site and include all othe vmdks.
But your task list is right when you use 1 volume vmdk server 1 raw lun database and logs 1 raw lun for snapinfo as you has written.