β05-01-2013 05:47 AM
Hi,
I'm using a SSR 2011 Management Solutions.
Here i've setup 2 policy's and 1 filter, meaning that a client receives 2 Backup Jobs.
Through the Management Agent the SSR 2011 on the client does receive its Jobs.
Each Jobs has a different destination.
When the first Job has been done succesfully but the second Job has failed.
It reports to the home screen that the system has been fully backed up.
The Jobs are running every week, but i found a Computer that had missed a job for half an year without reporting that it has missed a job.
How do i change this that every missed or failed job is reported.
With Kind regards and thanks in forward,
Dennis Velthuis
Solved! Go to Solution.
β07-30-2013 03:27 AM
As too many offsite backups failed and vprosvc.exe becomes into a 'hang' state.
Local backups were fine though.
I do not continue on this issue anymore, because were installing SSR 2013 now.
We only use the local backup feature of it. (The one that doesn't fail).
Making an own script to do the offsite copy job (SSR doesn't retry a BackupJob).
β05-01-2013 06:02 AM
So it sounds like the 2 jobs are backing up the same volume(s) - can you confirm.
β05-01-2013 08:00 AM
Yes the same volumes,
one Job does C:\ and D:\ to E:\
the other job does C:\ and D:\ to 'network destination'.
it doesn't matter which job gives the error.
Example from a computer:
If the local job (to E:\) runs into a fail, and the offsite job (to network) finished normally.
The message to the clients home tab says that it has been succesfully backed up. Same message on the SSR 2011 Management Solutions
β05-01-2013 08:08 AM
OK, I think this is expected behavior because the drive has been backed up recently.
Is there any reason why you have 2 jobs configured? I think a better way would be to have one job and then use the offsite copy feature to copy the recovery points to the network destination.
β05-01-2013 09:27 AM
The local job is incremental and runs every week.
The offsite job is independent and runs twice a month.
This due to network traffic
β05-01-2013 09:29 AM
But a job has failed, why it doesn't report it.
β05-02-2013 02:18 AM
You could setup STMP notifications which would allow you to monitor the status of backups.
Can you confirm what was causing the backup failure?
β05-02-2013 03:03 AM
DoesnΒ΄t matter which error is generated.
To confirm your question: not enough disk space for the backup.
Example from one of the computers:
12% disk space left, 9,6GB free on 80GB disk/partition. But the backup is bigger than 10GB.
Causing an error that the Backup to E:\ has failed.
While the offsite doesn't have an error it will report to the home screen and to the Management Solutions that the computer is backed-up.
β05-02-2013 04:14 AM
FYI
The network is not connected to the internet.
We did used the offsite copy method (not 2 jobs, but 1 job with copy feature)
If the Backup succeded and the copy had failed, no error was created.
β05-02-2013 05:35 AM
I'm not sure I follow you...
However, I will try and explain: if offsite copy fails, it will not affect the overall status of the machine (i.e. 'Backed Up, 'At Risk' etc).
β05-03-2013 03:19 AM
That's the reason we removed the offsite copy from the local job and made it a job of its own.
If the offsite fails, the 'SSR 2011 Management Solutions' will show the computer its status as 'Backed Up', thats incorrect because the offsite has failed.
β05-03-2013 03:32 AM
I see where you are coming from and I kind of agree with you.
However, the current design of the product is that the overall status of a machine wont be affected by the offsite copy success/failure. The primary backup was successful - that is the key as far as the overall status is concerned.
Going back to your original issue....can you clarify the exact schedule you are using for each job. Once I know this, I will see if I can try and reproduce the issue here.
β05-06-2013 11:40 PM
These are 2 policy jobs from Group A (set-up in the "SSR 2011 Management Solutions").
For each day of the week we got a different job (Group A(Monday) to Group G(Sunday))
Policy Job 1:
Type: Recovery Point Set
Drives: C: D: 0-1
Schedule: Every Monday 4:00 (Start a new recovery point set (base): Monthly
Destination: e:\backup\
Advanced options:
Activate Backup policy
Limit the number of recovery point sets (bases) saved for this backup Maximum: 2
Verify recovery point after creation.
Applied to:
Group A
Policy Job 2:
Type: Independent recovery point
Drives: C: D: 0-1
Schedule: Every 3:00 on days 1,12 of every month (For example: Group G is 7, 18)
Destination: \\<Networklocation>\systemimages\
Create subfolder for each computer
Advanced options:
Activate Backup policy
Limit the number of recovery point sets (bases) saved for this backup Maximum: 2
Applied to:
Group A
If one of these jobs failed, the SSR 2011 Management Solutions won't receive an error.
The primary backup was successful - that is the key as far as the overall status is concerned.
But the job had failed, meaning that the overall backup is not succesfull.
Edit: added 'Verify Recovery Point after creation' to Policy job 1.
This option was allready set, i forgot to mention it in this post.
β05-07-2013 12:27 AM
Today i encounterd the problem on a computer.
I discoverd it because "Backup(E:\)" has less then 10% free disc space.
I selected the 1st Backup job and the system is "Backed up" with the green check image.
I also tryed to select the 2nd Backup job but the "Backed up" message is still there.
I fixed the disk space error by deleting some old backups. On the Home screen everything is fine and the screen is green (Backed up).
I don't know why the backup job has failed. This task had nothing to do with E:\, and the system didn't went unstable when the backup job was running.
This time it did send a "attention needed" to SSR2011 Management solutions that a asssigned job hasn't run for a long time, or maybe missed it.
The basic inventory is send with an interval of 1 day.
But i also have seen systems that have not reported the missed backup for longer than 1 day. i didn't checked if the basic inventory was send for a long time, but will check it when i encouter it.
kind regards!
β05-08-2013 02:56 AM
I discovered that we don't have SP2 installed yet.
I asked my colleagues why they did not installed it yet. They replied that the update must be done with an internet connection.
The server can't be connected to the internet. How do i install the SP2 without an internet connection?
So far i've not found a manual for that yet.
β05-08-2013 03:22 AM
FYI:
clients are running:
SSR2011 server edition 10.0.2.44074
server is running:
Symantec management Console version 7.1.6851
Altiris Notification Server version 7.1
β05-08-2013 08:08 AM
SSR2011 server edition 10.0.2.44074
That is SP2. SP3 is the latest available and you can get it here:
http://www.symantec.com/docs/TECH195461
The server will need rebooting after installing this.
I'm not saying this will resolve your issue but it's good practice to update to the latest SP.
β05-13-2013 12:39 AM
I will install SP3 on some of our machines today.
As you confirmed that we have SP2 installed we still receive errors same like this:
http://www.symantec.com/business/support/index?page=content&id=TECH155022
β05-13-2013 01:41 AM
As per that article, you need SP2 for the Management Solution.
When I mentioned SP3 earlier, I was referring to the client versions.
These are 2 different things.
β05-13-2013 02:02 AM
I know you reffered to the client, and did install SP3 succesfully on one of the computers (not rebooted yet).
Some more information from SIM:
Symatec Management Platfom 7.1 SP1 (v7.1.6851)
Symantec NS WebServices (v7.0.60)
Symantec System Recovery 2011 Installer SP2 (v10.0.2)
Symantec System Recovery 2011 LightsOut Restore SP2 (v10.0.2)
Symantec System Recovery 2011 Management Solution x64 SP2 (v10.0.2)