07-11-2015 11:20 AM
I am a little confused about the behavior of SSR.
I have been using it for this client for a year now and it has never done exactly what I want...
My setup is this:
Windows SBS 2011 (2008/R2+goodies)
SSR for small business server 2013
A/D and Exchange server
Redirected Folders enabled.
About 500GB data stored on a RAID Mirror of 2X 2TB SAS (LSI RAID CARD)
An extra 1TB SATA to dump the backups to. (S:\)
RDX Drive (D:\)
Not virtualized but will be soon.
The copy on S:\ is for “daily backups” where I can recover a single file, etc back 45 days or more.
The off-site copy is meant for D.R.
Ideally, what I want from Symantec SR is this
1. Nightly Copy to S:\ (local 1TB volume dedicated for backups)
2. Off-site Copy to D:\ (Removable 1TB RDX cartridge, swapped nightly)
3. One full, followed by incremental forever
4. 45 days of backups (experience shows, 1TB of backup space has given me over 100 days!)
5. Automatic "wrap around", deleting the oldest first strategy
How exactly do I configure my backup jobs to do this?
I thought I had it right when it stopped doing backups after about 100 days, reporting that the destination was out of space.
Even though I had the 'automatically optimize destination' ticked.
Also, in the logs, it reported it as a user cancellation and did not send me a warning message that the backup had failed so no one noticed for several weeks that there was no backup. Could have been a total mess, potentially.
It's a simple enough requirement, what is the config for this, to get it right so that I don't find out 4 months later that it's wrong?
I am a little frustrated with it and have gone back to wbadmin batch file from the task scheduler, which achieves the above easily.
07-12-2015 06:04 PM
I think you have been following around the same queries under link :
09-11-2015 11:37 AM
can anyone answer this?
Why does it just stop doing backups and report out of disk space instead circulating the backups like it's supposed to?