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.
LVL 1
ohmErnieAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.