Here is an option to find out how much of a backup tape was used in DPM 2007.
- Select Recovery tab and select Browse button in the left pane
- Expand each protected server and select Protected data
- In the middle pane, right click on the protected and select Show all Recovery Points
- You will see the data size information there.
4 comments:
Hi,
i am getting error when performing inter forest migration between windows 2003 to windows 2008.
i am getting below error:
1.ERR2:7447 sid history can not updated. the credentials enter must have administrator privileges on the source domain.
2.wrn1: sidhistory could not be updated due to a configuration or permissions problem. the AD migration tools will not attempt to migrate the remaining objects.
i am getting below error in admt error log at the time of inter forest migration between win 2003 to win2008.
error:
wrn1:7392 sidhistory could not be updated due to a configuration or permissions problem. the AD migration tools will not attempt to migrate the remaining objects.
This is not related to DPM question. Try this solution - http://portal.sivarajan.com/2010/04/admt-service-account-permission-and.html
Otherwise post the question in my forum - http://www.sivarajan.com/forum/
In My windows 2003 AD environment event id 1862 got generated everyday in a specific time. Not sure why it is generated. Go through some blog they are saying please check Lost and Found folder in your environment. I check Lost and Found folder and found some DC's name there which are already decommissioned. Even i found some DC's name which are live in my environment. I am getting below error log in event viewer:
Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1864
Date: 2/16/2012
Time: 4:08:37 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: NLADV002
Description:
This is the replication status for the following directory partition on the local domain controller.
Directory partition:
DC=DomainDnsZones,DC=amer,DC=ad,DC=ici,DC=com
The local domain controller has not recently received replication information from a number of domain controllers. The count of domain controllers is shown, divided into the following intervals.
More than 24 hours:
1
More than a week:
1
More than one month:
1
More than two months:
1
More than a tombstone lifetime:
0
Tombstone lifetime (days):
60
Domain controllers that do not replicate in a timely manner may encounter errors. It may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled.
To identify the domain controllers by name, install the support tools included on the installation CD and run dcdiag.exe.
You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest. The command is "repadmin /showvector /latency ".
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Post a Comment