Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So I was happy to finally see the SnapVault tab in On Command System Manager 3.0 when I installed it. This looks like a much easier way to manage my SnapVaults going forward. I do have some questions:
1. What is the difference between a "transfer" and a "backup". Documentation states:
Transfer = Transfer data from a source volume or qtree to a destination qtree
Backup = Create a backup schedule on a volume
This is no help, as symantically, a backup is a tranfer of data. All my current pre-system manager snapvault relationships appear as backups, but I went with Transfer on my new relationship. It seems to be updating SnapVault properly, and creating a nightly snapshot properly.
However, the baseline snapshot is showing as busy. Is this normal?
Can someone explain?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My understanding is that the transfer schedule is when data actually starts transmitting from the source to the destination. Backup is when the snapshot is actually taken. So for example, you can set the snapshot to be taken at 6 p.m., but not actually start transferring data to the destination until 8 p.m. Hope that helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks. This would imply you need both a data transfer (to transfer the data) and a backup schedule (to create the snapshots). However, this is not what I'm experiencing. Just having a Transfer schedule seems to do both, but the baseline snapshot remains busy.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well if you only have a transfer schedule then the snapshot is taken at that time.
And the baseline always remains "busy, snapvault". That's just normal.
