This post is more than 5 years old

2 Intern

 • 

498 Posts

462

February 7th, 2018 14:00

First backup going FASTER then expected.

I know strange thing to worry about...

I have an old grid and a new grid.

clientA has been on the old grid for years backing up just fine.

     last backup on old grid was 1 tb with 2.6% on New Bytes

clientA was retired from old grid

software upgraded on client to match new grid and registered to new grid.

     first backup on new grid was 1 tb with 20% New Bytes

That New Bytes is "new to Avamar"?  and not the client?

Just wanting to make sure that the Client is getting all the data to the new grid, and not skipping anything because it sees it in its f_cache.dat file and thinking it has already sent it.

wondering if I should be removing the f_cache files on the clients when I register them to the new grid.

(Just me being paranoid)

2 Intern

 • 

2K Posts

February 8th, 2018 06:00

New bytes is "new to Avamar", yes.

The client has a mechanism where it asks the server to look up the root hash for each backup that's in the cache (the root hash is basically a backup's unique identifier). If the root hash is present on the server, we'll use the associated cache information but if the root hash is not present on the server, we won't.

You don't need to delete the caches.

2 Intern

 • 

498 Posts

February 8th, 2018 07:00

Thanks,

I guess the new grid and NIC is faster then the old grid and newly added servers are backing up fast enough to finish in time.

I was just being paranoid.

No Events found!

Top