1. Loan tape drive. Really, I do not believe it is impossible ☺
2. If you have enough space on source filer (you will need to store all data that is going to be replicated) it is possible to do “snapmirror to file” (similar to “snapmirror to tape”). This option is available in diag mode only, so you are strongly advised to contact support before doing it.
If you have a shelf of empty/spare disks on the primary system, you could create a new aggregate and volumes and do a local SnapMirror to them. I would then create a manual snapshot on the source and destination volumes (an extra precaution to ensure you have a common snapshot that can't be deleted by the snapshot retention policy). Then you would need take downtime to remove the shelf from the production system. Ship the shelf to the DR site and attach it to the DR systems and resync the SnapMirror relationship.
An alternative would be to enable SnapMirror compression to reduce the amount of data transmitted and set the replication throttling options to prevent SnapMirror from consuming all of the WAN bandwidth. Of course, it could take weeks to transfer all of the data but it wouldn't involve purchasing additional hardware.
One more possibility is to use lrep if QSM is an option. This allows to transfer data directly to (removable drive on) PC and then play back on DR site.
LREP is a logical replication utility that is useful for performing initial baseline (full) data transfers from a supported Open Systems SnapVault client or a SnapVault primary system onto a SnapVault secondary destination.
It require open system snap vault software to be installed?
Note
If lrep_writer needs to be run on a machine on which the Open Systems SnapVault software is installed, stop the Open Systems SnapVault service before using this tool.
