June 19, 2013 at 9:05 am
Hi every one,
My title shall give you all information.
I am not able to see any kind of logs getting recorded
when i perform them by using a scheduled job.
Even though the logs are not recorded.
I couldnot see any kind of error msg inspite shows success.
But if i do them manually they does get recorded.
Is it normal.. What am i supposed to do.???
NOTE: ROOKIE HERE :hehe:
June 20, 2013 at 11:04 am
hi,
to be honest I don't understand your question...
Tell us the following:
What is your current target?
What was the situation you started from?
What was the way to achieve your target? Provide us with your thoughts and, very important, your sql scripts.
And: What exactly is the problem for not reaching your target?
Please read this link before answering:http://www.sqlservercentral.com/articles/Best+Practices/61537/
With enough information I'm sure we will find a solution for you 🙂
June 20, 2013 at 11:54 am
Hi Wolf,
"What is your current target?
What was the situation you started from?
What was the way to achieve your target? Provide us with your thoughts and, very important, your sql scripts.
And: What exactly is the problem for not reaching your target?"
1. My target is to make transaction and full backups of databases located on Secondary server.
2. In order to acheive that i have created jobs in maintenance plan. They were running succesfully, but not able to see the physical files in the destination folder.
3. So i tried to check doing the backups (transactional and full) manually, on the same location, and i am able to do it, also i can see the physical files.
4. To solve this, I tried changing the locations of the destination files. I tried with both network location and also system location. But could not figured it out.
My doubt is, why is happening such. If i face any kind of disaster how can i recover my files.
I have two servers as DR. having same kind of problem with those,
* this is cluster configuration
* Databases are having ALWAYS ON feature for getting synchronized with secondary and DR servers
note: Backups on primary server are running succesfully, i can view the physical files too.
June 20, 2013 at 2:08 pm
hi,
now the situation is easier to understand 🙂
Question left for me: what is DR?
As I am new in the topic of "Always On" I summarize to be sure I understand the situation:
a)
You have 2 servers, using the "always on high availability group" feature.
( By the way, as far as I know this is a sql 2012 feature, there is a seperate forum for sql 2012)
b)
You defined your always on groups for doing backups on the secondary replica.
c)
Doing backup on the secondary replica, you don't see the backup files on the destination location.
d)
Backups done on the primary replica run successfully and you do see the physical backup files.
Ok.
I'm still new with topic always on but I try to do my best 🙂
You use Maintenance Plan for backup and you say it is running successfully.
* Do you use the Maintenance Plan wizzard or do you create sql-jobs of your own?
* Are you sure that the Maintenance Plan is running on the secondary replica and not on the primary?
* In the properties of the Always-On-Group: Did you check the settings for "Backup Preferences"?
* Are you sure the secondary replica is really the secondary and there was no failover?
* Are you sure the backup files of the primary replica are saved to exactly the same destination folder as backups on the secondary replica? Maybe the network shares are defined differently on primary and secondary?
Each Job, Maintenance Plan or SQL-Jobs directly, have an output in the job history. Post all you have!
Nice evening, Wolf
June 21, 2013 at 6:00 am
Hi sorry i haven't realized myself that there is an another forum for SQL 2012.
Always on high availability is SQL 2012 feature.
I have 4 node cluster, having 2 instances on each.
So, my primary and secondary comes under cluster network 1.
my DR (disaster recovery) come under cluster network 2.
every server is having separate maintenance plans, created through maintenance wizard.
each server is having different network path as a target location to save the backup files.
the db's are divided in to two different sets and scheduled some of them in instance 1 and some on 2,
These are made as Always On Highly Available on secondary and also Disaster Recovery(DR).
they are constantly synchronizing on all the servers. Changes made on any instance of any server will be updated to all..
I have scheduled Backup jobs for all of the instances with different target paths.
The maintenance plan on primary servers run successfully and files are saved at the target network path folder.
I have created separate maintenance plans for all of the servers on both the instances saving it to the target network path, (different path than the primary, every instance having its own destination path to save the files.)
As they all are synchronized, i believe they save same set of files. but i want to know why the maintenance plans does not report any job failure. as the files are not saved/created.
The backup files does create\save on manual back up on all the instances.
My question is why a scheduled back up doesnt save and return no error message but a manual back up is able to do.
*** is anything confusing***
:hehe:
June 22, 2013 at 1:37 am
rajborntodare (6/21/2013)
As they all are synchronized, i believe they save same set of files. but i want to know why the maintenance plans does not report any job failure. as the files are not saved/created.The backup files does create\save on manual back up on all the instances.
Still have no concretly idea. Two thoughts:
On the secondary, check the job history of you maintenance plan. It is actually executed?
Did you consider the backup configuration of your always on group? Read this: http://msdn.microsoft.com/en-us/library/82afe51b-71d1-4d5b-b20a-b57afc002405
June 24, 2013 at 11:35 am
Wolf,
That was great information. Ya i think it never happens a back up on secondary servers, unless the Cluster gets fail over.
Am i right????
:hehe:
June 24, 2013 at 11:43 am
That's the way I understand. Unless you configure the availiability group for backups on secondary replicas too. Just guess that, having my first always on getting started these days 😉
June 24, 2013 at 2:15 pm
Hi Wolf,
As they all part of the cluster, All of them are configured,
May be that is how it works, Need to research alot....
Please update here if you found any WOLF, i do same.....
It started for me recently, it was a month.. trying a lot to manage over here...
June 25, 2013 at 1:33 am
I'm not talking about the cluster but about the always on availability groups!!! Like the times before
You defined your always on groups for doing backups on the secondary replica.
In the properties of the Always-On-Group: Did you check the settings for "Backup Preferences"?
Did you consider the backup configuration of your always on group?
Have a look at the attachment.
Hope this helps.
June 25, 2013 at 6:46 am
Hi Wolf,
I just observed that, It mentioned as to be done on secondary Replica, if not available on primary..
** So Backups for DB which are ALWAYS ON cannot happen on all the servers simultaneously**
BUT If Secondary not availble then Primary.
A little knowledge added.......
Thanks For adding me the knowledge WOLF....:Wow:
:smooooth:
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply