I've worked with Netbackup 6.5 through 7.5, and integrated Celerra and VNX with NDMP backups. In each case, I've always the native Celerra/VNX snapshots with the backup process. If you look at the EMC document, Configuring NDMP Backups on VNX, it provides good instructions on not only on setup, but also on the use of several flags you can add to your policy.
On VNX and Celerra, you can add SNAPSURE=y to the NBU policy. This tells the Celerra to create a temporary snapshot to be used for backup purposes, providing a consistent image of data on disk. At the end of the backup, the snapshot is deleted. This is described in the guide.
Q: My understanding from docs is that after NDMP is already setup I do not need to do any more Celerra configuration or do I need to create a storage pool specifically for snapshots ? And if so how large does it need to be ?
If you are already using snapshots with your VNX and Celerra, you do not need to configure anything special or unique for snapshots called by NDMP backups. You can, however, create snapshot pools, if you so choose, then use those pools to hold the SavVol for those filesystems. You can find a few good posts on the forums regarding this, or look at the guide, Using VNX Snapsure.
Q: In this setup does the snapshot make a 1:1 copy or is it a COW snapshot that would just contain changes since the snaptime?
This is covered really nicely in Using VNX Snapsure, but snapshots are COW and would only contain changes since the creation of the snap.
I've taken NDMP backup of filesystems near the 16TB limit and never found a need to separate my SavVols from the source filesystem.
I had been looking at those docs and do still see some gaps. There is no tape unit in this setup. I think it's called a three way backup configuration. Celerra/IP NDMP -> Media Server -> DataDomain
The biggest unknown is around the storage unit. I can create one fine using the nasadmin and control station hostname but what does that do? What should I expect to see thin the status window ?
umichklewis
3 Apprentice
•
1.2K Posts
0
September 24th, 2015 15:00
I've worked with Netbackup 6.5 through 7.5, and integrated Celerra and VNX with NDMP backups. In each case, I've always the native Celerra/VNX snapshots with the backup process. If you look at the EMC document, Configuring NDMP Backups on VNX, it provides good instructions on not only on setup, but also on the use of several flags you can add to your policy.
On VNX and Celerra, you can add SNAPSURE=y to the NBU policy. This tells the Celerra to create a temporary snapshot to be used for backup purposes, providing a consistent image of data on disk. At the end of the backup, the snapshot is deleted. This is described in the guide.
Q: My understanding from docs is that after NDMP is already setup I do not need to do any more Celerra configuration or do I need to create a storage pool specifically for snapshots ? And if so how large does it need to be ?
If you are already using snapshots with your VNX and Celerra, you do not need to configure anything special or unique for snapshots called by NDMP backups. You can, however, create snapshot pools, if you so choose, then use those pools to hold the SavVol for those filesystems. You can find a few good posts on the forums regarding this, or look at the guide, Using VNX Snapsure.
Q: In this setup does the snapshot make a 1:1 copy or is it a COW snapshot that would just contain changes since the snaptime?
This is covered really nicely in Using VNX Snapsure, but snapshots are COW and would only contain changes since the creation of the snap.
I've taken NDMP backup of filesystems near the 16TB limit and never found a need to separate my SavVols from the source filesystem.
Let us know if that helps!
Karl
ScotN
76 Posts
0
September 25th, 2015 12:00
Thanks for the response Karl !
I had been looking at those docs and do still see some gaps. There is no tape unit in this setup. I think it's called a three way backup configuration. Celerra/IP NDMP -> Media Server -> DataDomain
The biggest unknown is around the storage unit. I can create one fine using the nasadmin and control station hostname but what does that do? What should I expect to see thin the status window ?