Across all of our sites, we are migrating to the Symantec System Recovery platform and so far, it seems to be a very powerful product.
One issue I am noticing, however, is that SSR tends to always stay connected to the backup location, at all times... We are sending our backups to a central backup server at each site, and simply specifying the UNC path to that folder in the backup job. From this, our backup servers seem to take a big hit -- I assume each connection requires some form of memory usage and the connection seems to stay open all of the time, in fact, I have 64 open connections from machines running SSR 2013, but no files being written or read... Just idle SMB connections.
Is this the intended behavior? Any way to turn it off?
I have considered running the backup to the local machine, then transferring over FTP to the backup server using the offsite copy methods, but several of our servers do not have a seperate disk or partition to store the image while it is being created.
Any suggestions?
Thanks,
J