• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2381
  • Last Modified:

Is it normal for the DfsrPrivate/Staging folder to still contain data after replication is completed?

Yesterday I created a replication group between the branch and hub office for backup.  After looking at the event viewer today, I see the event stating that initial replication has completed.  By checking the folder sizes on each server they are approximately the same 2gb (only diff would be excluded files bak, tmp, etc).  However, the DfsrPrivate/Staging folder is not empty on either server.

Is it normal for the DfsrPrivate/Staging folder to still contain data after replication is completed? They are about 1.5gb in size.

Also, when I run a full backup at the hub, the archive bit will be reset.  Will this change also be reflect on the branch server?  We run differentials and fulls backups.
0
ohmErnie
Asked:
ohmErnie
  • 2
  • 2
1 Solution
 
NJComputerNetworksCommented:
Is it normal for the DfsrPrivate/Staging folder to still contain data after replication is completed? They are about 1.5gb in size.

If data existed in the destination shares when the servers where first configured for replication, then YES, there will be data in the staging folder.  This will go away in a period of time...  


Also, when I run a full backup at the hub, the archive bit will be reset.  Will this change also be reflect on the branch server?  We run differentials and fulls backups.  

No, archive bit changes do not trigger replication.  
0
 
ohmErnieAuthor Commented:
So what is the recommend backup method for remote office data?  Running fulls everynight would be costly on tapes and disc space.
0
 
NJComputerNetworksCommented:
if the data your are referring to is the DFS replicated data, then you can just backup the data in one location (and not in all the replica's).

Or you may choose to backup the data in each location.  Either method is good.

You can still use differential backups.... these will work exactly the way they work today.  

The archive bit will not trigger replication...so you don't have to worry about accidently replicating data where only the archive bit changes...and not the actual data.

Sounds like differential backups in each remote site Monday through thursday and a full on friday will work for you.
0
 
ohmErnieAuthor Commented:
I would like to backup the data in the main site, not the remote site.  This was the purpose for setting up the replication to begin with.  The issue I am going to have is my backups, diff and full run based on the archive bit changes.  Is there any documentation on how one would run backups using the DFS replication?  It seems suprising that the archive bit will not be replicated seeing that the second type of replication group is for backup purposes.
0
 
Computer101Commented:
Forced accept.

Computer101
EE Admin
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now