[Veritas-bu] Backup not listed in history in BAR

2009-01-27 Thread bnetra
While trying to restore backup for a client I could not find all the backups taken (the client has a weekly backup schedule). There were no failures for any of the backups. But I am unable to see all the backups for the client. For example, if I want to restore a backup taken three months back,

Re: [Veritas-bu] Is anyone using a HP MSL 8096 tape library?

2009-01-27 Thread Justin Piszcz
On Mon, 26 Jan 2009, sql_noob wrote: > > we'll see what happens > > if we lock in 8 years of support then the TS 3310 is pretty much the same > price as the HP robot. At 3 years, HP is cheaper. > > i've read a lot of good things about IBM and Sun but not too much about HP > tape robots and was

Re: [Veritas-bu] Backup not listed in history in BAR

2009-01-27 Thread bob944
> While trying to restore backup for a client I could not find > all the backups taken (the client has a weekly backup > schedule). There were no failures for any of the backups. But Do you know that for a fact? How? Many operators/admins/managers destroy information by deleting failures from

Re: [Veritas-bu] Backup not listed in history in BAR

2009-01-27 Thread judy_hinchcliffe
We can add to bob944's list What you are looking for was backed under the virtual name of a cluster and not the physical name. 2 months ago they moved the data to a new server So now you backup by name serverB where 3 months ago you backed it up as serverA. The server was not in an active polic

Re: [Veritas-bu] HELP !

2009-01-27 Thread Clooney, David
Correction - couldn't start emm All We have just upgraded a SUN clustered Solaris 10 NBU 6.0 MP4 to 6.5.3. 6.5 GA went on fine, along with 6.5.3 with no errors whatsoever, however we initially couldn't start the emm. With the help of symantec we can now start emm however queries to emm are miss

[Veritas-bu] HELP !

2009-01-27 Thread Clooney, David
All We have just upgraded a SUN clustered Solaris 10 NBU 6.0 MP4 to 6.5.3. 6.5 GA went on fine, along with 6.5.3 with no errors whatsoever, however we initially could start the emm. With the help of symantec we can now start emm however queries to emm are missing volumes etc. Anyone had these so