G
GMan
OK here goes.
We're pushing out Symantec Backup EXEC to our systems. Each system has
2 physical drives. Secondary has 2 partitions - D and un-named. D
drive will be used for user data. They want C & D backup images to
reside on the un-named slice.
My gripe.....
1st - They are saving C & D in the same job to the same recovery
point.
2nd - When going through the configuration to create the recovery
points, it gives the option for where the recovery points should be
stored. They want it pointed to ...
C:\Windows\system32\config\backups.
When selected this generates a warning message that you are using the
drive to backup as your recovery point. It recommends saving to an
alternate drive. They accept this and march on. When the job is
completed, the images are stored in ...(You'll never guess this one!)
C:\Windows\system32\config\backups.
They're telling us that there's a problem when the jobs run because
the images are supposed to get saved to the un-named slice. I not sure
how it works when it is pointing them to the C drive.
So far so good ...
What happens when C drive dies if all the images reside on C? If it
will work as they anticipate then C can be restored from the un-named
slice. But the current config has all data sitting on C so ....
And what happens when D decides to go on a road trip? All of his
friends on the un-named slice are going along for the ride wether they
want to or not. C drive is still running but all the user data is
toast since it resides on the same physical drive as the backup data.
Thanks, I needed that!
We're pushing out Symantec Backup EXEC to our systems. Each system has
2 physical drives. Secondary has 2 partitions - D and un-named. D
drive will be used for user data. They want C & D backup images to
reside on the un-named slice.
My gripe.....
1st - They are saving C & D in the same job to the same recovery
point.
2nd - When going through the configuration to create the recovery
points, it gives the option for where the recovery points should be
stored. They want it pointed to ...
C:\Windows\system32\config\backups.
When selected this generates a warning message that you are using the
drive to backup as your recovery point. It recommends saving to an
alternate drive. They accept this and march on. When the job is
completed, the images are stored in ...(You'll never guess this one!)
C:\Windows\system32\config\backups.
They're telling us that there's a problem when the jobs run because
the images are supposed to get saved to the un-named slice. I not sure
how it works when it is pointing them to the C drive.
So far so good ...
What happens when C drive dies if all the images reside on C? If it
will work as they anticipate then C can be restored from the un-named
slice. But the current config has all data sitting on C so ....
And what happens when D decides to go on a road trip? All of his
friends on the un-named slice are going along for the ride wether they
want to or not. C drive is still running but all the user data is
toast since it resides on the same physical drive as the backup data.
Thanks, I needed that!