DPM 2010 questions

Soldato
Joined
5 Jul 2003
Posts
16,206
Location
Atlanta, USA
Hi,
We currently use DPM 2010 and have the backups set to whatever settings each protection group uses. Due to how we do off-sites, we can only go back upto 2 weeks.

We had an issue today where some data had corrupted before the 2 weeks of backups, so we couldn't recover it.

To alleviate this, i want to modify the backup routine.

Now, correct me if im wrong:
If i set the short term backups retention to 40 days, that means it wont delete any backups it makes for that protection group for at least 40 days. Correct?

Does anyone have any thoughts about automating a transfer to another site of some specific data? Over a 10Mbps connection (at their end).

Thanks.
 
- Correct
So if the retention is 40 days, and the backups occur every weekend, then it should keep 4 copies before deleting the oldest to make room for the latest, correct?

- Secondary DPM server (we have this setup)
What about using Filestreamer to put some virtual tapes on a share in a remote site...?
 
Yes, you are mainly limited by the numbe rof recovery points, and the amount of physical storage you have

Never used filestreamer i'm afraid. We have servers in our secondary location, so a full DPM server is ideal for us.
 
Yes, you are mainly limited by the numbe rof recovery points, and the amount of physical storage you have

Never used filestreamer i'm afraid. We have servers in our secondary location, so a full DPM server is ideal for us.

Filestreamer is basically a virtual tape software.
We tell it where to put the 'tapes' (Share, USB, Firewire, local disk, esata, ect; ) and it makes the 'tapes' appear in DPM.

Well its 50Mb upload here and 50Mb download at the destination, latency aside, that should be fine i would have thought....
 
Filestreamer is basically a virtual tape software.
We tell it where to put the 'tapes' (Share, USB, Firewire, local disk, esata, ect; ) and it makes the 'tapes' appear in DPM.

Well its 50Mb upload here and 50Mb download at the destination, latency aside, that should be fine i would have thought....

I know OF filestreamer, in fact i have mentioned it on the technet forums when people have requested solutions, however i have never used it so can't say for sure if there are any "gotchas".

I do know the the MS guys seem to have no issue with mentioning it themselves, so it must be pretty reliable. Oniy problem i would find, is that doing a server to server uses shadow copy so will not be sending ALL the data each time. We update our remote replicas every 12 hours. I guess it depends how much data you want to backup to remote.

Our weekly backup to tape takes 48h to a LOCAL tape drive.
 
Back
Top Bottom